SELF-HOSTED SERVER
Install the Tazmu server
Run the server your bots live on, on your own Mac or Linux machine, with Docker. Updates are new images. Your bots, chats, settings and engine logins stay on a Docker volume.
- macOSDocker Desktop
- LinuxDocker Engine with Compose v2
- WindowsComing soon
Before you start
- Docker with Compose v2.
docker compose versionshould print a version. - A Tazmu subscription or trial.
- A server credential. Sign in at accounts.tazmu.xyz/billing and create one under Servers. It is shown once and lasts 90 days.
1. Download it and read it
The installer is a short shell script. Read it before you run it.
curl -fsSLO https://tazmu.xyz/install.sh
less install.shCheck it against the published checksums:
curl -fsSLO https://tazmu.xyz/SHA256SUMS
shasum -a 256 -c SHA256SUMS --ignore-missing| File | SHA-256 |
|---|---|
| install.sh | af4c66a658f8b92deb3372eff083539f08004aed0945732c05661c71aecc0075 |
| update.sh | 3579fd8a66dc058944cb58597002c69cb776c66995ecd5e35ded06e1ab1030da |
| computer.sh | 9a1230fdf3d85a21068c75464e6980d8a304384bcbcddb6d03aa4cef42d4cded |
2. Run it
sh install.shIt asks how you will reach the server:
- The included Caddy serves HTTPS. For a server with a domain pointing at it and ports 80 and 443 free. Caddy gets the certificate from Let’s Encrypt.
- Your own reverse proxy. For a machine that already runs nginx, Traefik, Caddy, a Cloudflare Tunnel or Pangolin. You give the host name your proxy serves.
- Only this machine. The server answers on
http://localhost.
Without a domain, the server listens on a port on 127.0.0.1. The installer offers the first free one of 8080, 8090, 8180, 8280 and 18080, and you can type another.
To install without questions, for example from a script, set the answers as variables. With a domain pointing at the server:
TAZMU_DOMAIN=tazmu.example.com sh install.shBehind an HTTPS reverse proxy you already run on the same machine, with the host name it serves and a free port:
TAZMU_PUBLIC_HOST=tazmu.example.com TAZMU_PORT=8090 sh install.shPoint the proxy at http://127.0.0.1:8090, or whichever port the installer printed, and have it pass the original Host header. Requests for that host name then reach the server as HTTPS, so a browser on https://tazmu.example.com can pair and save changes. Without TAZMU_PUBLIC_HOST, a browser behind your proxy can pair, but the server refuses every change it makes as cross-origin.
Already installed without it? In ~/tazmu, delete compose.yaml and Caddyfile, then run the installer again with the settings you used before, TAZMU_PUBLIC_HOST, and TAZMU_VERSION set to the version in .env. The data volume and .env.secrets stay as they are.
It asks for your server credential, then:
- logs Docker in to
registry.tazmu.xyz, where the server images are, - writes
compose.yaml,Caddyfile,.envandupdate.shinto~/tazmu, - creates the data volume, starts the server and waits until it is healthy,
- installs the Codex and Claude Code command-line tools into the data volume,
- prints a one-time setup link.
It does not use sudo and changes nothing outside that folder and Docker.
Open the setup link to finish in your browser. It creates your account on the server, signs the server in to your Tazmu subscription, and signs in to Codex or Claude. The link works once, for 7 days. Lost it? In ~/tazmu, run docker compose exec omb node dist-server/tazmu.js account setup-link for a new one.
3. Update
The app tells you when a new version is out. Then run:
cd ~/tazmu && sh update.shIt backs the data volume up to ~/tazmu/backups, pulls the new image, restarts the server and prints its license status. If the server has to be signed in to your Tazmu account, it prints how. sh update.sh 0.1.107 moves to a specific version. The installer and the updater need 0.1.106 or later: older images cannot find the engine CLIs.
4. Roll back
Moving to an older version is not an undo. The older build would run on data the newer one has already changed, and nothing checks that it can read it. update.sh warns you and asks before it does that. A full rollback switches the image back, then restores the backup update.sh took before the upgrade.
First switch back. It backs up the current data, as backups/tazmu-<newer version>-<time>.tgz, and prints the name of the backup to restore:
cd ~/tazmu && sh update.sh 0.1.106Then restore that backup. Each one is named after the version that made it, so going back to 0.1.106 restores the newest backups/tazmu-0.1.106-<time>.tgz. These commands stop the server, save the current data to backups/before-restore.tgz, empty the volume, restore into it and start the server again. The && chain stops at the first failure, so the volume is never emptied without a fresh copy.
docker compose stop omb caddy
docker compose run --rm --no-deps -T omb \
node /app/scripts/backup-data.mjs backup /data - > backups/before-restore.tgz &&
docker compose run --rm --no-deps -T --user root \
--cap-add DAC_OVERRIDE --cap-add FOWNER omb find /data -mindepth 1 -delete &&
docker compose run --rm --no-deps -T omb \
node /app/scripts/backup-data.mjs restore - /data < backups/tazmu-0.1.106-YYYYMMDDTHHMMSSZ.tgz &&
docker compose up -dBackups leave out the engine CLIs, so install them again. Their logins are in the backup.
docker compose exec omb npm install -g @openai/codex @anthropic-ai/claude-codeChats and settings changed after the upgrade are gone after the restore. They stay in the backup the first step made.
Windows
A Windows installer is coming soon. Until then, Windows users can run the server on a Linux machine or VPS and connect from the Mac app, the iPhone app or a browser.