For engineering teams
If your team is already operating four or more datastores in production, the seams are showing — sync drift, pipelines breaking, oncall burnout. RedDB collapses the surface area into a single engine without giving up any of the data shapes.
The math
The "right tool for each job" stack made sense when each vendor solved a clearly different problem. With ASK, vector and graph all native to a Postgres-wire engine, the right tool for the job is one tool.
Today
With RedDB
Compare
Same workload, different surface area. Pick how many products you want to operate to answer one question.
| Capability | DIY stack Postgres + pgvector + Redis + Pinecone + Neo4j | Supabase Postgres + extensions | RedDB Cloud one engine, 7 models |
|---|---|---|---|
| Relational tables | yes | yes | yes |
| Vector search | pgvector + Pinecone | pgvector | native |
| Graph traversal | Neo4j | no | native |
| Time-series + retention | Influx | no | native |
| Queues / consumer groups | RabbitMQ | no | native |
| Natural-language ASK / RAG | glue code | glue code | one keyword |
| Domain types (IP, GeoPoint, Money, …) | app code | app code | 48 built-in |
| Services to operate | 5+ | 1 | 1 |
| Embedded mode (single binary) | no | no | ~30MB |
| Self-host option | yes | yes | yes (AGPL) |
| Vendor lock-in RedDB Cloud exports backups to your S3. Same file format as self-host. | low | medium | low |
DIY stack
Postgres + pgvector + Redis + Pinecone + Neo4j
Supabase
Postgres + extensions
RedDB Cloud
one engine, 7 models
DIY stack assumes Postgres + pgvector for relational and embeddings, Pinecone for production vector search, Redis for KV / queues, Neo4j for graph traversal, and Influx for time-series. Pricing and ops cost are not in this table — they belong in the TCO calculator.
Supabase row reflects the managed Postgres tier with pgvector and pgmq. Graph traversal, native time-series and queues are listed as “no” because they require app-side modelling or external services.
RedDB Cloud row reflects the engine's public capabilities at v0.2.x. Domain types and ASK are documented on the RedDB docs.
TCO
Plug your current vCPU, RAM, storage, traffic and per-vendor markups in. Get an apples-to-apples projection against RedDB Cloud.
Run the calculatorMedian results so far
Numbers are based on the first wave of design partners. Your shape will differ — the calculator works it out.
Migration
RedDB speaks the Postgres wire protocol, so existing clients keep working without driver changes. The CLI handles the rest — documents, vectors, graphs.
From
Wire-compatible. Existing clients (psql, pgx, JDBC, Prisma) connect with no changes. Vector data backfills via the same `WITH AUTO EMBED` pipeline.
# Connect with the Postgres URL — no driver swap.
$ psql "postgres://reddb:secret@db.reddb.io:5432/prod"
# Bring vectors over with auto-embed.
red migrate vectors --from "postgres://..." --collection notesFrom
Documents migrate per collection. RedDB keeps the JSON shape and adds a real query surface (joins, filters, search) on top.
# Stream collections, preserving _id and indexes.
red migrate documents \
--from "mongodb://..." \
--collection logs \
--collection eventsFrom
Index, embeddings and metadata move to a RedDB vector collection. ASK picks them up immediately without an external retrieval pipeline.
red migrate vectors \
--from-pinecone "$PINECONE_API_KEY" \
--index documents \
--to notesFrom
Talk to us — design partners get migration support directly from the engine team.
# Open a conversation:
$ mailto:founders@reddb.io?subject=Migration%20discussionFAQ
Pricing, security, migration, lock-in. If your question isn't here, email us.
Per resource: vCPU-hour, RAM-GB-hour, storage-GB-hour, traffic GB. The TCO calculator does the math against your current bill — most teams see 30–60% drop versus DIY 5-vendor stacks. Annual contracts available on Cloud Scale.
read more →SOC 2 Type II is in progress with a target of 2026 Q3. The engine is AGPL — your security team can read every line. DPA available on request, BYOK is roadmap on Cloud Scale.
read more →You point your existing Postgres clients at our wire endpoint — no driver swap. Vector data backfills via `red migrate vectors` while the new collection populates in the background, so the cutover is non-blocking.
Yes. The same binary that powers RedDB Cloud runs on your own VMs / Kubernetes / metal under AGPL-3.0. The .rdb file format is identical, so you can move workloads between Cloud and self-host without an export/import dance.
read more →Cloud writes the same .rdb file format as self-host and pushes continuous backups to a bucket you own. Worst case you keep running the open-source build with no migration. We're explicit about this because trust shouldn't depend on us being around.
Cloud Scale ships a 99.9% SLA, dedicated Slack/Teams channel, and named engineering point-of-contact. Annual contracts and procurement-friendly terms (DPA, MSA) available — email founders@reddb.io.