Demo route
Federated training with governance visible in one place.
Keep data where it lives; share only the update. This route walks through the seeded dashboard, round detail, and privacy budget story without hiding the approvals or proof work.
Active collaborators visible on the federation dashboard before the next round starts.
Round history stays visible so operators can compare drift, throughput, and review state.
Remaining privacy budget carried forward from the live privacy-budget editor.
The latest aggregation proof matches and remains attached to the round detail view.
End-to-end walkthrough
The release path the demo follows
Register a node and capture the provider, region, telemetry, and join token.
Approve the participant list before starting a new round.
Collect local model updates while source records stay inside each organization boundary.
Verify the aggregation proof and privacy-budget spend-down on one record.
Generate the audit export and hand the signed bundle to reviewers.
Seeded surface previews
Three previews, one seeded federation state.
Preview 01
Dashboard preview
Preview 02
Round detail preview
Preview 03
Privacy-budget preview
Live preview
Federation round preview
The website demo mirrors the same approvals, update collection, and proof state that the platform round view carries for operators.
Active collaborators visible on the federation dashboard before the next round starts.
Round history stays visible so operators can compare drift, throughput, and review state.
Remaining privacy budget carried forward from the live privacy-budget editor.
Latency: 248ms
Communication cost: 64 MB
Budget remaining: 0.84
No raw-record transfer is required for collaboration. Aggregation proof and participant health stay on the same release record.
Seed-backed scenarios
The kinds of federation stories this release is prepared to tell.
Hospital network coordination
Multiple clinical sites contribute local imaging updates while protected health information stays inside each hospital boundary.
Coordinators see round health, approvals, and proof on one release record.
Fraud signal sharing
Regional risk teams improve a shared model without centralizing transaction histories into a single warehouse.
Security and compliance reviewers can inspect proof before the next learning round starts.
Regional model operations
Country or partner-specific nodes keep local policy boundaries intact while contributing to a shared objective.
Privacy budget spend-down stays understandable for non-cryptographers.