Sleep and wake
VMs sleep when idle and pick up where you left off when they wake. What you pay while a VM sleeps.
Sleeping
A VM goes to sleep after it has been idle for a while. Using it, for example typing in a terminal, pushes that moment back. You can also put a VM to sleep yourself from its page, with homemade vm sleep, or through the API.
The time before sleep is the project's Default sleep after, and a VM can override it in its own settings. The choices are 10 minutes, 30 minutes, 1 hour, 2 hours, 4 hours, 8 hours, or never. The default is 30 minutes. Hobby allows up to 8 hours, and Pro also allows never. In a repo you can set it with sleep_after in .homemade/config, for example "30m" or "never".
A sleeping VM keeps its disk and its running state.
Waking
A sleeping VM wakes when:
- you press Wake VM on its page, run
homemade vm wake, or call the API; - someone opens one of its preview links and the project has Wake on visit switched on.
It picks up where you left it, with your files and terminals as they were.
If a VM stays asleep for a long time, it takes a little longer to wake. The dashboard tells you when a wake is taking longer than usual.
What you pay while a VM sleeps
You pay for the time a VM runs. A sleeping VM is not charged for running time and does not use your Hobby VM-hours. Its disk is kept for a limited time:
| Plan | Sleeping VMs are kept |
|---|---|
| Hobby | 7 days |
| Pro | 30 days |
| Pro with Unlimited sleep | Until you delete them |
After that time a VM that has not woken is deleted. You get an email before it happens (2 days before on Hobby, 7 days and 1 day before on Pro), and waking the VM starts the count again. Your project always stays, so you can create a new VM from it.
Unlimited sleep is a Pro add-on at $6 a month. It includes 200 GB of sleeping disk, then about $0.04 per GB-month. See Pricing and plans.