Memory that hits the disk
Local NVMe, 1 writer: AtticDB acked in 94 µs at p50, 9,799 acks/s.
AtticDB is an open-source memory database for coding agents. It acks a write only after fdatasync. One Rust binary, no model calls.
curl -fsSL https://github.com/Clawdlinux/atticdb/releases/latest/download/install.sh | shAn illustration of ack-after-sync, not a crash test. The real test cuts power on LazyFS. CI runs crash simulations on 2,000 seeds.
On your own disk
Every turn your agent takes is written to a tape on your own disk. Synced, then acked. Nothing leaves the machine.



1 of 16 records match, newest first
- Why did we pick ext4 for the durability runs? We need a tested filesystem for fdatasync and directory fsync.
The same search as memory_search. Every word must match, across every session and fact. No embeddings, no model call.
Three steps, then forget about it
Install it your way
Pick your system and your apps. The commands below are exactly what to run.
Install the binary. It checks the download against SHA256SUMS and never uses sudo.
curl -fsSL https:// github.com/ Clawdlinux/ atticdb/ releases/ latest/ download/ install.sh | sh If the installer says ~/.local/bin isn't on your PATH, add it.
export PATH="$HOME/ .local/ bin:$PATH" See what setup would change. It writes nothing.
atticdb setup --harness copilot,vscode, claude-code, codex --dry-run Connect your apps. Every edited file is backed up first.
atticdb setup --harness copilot,vscode, claude-code, codex Check the install. It writes nothing.
atticdb doctor --harness copilot,vscode, claude-code, codex
Wires itself into
Claude Code, GitHub Copilot CLI, VS Code and Codex. On macOS, Linux and Windows.
Measured, not promised
Medians of 7 runs on Azure, 24 October 2026. SQLite wins closed-loop p50, and we say so. Read the benchmarks
- 2.8
- times the durable acks of Redis, Valkey and DiceDB, at most. Premium SSD v2
- 1.3
- ms p50 under agent load, Premium SSD v2
- 94
- µs p50, 1 writer, local NVMe
- 0
- model calls per write
- 1
- binary, no other services
Local is free. Cloud is $15 a month.
The binary is free forever. Cloud adds sync across your machines and backups. Planned pricing.
Questions
Is it production ready?
No. AtticDB is early. Don't run it in production.
Does it call a model?
No. AtticDB stores turns and facts without model calls. Search finds them by words, without embeddings.
Where is my data?
On your own disk, in AtticDB's per-user home. ATTICDB_HOME moves it. Don't put it on network filesystems or in folders synced by cloud storage apps.
How is it different from Mem0 or Zep?
They extract memories with a model call and use a vector or graph store. AtticDB stores turns and facts as written, acks after fdatasync, and finds them by words. See the compare page.
What happens if the disk fills?
Below a free-space floor, AtticDB goes read-only. It keeps serving reads.
What will the cloud add?
Planned cloud adds sync across your machines and backups. Cloud Team adds shared team memory. Local stays free.
Ready to remember?

curl -fsSL https://github.com/Clawdlinux/atticdb/releases/latest/download/install.sh | shThen run atticdb setup to connect your apps.