NamiDB
ProductResearchOpen sourceCompanyRequest early access
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 private beta, this page reflects internal monitoring rather than public uptime — we will replace this with measured SLA data 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

  • Documentation (docs.namidb.com)

    Goes live with the Server beta.

    Planned

  • NamiDB CLI + Rust workspace

    701 tests passing workspace-wide. clippy + fmt clean.

    Pre-alpha

  • NamiDB Python bindings

    First release in the next milestone.

    Planned

  • NamiDB Server

    Open beta in 2026 Q3.

    Planned

  • NamiDB Cloud

    Internal monitoring. Design partners only.

    Private 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.

  • Fase 0 — Architectural validation — ~85%

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

    In progress

  • Fase 1 — Storage engine — 100%

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

    Done

  • Fase 2 — Query engine — ~98%

    PASS 4/4 IC queries on LDBC SNB SF1 + SF10 within the 2× Kùzu gate.

    In progress

  • Fase 3 — Multi-tenant SaaS — 0%

    Cloud private beta lands with the first design partners.

    Planned

  • Fase 4 — GraphRAG SDK — 0%

    Hybrid vector + graph retrieval primitives.

    Planned

  • Fase 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.

Build the next decade with us.

Early-access is open. One launch email when the engine is ready — never spam.

Request early access