Product
Roadmap
Phased themes you can reason about with security and platform teams: what strengthens next, without pretending we ship to a fixed month-by-month plan on this page.
Deep dive
The roadmap is organized by outcomes and themes, not by quarter. Shipping order changes with feedback, security findings, and partner integrations. Below expands what each theme means for operators; the homepage strip gives a scannable version of the same phases.
Foundation through planetary mesh
Foundation emphasizes control plane maturity, embeddings, identity baselines, and telemetry so every agent is attributable. Intelligence adds WASM density, prompt-defense depth, and CRDT-style shared state. Security doubles down on kernel-adjacent enforcement (eBPF, Cilium-class networking) and centralized authorization. Advanced scale covers GPU scheduling, confidential computing directions, and autonomy guardrails. Long-horizon items include WAN-native routing research and formal methods where they pay off.
Planetary mesh
The mesh phase spans registry records, gateways, WAN bridges, and discovery metadata (pilox-mesh.json) so cross-Internet agent discovery stays verifiable. DHT-style routing remains explicitly on the roadmap rather than oversold as shipped.
For mesh specifically, treat docs such as mesh-planetary-product and mesh-v1-done as the source of truth for phase language — this page summarizes intent only.
Related documentation
Roadmap
Phased delivery, public by default
Each row is a theme you can reason about: outcomes first, tech tags second. No month-by-month dates: order is directional, not a delivery promise.
- 1
Foundation
Control plane, embeddings, and identity baselines so agents are observable and attributable from day one.
MCPNATSpgvectorA2A SDKSPIFFEOpenTelemetrySigstore - 2
Intelligence
70B models on consumer GPUs, denser runtimes, and safer prompts: VPTQ + TurboQuant for extreme compression, WASM where it fits.
VPTQ 2-bitTurboQuant KVWASM tierPrompt-injection defensesLoro CRDTsOPALanceDBSDK publish - 3
Security
Kernel-adjacent enforcement and centralized authz, fewer blind spots as fleets grow.
Tetragon eBPFCiliumSpiceDBClickHouse tracesFalco - 4
Advanced scale
GPU paths, confidential workloads, and autonomy guardrails without a second orchestrator.
KAI schedulerConfidential computingStigmergySemantic watchdogEvolutionary optimizationApache Iggy - 5
Long horizon
Research-grade reliability and economics: WAN-native routing and hardware trends baked into the model.
libp2p WANCXL poolingCausal inferenceFormal verification - 6
Planetary mesh
Phases P1–P6 are described in the mesh product doc (not a delivery calendar).
Cross-Internet discovery and trust: registries, gateways, and WAN bridges, from Redis bus toward planetary routing.
pilox-mesh.jsonRegistryGatewayWAN busFederationDHT (roadmap)
Full mesh breakdown: see Mesh and docs/MESH_PLANETARY_PRODUCT.md in your distribution.
Enterprise
Work with us on rollouts
Whether you need a commercial license for a hosted offering, onboarding for a multi-team rollout, or a security questionnaire filled against a specific commit. Start with context in the form.
Direct
contact@maxence.design