Autonomy requires memory.
First came inference: how well can a model reason over one prompt. Then tool use: how can it act. The frontier now is autonomy: agents that work on a codebase for weeks, robots that run a warehouse shift after shift.
Autonomy without memory is a loop that never closes. Every session starts from zero. Every obstacle is rediscovered. Every preference is explained again.
Axonio is the memory that closes the loop: persistent, related, and versioned, so what an agent or a machine learns today compounds tomorrow, and can be undone when it shouldn’t.
Why the axon.
In the 1890s Santiago Ramón y Cajal stained single neurons with silver and drew what he saw. His drawings showed that the brain is made of separate cells, and that signals travel one way: in through the dendrites, out along the axon, on to the next cell. Memory, it turned out, is what those connections become.
We named the company after the axon because that is the job: carry what was learned forward, to the next step, the next session, the next machine. The drawings you see across this site are Cajal’s, in the public domain.
Axonio was previously called ClawDB. The open-source packages keep that name.
Open core, for real
Memory is versioned
Latency is a feature
Standards over glue
About us.
Why did ClawDB become Axonio?
ClawDB was the working name of the open-source engine. As the product grew from a database into memory infrastructure for agents and robots, we renamed the company and cloud after the axon: the part of a neuron that carries a signal onward. The engine’s packages keep the @clawdb and clawdb names for compatibility.
Is Axonio open source or commercial?
Both. The core engine is MIT-licensed and free forever. Axonio Cloud adds the hosted MCP server, dashboard, team features and managed infrastructure.
Why agents and robots?
Both hit the same wall: without persistent memory, every session and every shift starts from zero. The primitives they need (episodic, semantic, procedural, working and relational memory) are the same, so one engine serves both.
Where is the team?
We are a distributed, engineering-first team building in the open.