Getting StartedDeployingPreview DeploysCustom DomainsEnvironment VariablesDatabasePersistent StorageAddonsEnergy & BoostsScheduled TasksDeploy NotificationsEmail ProtectionCLI ReferenceAPI ReferenceMCP Integration

Energy & Boosts

How runtime budgets, boosts, and always-on work for your eggs.

Energy system

Your free account has a shared daily and weekly energy budget. Energy is consumed while your eggs are running, and every running egg draws from the same account-wide budget — it is not metered per egg. When the shared budget runs out, your free (non-exempt) eggs sleep until the next reset.

Shared across your eggs — per account, not per egg. If two eggs run at the same time they drain the budget twice as fast, three eggs three times as fast, and so on. Two eggs running continuously exhaust the daily budget in about 2 hours.

Static eggs (deployed with --runtime static) are always free and never consume energy. They don't count toward the 3-egg limit.

API and webhook requests always wake sleeping eggs regardless of energy budget. Only browser visitors see the out-of-energy page.

Daily budget240 minutes (4 hours) of runtime per day, shared across all your eggs (resets at midnight UTC)
Weekly budget960 minutes (16 hours) of runtime per week, shared across all your eggs (resets Monday at midnight UTC)
Idle sleepDynamic eggs sleep after 3 min idle, static eggs after 30 min (wakes on next request)

Exempt from the shared budget: Always On eggs, eggs with an active Boost, and static eggs. Exempt eggs never draw from the budget and never sleep for lack of energy — so they don't make the budget deplete faster for your other eggs either.

Check energy status

See your account-wide or per-egg energy usage from the CLI:

# Account-wide energy status
hatch energy

# Per-egg energy status
hatch energy my-egg-xxxx

You can also see energy status on the dashboard for each egg.

Boosts

Need your egg to keep running without energy limits? Buy a boost — a one-time purchase with no subscription.

Day boost€1 — 24 hours of uninterrupted runtime, no sleep, no energy limits
Week boost€3 — 7 days of uninterrupted runtime, no sleep, no energy limits
# Boost for a day
hatch boost my-egg-xxxx day

# Boost for a week
hatch boost my-egg-xxxx week

Boosts are per-egg. You can stack them — boost as many eggs as you need.

Energy Packs

Need a bit more runtime without a subscription? Buy an Energy Pack — a one-shot purchase of minutes that never expire (1,000 min for €3).

DailyFree daily budget — resets at midnight UTC
WeeklyFree weekly budget — resets Monday at midnight UTC
BonusReferral and promo credits — can be reset by their own rules
PackPurchased minutes — never expire, consumed last

Consumption order: daily → weekly → bonus → pack — free and expiring credits always burn before your paid minutes.

# Buy an energy pack (prints a checkout URL)
hatch energy buy

# Check all four balances
hatch energy

You can also buy a pack from the dashboard billing page. Minutes are credited as soon as the payment completes.

Always On

For production apps that need 24/7 reliability, subscribe to Always On at €10/month per egg.

Never sleeps — runs continuously 24/7
No energy limits
1 GB RAM per egg (vs 256 MB free)
Dedicated PostgreSQL (1 GB storage)
Cancel anytime

Subscribe from the dashboard egg detail page, or see Pricing for full details.

Resource profiles

Each egg gets CPU and memory sized for its runtime — static sites stay tiny, compiled binaries stay lean. Available from hatch vNEXT.

static128 MHz CPU · 128 MB RAM
go, rust256 MHz CPU · 256 MB RAM
bun256 MHz CPU · 384 MB RAM
node, python, php256 MHz CPU · 512 MB RAM (default for unknown runtimes)

Need more (or less)? Set an explicit override — it always wins over the runtime profile:

# Show current limits
hatch resources show

# Override memory (MB)
hatch resources set --memory 768

Overrides are capped by tier: free eggs up to 512 MB, Always On / boosted eggs up to 1024 MB — requests beyond the cap are rejected with 422.

Profiles and overrides apply when the job spec is regenerated — on the next deploy, restart or wake. Memory reductions never shrink a running egg in place.

What happens when energy runs out?

When your egg exhausts its daily or weekly energy:

  1. 1The egg is put to sleep by the platform
  2. 2Visitors see a "sleeping" page with a countdown to the next energy reset
  3. 3When energy resets (daily at midnight UTC, weekly on Monday), the egg can wake again
  4. 4Or buy a boost to wake it immediately and bypass energy limits
Hatch mascot