Product overview
Lattice Hub brings environments, service discovery, traffic governance, configuration, identity, AI registries, and observability into one control plane.
Lattice Hub is a cloud-native control plane for services and agents. It gives platform teams one versioned resource model for service discovery, configuration delivery, traffic policies, authorization, and operational visibility. MCP servers and A2A agents enter the same management boundary without turning the control plane into an application traffic proxy.
Use this page to understand the product boundary before moving into concepts, architecture, component guides, best practices, and reports.
The operating model
- A namespace defines an environment and release boundary.
- Teams register services, instances, configuration, governance rules, MCP servers, and A2A agent cards.
- Console and API workflows create drafts and immutable releases.
- SDKs, controllers, Pole Sidecar, protocol adapters, and agents consume the appropriate published view.
- History, events, statistics, and OpenTelemetry expose what changed and how the platform behaves.
Capability map
| Area | What Lattice Hub provides | Learn more |
|---|---|---|
| Environments | Namespace-scoped services, configuration, policies, and releases. | Features |
| Discovery | HTTP, gRPC, xDS, Nacos, Apollo, and Eureka-compatible entry points. | API and protocols |
| Governance | Routing, lanes, rate limiting, circuit breaking, detection, lossless lifecycle, mirroring, Mock, and call authorization. | Governance releases |
| Configuration | Drafts, versions, progressive rollout, rollback, and long-poll delivery. | Configuration rollout |
| AI Native | MCP Registry, A2A Agent Registry, and the human-gated Pole Agent workspace. | AI Registry and Pole Agent |
| Operations | Platform history, discovery events, statistics, and OTLP export. | Observability pipeline |
Main components
| Component | Responsibility |
|---|---|
| Control Plane | Owns APIs, embedded Console, Limiter runtime modes, domain services, caches, storage, governance releases, and registry resources. |
| Rust SDK | Offers a proxyless integration path for Rust services. |
| Thin SDK | Multi-language Sidecar Session / TargetService cores (Go, Java, Python, Node.js, C++, C#) for local Pole Sidecar. |
| Kubernetes Controller | Synchronizes Kubernetes resources and coordinates runtime injection. |
| Pole Sidecar | Provides a Pingora-based local data-plane skeleton for HTTP and gRPC traffic. |
| Specification | Defines shared governance and protobuf contracts across components. |
Recommended reading path
Start with features and integration options. Operators can continue with server installation and using the Console. Runtime and platform engineers should then read the architecture, governance, authorization, cache, AI, and observability principle pages.