Proof
Multiple databases per plan - dev/staging/prod without per-project bills.
For hobbyists
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
Mini calculator
Builder includes 10 databases, so a simple hobby portfolio with dev and prod for three apps fits on one published plan with room left over.
Apps
3
Three separate side projects in progress at the same time.
Per app
dev + prod
Two databases per app keeps testing and live data separate.
Total databases
6
That is well within the published Builder allowance of 10 databases.
Plan fit
Builder
Builder leaves four more database slots before you need to move up.
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.