Running since 29 September 2026, 17:30 UTC on the Telemach cluster. The rail — the door, the accounting cell and the DLT — has sealed every ten-minute period since, under a paced load of 100,000 objects a second and a fan of 10,000 simulated companies. Four companies' edges booked a thousand records a second each for 40 hours, folded every minute into one 32-byte commitment, and every period with records reached FINAL; they have been at rest since 1 October 2026, 15:50 UTC, waiting for their real sources. Everything on this page is read from the running system itself.
Click a card for the detail behind it.
In a cloud-edge continuum the record of what happened is spread over many providers and many edges, each keeping its own logs. To show a partner, an auditor or a court what was booked and when, today you copy data and trust whoever holds the log. Every copy is a leak; every log is a thing to argue about.
Every participant, a provider's server or a company's edge, keeps its own book and sends the rail only a 32-byte commitment a minute. The rail seals everyone's commitments every ten minutes with two witnesses and post-quantum signatures and keeps only the seals and a list of roots; each participant fetches its proof and keeps it. Any record is provable months later, offline, with public keys — nobody has to open a log. That shared, verifiable time is what makes many clouds and edges one continuum, at 33 bytes a minute per participant.
SAP / ApeiroRA: the audit-logging collector (otelauditcol, strict mode, source-signed) is the signal at every server — unchanged. Cotrugli / the NEO stack: the edge beside it, the door, the accounting cell, the DLT with its witnesses and seals (Ed25519 + ML-DSA-65), the NEO Chamber's small book for governance — 32-byte objects end to end. Iron: Telemach's Kubernetes cluster in Croatia, WireGuard between sites; before it, a month on OpenNebula. Everything on this page is the running system, read live.
Put the edge beside your collector on 15 servers of a test landscape: a container of about 250 MB of memory, six configuration values, a WireGuard peer — your collector unchanged, your data never leaves your server. From the first minute every server holds a proof per minute that anyone verifies offline. One engineer, one day for the first site; then 150 by December, and the continuum's evidence rail shown together at the 8ra General Assembly in Paris, March 2027.
Beside the four companies' edges (at rest since 1 October, below), two loads run through the same door into the same cell around the clock: a paced source at 100,000 33-byte objects a second — sixty million objects folded into one root every ten minutes, 8.6 billion a day — and a fan of 10,000 simulated companies, each opening a connection, sending its one object and closing, once a minute. The cell folds everything of ten minutes into one root; the DLT seals it; the rail deletes the archives fifteen minutes later. The fan's own counters: sent 338,213,927 · refused 18951 · mean 64.64 ms · slowest 15442.9 ms · rounds 33823.
The running total is the sum of the cell's own period counts: every period the cell folded since 26 Sep, read from its period files, plus every period closed since, read once from its receipt service as it closes; a period this watch could not read while its archive existed is left out, so the figure is exact or an undercount. Objects a second = the last closed cell period's count over its 600 seconds, read from the cell's own receipt service. Measured on this rail on 29 Sep: at 100,000 a second the cell folded 59.7, 60.1 and 60.1 million objects into one root each, nothing dropped at the door or the cell, every root sealed within nine seconds of the close. A company's proof is one block of 4,096 leaves and the block hashes — 26 hashes among 60 million, answered in milliseconds from an index the cell writes once per period and deletes with the archive — so every real edge's proof lands inside the fifteen-minute window at this pace. The rail's shape is the same at any pace: one root per period whatever comes in, 48 bytes per company in the Chamber's list.
NEOedge, NEOai, NEOcompute and mfgde — four synthetic companies' edges on the cluster — booked 1,000 records a second each for 40 hours, from 29 September 23:33 to 1 October 15:33 UTC, folded every minute into one 32-byte commitment and fetched every period's proof into their kits. The soak's verdict of 8 October: every closed period with records FINAL; nothing pending, in the outbox or unsent; the chain of seals without a gap; and every FINAL period in the four kits — 11,080, with those of the tests of 26–27 September — re-verified offline with the public keys, strict (Ed25519 and ML-DSA-65), 0 failures.
Since the feeders ended, the edges have booked nothing, so they send nothing: no new commitment, no new FINAL. They stay up with their books and kits intact until their real sources are connected; the rail above keeps sealing every period without them.
ApeiroRA's audit collector, in strict mode, passes only source-signed records to the edge on the same machine. The edge books each record (128 bytes, append-only) and every 60 seconds folds the period's records into one 32-byte commitment.
the book, the keys and the kit stay on the company's diskThe commitment and one flag byte, over one TCP connection. The door checks the shape, forwards, and keeps nothing: no journal, no signatures, no configuration per edge. A new edge is enrolled by being on the trusted network.
100,000 sends a second measured, 0 droppedThe cell folds every edge's commitments of the ten-minute period into one root and sends that one object to the DLT. The cell's archive lives 15 minutes after the root is final, then it is deleted.
one company's edge = one object a minuteTwo independent witnesses sign the period, the terminal seals it with Ed25519 and ML-DSA-65 (post-quantum). Seals chain from the genesis. The archive is deleted 15 minutes after the seal — only with the Chamber's receipt.
seal 4–11 s after the close, measuredThe Chamber takes each seal and the period's list of roots, checks that the list reproduces the sealed root, keeps it, and gives the rail its receipt. Seals are kept forever, lists for 35 days: any path is recomputed from the list.
48 bytes per company per period — 150 companies = 7 KBInside the window the edge fetches the proof of its period — from the record to the sealed root — and keeps it in its kit. Anyone with the public keys verifies a record, a day or a year offline. No server has to be alive.
the company's own legal retention, 5–11 years33 bytes a minute per edge. Not the records, not their content, not who did what — one commitment per period.
Everything: the records, the book, the keys, the kit with every proof. The rail keeps only seals — 3.7 KB every ten minutes.
This is how the four edges ran from 29 September to 1 October; the rail's part of it runs every period still. If the door is unreachable, the edge holds its closed periods in its outbox and sends them all in the first tick after the door returns; if the rail loses a commitment, the edge re-sends it in the next period. Measured on 28 September: the door killed for three periods, every period proven afterwards; the DLT down for seven periods, nothing accepted lost; the Chamber unreachable until the DLT's quota — every refused object re-sent and found.
The numbers and their evidence: the measured numbers. Every figure names the box it was taken on, the objects per send and the connections.
otelauditcol in strict mode, with one signing key per company; it already runs on the audit-logging path.On the rail's side a company costs 48 bytes per ten-minute period in the Chamber's list; the DLT's budget holds about 125,000 companies per period. Capacity is not the question; staying correct and unattended is — which is what this page shows.