NamiDB
Status

All systems
as expected.

A live mirror of the surfaces that exist today and the engine phases behind them. While the cloud is in closed beta, uptime reflects internal monitoring; measured SLA data publishes the day we go to public beta.

All public surfaces are operational.

Services

  • namidb.com marketing site

    Static. Served from the CDN edge.

    Operational

  • Waitlist intake

    Form submissions accepted. Data stays with us.

    Operational

  • NamiDB CLI + Rust workspace

    v0.5.1. Install via cargo. Workspace-wide tests + clippy + fmt clean.

    Shipped v0.1

  • NamiDB Python bindings

    v0.5.1. pip install namidb. abi3 wheels for Linux, macOS arm64, Windows x86_64.

    Shipped v0.1

  • NamiDB Server (Rust daemon + Docker)

    v0.5.1. namidb-server binary + container image. Bearer-token auth, REST API on /v0/*.

    Shipped v0.1

  • Documentation (docs.namidb.com)

    Reference docs + guides land alongside the Cloud public beta.

    Planned

  • NamiDB Cloud (managed multi-tenant)

    Closed beta on namidb.com. Design partners only. Request access from the homepage.

    Closed beta
Engine phases

Where the work
actually is.

The plan ships in phases. Each gate has an explicit definition of done. When we close one, the threshold number is published here in the same breath. When we miss one, the slip is published here too.

  • Phase 0: Architectural validation ~85%

    Continuous. Every non-trivial change starts as an RFC.

    In progress

  • Phase 1: Storage engine 100%

    Gate closed: cold p50 < 500 ms, warm p50 < 10 ms, ingest >= 10 K nodes/s. Real-WAN R2 measured.

    Done

  • Phase 2: Query engine ~98%

    PASS 4/4 IC queries on LDBC SNB scale=1.0. Low-millisecond warm p50, 3-5x over Kuzu on IC02 / IC08.

    In progress

  • Phase 3: Multi-tenant SaaS ~25%

    Cloud closed beta on namidb.com, design partners only. Public beta gated on docs + SLA targets.

    In progress

  • Phase 4: GraphRAG SDK 0%

    Hybrid vector + graph retrieval primitives.

    Planned

  • Phase 5+: GA + scale 0%

    Wire protocol freezes. LTS commitments begin.

    Planned

Subscribe

Status changes will be mirrored to the waitlist once the cloud is in public beta. Until then, expect quiet on this page. Incidents are handled internally with our design partners.

Incident reports

Every public incident lands as a postmortem in /research within seven days. Including the ones that embarrass us.

Run it on your own bucket.

Early access to the Cloud is open. One launch email when the engine is ready, never spam.

Request early access