A database that adapts to your data. Each write reshapes its memory, building associations as new information arrives. Run intelligence on everyday CPUs, without a separate model-training pipeline.
Each lab runs against HeatherDB. Open its inspector to see the memory and the API calls behind the result.
No separate model to build.
HeatherDB learns associations as you write data. Use that memory for recommendations, pattern completion and anomaly detection, without a separate training pipeline.
As new data arrives, the memory adapts in place. Connect your app through HTTP, using your own vectors or embeddings.
The read returns a reconstructed vector, not a stored row. This example binds to localhost and keeps data in a named volume. Use separate credentials and a pinned release for deployment.
CPU performance. Numbers you can check.
HeatherDB is read-optimized. Writes organize and persist the memory so reads can stay fast. Measured on an Apple M4 with 16 GB RAM.
Measured 2026-11-05 · Competitive mode · Apple M4 CPU · No GPU
Operation
64 dimensions
128 dimensions
384 dimensions
Single write
5.09 ms
5.23 ms
5.27 ms
Iterative read
17.47 µs
32.39 µs
120.07 µs
12.46 ms100 vectors in one batch
Compared with 526.41 ms for individual writes at 128 dimensions: approximately 42.3× faster in this run.
Measured 2026-11-05, HeatherDB 1.0.0. Means from 20 Criterion samples, using current engine defaults (data-seeded locations, k = 20). Native engine calls exclude HTTP, authentication, network and encoding. Speed does not measure associative recall quality.
HeatherDB 1.0 establishes the documented API and storage compatibility baseline. Vector dimension is fixed per database, and each data directory must have one engine process on local storage.
Associative reads can blend memories as a collection fills. Keep exact records through document APIs and evaluate recall on your own data. Deleting a document removes it from retrieval; removing its learned influence requires rebuilding the collection.
Terminate TLS at your proxy. There is no built-in Prometheus endpoint yet; use collection statistics, logs and audit records.
Contributions are welcome, including AI-assisted work. Every pull request is reviewed manually: explain your changes, document their behaviour and provide checks you have run. Read the contributor guide.