AI infrastructure you can see, change, and walk away from.
AI is becoming an operational lever as consequential as your ledger or your network. Operayde is the governed layer that keeps it in your hands: policy before every model call, a signed audit chain you can verify offline, sensitive work that never leaves your country, and an exit clause in every contract.
Illustrative request. Every readout maps to a live mechanism.
Prove
Every call, signed and hash-linked
Each request and policy decision is written to a chain whose daily root is published. Anyone holding an export can verify it offline, without trusting us.
Live root on the Trust Centre
Permit
Policy decided before the model answers
Rules on data classification, model, budget and residency are enforced at the gateway on every request — authored with you, signed, versioned.
OPA policy bundles
Leave
An exit clause in every contract
Annual walk-away right with full export of corpus, weights, adapters and audit chain. We retain nothing.
Export runbook in the diligence pack
controls · 06
The lever
Six questions your AI infrastructure must answer
Whoever can answer them holds the lever. Each answer below is a control that is live on the platform today, not a roadmap item.
01 / 06Live today
“Which model answered, and where did the data go?”
Route
Decide which model, in which location, may serve which data — cloud, your own provider keys, or open-weight models on an appliance inside your perimeter — through one API.
Every request and policy decision is hashed, linked to its predecessor and signed. The daily root is published; anyone holding an export verifies it offline.
The audit chain records every model call, every retrieval query, and every policy decision. Each event carries a SHA-256 hash of its predecessor — change one and the chain breaks. External auditors can verify integrity without accessing the data.
Exportable. Verifiable. Yours to keep if you leave.
SHA-256 hash-linked events
Ed25519-signed daily root
Verify offline, no data access
audit.v1.events — live chain
IDActionModelHash
evt-001chat.completionllama-3.3-70ba3f8…c21d
✓ merkle chain intact · 1/5 events
Pillar 3 · Local
Right model, right location, one API
The gateway checks each request against your OPA policy bundle: data classification, model capability, cost preference. Sensitive work stays on the appliance. Everything else routes to the best available cloud model — same API, same audit trail.
Select a request to see how the gateway routes it.
Gateway routing decision
Cloud Destination
Remote Model
Local Destination
Appliance
→ Appliancellama-3.3-70b
Classification: Confidential — financials
Capability accumulation
Day 1Retrieval over your corpus
Pillar 2 · Compound
What accumulates, and where
Every interaction generates signal: retrieval hits, evaluation scores, preference pairs, decision-outcome data. The platform holds that signal on your side of the boundary and turns it, step by step, into assets you own. None of it depends on a vendor's roadmap, and each asset is exportable.
Scrub the timeline. The sequence is indicative; the ownership is contractual.
pillars · 03 + sovereign
Every model call under your policy.
What accumulates is yours.
Sensitive work stays local.
One platform · three universal pillars · one sovereign track
What the platform actually does
Control
See · Change · Walk away
See every model call: which model, which prompt, which output, which policy decision. Externally verifiable audit chain. Open weights. Leave at any annual boundary and take the corpus, weights, and audit trail with you.
Every governed interaction leaves an asset on your side of the boundary: retrieval over your corpus, evaluation baselines that gate model changes, preference data, and adapters distributed and eval-gated through the same signed pipeline. What accumulates is exportable, and it is yours.
The five percent of your data that defines your edge never leaves your building. The other ninety-five percent uses whichever model is best. One audit trail across both — no per-tool sourcing projects.
If your AI purchase involves your auditor, your regulator, or a sectoral supervisor — EU AI Act, DORA, NIS2, sectoral rules — start with the sovereign track. Same platform, stronger compliance pack, dedicated process.
The same control plane, hosted or inside your perimeter
The six controls do not change with the footprint. What changes is where the compute sits.
Hosted
Available today
EU or GCC control plane, operated by Operayde
Tenant workspaces, gateway, policy and audit chain run from an in-region control plane. Your data stays in the region you choose; we operate the platform around it.
EU · UAE · KSA
Appliance
Where mandated
Inside your data centre, fleet-managed from the control plane
For residency, latency or air-gap requirements, the same gateway, policy and audit chain run on hardware sized to your estate. Specifications are published as ranges.
Technical spec
Indicative range
Who it's for
Starter20–250 FTE
64–128 GB · 1–2× GPU · 8–16 TB NVMe
Single-team pilots, professional firms, regulated SMEs.
Multi-site deployments, on-prem sovereign clusters, large enterprises.
compare · 08 rows
How we compare
Operayde vs the real alternatives
OperaydeBest choice
Cloud AI SaaS
DIY on-prem
Data stays on-site
Audit chain (externally verifiable)
Fine-tune on your data
Limited
Multi-model routing (local + cloud)
Managed hardware + updates
N/A
Walk-away portability
No GPU sourcing / MLOps team
Spend caps enforced before the call
Per key, at the gateway
Account-level
Build it yourself
wedges · 03
Why it matters
The consensus is wrong.
Wedge 01
“The cloud is the wrong default.”
For 40% of European firms, and more in the GCC, residency isn't a 'later' problem — it's a procurement condition. Governed infrastructure inside the boundary clears it once, for every model you use.
Wedge 02
“Tenancy is hosting. It isn't control.”
A private tenancy on someone else's cloud tells you where the data sits. It doesn't show you which model answered, which rule allowed it, or let you leave with the record. Control is being able to see, change, and walk away.
Wedge 03
“Evaluation beats generation.”
The bottleneck isn't model quality; it's the inability to tell when the model isn't working. Evaluation gates are built into the platform, and a model that regresses against your baseline is blocked from promotion.
Choose your path
Two doors, one platform
Whether your auditor is in the room or you simply want AI you can account for, the platform is the same. Pick the door that fits how you buy.
Enterprise & Regulated
Start with a discovery call
Custom hardware sizing, compliance mapping, on-site install. Your success engineer walks you from pilot to production.