About CapyDB

Why CapyDB exists

Because a lot of builders do not need a full backend platform, a proprietary database API, or a brand-new infrastructure philosophy. They need Postgres.

CapyDB keeps the product surface small on purpose: managed Postgres, direct access, disposable previews, backups, restores, imports, and the operational pieces around that core.

Who it is for

• >>Vibe coders turning a weekend build into a real app
• >>Hackers and tinkerers who want a connection string, not a ceremony
• >>Indie hackers and small teams shipping fast
• >>Self-aware slop makers cleaning up a fast-moving project before users notice

What we optimize for

• >>Simplicity: standard postgres:// connections and normal tooling
• >>Performance: direct and pooled access with a lean control plane
• >>Security: TLS, scoped credentials, secret handling, and auth boundaries
• >>Reliability: backups, restores, disposable previews, and predictable workflows

What we are not trying to be

Not a BaaS. If you want auth, storage, functions, and the whole kitchen sink, use a product built for that.

Not a key-value store. Not an edge-database science fair. Not a vendor-lock-in hobby. Just managed Postgres done with a clear point of view.