Mesh
Network
From Redis-class integrity on the LAN to signed federation and planetary discovery paths — without a second orchestrator in your head.
Deep dive
The mesh story is deliberately incremental: a fast local bus for co-located agents, cryptographic federation between trusted instances, then registry and gateway paths for cross-Internet discovery. You should not have to throw away your mental model when you move from a single cluster to multiple regions.
Local mesh (Redis bus v1)
On the LAN, agents coordinate through a Redis-backed pub/sub layer with HMAC integrity on messages. That gives low-latency fan-out without pretending every packet is globally trusted. Where NATS JetStream is enabled in your stack, WAN-oriented messaging can extend the same patterns.
Federation
Trusted Pilox instances exchange signed manifests and JWTs (Ed25519) so peers authenticate each other and anti-replay considerations stay explicit. Federation is not “open P2P”; it is pairwise or small-group trust you configure, review, and rotate.
Planetary path
Longer term, registries, gateways, and WAN bridges align on discovery documents such as /.well-known/pilox-mesh.json so automation and humans can reason about routes the same way they do about TLS or OIDC metadata. Phases P1–P6 in the mesh product documentation describe capabilities without pretending they are a dated delivery calendar.
- Twelve illustrative POPs on the map are schematic: they snap to land dots in the asset and do not represent live cable geography.
- Chords and animated beads are stylistic; real routing follows your configured topology and policies.
Related documentation
Global mesh
Edge to core topology
Pilox connects agents across regions the way operators think about infrastructure: a local bus, federated trust, then registries and gateways at the edge. The map is illustrative topology — not live telemetry or cable geography.
Federation & registry paths — phased rollout
Local mesh
Redis bus v1 on your cluster: fast pub/sub with HMAC integrity for co-located agents.
Federation
Trusted peers exchange signed manifests and JWT (Ed25519) so instances trust each other, not the whole internet.
Planetary path
Registry, gateway, and WAN bridges discover routes via /.well-known/pilox-mesh.json (phased rollout, same mental model).
- Mesh overview (in-tree: docs/MESH_PLANETARY_PRODUCT.md)
