Login

dormouse cloud

Serverless hosting for your hobby app

Sleeps when not used

Subsecond wake-up

Bring your own stack

No unexpected bills

How it works

Deploy a Docker image.
Your app runs as a normal HTTP service.
After idle time, the app is put to sleep.
State is saved, you don't pay for compute.
On incoming request, app is woken up.
Wake-up time is in hundreds of milliseconds.

209 ms

average wake up time in last 7 days

Try out now for free

Pricing

Per app, per month. Pay only for the time your app is awake.

Always sleeping

0.30€

Storage only — no compute while idle

Your usage

0.32€

4 hours awake per month

fully asleep fully awake

Always active

4.00€

Full compute, 24/7

Comparison

	Dormouse	VPS	Lambda	Lambda + SnapStart	Lambda + Provisioned Concurrency
Run a normal HTTP app	✓	✓	△	△	△
Bring your own stack	✓	✓	△	△	△
Pay nothing for idle compute	✓	✗	✓	✓*	✗
Subsecond wake-up	✓	✓	△	✓	✓
No server management	✓	✗	✓	✓	✓
No platform-specific rewrite	✓	✓	✗	✗	✗
Hard spending cap	✓	✓	✗	✗	✗

* SnapStart reduces cold-start cost for Java; you still pay for storage and other idle charges.

Technical details and FAQ

What can I deploy?

Any Docker image that runs a normal HTTP service, responds on port 8000, and not bigger than 512 MB compressed.

What happens when the app sleeps?

Dormouse saves the app state and releases the compute. The next request wakes it up.

Is local disk persistent?

No. Use external storage for anything that needs to persist.

Can I use a database?

Each new app gets its own PostgreSQL database (100 MB cap). Use the public connection URL from the app page for setup; the app receives DATABASE_URL automatically. Reconnect after wake if your framework needs it.

Do you support WebSockets or background workers?

Not yet. Dormouse currently targets request-driven HTTP apps.

How are environment variables and secrets handled?

You can configure environment variables for each app.

What are the CPU and RAM limits?

Apps currently have up to 512 MB of RAM. Maximum 1 vCPU. CPU capacity is shared, so sustained full-core performance isn't guaranteed.

How does billing work while sleeping?

Sleeping apps don't use billable compute. You only pay for base resources needed to keep the snapshot of your app.

What happens if my app crashes or fails to start?

You'll see the app status and logs so you can debug startup or runtime errors.

Can I use a custom domain?

Not yet, but it's on the roadmap. For now, every app gets its own subdomain with HTTPS.

How is my app isolated?

Each app runs in its own isolated environment with separate resource limits.