Skip to main content
Operayde
Book an executive briefing
Managed AI infrastructure · control-first

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.

Data stays in your country · Offline-verifiable audit trail · ISO 27001-certified operations

One request through the leverLive today
req · Draft credit memo · finance-desk key
  1. Routeappliance · eu-south · llama-3.3-70b
  2. Permitallow · policy bundle v14 · class: confidential
  3. Provesigned · evt a3f8…c21d · chain intact
  4. Cap41% of monthly key budget · enforced
  5. Keepcorpus + audit row stay in eu-south
  6. Leaveannual exit · export documented
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

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.

  1. 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.

    Mechanism

    OpenAI-compatible gateway · virtual keys · hybrid routing

    See how
  2. 02 / 06Live today

    Who allowed it?

    Permit

    A rule decides before the model sees anything: data classification, model, budget and residency, authored with you and enforced at the gateway.

    Mechanism

    OPA policy bundles, signed and versioned · ingress guardrails

    See how
  3. 03 / 06Live today

    Can we prove what happened?

    Prove

    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.

    Mechanism

    Hash-linked, Ed25519-signed audit chain · offline audit-verify

    See how
  4. 04 / 06Live today

    What did it cost, and who stopped it at the limit?

    Cap

    Hard ceilings per team, tool or key, enforced at request time. The gateway refuses before the spend lands, not after the invoice.

    Mechanism

    Per-key budgets · tenant spend caps

    See how
  5. 05 / 06Live today

    What do we keep?

    Keep

    Corpus, retrieval index, evaluation baselines, adapters and the audit trail stay on your side of the boundary, in your country.

    Mechanism

    RAG pipeline · eval gate · adapter distribution · residency at policy time

    See how
  6. 06 / 06Live today

    Can we leave?

    Leave

    An annual walk-away right in every contract, with a documented export of everything above. We retain nothing.

    Mechanism

    Exit clause · export runbook in the diligence pack

    See how

Pillar 1 · Control

Every call, hashed and chained

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.

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

Pillar 1 · Control

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.

Pillar 2 · Compound

Compound

Layer · Improve · Carry forward

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.

Pillar 3 · Local

Local

Inside · Routed · Sovereign-of-default

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.

Sovereign track · regulated buyers

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.

Visit the Regulated track

Where it runs

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 specIndicative rangeWho it's for
Starter20–250 FTE64–128 GB · 1–2× GPU · 8–16 TB NVMeSingle-team pilots, professional firms, regulated SMEs.
Professional150–500 FTE128–256 GB · 2–4× GPU · 16–32 TB NVMeDepartmental roll-outs, custom fine-tuning, dedicated engineering.
Entry / Premium500–5,000+ FTE256+ GB · 4–8× GPU · 32+ TBMulti-site deployments, on-prem sovereign clusters, large enterprises.

How we compare

Operayde vs the real alternatives

OperaydeBest choiceCloud AI SaaSDIY on-prem
Data stays on-site
Audit chain (externally verifiable)
Fine-tune on your dataLimited
Multi-model routing (local + cloud)
Managed hardware + updatesN/A
Walk-away portability
No GPU sourcing / MLOps team
Spend caps enforced before the callPer key, at the gatewayAccount-levelBuild it yourself

Why it matters

The consensus is wrong.

  1. 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.

  2. 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.

  3. 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.

EU SOVEREIGNGCC SOVEREIGN

Starter & Professional

Start with the discovery agent

Describe the workloads and the constraints. The discovery agent scopes the estate, recommends an offer, and points you to the right next step.