Save draft
Record the change without altering runtime state.
PRODUCT EXPERIENCEProduct experience is coming soon.
The public Lattice.Hub Console experience environment is being prepared.
Pole control plane
AI Native service governance.One control plane.
An AI Native control plane for services and Agents. Discovery, configuration, governance, and capability catalogs share one versioned release model.
Governance flowTwo user paths, two release versions, one Agent Service.
View full architectureUser A reaches stable BLUE while User B experiences GREEN; 80/20 is illustrative. The Gateway applies differentiated limits before identity auth, Secret, mirroring, mocks, and failover protect model calls.
01 / Console
Control-plane state, visibly real.
Screens below are from a local Lattice.Hub Console: metrics, governance, discovery, configuration, and AI capability catalogs share one control-plane view.
Platform MetricsControl-plane components and API metrics
Real Console UI evidence · local environment data is not described as production telemetry.
02 / Release
Change is not a save—it is a version.
Keep client habits; change how the plane is controlled. Protocol compatibility, domain modeling, and release semantics stay distinct.
Create version
Configuration becomes an immutable release snapshot; governance rules keep version history.
Controlled release
Promote the confirmed version through canary or full rollout.
Runtime consume
Rust SDK, Thin SDK, Pole Sidecar, and Gateway read or carry the same governance view.
03 / CAPABILITY MAP
Six resource types, one control-plane language.
Capability boundaries stay distinct while sharing runtime environment and identity context; configuration and governance further share versioned release semantics. Operators can trace a change back to its scope and runtime state.
Runtime environment
Namespace means environment—not tenant. Dev, staging, and production isolate release state for the same logical resource.
Service discovery
Unify multi-protocol registration, discovery, heartbeats, and instance views without forcing a single client protocol.
Configuration center
Separate “what is being edited” from “what runtime is using” through edit, version, release, and rollback.
Service governance
Nine governance rule types share scope, version, and release semantics instead of isolated policy silos.
Identity and permissions
Management-plane resource authorization and data-plane service identity answer “who may change” and “who is calling.”
AI capability catalog
MCP and A2A Registry register tools, Agent Cards, skills, and capability metadata for discovery.
04 / Topics
Three surfaces to go deeper.
Governance release, Agent change boundaries, and layered product relationships—each topic page expands without repeating this model.
01 / SERVICE GOVERNANCE
Service governance
Nine governance rule types form deterministic runtime policy through scope, versioning, canary release, and rollback.
Explore service governance02 / HUMAN-GATED CHANGEPole Agent
Within signed-in user permissions, read context, generate update proposals for existing configuration, and save edit-state drafts only after human confirmation.
Learn about Pole Agent03 / WHY POLEProduct comparison
Separate protocol compatibility, peer control planes, full Mesh, and data planes to choose the right replacement or composition path.
Compare product relationshipsGet started