Documentation
CapyDB gives you standard PostgreSQL with direct and pooled connections, disposable previews, backups, restores, imports, and organization-scoped API keys. No proprietary SDK required.
What you actually get
- Standard
postgres://connections for direct and pooled access - Hosted projects grouped under Clerk-backed organizations
- Disposable preview databases with empty or clone modes and TTL cleanup
- Backup, restore, import, and credential-rotation jobs tracked by the control plane
Why the surface stays small
CapyDB is intentionally boring in the best way. You get Postgres plus the few workflows that keep shipping teams out of trouble.
The goal is to let you keep your existing stack and swap infrastructure, not force a new way of writing apps.
Current deployment model
The current v1 layout runs the control plane and worker on Azure, hosts customer databases on managed Postgres VMs, and serves the frontend from Vercel.
Human authentication is handled by Clerk. CapyDB organizations are resolved from the active Clerk organization instead of a frontend-held admin token.