> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tai42.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Web stacks

> Run the optional marketplace and website images.

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.

| Image                                 | Repository                                                            | Serves                           |
| ------------------------------------- | --------------------------------------------------------------------- | -------------------------------- |
| `ghcr.io/tai42ai/tai-marketplace`     | [tai-marketplace](https://github.com/tai42ai/tai-marketplace)         | the marketplace registry service |
| `ghcr.io/tai42ai/tai-marketplace-web` | [tai-marketplace-web](https://github.com/tai42ai/tai-marketplace-web) | the marketplace browser UI       |
| `ghcr.io/tai42ai/tai-website`         | [tai-website](https://github.com/tai42ai/tai-website)                 | the public marketing site        |

## 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.

<Note>
  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.
</Note>

## Run one

```bash theme={null}
docker run --rm -p 8080:80 ghcr.io/tai42ai/tai-website:latest
```

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](/concepts/marketplace) install flow — a server points at
it to browse and install plugins.

## See also

* [Marketplace](/marketplace) — what the registry serves and how a server uses it.
* [Quickstart](/self-hosted/quickstart) — the core stack these sit beside.