Proof
Multiple databases per plan - dev/staging/prod without per-project bills.
For vibe coders
Create a database, copy a connection string, run your first query in ~15 seconds.
Proof
Multiple databases per plan - dev/staging/prod without per-project bills.
Proof
PgBouncer pooling with clear connection caps (20 / 50 / 150).
Proof
Daily backups with tier-based restore window (7 or 30 days).
Pain narrative
Shipping loop
The whole point is to keep your prototype feeling real. You keep a normal Postgres connection string, normal clients, and a database that stays on.
Wake-up tax
none
The database is meant to feel available when you come back to the project.
Billing mental load
flat plans
You pick a tier instead of tracking burst math or opaque platform units.
Tooling
standard Postgres
psql, ORMs, migration tools, and admin clients still work the way you expect.
Next step
ship the app
The database stops being the side quest so you can stay in product mode.
How it works
01
Spin up a database from the dashboard and label it by app or environment so you know exactly what it is for.
02
Grab the full DATABASE_URL from the dashboard and move it into your app platform secret store.
03
Use standard Postgres tooling right away, whether you prefer a shell, an ORM, or your normal migration flow.
Explicit tradeoffs
These pages are meant to help someone qualify MVP DB quickly, not discover surprises after signup.
Isolation model
Schema-level virtual database on shared infrastructure. Isolation is logical rather than a dedicated box.
Region
eu-central-1 (Frankfurt).
Billing
Secure billing. Yearly plans include a 14-day trial. Cancel anytime, and contact us if you're not satisfied.
Reliability
No formal SLA. Best-effort reliability for teams optimizing for simplicity and price.
Want the deeper operational details? Read the docs and platform notes before you migrate anything important.