> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dbhost.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Limits and what DBHost does not offer

> Plan quotas, per-database connection and role limits, the shared host model, and features DBHost does not offer, such as PITR, replicas or an SLA.

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

| Plan | Databases | Storage per database | Server connection cap (default / max) | API and CLI |
| - | - | - | - | - |
| Free | 1 | 250 MB | 2 / 4 | No |
| Pro | 5 | 1 GB | 3 / 12 | Yes |
| Business | 20 | 2 GB | 4 / 24 | Yes |

Prices and billing are on [Settings](/dashboard/settings#billing).
[Preview databases](/guides/preview-databases) count toward the database
limit and are available on Pro and Business with limited access.

## Per database

| Limit | Value |
| - | - |
| Server connection cap | Plan default (2 for development databases), adjustable from 2 to the plan maximum, shared by all roles ([details](/guides/connection-limits-and-timeouts)) |
| Query timeout profiles | Standard 60/10/30 s, Balanced 30/3/15 s, Short 15/1/5 s (statement / lock / idle in transaction) |
| SQL roles | Owner, runtime and read-only, plus up to 10 additional roles ([details](/guides/database-roles)) |
| Extensions | `citext`, `pg_trgm` and `pgcrypto` only ([details](/guides/postgres-extensions)) |
| Direct migration access | Exact public IPs only, lease up to 120 minutes, 1–2 sessions ([details](/guides/direct-migrations)) |
| Logical backup retention | 30 days ([details](/backups-and-retention)) |
| Deleted database recovery | 7 days, then permanent deletion |

## 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](/guides/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](/guides/restore-your-own-dump)
* 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


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.