NordStern Docs
Internal Engineering

Ports & Service Mapping

Configuration index of all network ports, container linkages, and host routes.

This section lists the network ports, volumes, and domain configurations of the NordStern platform.


Port Configurations

Service NamePort (Host)Port (Internal)Routing HostnameProtocol
Traefik Edge8080*.localhost / *.nordstern.liveHTTP / TCP
Traefik Admin80908080NoneHTTP
Platform API40004000api.localhost / api.nordstern.liveHTTP / JSON
Founder Console40013000register.localhost / register.nordstern.liveHTTP / HTML
Admin Console40023000admin.localhost / admin.nordstern.liveHTTP / HTML
Control Plane30023002None (Internal only)HTTP / JSON
Aggregator30053005None (Internal only)HTTP / JSON
Database (Postgres)54325432NoneTCP
Secrets Manager45664566NoneHTTP (AWS SDK)

Dynamic Tenant Port Configurations

When the Control Plane provisions an anchor cell, the containers are assigned dynamically within the Docker network. The reverse proxy maps external hostheaders to these containers:

ContainerInternal PortEdge Host Header Routing
anchor-platform-<slug>8080 (public)
8085 (private)
Host("<slug>.anchors.localhost")
business-server-<slug>3000Host("api-<slug>.anchors.localhost")
operator-console-<slug>3001Host("console-<slug>.anchors.localhost")
anchor-client-<slug>3001Host("client-<slug>.anchors.localhost")

Volume Mounts

  • pgdata (Postgres Volume): Persists data for platformdb, controldb, aggregatordb, and all anchordb_<slug> instances.
  • ANCHOR_CONFIG_HOST_ROOT: Bind-mount on the host filesystem mapping generated anchor configuration templates (stellar.toml, anchor-platform.yaml, assets.yaml) into the container stacks.

On this page