The database that never sleeps, so it never wakes

Serverless databases solved idle cost by suspending compute: and bought a cold start. The first query after a quiet weekend pays a wake-up tax, so you keep a ping cron running to keep the thing warm, which is a strange way to spell "always on."

On Hoody the math is structural, not behavioral. An idle database container burns no CPU; containers cloned from one base share their disk blocks copy-on-write, and the kernel's page cache loads their identical binaries once. Idle costs approximately nothing: not because anything slept, but because duplicate state folds. Monday's first query runs at the same speed as Friday's last one. Your staging and preview databases sit there all month on the flat-rate box you already pay for.

Nothing sleeps, so nothing has to wake.