Enforces authority
The Refinery
Your outputs reach customers, examiners, or counterparties -- so the model's claims get verified against registered oracles before anything ships. The ontology defines what must be known. The gate enforces it. If the evidence is missing, the output is blocked. You deploy in your VPC with a named account and SLA.
Without this
Without the Refinery, claims go out unchecked. The first person to discover a wrong answer is the person who acted on it — your customer, your patient, your claimant.
How it works
Every claim passes through the gate. If evidence is found, the claim is authorized and emitted. If evidence is missing, the claim is blocked — the system refuses rather than guesses. The consumer never sees uncertainty.
Failure mode: Fails closed — Uncertainty does not pass. Missing authority results in refusal. Runtime judgment is removed.
Who operates it, who receives it
Operator
The Engineer
Managing a continuous process where raw inputs must be purified into reliable outputs.
Consumer
The Customer
Should never see uncertainty or internal debate.
When to choose this
Deploy for
- Customer-facing AI in regulated domains
- Financial reporting and disclosures
- Insurance explanations and determinations
- Legal analysis and compliance workflows
- Healthcare administration
Do not deploy for
- Medical treatment decisions
- Safety-critical control systems
- Defense or classified environments
Where it runs
Deployment
Enterprise license / VPC-bound
Dedicated tenant / region-locked
Support
Named account + SLA
Execution
Isolated tenant / VPC-bound
Moderate regulatory exposure
What it costs
$12,000 / month
Scale with The Refinery →The Refinery is The Studio hardened for production. Signed metadata, version-controlled oracle registries, CI/CD for prompts and ontologies, staging environments for governance testing before deployment. This is where a company goes after proving the concept and rolling governance across departments.
- Multi-domain governance — run multiple oracle-backed domains in parallel
- Multi-seat with role-based access control
- Signed metadata on all governance artifacts
- Version-controlled oracle and ontology registries
- CI/CD pipeline integration for governance configuration
- Staging environments for governance testing before production
- Advanced Tavily and tooling orchestration — multiple research sources, custom API integrations, scheduled oracle refreshes
- Audit logs with signed entries
- Dedicated onboarding support
How the tools work here
Every environment uses the same platform tools — the difference is how aggressively each tool enforces.