A database of your own.
$5 a month.
A managed database for the sites and apps we build for you. One isolated database per site — not a slice of a shared one — provisioned, monitored, and tuned by us. A flat $5 base covers what a well-built site uses. If you ever go over, the meter is public, the rate is fixed, and your database keeps running.
One number, and what it covers.
- + 20 CU-hours of compute / month
- + 1 GB storage
- + Isolated database per site
- + Provisioning, wiring, monitoring
- + Prerendering + query tuning
- + No usage cap, it never stops at a limit
- + Standard connection string
- + Real human if something breaks
Most sites we build use 6–12 CU-hours a month — well inside the 20. Overage starts only above the allowance, at $0.40 per CU-hour and $2 per GB-month. There's no usage cap, so nothing stops when you go past it.
On a VPS or WordPress Hosting with us? Your sites already have a database. This is for application hosting sites, where the app runs stateless and needs a database that isn't tied to one server.
What a CU-hour is, and why you rarely pay for one.
CU-hours
A compute unit is a slice of database CPU and memory. Your database sleeps when nothing is talking to it and wakes on the first query. You pay for awake time, in CU-hours. Asleep, it costs nothing.
Why a good site barely registers
A prerendered site wakes the database when content changes or someone hits a genuinely dynamic page, not on every visit. Six to twelve CU-hours a month is typical. 20 is the allowance.
What burns compute
Pages rendered on every request that could have been static. Timers or jobs that poke the database. A CMS someone works in all day. The first two are our job to prevent; the third is real usage.
Whose fault overage is
Honest answer: usually ours. If your database trips its allowance, the first thing we check is our own build — routes that should be static, revalidation set wrong. When that's the cause we fix it and you aren't billed for it. Overage is for real growth: more traffic, a bigger catalog, heavy admin use.
No usage cap
Your database never stops because of a limit. Past the allowance you pay the fixed rate for what you use. If a database reaches 60 CU-hours in a month, three times the allowance, we look into why and tell you.
Storage
Content sites are tens of megabytes. 1 GB is included; past that it's $2 per GB-month, rounded up to whole gigabytes. Storage isn't capped — it's a level, not a rate, and it moves slowly.
A database, and the people who watch it.
Isolated per site
Every site gets its own database and its own credentials. Nobody else's traffic is in your database, and nobody else's bad day is either.
Provisioned by us
We create it and wire the connection string into your app. You never touch a console you didn't ask for.
Monitored by us
Compute, storage, and wake-ups read daily. Usage alerts go to us first, then to you if it matters. Your dashboard shows the same numbers your invoice uses.
No suspensions
Free database tiers stop cold when you hit their quota, mid-month, with no warning. Yours doesn't — it's on a paid plan with no usage cap, so it keeps running.
Built to stay cheap
The prerendering and query work that keeps a site inside its allowance is part of the service, not a change order. Cheap is a thing we build, not a thing you're charged for.
Nothing proprietary
It's standard Postgres under the hood, reached with an ordinary connection string. Any driver, framework, or database tool your developer already uses works with it, and there's nothing to migrate off of if you ever leave.
How it's measured, in plain English.
How usage is measured
Compute is metered upstream per database, in compute-unit seconds, and summed over the calendar month (UTC). Storage is the month's average of daily peak size. We read both daily. Only the part above the allowance is ever billed, rounded up to whole CU-hours and whole gigabytes.
When you hear from us
When a database reaches 60 CU-hours in a month, three times the allowance. Before any overage lands on an invoice we've looked at it ourselves — and if the cause is our build, it doesn't land.
What a month can cost
There's no usage cap, so nothing slows or stops your database and the bill follows usage at the fixed rate. The only ceiling is size: a database scales up to one compute unit, so a month's compute can't pass 744 CU-hours, a $294.60 month.
Where it runs
Your database runs on a serverless database provider we resell, in a project that is yours alone. We monitor it, but we don't operate their hardware — so we don't publish an uptime number for this tier. When it has a bad day, you hear about it from us, with what happened.