The fed8ra pilot explores how European providers could share compute, AI, storage and network resources, account for their contributions and settle net obligations with a connected evidence trail. This page describes the pilot, its demonstrations and the work ahead.
Explore the user-portal concept ▸See the netting demonstration ▸
fed8ra is a proposal by HashNET for cooperation across the 8ra federation. The pilot brings together reference integrations, resource accounting and evidence-based clearing. A shared customer portal and the federation’s governing body are proposed next steps.
A possible customer experience: find resources, configure a service and review a request in one workspace. The separate interactive concept shows that direction with fictional offers; it is not a connected marketplace.
The reference trail follows an order through agreement, delivery and measurement. The netting demonstration then explores how mutual resource claims can be offset and connected to a signed settlement record.
A member-led non-profit could define participation, contribution, clearing and dispute rules. Its governance, fees and billing responsibilities still need to be agreed; the web demonstration does not establish them.
ACTIVE: the public read-only viewer and historical-review connection on the dedicated Telemach FED8RA LAB. VERIFIED: historical NEO inclusion of the synthetic €100 case, plus a separate strict N8 FINAL proof for its hosted review after interruption and recovery.
PENDING: Revolut sandbox access, a matching bank confirmation and the main company portal connection. Historical inclusion is not N8 FINAL or proof of payment. Dated status: 15 October 2026; no live bank feed.
The roster groups 20 provider entries by resource family. Use “View example” to replay the same historical reference flow with a selected label. These entries are not bookable offers or statements of available capacity.
Virtual machines, Kubernetes, GPU hours — the clusters the continuum runs on.
8 providersPrivate LLM inference, fine-tuning and chat, inside the EU, on the buyer's own data.
4 providersObject and block storage, backup and archive, with the proof of where the bytes sit.
4 providersInterconnection, private links and exchange points between the federation's sites.
2 providersIndustrial and on-site edge, next to the plant, the turbine, the hospital.
2 providersThe families reflect the pilot roster’s role mapping. Platform Mesh is the reference integration used by this demonstration; it does not imply that each named firm has published a service there. The providers are the 8ra consortium's — the public participant list on www.8ra.com, under the NEO names the twin uses (neoedgex deploy/neo8ra-twin/roster.py).
Six steps from the catalog to the invoice. Each step shows the record it leaves — the reference trail as booked at four real edges in the lab on 1 October 2026, in the names Platform Mesh itself uses.
The animation explains discover, agree, deliver, measure, clear and invoice using the recorded lab example. It does not submit an order or provision resources for the selected firm.
The trail: cotrugli.tech/demo/8ra/mesh/ — the Platform Mesh flow of a private LLM subscription (APIExport → Account → APIBinding → LLMInstance → the day measured → the week stated), 32 events in four books, booked at four real edges on neo-7 (core 116ad2c, 1 Oct 2026 14:13Z) with every hash as predicted. The clearing and the invoice are fed8ra's steps on top of that trail; in the pilot the Revolut Business sandbox stands in for SAP's billing (TRU-wallet, settled 18 Aug 2026, rail transaction 055746a9…).
This configuration sketch explores how a participant might combine a marketplace, billing, evidence and governance. Changing these options illustrates the proposed model; it does not configure a live integration.
HashNET's triple-entry bookkeeping is one tissue among several — FACIS and OpenNebula bring their own. fed8ra's clearing takes any party's measured usage that arrives with a verifiable head: a NEO edge's seal, a FACIS DCS Merkle head over HTTPS, the carrying marketplace's signed statement. A party without a NEO edge still clears.
fed8ra nets every member's position from the measurements both sides booked. The month on OpenNebula shows what netting through one body saves against settling pair by pair.
The clearing produces positions; an invoice and a payment are separate acts on a bank rail, by the marketplace's billing. The books count in CLU; money is euro. All three are shown apart, always.
The core attests and never decides, owns or settles. fed8ra clears and rules as the members' body, by rules they ratified, and every ruling and every clearing comes back as a new record — the book it settles is never edited.
The federation's 122 members as twins on the rail for a month — 92 deals in a day, one breach, ten rulings, the month cleared. The twin — its live page follows from 15 October.
The month: cotrugli.tech/demo/8ra/month/ — three providers, one customer, nine services, 31 records in four books; the figures above are its pack's (month-pack.json, settlement claims 10). The Guardians' fee and the members' shares are the body's to set; this historical example does not set resource prices.
A new fed8ra pilot demonstration: five members exchange compute, AI, data and network resources. Multilateral netting turns 300 million CLU of gross obligations into €40 million for four providers.
Reciprocal use and a three-member resource cycle cancel before settlement. Each provider keeps its net entitlement.
NEO Chamber Book connects the mandate, agreement, acceptance, allocation and simulator outcomes. Inspect the signed snapshot and recompute the netting.
GnuCOBOL provides the recorded calculation in integer cents with explicit rounding rules — a familiar technical component for banking audiences.
Explore resource netting ▸Inspect the evidence ▸
Separate synthetic scenario. Illustrative conversion: 1 CLU = €0.50. Four simulated settlements; no bank transfer or new NEO attestation. The percentage describes settlement volume, not resource-price savings. The original OpenNebula month above is unchanged.
The pilot explores cooperation between European providers and a record of where services run, who authorises their use and how contributions are settled. Service availability, data-residency commitments and customer assurances would need to be established for each production offering.
122 entries by country from the pilot roster. The roster is a reference map, not a list of onboarded customers or a certification of service readiness. The evidence demonstrations show technical records; production assurance is further work.
Publish and subscribe through kcp's APIExport and APIBinding; the pilot's four real edges live on the Telemach cluster since 29 September; the flow with its 32 booked events. The flow · the pilot, live.
Nine services across three provider clusters, one rule — German data stays in Germany — a host failure survived, the month settled from the records alone. The month.
Its own connective tissue meets fed8ra at the seam: a DCS Merkle head (ADR-16) over HTTPS is a verifiable head the clearing accepts. The door is open; the trail is the next round.
Every marketplace and initiative of the federation enters with the modules it accepts — its catalog in a future portal, its orders on its own door, its measurements in the clearing.