FAQ.
The questions every review asks. Grouped, outcome-first, honest about the limits.
Operator-level reference lives in /docs/faq.
Understanding
What Aarmos is, and what it isn't.
What is Aarmos?
Aarmos is the Governance Runtime for Autonomous Software. It decides what an agent may do before an action runs, and produces a signed Receipt anyone can verify afterward.
Why do we need this — can't we just prompt carefully?
Prompts describe intent. Production needs an enforceable decision at the moment of action and portable evidence afterward. Aarmos is the layer that produces both.
How is this different from an LLM guardrail or MCP?
Guardrails filter model output. MCP is one transport we support among many. Aarmos governs the actual action across any framework, any protocol, and produces evidence that outlives the run.
What does Aarmos not do?
It does not guarantee that a model or tool behaves as documented. It does not inspect payloads that stay on the operator's machine. It does not claim any certification.
Adoption
How teams start, and how far they can go without us.
How do we start?
One agent, one policy, one Receipt. Reversible from day one. See the pilot.
Why not build this ourselves?
You can. Most teams stop after the first Receipt format changes, the first cross-framework integration, or the first auditor asks for portable evidence. The runtime is the boring, load-bearing part — that's what we do.
Which frameworks and protocols work today?
LangGraph, CrewAI, raw HTTP, custom code. Protocols: MCP, OpenAPI, deep-links, custom APIs. BYO-LLM: OpenAI, Anthropic, Google, Groq, OpenRouter, Ollama, Azure OpenAI.
Is this hosted?
No. Decisions run on the operator's machine. There is no hosted request path. Team sync is opt-in and scoped to Receipts, not payloads.
Trust
Independence, portability, and what happens if we go away.
What if Aarmos disappears?
Receipts still verify. The verifier is a portable Apache-2.0 artifact and the Receipt format is an open spec. Your evidence is not hostage to us.
Vendor lock-in?
Policies are yours. Receipts are portable. Verification runs offline without a network call to Aarmos. The exit path is the same as the entry path.
Can we verify Receipts without Aarmos running?
Yes. The verifier is standalone, offline, and independent of the runtime.
Where does data live?
On the operator's machine by default. Nothing leaves unless a policy and a destination say so.
Enterprise
The review-board answers.
Does this help with SOC 2 or the EU AI Act?
Aarmos produces the continuous, portable evidence those regimes ask for — decisions, inputs, and outcomes signed at the moment they happen. It does not replace your control environment or legal review.
How does it fit alongside our SIEM and IdP?
Receipts stream to your SIEM. Identity comes from your IdP. Aarmos governs the decision in between; it does not replace either.
Pricing?
Purpose-based, not per-seat. See pricing principles. Talk to us if you want to be a design partner.
Who is the buyer?
Platform engineering, SRE, and security leaders operating AI agents in production. Auditors and CIOs are the second audience — they read the Receipts.