Sovereign by architecture, tested by you.
Do not take our word for it. Put the same four questions to every vendor on your shortlist, including us.
Questions to put to any vendor.
Ask these of every vendor on your shortlist, including us. They are not unique to Skipr · disconnected infrastructure is available from several hyperscalers. Disconnected authority, the policy root and the decision rather than the compute, is the part still missing.
| Test | The question | Skipr's design |
|---|---|---|
| No call home. | Does any authorization decision require a connection to a service you operate? | No authorization decision is designed to require egress to a Skipr operated service. |
| No foreign kill switch. | Can you, or a government you answer to, stop or alter our decisions remotely? | Designed with no remote stop. The policy root and keys stay with the customer. |
| Authority transfer. | Can we take full authority from you, including the policy root, without your consent? | The customer holds the policy root and key custody and can revoke independently, including against ours. |
| Evidence custody in country. | Does the evidence of each decision stay in our jurisdiction, verifiable without you? | Each protected decision is designed to produce a signed, jurisdiction tagged record the customer can verify with Skipr unreachable. |
Who holds the roots, and who can check the record.
Sovereignty
The customer or government holds the policy root, the identity root and the keys. Decisions don't depend on reaching Skipr or any foreign control plane. The design goal is that the system keeps deciding while disconnected.
Evidence
Receipts are signed by the component that made the decision and tagged to a jurisdiction. They are stored in an evidence environment separate from the decision system. A regulator or auditor can verify them without Skipr. The plan is to anchor them into accredited trust infrastructure rather than ask anyone to trust our ledger.
McKinsey calls audit and control mechanisms a liability firewall for the organisation deploying AI. The receipt is that firewall, held by you.
Who holds which root.
The operator or host holds platform root
Platform-level authority and jurisdictional standing sit with the entity accountable in that country.
Each customer holds its own policy root and key custody
Within its own tenant the customer holds the policy root and key custody, and can revoke independently, including against the operator's preference and against ours.
No layer both proposes and permits.
- 01
Intelligence may propose
Models, agents and people interpret, classify, plan and recommend. They never receive authority simply because they were able to formulate a request.
- 02
Deterministic knowledge establishes what is true
Structured facts, provenance, relationships and constraints determine which rules apply and which actions are even eligible.
- 03
Skipr determines authority
Allow, deny, limit, escalate, route or revoke, bound to a verified actor, target, action, arguments, policy version and current state.
- 04
The enforcement boundary holds the capability
The credential, capability or network path required for protected execution sits here, not with the requester. It is designed so the requester holds no bypass path.
- 05
An independent safety layer can override everything above it
Revoke, quarantine and safe-state controls that the governed intelligence cannot reach through ordinary runtime authority.
- 06
A separate evidence layer makes it reconstructable
Who asked, what was known, which policy applied, what authority was issued, what executed, what changed, signed and portable.
Stated publicly, not hidden.
- To make a model truthful, aligned, unbiased or incapable of harmful output
We do not believe any vendor can. Our value assumes the model is sometimes wrong, that is the premise, not a caveat.
- That deterministic logic is automatically correct
A deterministic decision is wrong if the policy, state or data is wrong. We claim governability, not infallibility.
- That rotation or replacement reverses a compromise
Rotation limits persistence on replaceable components. It does not undo exfiltration.
- That all infrastructure can be stateless or continuously replaced
Stateful and hardware-bound systems need separate controls.
- That cryptography alone creates security
Trust depends on key custody, policy roots, supply chain, enforcement placement, recovery and operations.
- To make AI safe by design
We address the narrower, testable problem of bounded authority and governed execution.
- To be a model host, an agent platform, a detection engine or a cloud
Each would destroy neutrality, which is the one property a vendor of the governed thing cannot hold.
Cut the link. Check the record.
On your own infrastructure, we will run a disconnection drill with your team: cut the link to Skipr, keep deciding, and verify the signed records yourself.
Found a vulnerability? See our responsible disclosure policy.