# Deployment
URL: /docs/deployment

Running Tachyon in production with Docker.



## Docker [#docker]

Deploy Tachyon as a single container, with a persistent volume for
`--data-dir`:

```bash
docker run -d \
  --name tachyon \
  -p 8108:8108 \
  -v tachyon-data:/data \
  -e TACHYON_ADMIN_KEY=change-me \
  adikeshri/tachyon
```

Set `TACHYON_ADMIN_KEY` (and optionally `TACHYON_SEARCH_KEY`) for anything
beyond local development — see
[Configuration → Authentication](/docs/configuration#authentication).

## Backups [#backups]

Because all state lives under `--data-dir` (the WAL plus on-disk segments),
back up a Tachyon instance by snapshotting that directory — for example,
snapshotting the volume, or copying it while writes are quiesced.

## Recovery [#recovery]

A restarted instance replays its write-ahead log automatically — see
[Persistence](/docs/persistence) for exactly what that does and doesn't
protect against.

## Orchestration [#orchestration]

Tachyon ships as a single container by design — no Docker Compose file,
Kubernetes manifest, Helm chart, or systemd unit required to run it. Point
your own Compose, Kubernetes, or systemd setup at the image above using the
flags on the [Configuration](/docs/configuration) page; first-party manifests
for common orchestrators are on the [Roadmap](/roadmap).