Agents on the org chart.
Agentic AI works in demos. In production, it falls apart at the coordination layer — which agent did what, when, with whose data, on whose authority, with what cost.
Teams that try to scale past a single agent hit the same wall: operations. No visibility. No audit. No control. Impressive demos that can't survive contact with a real organization.
Rogue Agents is building the suite that solves it. Two products, one underlying model: agents as first-class operators, humans with real visibility and real control.
Atrium for individuals and small teams. Locus for enterprise. The same model underneath.
Most agentic AI was built to impress in a demo. You give it a goal, it executes, results appear. Clean. Impressive.
Production is different. In production, you need to know:
This is the operations problem — the gap between "agent that can do a task" and "agent infrastructure a real organization can actually run." Locus and Atrium exist to close that gap, from a solo operator's desk to an enterprise's org chart, with the same model of how agents work underneath.
Three commitments shaped the suite.
Desktop-based agent management for individuals and small teams. Cloud-backed for persistence. Local-first for speed. The right starting point for a founder, a consultant, a small in-house group running real work through agents.
Enterprise agent infrastructure. Multi-team, multi-tenant operations. Org-level authority and audit. Built for the organization where agents need to be managed the way employees are — with identity, accountability, and control at scale.
Atrium and Locus share the same underlying architecture. A team can start with Atrium and graduate to Locus without rebuilding their agents, their data, or their workflows. The suite grows with the team — solo to small to enterprise — without breaking the operator's mental model.
Atrium ships to individual operators and small teams in summer 2026. Locus is being deployed in enterprise environments where agentic AI needs to scale past one team. For evaluation engagements, design partnerships, or enterprise rollouts, pitch us a project.
Two surfaces. Same substrate. Built to grow with the team. Four layers, from identity to surface.
Every agent in the suite has a persistent identity — a name, a history, a set of relationships, a defined scope of authority. Not a session that resets. Not a thread that disappears. An operator with a record.
Every agent's authority is explicitly bounded. Widening that scope requires a human decision, recorded in the audit trail. The trail spans the agent's full lifetime, not just the current session — so nothing disappears between conversations, and nothing is decided without attribution.
Agent state lives in markdown — readable, diffable, version-controllable. No opaque internal state. Nothing the operator can't open and read. Every action is timestamped, attributed, and reviewable after the fact.
Replay and inspection are first-class operations, not afterthoughts. If an agent made a decision three weeks ago that now looks wrong, you can find it, read it, and understand exactly what happened. The audit isn't a compliance layer bolted on — it's structural.
Real agentic work isn't a single agent executing a single task. It's handoffs — agent to agent when the work changes character, agent to human when a decision requires authority or judgment beyond the agent's defined scope.
The coordination layer defines those handoff patterns, the escalation rules, and the shared context that flows across an agent team. Memory and state persist between agents. Nothing disappears at the boundary between one agent and the next.
The two surfaces share the same underlying architecture. A team can start in Atrium — the desktop-based, cloud-backed management layer built for individual operators and small teams — and graduate to Locus without rebuilding their agents, their data, or their workflows.
The mental model is constant from solo to enterprise. Only the surface changes: from a single-operator desktop to a multi-team, multi-tenant organizational infrastructure with enterprise-grade identity, access, and audit baked in.
The differentiators here are architectural. Four commitments that shape every decision in the suite — and that explain why it's one product, not two.
Anything an agent does is reviewable in a markdown file. No black boxes, no proprietary formats. State that any operator can open, read, and version-control.
Agents act within explicit scopes. Authority widens only by human decision, and that decision is recorded. The system cannot grant itself more power.
Agents have names, histories, relationships — not session IDs that reset. An agent that worked with your team last month still remembers last month.
Atrium and Locus run the same model of how agents work. Start small, grow large, don't migrate. The architecture doesn't change when the team does.
The suite is in active development. Atrium ships to individual operators and small teams in summer 2026. Locus is being deployed in enterprise environments where agentic AI needs to scale past one team, with the operational visibility the enterprise requires.
The production gap in agentic AI is real. Most teams hit it around their second or third agent. The coordination problem isn't hard to name — it's just hard to build for, and almost no existing tooling was designed with it in mind from the start.
Available now under the Rogue Agents banner. For evaluation engagements, design partnerships, or enterprise rollouts: pitch us a project.
Tell us where you are in the build. We'll tell you how the suite fits.
Pitch us a project