Energy & Boosts
How runtime budgets, boosts, and always-on work for your eggs.
Energy system
Every free egg has a daily and weekly energy budget. Energy is consumed while your egg is running. When energy runs out, the egg sleeps until the next reset.
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.
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-xxxxYou 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.
# Boost for a day
hatch boost my-egg-xxxx day
# Boost for a week
hatch boost my-egg-xxxx weekBoosts are per-egg. You can stack them — boost as many eggs as you need.
Always On
For production apps that need 24/7 reliability, subscribe to Always On at €10/month per egg.
Subscribe from the dashboard egg detail page, or see Pricing for full details.
What happens when energy runs out?
When your egg exhausts its daily or weekly energy:
- 1The egg is put to sleep by the platform
- 2Visitors see a "sleeping" page with a countdown to the next energy reset
- 3When energy resets (daily at midnight UTC, weekly on Monday), the egg can wake again
- 4Or buy a boost to wake it immediately and bypass energy limits
