Roles and access
Owner, runtime and read-only roles on every managed database, plus up to 10 more. Pick Read only, Read & write or Custom, then rotate, revoke or delete any role.
3 base roles + up to 10
For indie hackers, hobby devs, and small teams who'd rather ship than babysit a Postgres box. Every database includes PgBouncer pooling, separate SQL roles and daily backups by default. Pro and Business add the REST API and published CLI, with flat plan pricing and no usage meter.
From provisioning to monitoring, DBHost handles the complexity so you can focus on shipping.
Spin up a new PostgreSQL database in seconds. DBHost creates the database, provisions credentials, and wires PgBouncer before the new instance becomes active.
Built-in PgBouncer on every database. Multiplexes connections for lower overhead and better performance.
Daily pg_dump backups by default (always for production) with 30-day history and encrypted off-host storage. Trigger an on-demand backup from the dashboard on every plan.
Pro and Business include a REST API that fits into any stack. No SDK required. Use selected-database keys for least-privilege automation or full-access keys for account-wide workflows.
Owners can browse public tables or run guarded read-only SQL directly from the dashboard. Explorer keeps destructive and system-level statements blocked by default.
Create least-privilege keys for selected databases or full-access keys for account-wide automation. Selected scope is the recommended default.
A hybrid architecture that separates your control plane from your data plane.
Vercel · Next.js 16
Ubuntu · Hetzner HEL1
The management dashboard and database runtime are separate, so a control-plane incident does not run inside the data plane.
Control-plane actions reach the agent over an authenticated HTTPS channel before any provisioning or backup work happens on the VPS.
Applications connect through PgBouncer on port 6432 so traffic spikes are absorbed by the pool instead of overwhelming PostgreSQL backends.
Managed databases come with the controls a production app needs, from per-role credentials to a separate path for migrations.
Owner, runtime and read-only roles on every managed database, plus up to 10 more. Pick Read only, Read & write or Custom, then rotate, revoke or delete any role.
3 base roles + up to 10
Run schema tools over a short-lived session on migrate.dbhost.app:5432, bound to your public IP, while your app keeps its pooled connection.
10–120 min lease · verify-full TLS
See logins and connection attempts with their TLS status, and a log of role, credential, member and network changes.
7 d events · 30 d daily · 90 d audit
Install citext, pg_trgm and pgcrypto from the dashboard, API or CLI. DBHost only offers versions it can back up and restore.
citext · pg_trgm · pgcrypto
Set how many server connections a database may use and choose one of three query-timeout profiles for new sessions.
Cap 3 by default, 2–8
A deleted database stays recoverable for seven days. After that, DBHost deletes it and its deletion backup automatically.
Recover from the dashboard
Roles, extensions and the migration channel apply to databases with managed SQL roles. API and CLI access needs Pro or Business.
Pro and Business can use the REST API directly or work from the published CLI. No SDK required.
npx @dbhost-app/cli@latest auth login --api-key dbh_...
npx @dbhost-app/cli@latest databases create analytics-v2 \
--display-name "Analytics V2" --jsonSaved credentials to ~/.config/dbhost/config.json
{
"id": "6f2d7f1a-6ec4-4ac9-bf5b-69a36c8f8d3d",
"name": "analytics-v2",
"displayName": "Analytics V2",
"status": "active",
"host": "db.dbhost.app",
"port": 6432
}Managed PostgreSQL hosting for developers. DBHost is designed for teams that want managed Postgres without turning database operations into a side project.
Ship a managed PostgreSQL database fast, keep the setup simple, and add API or CLI automation when the product matures.
Stand up project-specific databases for dashboards, automations, and line-of-business tools without running your own Postgres box.
Create separate PostgreSQL databases for previews, QA, and test runs, then reset passwords or trigger backups as part of your workflow.
Keep multiple client databases in one developer-friendly control plane and use scoped API keys when you need tighter access boundaries.
Clear operational details and sensible boundaries help teams choose the right fit faster, especially when a database ends up in the critical path.
Every database is fronted by PgBouncer on port 6432, so app traffic goes through the pool instead of opening a PostgreSQL backend for every idle connection.
Production databases always receive daily pg_dump backups, and other databases do too unless you turn daily backups off. Backups are stored off-host in encrypted S3 for 30 days, and a deleted database stays recoverable for seven days. Preview CI databases (limited access) have no daily logical backup by default and can choose daily backup. Every plan can trigger on-demand backups from the dashboard; Pro and Business can also use the API or CLI.
Use scoped API keys when automation should touch only selected databases, keep the dashboard SQL Explorer owner-only and read-only, and rely on public route budgets and abuse controls to make direct HTTP probing less noisy.
DBHost is a strong fit for small SaaS apps, internal tools, staging environments, and agencies managing several app databases. It does not yet offer replicas, PITR, or multi-region failover.
Shared plans use separate PostgreSQL databases on shared DBHost infrastructure, with PgBouncer transaction pooling in front of PostgreSQL. We monitor disk, connectivity, backup freshness, and pool pressure. If your app outgrows the shared limits, we'll work with you on a migration path - but if you need horizontal scaling or read replicas today, DBHost isn't the right fit yet.
The system is stricter in the places that matter most: automation paths stay scoped, explorer traffic stays boxed in, and direct HTTP abuse burns budget before it becomes useful.
These changes are meant to feel structural, not ceremonial. Every control closes a specific path, while paid-plan CLI and REST API workflows keep their narrow authorization boundaries.
A selected-database key lights one path and leaves the rest cold.
Read-only queries pass through a tighter gate. Destructive ones die at the boundary.
Burst traffic is metered, connections stay pooled, and backups keep copying quietly in the background.
Simple, transparent pricing. No surprises.
Includes
$5/month
Indie devs and small SaaS teams.
Includes
$15/month
Agencies, multiple apps, and heavier production use.
Includes
Managed PostgreSQL starting at $0/mo. No credit card required.