Six system types.
One engineering standard.
Each type is a different problem shape. Start from the symptom you recognise, it routes you to the system type, the proof, and the case file behind it. Every build ships eval-gated, observable, and owned by you.
Pick your seat.
We'll route the rest.
Each role gets a first step, the system types worth reading, and the Agentix-owned products that apply. Where no owned product fits, we say so: that work is a custom build you own.
Operations leader VP Ops · COO · Operations Director
Manual processes eat the week, and there is no development team free to fix them.
None. For this role the work is a custom build: self-hosted, eval-gated, and yours outright.
Engineering leader CTO · VP Engineering
AI pilots stall before production, with no eval harness and a real fear of lock-in.
Business owner CEO · MD
Unsure what AI is worth to the business, and wary of an expensive experiment.
None. For this role the work is a custom build: self-hosted, eval-gated, and yours outright.
Different problem, same spine.
Whatever the system type, the architecture is the same five stages, input passes a typed MCP boundary, specialist agents do the work, and nothing reaches you until it clears the eval gate.
The MCP boundary and eval gate are structural, not policy, an agent can't reach a live system without the typed gateway, and a build can't ship if its eval score drops more than 5pp.
System types
Six standards, whatever
the system type.
These aren't optional extras, they're the engineering baseline under every system we ship.
Eval harness first
100+ scenario stories written and passing before any production deploy. Verified, not just tested.
CI regression gate
Every PR runs the eval. Score drops more than 5pp and the build is blocked. No silent decay.
MCP system boundary
No agent touches a live system without a typed FastMCP gateway. A structural boundary, not a policy.
Full observability
Langfuse traces on every run, Prometheus metrics, inputs, outputs, latency and cost, from day one.
You own everything
100% of the code, infrastructure and data. No licence fees, no hosted dependency. Forkable on day one.
Read-only by default
Systems read; writes need explicit human approval or a named, reviewed exception. Enforced in code.
Not sure which
one fits?
Describe what you want to automate. We'll tell you which system type fits, what the build involves, and what the eval harness looks like. 30 minutes, no commitment.