Notes from the
no-BS database desk.
Short posts on managed Postgres, disposable databases, and why smaller product surfaces are usually easier to ship.
PostGIS, threshold alerts, an MCP server, and a Terraform provider
The extension allowlist nearly doubled and extensions became manageable per database. Usage alerts now warn you before the wall. And two new official clients - MCP for agents, Terraform for infrastructure as code.
Webhooks, integrations, and a real API surface
The product grew the connective tissue everything else plugs into - signed webhooks, Vercel and Netlify integrations, Clerk user sync, project-scoped keys, and an import preflight that says no before anything breaks.
Disposable databases are not a toy
Throwaway databases make testing, review flows, and bug reproduction faster without polluting the database you actually care about.
We are very intentionally not a BaaS
If you want auth, storage, functions, and platform kitchen-sink energy, there are good tools for that. CapyDB is not trying to be one of them.
A small product surface is a feature
Every layer between you and Postgres is another thing to learn, debug, or rip out later.