Editions & images
Community (:latest) vs Kubernetes (:k8s) images, and the optional Web UI image.
Eddytor ships as prebuilt public images - no source, no build. Two editions
of the server/engine image are published to ghcr.io/nordalf, plus a separate
image for the optional Web UI.
The two editions
| Edition | Tag | Use it for |
|---|---|---|
| Community | :latest | Docker Compose / single host. Server and engine talk over direct TCP. |
| Kubernetes | :k8s | The Helm chart. Built for DNS-based engine discovery, so the server can fan out across engine replicas. |
They are the same Eddytor - the difference is how the server finds engines: direct TCP for a single host, DNS discovery for a scaled-out cluster.
Good to know
:latest if you run Docker Compose, :k8s if
you install the Helm chart. The chart
defaults to the :k8s images automatically.The Web UI image
Eddytor is API-first - the server is REST + gRPC + MCP, not a UI. An
optional browser UI ships as a separate image, ghcr.io/nordalf/eddytor-ce-ui,
enabled as a Compose profile or a Helm option. It runs on its own origin and
proxies to the server. It tracks its own release cadence, independent of the
server/engine version. See Deploy the optional Web UI.
Versioning & upgrades
Versions are pinned per image (EDDYTOR_VERSION / image.tag, and separately
EDDYTOR_UI_VERSION / ui.image.tag for the Web UI); the upgrade procedure is in
Upgrades & migrations.