01
PostgreSQL, per project
Every project starts with its own PostgreSQL database. Keep your application data in a database you know, with direct access when you need to inspect, migrate, or integrate it.
Features
A smaller stack
for shipping sooner.
KoedoDB brings together the backend pieces that independent products reach for first—without asking you to assemble and operate a cloud platform.
02
Authentication that belongs to the project
Set up authentication alongside your database rather than stitching it on later. Projects keep their users, credentials, and configuration separate from one another.
03
Optional managed Valkey
Add Valkey when caching, lightweight queues, rate limits, sessions, or ephemeral data become useful. Keep it out of the way when Postgres is all your application needs.
04
Frontend hosting, close to the backend
Deploy a static frontend with the rest of your project. Start with a platform hostname and connect a custom domain when your product is ready for one. We recommend putting your custom domain behind Cloudflare's free tier for CDN and DDoS protection.
05
Backups without a second job
Databases are backed up automatically every day with a logical dump, so routine recovery does not begin with inventing a backup system. See our Security page for the current backup and recovery approach.
06
Clear project boundaries
Projects are isolated at the platform level, with separate databases, credentials, runtime boundaries, and network controls. Your side project should not have to share a security boundary with someone else’s.
07
Built for AI-assisted development
Use the tools you already know: PostgreSQL schemas, SQL migrations, Row Level Security, environment variables, and application code. AI coding tools can work with ordinary, inspectable building blocks instead of learning a proprietary data model first.
Start simple