Changelog

v1.3.0 — memory you can evolve and operate

This release collects the engine, integration, security, and support changes since v1.2.0.

• Vector lifecycle and history. WAL-durable VMIGRATE shadow-index lifecycle, VSEARCH AS_OF over retained WAL, ordered concurrent WAL writes, and tenant-local replay scratch space.
• SDK and applications. LangChain and LlamaIndex adapters, optional installation extras, bounded batch ingest, RAG examples, Legal Auditor, and Jurix.
• Worker isolation. All-thread Landlock and no_new_privs, Unix-only seccomp networking, and worker memory limits tied to tenant quotas. Strict workers require a build with CGO_ENABLED=0.
• Replication. Mutual HMAC-SHA256 authentication and per-connection AES-256-GCM WAL encryption with tamper/replay rejection. Primary acknowledgements remain local.
• Support. Tenant-allowlisted diagnostics, separate optional wake credentials, durable audit, cooldown and post-checks, stable WAL/panic log codes, local bundles, 43 support tests, and 1,340 synthetic drills.
• Operator experience. Updated dashboard views and navigation, coordinated tenant starts, HTTP command-string/argument-array parsing, deployment wiring, and Linux/Windows support release gates.
• Version alignment. Binaries, HELLO/INFO, HTTP info, Python SDK, dashboard, Helm app version, deployment examples, and public site now identify DBX as 1.3.0. The support extension keeps its independent 0.4.0 version.

Migration needs re-embedding and temporary storage; historical search is retention-bound. Migration lifecycle replication, transparent S3 paging, and broad automatic repair remain outside this release. Published benchmark numbers retain their original measurement context.

Release announcement · Upgrade steps · Source comparison

v1.2.0 — recall surface, playground, and the public site

v1.1.0 shipped Isolation Kernel and a VSEARCH-shaped recall path. v1.2.0 is the same kernel with the recall verbs an agent actually uses, plus the site that demonstrates them. Isolation numbers, certified ANN p50, and the 100-tenant / 100k-vector-per-tenant envelope are unchanged. This is a better product cut, not a faster kernel.

• Recall verbs. VSEARCH takes MIN_SCORE, EF, and optional SPACE. VSIM ranks neighbors of a stored id (self excluded). VFUSE late-fuses query vectors with per-vector weights (weighted cosine sum, not a multimodal model). Optional SPACE on VADD / VDEL / VCOMPACT.
• Python / dashboard. vsearch / vsim / vfuse on the SDK. TenantMemory.similar and TenantMemory.fuse. Playground tabs: Semantic, Similar-to-id, Multimodal. Dashboard package 1.2.0. HELLO / INFO / GET /info stamp 1.2.0.
• Site. Toy cosine bench, density slider, fit quiz, playground hotspots, DEK-shred sketch, clickable video chapters, Updates page with a header badge, narrated two-minute recall clip, labeled shared-cluster vs DBX isolation sketch. ⌘K indexes row.k keywords.
• Container. GitHub Release v1.2.0 ships dbx-server / dbx-orchestrator archives and SHA256SUMS. Publishing the tag also builds GHCR dbx-orchestrator:v1.2.0.

Merged as PR #39, PR #40, and PR #41. Walkthrough: demo.html. Updates: v1.2.0 post.

Public site on dbxdb.co.in

Canonical URLs, sitemap, and website/CNAME point at dbxdb.co.in. GitHub Pages still needs the custom domain saved in repo Settings and GoDaddy DNS A/CNAME records (see website/README.md). Mail to hello@dbxdb.io is unchanged and still has no MX.

Incubation pitch deck

A 20-slide 16:9 briefing for incubation meetings: thesis, USPs, Isolation Kernel, certified v1.1.0 numbers, BSL business model, 18-month plan, and the ask. Present at pitch.html (arrow keys, full screen, Print → PDF). Claims stay aligned with positioning and isolation docs — no invented ARR, no Redis-replacement language, no SOC 2 badge.

v1.1.0 — Isolation Kernel, Unix data plane, walkthrough

Published as GitHub Release v1.1.0 with dbx-server / dbx-orchestrator archives (linux/darwin/windows) and SHA256SUMS. Product stamps match this cut: dbx-server -version, HELLO/INFO, GET /info, the Python SDK, and the dashboard package. Publishing the tag also builds GHCR dbx-orchestrator:v1.1.0. Since v1.0.0: Linux strict Isolation Kernel, Unix-socket engines, faster vector ingest, tenant checkpoints, the public site on GitHub Pages, and the recorded product walkthrough. Landlock restrict_self is pinned to one OS thread so a busy Go runtime cannot get EPERM and fail-closed a tenant worker.

Product walkthrough — site and dashboard

A recorded demo walks the public site (isolation bench, product pages, docs, pricing) and the operator dashboard (login, provision, tenant keys, console SET/GET/VADD, explorer, backup). Companion page: Walkthrough. The dashboard itself stays on :8000; GitHub Pages only serves the marketing site.

