/* April 1, 2026. Every layer between you and Postgres is another thing to learn, debug, or rip out later. */
A lot of infrastructure products keep expanding until the database is just one tile in a much bigger platform story.
CapyDB goes the other way. The database is the product. Everything else exists to make using that database easier.
If your app already works with Postgres, CapyDB should feel like a hosting decision, not a rewrite. That keeps migration costs lower and your options more open later.
Smaller scope also makes the messaging better. We can say exactly what the product does, exactly who it is for, and exactly which adjacent categories it is not trying to replace.