Site + dashboard

Product walkthrough

What shipped so far, shown on the public site and on the operator dashboard from make run-dev. Pause on a chapter if you only need one surface.

5 min 18 s. Site plus a live operator dashboard: console CLI, explorer, semantic search, keys, runtime, settings. Engineer voiceover over a 140 BPM tech bed. The isolation bench is a browser sketch, not a live node.

Chapters

What the recording covers

01 Marketing site — thesis, isolation bench, product pages 02 Features — tenant lifecycle, Isolation Kernel, fail-closed 03 Get started — Docker / source / Compose, AUTH on :6380 04 Dashboard — login, provision, mint a writer key 05 Operations — console SET/GET, explorer, VADD/VSEARCH, backup

Marketing site

Start at the homepage. The certified profile is 100 tenants/node, 100k vectors/tenant, durable strings + vectors. Isolation is a directory, a WAL, and an HNSW index — not a key prefix.

The isolation bench (acme / harbor / lumen) is an in-browser sketch. Type AUTH harbor, SET session:1 intake, then AUTH acme and GET: acme cannot see harbor’s session. Click a cabinet to inspect that tenant. Pause / Replay controls the scripted loop.

Then walk Product → Features, Architecture, Get started, Performance; Docs; Pricing; Security; Contact. ⌘K / Ctrl+K is the command palette.

Features that have to stay true

Tenant is a first-class object: provision, backup, restore, export/import, hibernate/wake, delete. State and vectors live in one engine. Cost is meant to track active tenants (SQ8 mmap). Self-host is a single binary. Isolation Kernel on Linux strict is own process + Landlock + encrypted WAL/meta/graph.

Honest limits: default make run-dev is inprocess (shared Go runtime, not the security USP). SQ8 .vec rows stay mmap plaintext. Raft, cluster, tiering, and non-string RESP mutations fail closed. Hibernate/wake are control-plane HTTP APIs; the dashboard today exposes backup from tenant Overview.

How to run it

Dashboard/control plane on :8000. Public RESP on :6380. First data-plane command is AUTH tenant:key_id secret. On Linux/macOS, orchestrator-managed engines bind Unix sockets; the public port is still :6380.

Local demo used in the video:

shell

make site          # http://127.0.0.1:8765
make run-dev       # http://127.0.0.1:8000  (admin / adminadminadmin)

Self-host is free under BSL 1.1, including inside your own SaaS. Paid only if you sell managed DBX. Contact until MX exists: GitHub issues — dbxdb.io is NXDOMAIN, so hello@dbxdb.io cannot receive mail yet.

Operator dashboard

The dashboard is compiled into dbx-orchestrator. It is not hosted on GitHub Pages. Sign in, provision a tenant (name + id, replicas = none for the certified path), open it, then Tenant keys → Mint key as writer. The secret is shown once. Application clients AUTH that pair on :6380. The in-dashboard Console uses the operator JWT against /t/{id}/query — it is not a substitute for AUTH on the public port.

Operations

Console: PING, SET session:42 onboarding, GET session:42, VADD memories doc:1 0.1 0.2 0.9, VSEARCH memories 0.1 0.2 0.8 5.

Data Explorer: list keys, inspect a string, add another key.

Vector Playground: search an index (384-d MiniLM in the browser, or a smaller dim without the model). Prefer Console VADD if the model download is slow.

Overview: live ops/memory, point-in-time backup.

Runtime: Hardware, Storage, Network, Hosting. Control plane: Settings, Security, Replication (async WAL replicas; not Raft).