Lattice Hub Docs

Protocol ports

Default Control Plane listen ports; compatibility ports listen only when enabled.

Ports follow pole-control-plane/deploy/conf/pole-apiserver.yaml and Console config. A port does not listen unless its apiserver plugin is enabled.

Default port matrix

Plugin / entryDefault portProtocolPurpose
Console (pole-server)8080HTTPEmbedded admin UI and Console gateway
api-http8090HTTPControl-plane REST / OpenAPI-style API
service-grpc8091gRPCService registration, discovery, governance views
config-grpc8093gRPCConfiguration read/write and discovery
xds-v315010gRPC (xDS)Envoy xDS v3 control plane
service-eureka8761HTTPEureka-compatible discovery
service-nacos8848 (HTTP); gRPC defaults to 9848HTTP / gRPCNacos-compatible discovery/config
service-apollo8890HTTPApollo-compatible config

Post-install checks: Server installation. Integration choices: Integration options.

Enable and disable

  • Each protocol entry is a separate apiserver plugin; comment out or remove its name block to stop listening.
  • api-http can further gate surfaces via api.admin / api.console / api.client / api.aimcp / api.aia2a.
  • In production, tighten exposure: keep admin / Console API on private networks; expose only gRPC or compatibility ports to clients as needed.

Quick local probes

# Console
curl -I http://127.0.0.1:8080

# HTTP API (control plane must be up; unauthenticated calls may return business codes but still prove the port listens)
curl -sS -o /dev/null -w '%{http_code}\n' http://127.0.0.1:8090/auth/v1/system

Probe gRPC / xDS with grpcurl or an SDK; validate compatibility ports with their native clients.

On this page