One governed runtime. Every app inherits it.
Frontline isn't a chatbot builder. It's a fixed, governed runtime — knowledge grounding, policy enforcement, human approval, and signed Trust Receipts. The Architect only writes configuration; the runtime does the rest, safely.
- Intent detected
- Grounded in approved knowledge
- Policy: pricing → human review
- Human approval
- Grounded answer sent
- Trust Receipt minted
Two planes
The Architect builds it. The runtime governs it.
A clean split: describe-time generates configuration; run-time enforces it. The moat isn't the generator — it's the fixed, governed runtime everything runs on.
The Architect
Turns a plain-English workflow into configuration — data model, agents, policies, and workflows. It never writes arbitrary server code, so nothing it ships can escape the runtime.
“A refund desk that answers from our refund policy and escalates big refunds.”
- Data model
- Governed agents
- Policies & approvals
- Workflow
The governed runtime
Executes that configuration under enforcement — grounding answers, gating risk to humans, and signing a Trust Receipt for every action.
Runtime modules
Eight modules. Composed into every vertical.
Not features you wire up per app — the fixed foundation the Architect configures. Grounding and governed chat run today; workflows, tool calling, and channels are available per tenant.
Safety isn't a setting you can forget to turn on.
Because apps are configuration on a fixed runtime — not arbitrary code — grounding, policy, approval, and audit apply to every app by default. There's no path around them.