RotaGrant Is Live
TL;DR: RotaGrant is available today. It states what an agent may do before it acts, refuses what exceeds that, and records what was decided either way. It runs single-tenant in your environment and calls no model anywhere. There is a live deployment you can sign in to with a work address, and it is a real deployment rather than a recording.
What we built
Every post on this blog for the last two years has circled the same argument. Model evaluation tells you how a system scores on a benchmark. It does not constrain what an agent may do on a Tuesday afternoon with a payment API in reach. Those are different problems, and the second one has no product.
RotaGrant is the second one. Before a consequential action, the agent asks whether it is authorised. Nine gates evaluate in a fixed order (authority, status, window, scope, clean context, bounds, policy, budget, review) and return one of six outcomes. The answer arrives before the action, and the decision is recorded whether it was allowed or refused.
Three things follow from that shape, and they are the reasons it exists.
Authority is a grant a named human signed for, with a scope, a limit and an expiry. Not a service account. When an auditor walks the chain up from an action, it terminates in a person.
Delegation subdivides and never multiplies. A delegated grant cannot exceed its parent on any dimension, and the API refuses to issue one that does. Spend debits every ancestor, so the root’s ceiling is the whole tree’s ceiling.
Refusals are first-class. An agent that was stopped is the evidence that the control operated, and it is the half that systems built to log successes do not have.
What it does not do
We would rather say this here than have you find it in a procurement call.
It does not evaluate models, score them, or make your agent correct. It inventories what is deployed because a regulator will ask, and stops there.
It does not make you compliant. It assembles evidence, maps it to clauses, computes what it can, and names what it could not find. Whether that satisfies your obligations is regulatory interpretation and it rests with you and your counsel. That disclaimer sits inside the signed payload of every pack, so removing it invalidates the signature.
It ships clause maps for four instruments: the EU AI Act, GDPR, SR 11-7 and the NIST AI RMF. DORA and ISO 42001 have numbered articles and are unmapped because we have not written them yet. MAS FEAT and the UK approach have nothing enumerable to map, which is a different reason, and each page says which of the two it is.
Rotascale holds no SOC 2 and no ISO 27001, and makes no HIPAA or FDA claim. What a certification would attest to is largely answered by the deployment model instead: the software runs in your environment and we hold none of your data.
The demo is a running deployment
Not a video, not a sandbox with fixtures. A deployment on real infrastructure where agents run every day and produce real records, including the refusals.
Right now it holds a payment agent stopped at gate 8 because an ancestor grant was exhausted while its own allowance had room. A document analyst gated because it read an unverified upload and the grant required a clean context. A refund assistant running simultaneously at three rungs of the enforcement ladder, where the observe and canary copies refunded the same tickets the enforcing copy refused.
Access needs a work address and one click. The session is read-only: you can read everything and export any pack, and it cannot write because the role is absent from the platform’s write roles, not because the page is hiding buttons.
Three live bugs were found by taking the screenshots for this site as an ordinary visitor. That is the argument for a real demo, made against ourselves.
Enforcement is a dial
Nobody switches a production estate from nothing to blocking in one step, so the platform does not ask.
Observe records what the check would have done and changes nothing. Shadow does the same with the full decision path exercised. Both are free, and both are genuinely useful on their own: a fortnight of observe against production tells you what your agents are actually doing, and that first week reliably contains a behaviour nobody knew about.
Canary and enforce refuse. You move one grant at a time, when the team that owns it agrees.
The mode is sealed into every record at the moment of the decision, so a pack states what was enforcing then, not what is configured today. That distinction is what makes reconstruction possible eighteen months later.
Where it runs
Single-tenant, in your environment: your cloud, your data centre, or airgapped. No payload reaches us on any code path, and the deployment refuses to start if any setting selects a service outside your network. It also tells you which evidence property you gave up by disconnecting it, rather than pretending nothing changed.
It calls no LLM anywhere. Not for summaries, not for classification. A test fails the build if a model provider appears in the dependency graph. In a category where every product is an AI product, we think that is the stronger claim.
Market profiles ship for the EU, US, Singapore and Australia. India is served by Rotavision, a separate company that encodes the Indian instruments properly.
This is not only for regulated firms
The category is sold almost entirely to organisations with a supervisor, and that framing points it away from the teams with the largest agent estates. Platform and AI-native companies ship agents fastest, into the most accounts, with the widest reach, and no statute is coming for them soon.
Their obligation arrives through a customer’s security questionnaire instead, which in practice is sooner. And they can do something a bank cannot: put the record in their own product, so a per-tenant verifiable account of what their agent did becomes a feature rather than an archived artefact.
What happens next
The specification is open and published, because an authority format that only one vendor can read is not an interface, it is a lock-in with a schema. Clause maps are YAML validated at load, so a regulatory analyst can author one without waiting for a release.
The honest state of the roadmap: DORA and ISO 42001 maps, a UK profile, and more sector scenarios in the demo so that every industry page can show a real record rather than three of them.
Start where it costs nothing
Sign in to the demo with a work address and look at the refusals. They are the part that is hard to fake, and the part that shows what the product is for. Then bring the agent you are most nervous about, and we will put it behind a grant while you watch.
That is the whole offer. No pilot fee, no slide deck, and nothing we have said here that you cannot check.