Frequently asked questions
This page answers how Moji runs, prices and checks your agent swarms, and where you can host it.
Swarms
What is an agent swarm?
An agent swarm is a group of AI agents that work through a job step by step, each step with its own agent and its own check. Moji runs the swarm, prices each step and records who did what.
What does Moji do?
Moji runs your team’s agent swarms inside a stateful runtime. Moji scopes each agent to a step, checks every output as the step completes, retries or repairs a failed step in place and keeps each swarm within the spending cap you set. Moji records every step, so you can see what ran, what it cost and what passed.
Can I see what my agents are doing?
Yes. Open any job to read in plain words what its agent is doing and why, with a link to its branch, changes and pull request on GitHub.
Is Moji a workflow builder?
Moji runs swarms that you define in your repository, and it draws them as a live map. You change a swarm by editing its file or by asking for what you want.
What does Moji add to Claude Code or Codex?
Claude Code and Codex do the work inside each step. Moji adds a price, a check and a recovery path around every step, and one record across all your agents.
Can Moji run security testing agents?
Yes. A security swarm can attack your own systems on a schedule, confirm each finding and send each fix back through the same test before a person approves it.
Cost and quality
How does Moji control AI spend?
Moji prices each step from past jobs and adds the prices into a budget for the whole job. You commit the budget, Moji counts each step’s reported usage against it, and new work waits at the cap.
How can Moji price a job before it runs?
Moji prices each step of the swarm from measured jobs. Those step prices add up to the job budget, which Moji then meters live while the job runs.
How do you define quality?
Your team writes its quality checks into the swarm. They can be rules on a step’s result, a score from a separate reviewing agent, files that must exist, your own CI tests or a named person’s approval. Moji runs them on every step’s output, and the report shows first-pass yield, exception rate, cycle time at the 95th percentile and budget reliability.
What happens when a step fails?
Moji retries the failed step in place up to the number of attempts you allow, or sends the work to the repair step your swarm defines. Completed work keeps its state, and a step whose outside effect is uncertain waits for a named person to confirm what happened.
What happens when I change a swarm?
When you ship a new version of a swarm, Moji prices it. New jobs use it once you commit it, and work already moving finishes on the version it started with.
Autonomy
How does a swarm become autonomous?
Every swarm starts with a person reviewing its work. Moji records budget reliability, first-pass yield, exception rate and cycle time in the swarm’s report. When that evidence shows the swarm meeting its thresholds, you can switch on Autopilot for it, and Moji records every automatic approval.
Can Moji run agents continuously?
Yes. With Autopilot on, a swarm keeps taking new work as it arrives, and Moji records every automatic approval. The swarm stops taking new work when it reaches its spending cap.
Running Moji
Where does Moji run?
Moji runs on your own infrastructure: one machine, or inside your private network behind your own proxy. Your workers always run on your own machines. Moji can also host its central service for your team by invitation, with your workers and code on your own machines.
Does Moji have a SOC 2 report?
We do not have a SOC 2 report yet. Moji runs inside your own security boundary, so your code and data stay in systems your review already covers, and we answer your security questions during the pilot.
How do you handle my data?
Your code, documents and agent logins stay on your machines. Moji stores each job’s state, results and costs, and your agents call their model providers under your own accounts.
Fit
How is this different from a gateway or a model router?
A gateway or model router works at the request boundary and may choose a model for one call. Moji works across the whole multi-step job, and it keeps the job’s budget, checks, recovery state and record together while the job runs.
How is this different from an agent platform?
An agent platform hosts agents you build on it, and permissions what an agent may use and spend before it acts. Moji runs the agents you already use on your own machines and controls the work while it moves. Moji checks every step, fixes failures in place and keeps the job within its budget.
Who is Moji for?
Moji fits teams that run repeated multi-step agent work in production, where a wrong result matters, a failed step should not restart the whole job, and inference is a material cost.
Getting started
How do I get started?
Leave your work email on the early access page, or email team@mojisystems.com with one piece of agent work you want to hand off. We set the success criteria up front, connect one swarm and begin with a person reviewing each job.
How does pricing work?
Pricing is set per customer and agreed before anything starts. Every figure on this site is illustrative.