instantDocumentation menu / search
Search documentation →Start here
Quick startConnect through MCPOpenCode native memoryOpenCode memory controllerMemory API & local modelsUse the service
Memory & compactionMemory lifecycle controllerLocal agents & swarmsCLI referenceHTTP referenceRun a node
ConfigurationOperations & backupsLocal memory & ARMEvidence
Performance & device targetsFull retrieval reportBenchmark methodologyEvaluation policyMemory benchmark notesBuild with us
Architecture & schemaTechnology & learning mapRepository maintenanceContributingSecurityWebsite & deploymentSearch & agent discoveryPrivate product measurementEngineering referencesProject
Cleanup & release planRoadmapLocal AI memory: when instantKV fitsFeaturesChangelogHistory
Verification historyProposals
Distributed memory proposalBuild with us / single-node · source MVP
Engineering references
Practices adopted from database, low-level and KDE projects.
These projects informed repository structure and storage verification. The table links to their code and documentation. instantKV code and artwork are original.
| Reference | What instantKV adopts |
|---|---|
| Valkey | Start the README with something runnable; keep configuration, tests and benchmark commands discoverable |
| TigerBeetle and safety design | Write explicit invariants; verify failed writes preserve state; state durability boundaries and outstanding fault tests |
| redb | Reuse an embedded transactional engine; preserve immediate durability; document its one-writer constraint |
| KDE KCoreAddons | Keep source, tests, examples, licensing and CI easy to locate; treat documentation as part of the project |
| KDE Extra CMake Modules | Provide repeatable build checks and clear contributor entry points; use Cargo for this Rust repository |
| MCP Rust SDK | Use the maintained protocol implementation and typed tool schemas |
Project checks include locked dependencies, formatting, Clippy, invariant tests and HTTP/MCP tests. They also include restart demos, container checks, offline restore tests and raw benchmark reports. Deeper fault tests and real-model evaluation remain on the roadmap.
Visual direction
The original Monolith artwork uses a chrome split-K, graphite surfaces and Space Grotesk. It replaced an earlier desktop theme. The current website uses a black split-K, white surfaces and locally served Geist. Architecture diagrams retain their original artwork and status labels. Editable sources and licenses.