QuoxCORE components · governance

Don’t build your own guardrails.

Policy, approvals and spend control for autonomous work. The part everyone underestimates, and the reason agent projects stall at the demo.

See what ships Try the live demo

Included in QuoxCOREFree, self-hosted, nothing to buy.

Build it yourself and you are signing up for

A policy engine that runs before executiondeclarative rules evaluated on every action, not advisory logging after the fact
Approval routing with real deadlinesthe risky step waits for a person, and nothing auto-approves on timeout
Spend metering that can stop a runcost, tokens and tool calls, capped per organisation, objective, execution and iteration
Change control on the controls themselvesstaged policy edits with second-approver sign-off, or the guardrails are just config

Or install QuoxCORE. All of it is already there.

In plain words

What it is, where it lives, when to reach for it

What is it: The control surface of QuoxCORE: declarative policies, approval routing and enforced spend budgets over agent actions.
Where do I use it: In the dashboard governance pages, and in your terminal through quox governance policy and quox budget.
When would I use it: When agents get real access and you need limits that hold without you watching every run.
How do I use it: Budgets are one command: quox budget create. Policies are managed with quox governance policy or the dashboard.

QuoxCORE is the free, self-hosted platform underneath this. What is QuoxCORE

policy & guardrails

Decided before it runs.

Rules are declarative and evaluated ahead of execution: what may run, what pauses for a person, what is refused outright. The workflow engine carries the same gate on any step, so a policy is a checkpoint, not a comment.

Changing the rules is itself governed: policy edits can be staged for a second approver to sign off, and template packs give you a starting set instead of a blank page.

How do I use itquox governance policyDashboard: Governancequox governance template lists the policy packs; quox governance approval handles staged sign-off.

The governance policy centre in the QuoxCORE dashboard: declarative policies with their scopes and states

budgets & limits

Caps that hold.

Budgets attach at four scopes: organisation, objective, execution and iteration. Each caps cost, tokens and tool calls, and the hard stop terminates a run that breaches it rather than politely logging the overrun.

The iteration scope exists for loops: one runaway turn cannot spend what the whole execution was given.

How do I use itquox budget createDashboard: Governancequox budget usage shows rolled-up spend with a daily breakdown per budget.

$ quox budget create --scope org --max-cost-usd-micro 250000000 \
    --max-tool-calls 50000 --period-start 2026-09-01 --period-end 2026-10-01
  hard_stop            yes
$ quox budget list
 Scope   Period                      Max Cost (micro-USD)   Hard Stop
 org     2026-09-01 to 2026-10-01    250000000              yes

Real commands · demo organisation · captured 2026-09-09

Where it sits

Between intent and action.

Bundled with QuoxCORE; the guardrails are not an add-on. Approvals route to the HITL inbox, and every decision the gate takes lands in the evidence layer below.

if that’s not enough ...your code goes hereyour plugin can use everything underneath

you build this

Policy docs/Governance concept/HITL approvals/QuoxCORE

Ready when you are

Give agents room, not rope.

Policy, approvals and budgets ship in the box with QuoxCORE: no extra licence, no extra install.

See the platform Try the live demo