Scoped access
Selected-database keys keep automation narrow by default.
Security
Secure defaults for the Postgres work you do every day.
DBHost is built for developers who want tighter boundaries without turning database operations into their own platform project. The core controls are simple: narrow the key, guard the read path, and meter the public edge.
Guarded tooling
The SQL Explorer stays owner-only, read-only, and inspection-first.
Operational safety
Daily backups, pooled connections, and abuse controls are part of the default path.
Core protections
The product now shows its boundaries instead of hiding them.
Each scene maps a concrete control to a user-facing workflow. This is the part that matters for scripts, bots, direct HTTP clients, and day-to-day operator safety.
01Scope
Scoped API keys
A selected-database key lights one path and leaves the rest cold.
02Read path
Guarded explorer
Read-only queries pass through a tighter gate. Destructive ones die at the boundary.
03Safety rails
Traffic, pooling, backups
Burst traffic is metered, connections stay pooled, and backups keep copying quietly in the background.
Operational stance
Built for honest developer infrastructure.
DBHost is meant to remove recurring database chores for teams that want sane defaults. It is not pretending to be every kind of database platform.
A strong fit today
- Small SaaS apps that need sane defaults instead of an in-house database platform
- Internal tools and operational dashboards where a database should be available, not distracting
- Preview and staging environments that benefit from backups, pooling, and clear access boundaries
- Agencies managing several app databases through one developer-friendly control plane
What DBHost does not claim yet
- A multi-region or read-replica-heavy database platform
- A compliance-marketing product built around certifications we do not hold
- A PITR-first or enterprise procurement workflow with platform-level custom controls
Next step
Read the details, then ship faster with fewer database chores.
If DBHost fits your workload, the shortest path is still the best one: create a database, connect through PgBouncer, and keep the access surface narrow as your app grows.