Positioning

# The AI industry has
a theater problem.

Mac mini farms. Glowing terminals. "I'm vibe-coding while my agents run my business." The optics have eaten the output. Watch any timeline for ten minutes and you'll see a thousand demos of agents doing nothing, gracefully. Axocoatl is for the opposite kind of team — the one with actual work to ship.

## What we're not.

We are not a personal coding copilot. We are not a chat interface with a hidden agent loop. We are not a framework you wire up in Python notebooks. We are not optimized for screenshots.

Most of what gets called "agent tooling" today is a wrapper around a single chat completion with a tool-calling loop on top. It looks productive in a demo. It falls apart in a real business because the agent has no memory, no persistence, no supervision, no coordination, no schedule. The first time the process crashes — or the laptop sleeps — the work disappears.

## What we are.

Axocoatl is a runtime. A single 25 MB Rust binary that runs on your box, supervises a constellation of agents, and routes work between them through a coordination layer called the event lattice. Agents declare what they depend on; the lattice cascades work without an orchestrator. They survive process restarts via checkpointing. They run on your LLM of choice. They execute on schedules and react to events without you in the loop.

The dashboard is a real control panel: live agent telemetry, a directory-scoped session sandbox, an automations editor, an MCP server gallery, and a chat surface for the moments you do want to be in the loop. None of it leaves the box unless you wire it to.

## What it's actually for.

The teams we're building for are the ones who already automate the boring parts of their business and want agents that do the same. Release pulse. Support triage. Daily briefings. Bug bisection. Customer follow-up. Contract review. The unglamorous, recurring work that adds up to a margin. Not the work that makes a video.

If that's the work you're trying to do, we built this for you. The rest of this page is the comparison frame — what changes, concretely, when you pick a runtime over a framework, and a local binary over a cloud platform.

Anonymous comparison

## Where we differ from the field.

We don't name names. Pick your tool and slot it in mentally — you'll know which row applies.

## Open source, on purpose.

Axocoatl is Apache-2.0. The code is the product; we don't gate features behind a paid plan because there is no paid plan. If you need support, you can pay for it. If you need a feature, you can build it or fund someone to build it. The runtime itself is yours.

This isn't a strategic loss-leader funnel into a hosted version. We don't plan to ship one. Local-first is part of the brand, not a launch tactic. The promise that nothing leaves your box unless you wire it to is the whole point — flipping that later would invalidate the original choice.

## Stop performing AI. Start running it.

One command. Sixty seconds. The runtime is on your box.

Install → How it works