dbhost.app valid

DBHost

Managed PostgreSQL hosting for developers: PgBouncer pooling, verify-full TLS, separate SQL roles, backups with 30-day retention, and API and CLI automation on paid plans.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T19:08:39.994Z. Cached copy · Source on dbhost.app

# DBHost

> Managed PostgreSQL hosting for developers: PgBouncer pooling, verify-full TLS, separate SQL roles, backups with 30-day retention, and API and CLI automation on paid plans.

- [Introduction](https://docs.dbhost.app/introduction.md): DBHost is managed PostgreSQL hosting with PgBouncer pooling, daily backups, separate SQL roles, scoped API keys and a read-only SQL explorer.
- [DBHost quickstart: your first PostgreSQL database](https://docs.dbhost.app/quickstart.md): Create a managed PostgreSQL database on DBHost in about two minutes, pick your SQL roles and connect with psql over verify-full TLS on port 6432.
- [DBHost CLI reference](https://docs.dbhost.app/cli.md): Install the @dbhost-app/cli package and manage DBHost databases, backups, roles, extensions and access from the terminal on Pro and Business.
- [DBHost core concepts: databases, pooling, backups, roles](https://docs.dbhost.app/concepts.md): How DBHost works: shared PostgreSQL host, PgBouncer pooling on port 6432, backups, API keys, team roles and customer webhooks explained.
- [Limits and what DBHost does not offer](https://docs.dbhost.app/limits.md): 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 security model and honest limits](https://docs.dbhost.app/security.md): How DBHost protects your PostgreSQL data: verify-full TLS, scoped API keys, IP allowlists, encrypted credentials, backups and what it does not offer.
- [Backups, retention and deletion](https://docs.dbhost.app/backups-and-retention.md): What DBHost backs up per environment, how long logical backups and snapshots are kept, and how deleted databases are recovered or purged.
- [Connect to DBHost with verify-full TLS](https://docs.dbhost.app/guides/tls-connections.md): DBHost requires TLS; use sslmode=verify-full. Set up certificate verification for psql, node-postgres, Prisma, Drizzle and psycopg with a public CA.
- [Next.js and PostgreSQL: Prisma, Drizzle or pg](https://docs.dbhost.app/guides/nextjs-postgres.md): Choose Prisma, Drizzle or node-postgres for a Next.js app on DBHost: pooled runtime queries on port 6432 and a direct connection for migrations.
- [Next.js and Prisma with DBHost PostgreSQL](https://docs.dbhost.app/guides/nextjs-prisma.md): Connect Prisma Client to a pooled DBHost database from Next.js and run Prisma Migrate over the direct migration connection with the owner role.
- [Next.js and Drizzle ORM with DBHost PostgreSQL](https://docs.dbhost.app/guides/nextjs-drizzle.md): Connect a Next.js app to DBHost with Drizzle ORM: pooled runtime queries on port 6432 and Drizzle Kit migrations over the direct connection.
- [Next.js and node-postgres (pg) with DBHost](https://docs.dbhost.app/guides/nextjs-pg.md): Connect a Next.js app to DBHost with node-postgres: one shared pool on the pooled URL, verify-full TLS and a server-side query in a few steps.
- [Run schema migrations over a direct connect
…

Related sites

Explore similar publishers →

Category suggestions: other listed sites in Data and analytics. These share a category. See the whole category →

Machine-readable: GET /v1/resolve?q=dbhost.app · GET /v1/domain/dbhost.app · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for dbhost.app:
1. POST https://agentwebmap.com/v1/sites/dbhost.app/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://dbhost.app/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/dbhost.app/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/dbhost.app).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.