Four cases. Pick one. Sound on.

Inference is moving into your halls. The proof can live there too.

Inference Exchange and Fabric Intelligence are public Equinix products. Every tenant, firm and number in these cases is fictional.

Try it yourself

Change the record. Watch it stop matching.

This is the record kept for Kestrel decision 0412. The fingerprint on the right was taken when it was sealed. Change anything and your browser recomputes it on the spot. Nothing is sent anywhere.

INFERENCE DECISION RECORDExample · not Equinix data

Tenant: Kestrel Bank (fictional)
Decision: 0412
Route: Fabric FR2
Prompt left the hall: No
Metro
Model

Sealed fingerprint...

Fingerprint now...

MATCHESThis is the record as it was sealed.

SHA-256 over the record fields, computed by your browser with the Web Crypto API. Example values only. The Fabric map, verifier and full pack are linked below.

For the Fabric team

Where it plugs into Fabric, and a kit your engineers can run.

The map shows where each Hive record attaches to something Fabric already runs. The kit lets your team check the records on their own machine, with the network unplugged. Neither one touches customer data.

The Fabric map

Four Fabric surfaces. Four places a record attaches.

Read each row left to right. The Fabric surface you already run, then what Hive keeps beside it. Hive reads a fingerprint and a rule number. It never reads the payload.

Distributed AI HubWhere the AI decision is made
Proof Pre-FillThe record is ready the moment the decision forms
The interconnection portWhere traffic crosses between parties
InkFrameChange one byte and the signature breaks
Geo Zones for FabricWhere a workload is allowed to run
Disclosure-Free ReplayRebuild the route with no payload present
Fabric IntelligenceWhere agents route and change flows
Arrival CountersignatureWhat ran matches what was cleared to run

Open the full Fabric map What could come next

The verifier kit

Check it yourself, offline.

A 20 KB download. Node 20, three open source crypto libraries, no account and no call to Hive. It runs four checks:

01Builds a real signed record and verifies it
02Flips one byte. Verification has to fail
03Re-verifies a published 5,000 record benchmark
04Rebuilds a route with no raw text anywhere

$ npm install
$ node make-sample.mjs
$ node verify.mjs
all four checks passed.

Download the kit Run it in the browser

Signatures are Ed25519 plus ML-DSA-65, and both must verify. The kit ships verification code only. Hive's private engine and any keys stay out of it. We re-ran all four checks from a clean download on September 28, 2026.

The four cases, in one line each

The questions that come after an AI decision, answered from one record.

Where it ran

"Which metro, which model?"

Request, route, answer and arrival, sealed as they happen.

Agent changes

"Was the agent allowed?"

Every grant checked against the one above it.

Rivals on one floor

"Did the shared limit hold?"

Both sides commit blind. Neither sees the other.

Quiet windows

"Did nothing really happen?"

Quiet where watched, and honest where not.

Who does what

Equinix runs the floor. Hive keeps the record beside it. People decide.

EQUINIX

Runs the floor

Runs the halls, Fabric and the exchange, and keeps every customer relationship. Nothing about that changes.

HIVE

Keeps the record

Reads agreed events, fingerprints each one, chains them in order and signs the chain. Never in the traffic path, and never holds customer data.

PEOPLE

Decide what it means

Customers, auditors and Equinix read the record and decide. Hive never rules on anything.

Hive never sees a prompt or a payload
Hive never sits in the traffic path
If Hive is down, Fabric runs normally
Customer data never leaves the hall
Each party sees only what it is authorized to see
A record shows what was recorded, not whether it was right

The proposal

Test it on one route or workflow for 90 days.

One one route or workflow, one reviewer on your side. Hive stays outside the operation the whole time, and Equinix keeps working if Hive is down.

Days 1 to 14Set up beside it
Agree the one thread and the events that count. Hive reads a read-only copy of records Equinix already keeps. Nothing about the operation changes.
Days 15 to 60Let records build up
Every agreed event lands on the record. A one-page report goes out every Friday.
Days 61 to 80Try to break it
Four planned tests, each approved by Equinix: an altered copy, a missing step, a late entry and a correction.
Day 90You pick events
Can the reviewer rebuild each one from the record, faster than today?