Self-hosting with Docker

Run the full Manifest stack on your own machine. No Node.js required, just Docker. To run Manifest somewhere other than your own machine, see the other self-hosting paths. All three paths end in the same place: a running stack at http://localhost:2099 where you sign up. The first account you create becomes the admin. No demo credentials are pre-seeded.

The bundled compose file binds port 2099 to 127.0.0.1 only, so the dashboard is reachable on the host machine but not over the LAN. See Exposing on the LAN to change this.

Installation

Quick install (recommended)
Docker Compose
Docker Run (BYO PostgreSQL)

One command. The installer downloads the compose file into ~/manifest, generates a secret, and brings up the stack. First boot pulls the app image and Postgres, so give it up to a couple of minutes.

bash <(curl -sSL https://raw.githubusercontent.com/mnfst/manifest/main/docker/install.sh)

Prefer to review the script before running it?

curl -sSLO https://raw.githubusercontent.com/mnfst/manifest/main/docker/install.sh
less install.sh
bash install.sh

Useful flags: --dir <path> to install elsewhere, --dry-run to preview, --yes to skip the confirmation prompt.When the installer finishes, open http://localhost:2099 and sign up for an account. Then head to the Routing page to add an LLM provider (OpenAI, Anthropic, Gemini, etc.) with your API key.

Same underlying flow as the install script, but you drive it yourself so you can edit the config before booting the stack.

Download the compose file and the env template

curl -O https://raw.githubusercontent.com/mnfst/manifest/main/docker/docker-compose.yml
curl -O https://raw.githubusercontent.com/mnfst/manifest/main/docker/.env.example
cp .env.example .env

Set a real BETTER_AUTH_SECRET

Open .env in your editor and set BETTER_AUTH_SECRET to a random string. You can generate one with:

openssl rand -hex 32

Optional: to use a stronger database password, set both POSTGRES_PASSWORD and DATABASE_URL in .env — they must agree, and any special characters in the password need to be percent-encoded in the URL.

Start the stack

docker compose up -d

Give it up to a couple of minutes on a cold pull — you can watch startup with docker compose logs -f manifest.

Create your admin account

Go to http://localhost:2099 and sign up. The first account you create becomes the admin.

Connect a provider

Open the Routing page and add an LLM provider (OpenAI, Anthropic, Gemini, etc.) with your API key.

Before exposing this instance beyond localhost, double-check that BETTER_AUTH_SECRET is a real secret (not the placeholder), and if you enable email verification, set BETTER_AUTH_URL to a reachable public URL so the verification links resolve.

If you already have a PostgreSQL instance, replace user, pass, and host with your actual database credentials:

docker run -d \
  -p 2099:2099 \
  -e DATABASE_URL=postgresql://user:pass@host:5432/manifest \
  -e BETTER_AUTH_SECRET=$(openssl rand -hex 32) \
  -e BETTER_AUTH_URL=http://localhost:2099 \
  manifestdotbuild/manifest

Windows (PowerShell)

$secret = -join ((48..57 + 97..122) | Get-Random -Count 64 | ForEach-Object { [char]$_ })

docker run -d `
  -p 2099:2099 `
  -e DATABASE_URL=postgresql://user:pass@host:5432/manifest `
  -e BETTER_AUTH_SECRET=$secret `
  -e BETTER_AUTH_URL=http://localhost:2099 `
  manifestdotbuild/manifest

Windows (CMD)

Generate a 64-character hex secret with any tool you trust, then:

docker run -d ^
  -p 2099:2099 ^
  -e DATABASE_URL=postgresql://user:pass@host:5432/manifest ^
  -e BETTER_AUTH_SECRET=<your-64-char-secret> ^
  -e BETTER_AUTH_URL=http://localhost:2099 ^
  manifestdotbuild/manifest

Verify

After connecting a provider, send a test request and watch it land in the dashboard. Grab your Manifest API key from the dashboard (it starts with mnfst_) and run:

curl -X POST http://localhost:2099/v1/chat/completions \
  -H "Authorization: Bearer mnfst_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{"model": "auto", "messages": [{"role": "user", "content": "Hello"}]}'

If the response comes back with That doesn't look like a Manifest key, you’re still using the placeholder — replace mnfst_YOUR_KEY_HERE with the real key from the dashboard.

Verifying the image signature

Published images are signed with cosign keyless signing (Sigstore). Verify before pulling:

cosign verify manifestdotbuild/manifest:<version> \
  --certificate-identity-regexp="^https://github.com/mnfst/manifest/" \
  --certificate-oidc-issuer="https://token.actions.githubusercontent.com"

Custom port

If port 2099 is taken, change both the mapping and BETTER_AUTH_URL:

docker run -d \
  -p 8080:2099 \
  -e BETTER_AUTH_URL=http://localhost:8080 \
  ...

Or in docker-compose.yml:

ports:
  - '127.0.0.1:8080:2099'

…and in .env:

BETTER_AUTH_URL=http://localhost:8080

If you see an “Invalid origin” error on the login page, BETTER_AUTH_URL doesn’t match the URL you’re accessing the dashboard on. The host matters as much as the port.

Upgrading from a pre-2099 install? Your existing stack keeps running on port 3001 with no changes — the backend’s own fallback is still 3001, so the new image works against your old compose file. If you want to refresh your compose file but stay on the legacy port (to avoid reconfiguring OAuth callbacks, reverse proxies, or bookmarks), set PORT=3001 in .env and the bundled compose file will honour it for both the host binding and the internal listener.

Exposing on the LAN

By default the compose file binds port 2099 to 127.0.0.1 only. The dashboard is reachable from the host but not from other machines on the network. To expose it on the LAN:

Change the port binding

Edit docker-compose.yml and change the ports line from "127.0.0.1:2099:2099" to "2099:2099".

Set BETTER_AUTH_URL

In .env, set BETTER_AUTH_URL to the host you’ll reach the dashboard on, e.g. http://192.168.1.20:2099 or https://manifest.mydomain.com. This must match the URL in the browser or Better Auth will reject the login with “Invalid origin”.

Apply

docker compose up -d

Image tags

Every release is published with the following tags:

Tag	Example	Description
`major.minor.patch`	`5.46.0`	Fully pinned
`major.minor`	`5.46`	Latest patch within a minor
`major`	`5`	Latest minor+patch within a major
`latest`	—	Latest stable release
`sha-<short>`	—	Exact commit for rollback

Images are built for both linux/amd64 and linux/arm64.

Upgrading

Manifest ships a new image on every release. To upgrade an existing compose install:

docker compose pull
docker compose up -d

Database migrations run automatically on boot, no manual steps. Your data in the pgdata volume is preserved across upgrades. Pin to a specific major version (e.g. manifestdotbuild/manifest:5) in docker-compose.yml if you want control over when major upgrades happen.

Backup and persistence

All state lives in the pgdata named volume mounted at /var/lib/postgresql/data in the postgres service. Nothing else in the Manifest container is stateful. Back up (from the host, with the stack running):

docker compose exec -T postgres pg_dump -U manifest manifest > manifest-backup-$(date +%F).sql

Restore into a fresh stack:

docker compose up -d postgres
cat manifest-backup.sql | docker compose exec -T postgres psql -U manifest manifest
docker compose up -d

To list or remove the volume manually:

docker volume ls | grep pgdata
docker compose down -v    # destroys all data

Environment variables

Core

Variable	Required	Default	Description
`DATABASE_URL`	Yes	—	PostgreSQL connection string
`BETTER_AUTH_SECRET`	Yes	—	Session signing secret (min 32 chars)
`BETTER_AUTH_URL`	No	`http://localhost:2099`	Public URL. Set this when using a custom port
`PORT`	No	`2099`	Internal server port
`NODE_ENV`	No	`production`	Node environment
`SEED_DATA`	No	`false`	Seed demo data on startup

Only the first two are required, and the installer generates both for you, so a default install boots without you setting anything. Everything else is optional: bind address and CORS, rate limits, provider timeouts, email delivery for alerts and password resets, OAuth logins, connection-pool sizing, and Sentry. See Environment variables for the full list with defaults.

Stop and clean up

docker compose down       # Stop services (keeps data)
docker compose down -v    # Stop and delete all data

Data and privacy

Manifest keeps metadata about each request — model, provider, tier, token counts, cost, latency — and never the message bodies. Prompts and completions are not written to the database.

Telemetry

Once a day, each install sends an anonymous aggregate report: version, provider mix, token and cost totals. Never prompts, keys, or anything tied to a user. Set MANIFEST_TELEMETRY_DISABLED=1 in your .env to turn it off. Full field list, what’s never sent, and how to point it at your own endpoint: Data and telemetry.

Docker Hub

The image is available at manifestdotbuild/manifest on Docker Hub.

Getting Started

Self-hosting

Features

Providers

Reference

Self-hosting with Docker

Installation

Verify

Verifying the image signature

Custom port

Exposing on the LAN

Image tags

Upgrading

Backup and persistence

Environment variables

Stop and clean up

Data and privacy

Telemetry

Docker Hub

​Installation

​Verify

​Verifying the image signature

​Custom port

​Exposing on the LAN

​Image tags

​Upgrading

​Backup and persistence

​Environment variables

​Stop and clean up

​Data and privacy

​Telemetry

​Docker Hub

Installation

Verify

Verifying the image signature

Custom port

Exposing on the LAN

Image tags

Upgrading

Backup and persistence

Environment variables

Stop and clean up

Data and privacy

Telemetry

Docker Hub