Prove the first governed spend lane before money moves.
- Best for one builder or one small team validating a first lane
- Policy engine, receipt trail and monthly statement
- 1.00% fee only when NORNR executes settlement
NORNR
Governed agent spend before money moves.
NORNR / Pricing
Buyer-firstPay for the control plane, not just the rail.
Start free, prove one spend lane, then upgrade by rollout fit. Governed spend is secondary headroom. Agents, workspaces and intents are guardrails behind the plan, not the whole buying story.
Subscriptions carry the product. Settlement fees are secondary and only apply when NORNR executes the settlement rail for that spend.
Plans
Four plans, one pricing model.
Self-serve for Free, Builder and Growth. Enterprise stays custom. Design partner pilots stay bounded and convert into a standard plan afterward.
Run one real team through governed spend in production-like workflows.
- Best for one team moving from test to real approvals and exports
- Slack approvals, anomaly inbox and audit export
- 0.50% fee only when NORNR executes settlement
Standardize review and close across multiple teams and critical workflows.
- Best for cross-team rollout, finance operations and stronger reporting
- Shadow policies, cost attribution and signed close bundles
- 0.30% fee only when NORNR executes settlement
Treat NORNR as an institutional control layer with buyer-specific terms.
- Best when limits become contractual, not self-serve
- SSO / SAML, deployment and retention options
- Support and SLA by agreement
The model is simple: subscription first, rail fee second. NORNR charges for policy, review, evidence and audit posture even when settlement happens elsewhere.
How to Think About It
One buying axis, one secondary axis, and the rest as guardrails.
This keeps pricing understandable for buyers while preserving the real operational limits behind the product.
Rollout fit
Choose based on who needs the product now: one builder, one real team, multiple teams, or an enterprise buying committee.
Governed spend headroom
Use governed spend as a practical ceiling for the lane you are controlling, not as the whole reason to buy.
Agents, workspaces and intents
These are there to keep the plans productizable and supportable. They are not meant to be the first thing a buyer anchors on.
Upgrade Triggers
When buyers usually move up
The cleanest upgrade moments are operational, not purely volumetric.
Approvals or finance review become real operations
Move up when the first lane stops being a demo and someone outside engineering has to trust or defend it.
Multiple teams need one shared control standard
Move up when review, reporting and close can no longer live inside one team’s local workflow.
Limits become contractual and compliance-bound
Move up when deployment, identity, retention or procurement terms become part of the buying boundary.
Best customers now
The right buyer already has one workflow close to money.
Pricing becomes much easier to understand when the team can point to one live lane that needs policy, review and a defended record now.
One real team, one real lane
Browser checkout, vendor APIs, procurement actions or paid tools are the cleanest first lanes because they make the control problem concrete fast.
Compare your lane against the canonical buyer proof
If you can map your workflow to one intent, one approval state and one defended record, you can usually buy the right plan quickly.
Not a fit for abstract governance shopping
Teams that cannot yet name one concrete spend lane usually stay too conceptual. The product is strongest once one workflow is already close to real money.