Skip to main content
DBHost is built for small apps, internal tools and staging environments. This page lists the limits that matter when you decide whether it fits.

​
Plans

Prices and billing are on Settings. Preview databases count toward the database limit and are available on Pro and Business with limited access.

​
Per database

​
Shared host

Customer databases run on a shared PostgreSQL 16 host. SQL roles, grants and the connection cap separate access, but CPU, memory and disk are shared. There is no hard per-database CPU, memory or disk quota, and a busy neighbor can affect latency. New databases and connection cap increases are admitted from measured connection use on the host. When the host is close to full, DBHost refuses the request with 503 CLUSTER_CAPACITY_FULL before the database is created; retry later with the same request.

​
Inactive databases

Free and development databases that have had no client connections for 14 days in a row are paused. A paused database keeps its data, roles, credentials and existing backups. Its status is stopped and the API returns a pause object. Start it from the dashboard or the API; see Inactive databases.

​
Not offered

  • Point-in-time recovery (PITR)
  • High availability, failover or read replicas
  • A service level agreement (SLA)
  • Restoring uploaded SQL files or dumps through DBHost; import them yourself with psql or pg_restore
  • Cloning a database that has additional roles
  • Extensions other than citext, pg_trgm and pgcrypto
  • Superuser, CREATEDB or CREATEROLE for customer roles
  • Multiple regions or region choice