Contact — hello@dbxdb.io is not receiving mail yet

dbxdb.io has no DNS or MX (NXDOMAIN). Mail to hello@dbxdb.io and security@dbxdb.io cannot be delivered. The contact page now says so, copies the composed message, and opens a GitHub issue draft for non-security topics. The LICENSE address is unchanged; it starts working when the domain has a mailbox.

Public site — color, motion, and operator UX

The marketing site keeps the ice-on-navy identity but reads more like a product surface: aurora wash, pointer glow, pill CTAs, tenant color-coding (acme / harbor / lumen), scroll reveals, a perspective SaaS grid, fluid orbs, themed scrollbars, screenshot lightbox, tenant inspector popups, hover tips, a command rail, and a back-to-top control. The isolation bench now accepts AUTH / SET / GET / VADD in the browser, ⌘K jumps across pages, certified counts animate in, and the architecture schematic uses the same tenant colors. Copy and certified limits are unchanged.

Unix data plane, faster ingest, tenant checkpoints

Orchestrator-managed engines bind Unix sockets on Linux/macOS instead of a loopback TCP port each. Public :6380 still AUTH's once, then reuses a small pool of unused worker dials. Vector ingest no longer holds the index write lock across HNSW insert, so search can run during graph construction. Checkpoints flush vector metadata, record per-index seals, and name the live snapshot in CURRENT so recovery does not pick a file by mtime.

Public site on GitHub Pages

The marketing and docs site is live at vanshjain-0702.github.io/DBX-Database-Extreme. Canonical URLs, sitemap, and the README globe link point there. dbxdb.io stays the intended custom domain; do not add website/CNAME until DNS is actually pointed at Pages.

Isolation Kernel — kernel-enforced per-tenant seals

Each tenant is a separate dbx-server process on Linux strict mode. Landlock LSM stops cross-tenant file access. WAL, snapshots, .vec.meta, and .hnsw are AES-256-GCM sealed under a per-tenant DEK; shredding the DEK provides O(1) cryptographic deletion. Unix sockets with SO_PEERCRED accept only the orchestrator PID. Per-worker control tokens prevent neighbour authentication. Production (TLS or DBX_PRODUCTION=1) refuses inprocess unless DBX_ALLOW_INPROCESS=1. Set DBX_REQUIRE_DISK_ENCRYPTION=1 to refuse boot on a plaintext volume.

Python SDK: TenantMemory.remember / recall / forget plus ControlPlane.shred. Measured under strict: 50k keys + 20k vectors survived restart; 100k sealed vectors at recall@10 0.950; idle worker ~14–17 MiB RSS. Honest limits: SQ8 rows unencrypted (use LUKS/fscrypt), Landlock governs file opens only, cgroup best-effort in containers.

Public site, Python tests, orchestrator image

Marketing and docs pages live in website/ and deploy from GitHub Actions Pages (.github/workflows/pages.yml). Live host is vanshjain-0702.github.io/DBX-Database-Extreme; dbxdb.io is reserved for a later custom domain. Python Lint runs flake8, Black, and pytest; live AUTH tests skip without env. make python-check is the local match. Docker publish and the root Dockerfile build deploy/Dockerfile (cmd/dbx-orchestrator), not the old cmd/orchestrator entrypoint. GHCR tags appear when a GitHub Release is published.

v1.0.0 — industry launch profile

Reader keys cannot SET or VADD (tested). Orchestrator tenants have no default superuser. Production /metrics requires a Bearer JWT or DBX_INTERNAL_API_TOKEN. Dashboard Tenant keys mints reader/writer/tenant-admin credentials. Still a single-node profile: 100 tenants/node, 100k vectors/tenant. Not SOC 2. Not a cluster.

Usage, hibernate, soak harness

Per-tenant usage API and Prometheus /metrics. Export/import aliases for the portable tenant archive. Hibernate/wake evicts a cold engine without deleting it. CI runs a 12/4 density soak plus backup/restore; operators run make soak for 100 idle / 25 active. Python 15-minute path: examples/quickstart.py. Durable SETEX (node-redis setEx) sits on the same WAL path as SET … EX. Next.js and LangChain examples AUTH on :6380.

v1 GO — single-node profile

Cleared for production under 100 tenants/node, 100k vectors/tenant, durable strings + vectors. Windows certification: SET 186,147 ops/s, GET 284,785, ingest 7,233 vec/s, search p50/p95/p99 2.304 / 3.132 / 3.730 ms, recall@10 0.920 / p05 0.800. Hardware is attached on the performance page.

WAL v2, quotas, bounded expiry, panic boundaries, scoped keys, single RESP ingress on :6380, tombstones, and checksummed restore shipped in the August hardening. Optional async WAL replicas ack locally. Raft, cluster, tiering, and non-string RESP mutations fail closed.

Engine-package coverage

Remaining follow-up from the roadmap is raising engine-package test coverage. Async replicas are available; they do not replace an operator 100/25 soak on your hardware.