Engineering · 2026-05-16 · By RedDB team · 1 min read
Hello from inside the engine
A first note on what we're building and why a multi-model engine matters in 2026.
Why another database
Most teams glue together three or four engines to ship a single product: a row store for OLTP, a search index for retrieval, a vector store for RAG, an object store for blobs. Each one has its own consistency model, its own failure surface, its own ops playbook.
RedDB collapses these into one engine with one transactional boundary. You write once, you query across modalities, you don’t reconcile.
What this blog will cover
- Internals of the storage layer — LSM trees, segment compaction, snapshot isolation.
- RAG primitives that live next to your transactional data.
- The vault: per-row encryption with key rotation that doesn’t require downtime.
- Honest notes on what we got wrong before 1.0.
Subscribe
This is the first post. Grab the Atom feed and we’ll show up in your reader as new pieces land.