What this is
FeirOS is FeirAI’s control layer: it sits between your agents and the systems they touch, in your environment. Policy, approvals, and budget checked before an action runs. Scoped, short-lived credentials the agent never sees. A signed, tamper-evident record afterward, verifiable outside FeirOS.
FeirOS runs in production at an EU crypto company today. The reference-customer track is how the next deployments are shaped: a small number of teams, each governing one real workflow, each with direct influence on what gets built next.
What you get
- One sensitive workflow governed end to end: policy, approvals, budgets, credential brokering, sealed evidence.
- Deployment done with you, by the founder. Your agents keep running as they are. Adapters for LangChain, Hermes, and custom code, Python and TypeScript, any model.
- A control mapping of your workflow before we touch a line of configuration, yours to keep either way.
- A direct line to the roadmap. What you need moves to the front of it.
- Reference-customer pricing on the first deployment and the first months of the retainer.
What we ask
- A named owner on your side, the person accountable when an agent gets it wrong.
- A 30-minute call every two weeks, and honest feedback in between.
- One workflow to start. We expand only after the first path has earned trust.
- If it works for you: a named reference. That is the trade for the pricing.
What it costs
A fixed-scope first deployment at reference-customer pricing, then a monthly retainer to run and extend it. We agree the number on the readiness check, and it stays below what one engineer-quarter of building in-house costs. No obligation to continue past the first workflow.
Who qualifies
- Your agents already take write actions, or will within a quarter: refunds, payouts, orders, access grants, record changes.
- Those actions touch something regulated, financial, or otherwise hard to undo.
- Someone on your team is accountable for the outcome and wants control they can point to.
How it runs
| When | What happens |
|---|---|
| Week 1 | Control mapping agreed. One protected action routed through the boundary. |
| Weeks 2 to 3 | Authority defined. An allow, a deny, an approval, a stop, and a budget response exercised for real. |
| Week 4 | Sealed evidence exported and verified independently, by you, outside FeirOS. |
| After | The next workflow, only once the first has earned it. |
Honest limits: FeirOS governs actions routed through its boundary; uninstrumented actions stay outside it. Budget ceilings carry a bounded, stated overshoot rather than a zero-lag cutoff. Evidence carries a declared trust level.