Skip to main content
Three optional web services ship their own images on GHCR, separate from the core tai image. Run them only if you want to self-host the marketplace registry, its browser UI, or the public website — none is required to run a server.

​
Tags and builds

Each image is built and pushed on every push to main, tagged both :latest and :<sha> (the commit SHA). Pin the :<sha> of a known-good commit rather than :latest. The website image builds only after its own type-check and build pass, so a tree that fails them never publishes.
These images are linux/amd64 only — unlike the multi-arch core tai image — and follow their repository’s visibility on GHCR. A private repository’s image needs a registry login to pull.

​
Run one

Each image reads its own configuration; consult the service repository for the environment it expects and the port it binds. The marketplace registry service backs the marketplace install flow — a server points at it to browse and install plugins.

​
See also

  • Marketplace — what the registry serves and how a server uses it.
  • Quickstart — the core stack these sit beside.