Coming soon
The static plan doesn't run a database today — that's exactly what keeps it at 99¢. Here's what's planned, what to use meanwhile, and why static-only is the right trade for now.
Status
There's a difference between "eventually, maybe" and a feature that already has a shape. This is the second one — just not shipped, and not priced, yet.
A small SQLite database attached to a site — sized for the same kind of site the static plan already hosts, not a replacement for a full backend.
Expected to follow the same flat, small-add-on shape as a custom domain — but nothing is priced until it actually ships.
Shows up on this page, and in your inbox if you're on the list, the day it's available — not before.
Not part of the static plan today. The plan hosts files, not a database — there's no server-side process running anywhere in it. This add-on is a distinct, future piece, not a hidden switch on the plan you can buy right now.
Meanwhile
Plenty of static sites already pair with a separate service for the parts that need to store something — a contact form, a comment thread, a signup box. Point a script tag or a form action at one of those, and the rest of the site — still deployed by Git, zip, CLI, or your assistant — stays exactly as static as it is today.
Why static-only, for now
A database means something has to run, patch, back up, and scale on our end, around the clock — that's most of what makes ordinary hosting cost nine dollars instead of one. Staying static-only is what keeps the base hosting plan at 99¢ today — the same discipline that keeps backups and SSL included rather than upsold. The add-on, when it ships, is meant to extend that without disturbing it — not quietly turn it into a different, more expensive product.
Join the list and we'll email you when the database add-on ships — same list as everything else, one email at a time.