Features
Understand Lattice Hub through environments, discovery, governance, configuration, identity, AI registries, and platform operations.
Lattice Hub is not a collection of unrelated APIs. Services, instances, configuration, governance rules, permissions, and AI capability records become versioned control-plane resources that different runtimes can consume.
For shared vocabulary (Namespace, Active Release, MCP/A2A boundaries), start with Concepts and terminology.
Product capabilities
| Capability | Product boundary | Learn more |
|---|---|---|
| Service discovery | Namespaces, services, instances, health, and revisions. | Control Plane |
| Environments | Namespace separates dev/staging/prod content and releases. | Integration options |
| Traffic governance | Nine families activate through releases. | Governance releases |
| Configuration | Publish, rollback, watches; one file can keep multiple active gray releases, and full publish does not end them. | Configuration guide · Progressive delivery |
| Identity and audit | Users, roles, policies, resource mapping, history. | Authorization |
| AI Registry | MCP servers and A2A agents in API/cache/store. | AI Registry |
| Pole Agent | Real LLM/MCP loop; writes stay drafts after confirmation. | AI Registry |
| System config & ops | 63 typed settings; OTel → Collector → GreptimeDB. | Observability |
| Multi-runtime access | Console, SDK, Controller, Sidecar, protocol adapters. | Integration options |
Nine governance families
Route, lane, rate limit, circuit breaker, fault detect, lossless lifecycle, traffic security, traffic mirror, traffic mock—all share edit → Rule Release → active view consumption.
Multi-protocol entry points
Polaris-style HTTP/gRPC, Envoy xDS v3, and Nacos/Apollo/Eureka-compatible adapters share Domain Servers for auth and business semantics. See Specification.
Design principles
- Unify control-plane resources before debating client shapes.
- Separate management objects from runtime views via active releases.
- Cache/event paths serve reads; store remains source of truth.
- AI registries join the resource model; they are not side UIs.
- Agents prepare changes; humans publish.
Explicit non-goals
- Namespace is not multi-tenant/team space.
- A2A Registry is not a task runtime.
- Not every system setting is hot-reloadable.
- Control-plane telemetry is not a full APM product claim.
Introduction
Lattice Hub brings environments, service discovery, traffic governance, configuration, identity, AI registries, and observability into one control plane.
Product comparison
Understand how Lattice Hub relates to Nacos, Apollo, Consul, PolarisMesh, Istio, and Kmesh, including compatibility boundaries and composition options.