Visca
The Stack/Trust plane

Fabric

Plexus

The fabric layer of the self-hosted stack.

The fabric primitive of the stack, run inside your perimeter. Discovery, mTLS, and routing across every autonomous actor and every resource an actor reaches — rooted in the same Sigil identities, not hardcoded URLs, and never crossing your boundary.

Plexus is a primitive of the Visca stack — it ships with the stack, versions with the stack, and audits with the stack. It is not separately purchasable.

What it is

The role Plexus plays in the stack.

A plexus is the network of nerves and vessels in a living body that carries signals among autonomic systems. Plexus does the same for autonomous-system fabric, entirely within your walls. Every connection is rooted in the same Sigil identities the rest of the stack uses. Every message is authenticated, encrypted, and routed with awareness of actor semantics. Agents find other agents, MCP servers, tools, and robotic actuators by capability descriptor — not by URL. The brittle web of point-to-point coupling that defines autonomous-system estates today gives way to capability-based discovery rooted in one identity model and recorded to one audit trail.

The problem

What goes wrong without it.

Autonomous systems today find their dependencies by hardcoded URL. A bash variable points the agent at an MCP server. A configuration file points the robot at a planner. Mutual authentication is haphazard. The estate becomes a brittle web of point-to-point coupling with no consistent answer to who is reachable, who is calling whom, and whether every connection is authenticated — and traffic leaks across vendor boundaries the security review will never accept.

Capabilities

What Plexus does.

Open and commercial

Built in the open. Run in your tenancy.

Plexus has two surfaces: an open-source reference in Lattice Runtime (MPL 2.0), and a managed delivery as part of the Visca stack on Visca Cloud. Features in the open never move behind the paywall.

Open

Lattice Runtime — open foundation

MPL 2.0 · self-hostable · foundation-track governance

  • ·Plexus wire protocol specification
  • ·Reference agent
  • ·Local control plane
  • ·MCP integration primitives

Commercial

Visca Cloud — managed sovereign delivery

Your tenancy · dedicated · self-managed · air-gapped

  • ·Hosted control plane
  • ·Cross-organization capability federation
  • ·Premium routing policies for compliance and residency
  • ·High-availability control plane
  • ·Traffic analytics

TRUST · same plane

Inside the trust plane with Plexus

Across the stack

Composing with the other planes.

The whole stack. Self-hosted. One ecosystem.

The entire agent stack, inside your own walls.

Models, identity, tools, voice, payments, runtime, and audit — as one integrated ecosystem, self-hosted, sovereign, air-gapped. Nothing stitched from vendors. Nothing leaves your perimeter. Open at the core. No license rug-pulls, ever.