Documentation

Source-of-truth docs, references, plans, and product material across Harbor surfaces.

Docs / Product Surfaces
Product Surfaces

Ports And Services

These ports and services reflect the current Harbor stack. Some public/static surfaces are served as generated sites rather than long-running app servers, so the serving port can vary by environment.

portsservicesnode
Source: PORTS_AND_SERVICES.md

PORTS_AND_SERVICES.md

These ports and services reflect the current Harbor stack. Some public/static surfaces are served as generated sites rather than long-running app servers, so the serving port can vary by environment.

Public / cloud stack

Website

  • Service: apps/website
  • Port: static site, commonly served on 11824 in local dev
  • Purpose: public Harbor website, install path, member/account entry

Cloud API

  • Service: apps/cloud-api
  • Port: 11825
  • Purpose: account verification, licensing, enrollment, entitlements, support metadata

Dock / Hub

  • Service: apps/hub
  • Port: 11826
  • Purpose: hosted catalog for safe Harbor integration metadata, manifest fetch, and future HarborHub-style discovery

Cloud Admin

  • Service: apps/cloud-admin
  • Port: static site, host-defined in local or internal deployment
  • Purpose: internal admin/support tooling for accounts, licenses, enrollments, and notifications

Docs

  • Service: apps/docs-site
  • Port: static site, host-defined in local or public deployment
  • Purpose: Harbor documentation frontend

Cloud Postgres

  • Service: postgres
  • Port: 5432
  • Purpose: user/account/license/premium metadata

Cloud Redis

  • Service: redis
  • Port: 6379
  • Purpose: cache, queue, session, transient state

Harbor Node stack

Harbor UI

  • Service: apps/harbor-ui
  • Port: 11820
  • Purpose: local product UI

Harbor Node API

  • Service: apps/harbor-node-api
  • Port: 11821
  • Purpose: local action API for scripts, agents, SDKs, and the UI

Harbor Node Internal / Auth Helper

  • Service: reserved
  • Port: 11822
  • Purpose: optional internal helper, auth bridge, sidecar, or future local broker separation

Harbor Node database

  • Preferred for MVP: SQLite file
  • Optional later: Postgres if needed

API access modes to support

Harbor Node API should eventually support:

  • curl
  • PowerShell Invoke-WebRequest / Invoke-RestMethod
  • Python requests
  • TypeScript SDK
  • future local client service / desktop helper

Port naming note

Port numbers are not sacred. The product naming and trust model matter more than the first chosen numbers.