RealmMesh V1 Roadmap

At InterRealm, our mission is ambitious: to build a decentralized operating layer where intelligent agents can collaborate, route messages, and form loops across organizations and networks.

The internet gave us protocols for moving packets and documents. What's missing is a secure, policy-driven layer for autonomous agents to interact across trust boundaries. That's where RealmMesh comes in.

InterRealm vs. RealmMesh

Think of InterRealm as the global fabric — a connected set of distributed, decentralized RealmMesh clusters. Any organization can run its own RealmMesh, and through policies and cryptographic contracts, those clusters can extend their mesh outward, connecting to others. Some may even choose to act as backbone routers, helping carry large-scale message traffic across the InterRealm.

RealmMesh, on the other hand, is the open source Kubernetes-native platform we're building today. It provides:

• Intra-cluster routing: AI agents organized into "realms" communicate securely using policy-based routing.
• Sidecar-driven enforcement: Every message is checked by a routing proxy sidecar, ensuring policies are enforced consistently.
• Extensibility to bridges: Special "Bridge Realms" can connect one cluster's RealmMesh to another, forming the first steps toward a global InterRealm.
• Auditability: Every route leaves a trace, enabling transparency and accountability.

In short: RealmMesh is the substrate. InterRealm is the network it enables.

RealmMesh V1: What We're Shipping

RealmMesh V1 is the first production milestone. Its focus is proving the routing model works within a single cluster.

• Policy-Based Routing: Messages between realms travel recursively up through parent realms, with each hop enforcing policy.
• Routing Sidecar: A lightweight proxy (written in Go) runs alongside every realm container. It intercepts traffic, checks headers, looks up policies in Postgres (cached in Redis), and forwards or blocks.
• Bridge Ready: While V1 focuses on intra-cluster, the architecture is designed to support Bridge Realms for secure cross-cluster connections.
• Observability: An audit sidecar (using OpenTelemetry) captures every route decision for later analysis in Jaeger/Grafana.

Beyond the Service Mesh

Service meshes like Istio solved the challenge of managing microservice-to-microservice traffic inside a single organization's cluster. But they were never designed for what's coming next: autonomous agents, distributed across multiple clusters and organizations, needing to collaborate securely.

RealmMesh builds on that foundation and extends it:

• It enforces policies at the realm level, not just the service level.
• It introduces the concept of recursive routing through parent realms, creating a governance structure for how traffic flows.
• And it prepares for the future of cross-cluster collaboration, where Bridge Realms connect different organizations into the InterRealm.

Where the service mesh was about reliability inside your datacenter, RealmMesh is about trust, policy, and collaboration across datacenters and domains.

Roadmap Beyond V1

RealmMesh V1 is just the beginning:

• Phase 2 – Cross-Cluster Bridges: Bridge Realms establish secure contracts between clusters, authenticated with JWT and mTLS.
• Phase 3 – Backbone Participation: Clusters may choose to act as backbone routers, incentivized to carry global message traffic.
• Phase 4 – Multi-Agent Loops: Eventually, RealmMesh will support agent loops across clusters, enabling true distributed AI workflows.

Conclusion

The future of the InterRealm starts here.

With RealmMesh V1, we're proving the model: policy-driven routing, security at every hop, and the foundation for connecting realms across organizational boundaries. InterRealm is the vision — a decentralized, globally connected fabric. RealmMesh is the open source engine that makes it possible.

If you want to be part of this journey, join us as we build the next layer of the internet: a message bus for intelligent agents across realms.