NEO evidence rail · the pilots for SAP

One rail, four steps: their signal, a month, the live pilot, the federation's twin

What we built for SAP, in the order it was built — every step measured, every figure read from the running system or the evidence files, every page one click below. The rail underneath never changed: a company keeps its own book, one 32-byte commitment a minute leaves, the rail seals every ten minutes and every company holds its proof.

the rail, live · data from 2026-10-23 17:27:30 Z · 99,668 objects a second through the door

The pilots, in order

1
20 September 2026 · measured

Their audit-logging signal, 10,008 companies

ApeiroRA's SDK and collector as published, into a NEO sink that keeps every company's records in its own book and answers each with a receipt; one seal a minute leaves. Two hours, none failed; the sinks stopped mid-work and came back with nothing lost.

10,008companies, each its own book
58,623,047audit records answered, none failed
8,140/srequests a second, one record each
Open the pilot ▸
2
25 September 2026 · run 3, four reviews

A month on OpenNebula — three providers, one customer, one rule

OpenNebula places nine services across three provider clusters; every start and stop lands in the executing provider's own book. A German manufacturing group buys under one rule — German data stays in Germany — a host fails, the assistant moves inside the rule, and the month settles from the records alone.

31records in four books — three providers and the customer
513,650µCLU to settle after community netting
58.4 %less than settling pair by pair
Open the pilot ▸
3
since 29 September 2026 · the rail live · the edges at rest since 1 October

The pilot on Telemach — one rail live, four companies proven

Four companies' edges booked a thousand records a second each for 40 hours (29 Sep – 1 Oct), folded every minute into one commitment, and every period with records reached FINAL; they rest since 1 October, waiting for their real sources. The rail keeps running: ten thousand simulated companies send one object a minute and a source loop pushes a hundred thousand objects a second through the same door; every ten minutes the rail seals it.

99,668objects a second, now
207,287,145,465objects through the door, in all
2,735periods proven at one real edge, to 1 Oct
Open the pilot ▸
4
from 15 October 2026 · with SAP

The federation's twin — every firm of the 8ra consortium, with SAP's signal at every server

The consortium's organisations run as twins on the same rail, each with its edge and SAP's collector in front: registrations, a deal day in the marketplace, data that stays home, one breach and ten rulings in a day, the month netted — the room's three figures, all read from the system.

122members — the consortium's firms as twins
20providers with SAP's collector in front
92customers buying on the deal day
Open the pilot ▸

Behind the four: the demonstrations page for ApeiroRA / 8ra (/demo/8ra/, the evidence files and the offline verifier), the marketplace with 2.7 million offers (/marketplace/), and the architecture. Nothing on these pages is promised that is not built.

Platform Mesh marketplace

A service lifecycle across providers, the platform and a subscriber: records at each stage, failure and metering-dispute examples, and a public cryptographic verification kit. Historical lab results and illustrative scenarios are identified separately.

Open the Evidence Explorer →

Standalone Cotrugli demonstration · synthetic proof fixture · prepared for fed8ra integration.