Consumers
Eelden is a multi-tenant-by-default database engine and query language. This half of the docs is for people who want to run queries, ship apps against the local engine, or explore Studio and the playground — not for hacking the Rust crates themselves.
Start with Status if you need the honest capability inventory. Everything else here describes what the product does now.
For the commercial / executive framing of why isolation and migrations leave the business layer, see Business & sales.
Path
Work through these in order:
- Install — stable Rust + Node, clone the repo, build the CLI (wasm optional for the playground).
- Quickstart — four paths: playground,
eelden run, Studio, named-query codegen. - Language — schemas, pipelines, types & Money, named queries, migrations.
- Clients — Studio UI, playground,
@eelden/client. - CLI / HTTP — product commands and the local API Studio uses.
- Operations — database layout, health & compact, CDC.
Concepts
| Page | Why read it |
|---|---|
| What is Eelden? | Founding bets and surfaces that ship today |
| Shift left | What leaves your app and lands in the engine |
| Status | Capability contract — Yes / Not yet |
| Tenants | Consistency boundary, catalog ops, routing |
| Transactions | atomic { … } — SI, RYW, conflict |
Other audiences
- Business & sales — value thesis, capability map, stakeholder pitch
- Maintainers — build, architecture, review process