EeldenMulti-tenant by default

A clean-room local database engine and pipe-based query language — tenants as first-class primitives, types at edit time, storage that stays out of the way. Isolation, audit history, and fleet migration leave the business layer.

Quickstart

Business & sales

Open playground

Maintainer build

Shift left into the database

Multi-tenant isolation, lazy schema rollout, forks, snapshots, and CDC are engine work — not tenant_id middleware, migration fleets, or audit glue in every SaaS.

The shift-left bet

Tenant = consistency boundary

Isolation is the zero-config case. Forks, snapshots, and residency are engine operations. Cross-tenant work is CDC and sagas — never a distributed transaction pretending to be local.

Eelden Lang

Pipe-based, LSP-first queries. Schemas are code. Money is never a float. Named .eel files plus codegen for apps.

Local-first engine

A directory on disk is the database — durable pages and recovery built in. The in-browser playground runs the same language and executor model when you want zero setup.

Studio

Browse collections, run pipelines, shape-at-cursor completions, live CDC, health — the engine's first real client.

Honest maturity

Pre-alpha. Read Status before you plan on a capability — if it isn't Yes there, it does not ship yet.

Status — what works today