Management decides change
Caller, callee, rule content, and release timing are reviewed by platform engineers; embedded Console is the entry point.
PRODUCT EXPERIENCEProduct experience is coming soon.
The public Lattice.Hub Console experience environment is being prepared.
ORGANIZATION ARCHITECTURE
Many components,one shared governance model.
This page does not dive into Control Plane storage, cache, or event internals. It answers three visitor questions: which components exist, how they connect, and where governance rules ultimately execute.
01 / COMPONENT MAP
Components stay distinct; the control plane stays unified.
Control Plane (embedded Console; Limiter as an optional in-repo process) and Controller connect from management and cluster sides; Rust / Thin SDKs and proxy data planes connect from runtime; Specification gives every component a stable contract.
Solid lines are current management or protocol paths; dashed lines are sync, injection, or integration boundaries still evolving with each component’s scope.
02 / COMPONENT RESPONSIBILITIES
Start with component roles, then internals.
Each component commits only to roles it already owns. Console and Pole Agent are management capabilities inside Control Plane; Observability is platform integration—they are not packaged as separately deployed components.
01Core control plane
Control Plane
Unifies discovery, configuration, governance, permissions, capability catalogs, and multi-protocol entry; embeds Console; Limiter ships in-repo via limiter-server / full modes without entering the business-traffic hot path.
Learn about component02Proxyless clientRust SDK
Lightweight Proxyless access for Rust applications, reusing the organization’s open protocol contracts.
Learn about component03Multi-language Sidecar contract clientThin SDK
Sidecar Session / TargetService v1 contract cores for Go, Java, Python, Node.js, C++, and C# aimed at local Pole Sidecar. Contract cores ship today; end-to-end Sidecar compatibility still evolves by implementation scope.
Learn about component04Cluster integrationKubernetes Controller
Syncs Service, Endpoints, Namespace, and ConfigMap; injects Pole Sidecar, Java Agent, or Envoy per configuration.
Learn about component05Local data planePole Sidecar
Currently a lightweight data-plane skeleton supporting HTTP, HTTP/2, gRPC-h2c forwarding, prefix routing, and round-robin.
Learn about component06Shared contractSpecification
Defines service management, traffic governance, fault tolerance, access control, and MCP protocols with multi-language generation entry points.
Learn about component03 / GOVERNANCE EXECUTION
Rules publish on the control plane; enforcement sits closest to traffic.
Platform engineers confirm scope and publish rules through Control Plane Console or API. The control plane hands consumable governance views to runtimes; SDKs, the Limiter runtime module, or proxy data planes enforce only what they support today.
Control plane delivers views
The control plane provides published, consumable governance views without entering every business request’s synchronous hot path.
Runtime enforces rules
Routing, protection, authorization, and test capabilities are enforced by SDK or proxy data planes within protocol and implementation scope.
04 / RESPONSIBILITY BOUNDARY
Who manages, who distributes, who executes—keep them separate.
This boundary keeps the site honest: protocol compatibility does not mean every runtime fully covers all governance rules, and roadmaps are not written as current capability.
LayerComponentsResponsibility
Management planeControl Plane Console · Pole Agent
Prepare, review, and decide change—does not execute real service requests.
Control planeLattice.Hub · Controller · Limiter module
Owns the unified resource view, connects Kubernetes, and optionally runs Limiter as a separate in-repo process for distributed rate limiting.
Execution planeRust SDK · Thin SDK · Envoy / Gateway
Influence service calls within each component’s supported protocols and capabilities.
Extended data planePole Sidecar
Currently a proxy skeleton; dynamic governance access and more execution capability evolve with implementation progress.