/* CapyDB gives you standard PostgreSQL with direct and pooled connections, disposable previews, backups, restores, imports, and organization-scoped API keys. No proprietary SDK required. */
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.
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.
Create a project, copy the connection string, and ship without learning a custom platform first.
CapyDB speaks normal Postgres: one direct URL, one pooled URL, both usable from standard clients and frameworks.
Keep your framework. Change the connection string.
Disposable Postgres databases for testing, review apps, debugging, and other controlled forms of chaos.
Backups and restore flows exist for the moments when confidence and correctness stop matching.
Move an existing Postgres database into CapyDB without rebuilding your app around a new platform.
API keys are organization-scoped and intended for programmatic access to normal project routes without weird magic.