For Startups
Startup Database Choices with Alopex DB
Day-0 speed, all the way to scale.
SQLite for the MVP, Postgres when you grow, a vector DB for AI features, a rewrite when you scale. Alopex DB is built to cut that chain of migrations with one engine. Start with zero-config embedded mode today and move up to a single-node server. Multi-node scaling is in active development.
SQLite for the MVP, Postgres as you grow, a vector DB for AI features. See how Alopex DB cuts that chain of migrations, stage by stage.
- Initial cost
- $0
- Migration work to scale
- Goal
Key points
- Launch your MVP same-day with the zero-config embedded mode
- A design goal: carry the same data into embedded, server, replica, and cluster stages
- SQL + vector search (HNSW) built in — AI features in the same engine
Challenge
What you need today and in a year are different
A startup's data requirements grow in steps — and every step forces a database migration.
- SQLite is fastest for the MVP — until server mode, AI features, or scale force a rewrite
- Vector search became table stakes; adding a vector DB means sync, consistency, double bills, and double ops
- Migrations (conversion, dual writes, rewrites) land at the busiest moment: exactly when users are surging
The essential difficulty of choosing a database at a startup is that what you need today and what you need in a year are different. Alopex DB is designed around the goal of reducing that “scaling cliff”: the same data file is intended to move from embedded to server to replicated to cluster.
This page is grounded in a stage-by-stage use-case analysis. Alopex DB is OSS (Apache 2.0), available from GitHub Releases. The embedded and single-node paths work today.
Erase the scaling cliff before it forms
Same data file, from embedded to single-node, replicated, and distributed clusters. Alopex DB is designed so you do not have to switch databases at every step up.
- MVP: a single-file embedded mode with zero config and full ACID
- Growth: the same file becomes an HTTP/gRPC server, then adds read replicas
- AI features: VECTOR(N) + HNSW for hybrid SQL + vector search in one query
- Data conversions
- Design goal
- Database products to avoid adding
- Design goal
Stages
How to use it, stage by stage
Switch deployment modes as your startup grows, from MVP to scale.
MVP (0→1)
AvailableEmbedded mode
- SQLite-like single file, zero config
- Iteration speed that survives weekly schema changes
- Also fits local RAG, edge, and desktop products
PMF to Growth
AvailableSingle-Node / Replicated modes
- One binary turns it into an HTTP/gRPC server
- CLI and the Python remote client connect to the same data
- Monitor cheaply with Skulk, the sister time-series DB
Scale
Distributed mode (in development)
- Multi-Raft cluster with range sharding (roadmap v0.8–v0.9)
- Same data file, same application code
- Cluster networking on the Chirps mesh
Why Alopex
Four properties that matter to early teams
The practical benefits, derived from the use-case analysis.
Vector search built in
VECTOR(N) + HNSW integrated into SQL — no separate Pinecone/Qdrant contract, no dual infrastructure to sync
A single Rust binary
Deploy and run with zero dependencies; CLI binaries and Python wheels ship with every release
OSS (Apache 2.0)
No usage billing before PMF, no lock-in — it costs nothing until you need it to
A design goal to reduce migration debt
Alopex DB is designed to carry the same data file into later modes, cutting the cost of migration.
Alternatives
Against the existing options
All excellent software — the difference is whether every stage transition forces a switch.
SQLite / DuckDB
Embedded standards
Postgres + pgvector / managed DBs
Production standards
Dedicated vector DBs
Pinecone / Qdrant, etc.
Status
Current status
The Rust/Python embedded, CLI, HTTP/gRPC server, and Python remote-client paths are released. Multi-node distributed execution is on the roadmap. See the analysis article for the full reasoning.
“Start from the problem you have today. You will see quickly what this product removes.”
Takamine Akari
Product guide
“Open the repository and read the design rationale and the tests yourself.”
Asmati Tatsumi
Technical explanation
Public Resources
The latest documents, code, and community links in one place.
Get Started
Start at day 0
Try it in minutes via cargo add or a prebuilt binary. Your feedback shapes the product.