§ Federated Mesh Architecture

Federation Dashboard

Connected federated meshes with handshake status, health, capabilities, and routing distribution. Federated routing selects the best mesh based on capability, region, cost, and routing weight.

Syncing ecosystem state…
5
Federated meshes
3
Verified meshes
28
Active routes
27753
Total routed

Federated routing test

Connected meshes

Test Mesh
us-west · mesh_dcb4fe31-e7ac-48bc-92ee-4b0a43653f79 · 0 active · 0 total
unknown Pending
Cost/1K: $0
Weight: 1
SLA: standard
Max nodes: 100
llama-3-8b
EU-Sovereign Mesh
eu-west · mesh_b4f8f926-b334-41bc-b1ae-bee0e97c17db · 11 active · 8233 total
healthy Active
Cost/1K: $0.0025
Weight: 1.8
SLA: premium
Max nodes: 3000
llama-3-8bmistral-7b
APAC Compute Mesh
ap-south · mesh_8d7654fb-a5cf-4084-8d9f-34a78719fcb3 · 5 active · 4100 total
degraded Active
Cost/1K: $0.0015
Weight: 1.2
SLA: standard
Max nodes: 2000
llama-3-8bqwen-7b
LATAM Edge Mesh
sa-east · mesh_48deafe0-1fa7-4d73-980d-9380c4d098a2 · 0 active · 0 total
unknown Pending
Cost/1K: $0.001
Weight: 0.8
SLA: basic
Max nodes: 500
llama-3-8b
MeshInfer US-East
us-east · mesh_fa142137-dfa7-454d-87f4-a0f89bca6406 · 12 active · 15420 total
healthy Active
Cost/1K: $0.002
Weight: 2
SLA: enterprise
Max nodes: 5000
llama-3-8bllama-3-70bmistral-7b*

Federation handshake protocol

Three-step federation handshake
1. Register: A mesh operator submits mesh_name, region, public_key, and capabilities. The mesh enters 'pending' status.
2. Verify: The federation verifies the public key format and activates the mesh to 'verified'.
3. Sync: The mesh syncs its latest capabilities, cost, and routing weight, becoming 'active'.
registerMeshSubmit mesh identity + public key + capabilities → pending status
verifyMeshValidate public key → verified status (key must be ≥32 chars)
syncCapabilitiesUpdate capabilities, cost, routing weight → active status
routeInferenceAcrossMeshesScore all active meshes by region, cost, weight, health → select best