One open source server. Every tool you use, every device you work from. No cloud rental, no vendor lock-in, and the continuity is yours.
I was copying conversations between Claude and ChatGPT, generating handoff docs, re-explaining the same decisions over and over. That's when it hit me: I was the continuity layer between every AI tool, had to be it for them, and worst of all, I'm lossy too.
Brandon Lehmann, creator of Neural Ram
You've re-explained the same project to a blank chat more times than you can count. You keep a doc of decisions so the next tool can catch up, and it's stale by the time you've switched. The sharpest thing you worked out last week is buried in a conversation you'll never scroll back to. The carrying, the re-explaining, the copy-paste from one window to the next: that's a job, and right now it's yours.
Nobody's good at it. You lose the thread, you lose the nuance, you lose the best version of the idea, and you never notice the moment it slips. Whether you're wiring up agents or just living across a dozen tabs, nram keeps the thread.
Memory today lives inside one tool: one app, one agent, one vendor. nram is the layer underneath them instead, not another memory app bolted onto one of them. Researching on a laptop, coding on a desktop, drafting on a tablet, picking it back up on your phone, switching between Claude, ChatGPT, Grok, Mistral, Perplexity, Cursor, and your own scripts: none of that should reset the work every time you change rooms.
Your agent already reads the PDF, watches the video, runs the test, scrapes the page. nram's job is to keep what mattered. Across every tool. Across every conversation. On infrastructure that belongs to you.
A single server covers work that today is split across four separate products: conversational memory, document and corpus recall, standing rules, and agent state. One substrate does all of it, so there's nothing to stitch together and nothing to keep in sync.
You've felt it. The fix that arrives in the shower, the connection that surfaces on a walk, the problem that's somehow simpler after a night's sleep. Your mind keeps working when you step away from it, sorting what counts from what doesn't, settling what was left unsettled.
nram does the same. What matters carries forward, across tools, across devices, across weeks. While nram sits idle, it dreams: folding in what's new, resolving contradictions instead of stacking them, letting the stale fade. You come back to memory that's been refined while you were gone, not just stored.
"Self-hosted" in this space usually means a Python library you embed, a localhost shim with no auth, or an open-source wrapper sitting on rented infrastructure. None of them survive the moment "self-hosted" was supposed to matter. nram is a real server.
/metrics. Every tool you use shares one server.nram does the part of memory that's actually hard.
nram is free and open software, and always will be. You can run it, read it, change it, and build on it, for anything you want. No one, us included, can ever take that back. No bait and switch. No "enterprise edition" that hides the features you actually need behind a contract. The substrate stays open. The economics stay aligned with the people using it.
Because it runs on your infrastructure, nothing happens to your memory you can't see. Every memory keeps its source and lineage, nothing gets quietly overwritten, and each dreaming cycle writes an audit log. You can always trace why nram knows what it knows.
Go 1.26+, Node 18+, a few minutes. SQLite by default, no signup, no cloud.
Working memory is what your brain holds while you're working. It moves between tools without you thinking about it. Neural Ram is that, for your AI.