Quadrazene
Quadrazene™

Refineries

Give every team a corner,
with a budget and a boundary.

Enterprises are trees: groups, divisions, departments, teams. A Refinery is a single container type that nests inside itself, so each level can own its content, grant access to its people, and spend a bounded amount on AI, without a platform administrator in the loop.

One recursive containerInherited accessScoped rolesMonthly AI capTemplates
quadrazene.app/admin/refineries
quadrazene v0.2.16
Quadrazene
ReactorReactionsReagentsRecipesRefineriesRegulationsResolverRecordsInbox
⌘K
Refinery tree
▾Acme Groupcap $4,000/mo
▸Financecap $1,200/mo
▸Accounts payablecap $500/mo
▸Treasuryinherits pool
▸Operationscap $2,000/mo
▸Network opscap $900/mo
Finance · monthly quota
AI cost cap$1,200
Token budgetinherit
Approval capinherit
Reaction capinherit
Bound roles
  • Priya · owner
  • Finance analysts · contributor
  • Internal audit · reader

Scoped access

Grant a role on one Refinery, and everything beneath it.

Bind a role to a Refinery instead of the whole tenant. Access flows down the tree, so a department head runs their subtree and nothing else.

refinery-owner

Owner

Author, publish and activate content, and manage budgets and members.

refinery-contributor

Contributor

Author new versions and bind references. Cannot activate content or change budgets.

refinery-reviewer

Reviewer

Read and run the content and review bundles. Cannot author.

refinery-reader

Reader

Read-only: sees the content and its run history. Cannot invoke Skills or author.

A root-level Refinery plays the part a cost center or business unit would elsewhere. Scoped members see Refineries in their nav without being tenant administrators.

Budgets that bite

Spend caps at every level of the tree.

Monthly AI cap

Set a monthly dollar cap on a Refinery. Reactor questions and Radar Interpret are checked before they run, and a request over the cap stops with a clear message instead of failing silently.

Nearest cap wins

A Refinery with no cap of its own inherits the closest ancestor's. The root's cap is effectively the tenant-wide AI ceiling.

Carve-outs that add up

A parent can guarantee slices to its children, but the children's explicit caps can never sum to more than the parent's own.

More than dollars

The same allocation rule covers a token budget, human-approval volume and reaction count.

Checked against month-to-date spend

The cap is compared with the tenant’s LLM spend since the start of the UTC month, so it stops runaway use whichever team causes it.

Real-time check

Enforcement is a live sum at request time, not a nightly reconciliation that lets a runaway job through.

A home for authored work

Templates in. Reagents out.

Content lives in the tree

Skills, Formulas, Chains, Views and triggers are filed under the Refinery they belong to, so ownership and review follow the org chart.

Install from a template

The tenant Catalog carries installable Refinery templates. Stamp out a new team's starter set in one step.

Cost-center labels

A free-form cost-center code on each node lets finance roll spend up however it already reports.

Tree-aware pickers

Everywhere the product asks 'which Refinery?', it shows the tree and the ancestor path, not a flat list.

Never unowned

Every tenant has a default root Refinery, so content and spend always have a home even before you model the org.

Portable

What a Refinery authored can leave it as a signed Reagent bundle.

Identity & access →Cost in Observability →

Model your organization once.

We'll sketch your org as a Refinery tree, with a cap and a scoped owner at each level.

Request a demoLLM routing & spend →