One-click deploys
Bunker is one program and one data folder. Pick a button, wait a couple of minutes, open the URL, and create your admin account.
Buttons
Section titled “Buttons”| Where | Keeps your data? | Guide | |
|---|---|---|---|
| Deploy to Azure | A small Ubuntu VM with a managed data disk, a free *.cloudapp.azure.com name and HTTPS |
Yes | Azure VM |
| Deploy to Render | Web service + 5 GB disk (Starter plan or higher) | Yes | Render, Railway, Fly |
| Deploy on Railway | Service + volume at /data |
Yes | Render, Railway, Fly |
fly launch --from https://github.com/kucukkanat/bunker --copy-config |
Fly.io: one machine + volume | Yes | Render, Railway, Fly |
| Deploy to Koyeb | Koyeb | Only after you attach a volume at /data |
|
| DigitalOcean App Platform | App Platform | No, demo only: data resets on every deploy. For real use, a Droplet + the Linux installer | |
| Heroku | Heroku | No, demo only: data resets daily | |
| Google Cloud Run | Cloud Run | No, demo only |
Self-hosting platforms: Coolify (deploy/coolify/docker-compose.yml) and CapRover (one-click template deploy/caprover/bunker.yml).
Commands
Section titled “Commands”# Any Linux server: hardened systemd service, automatic HTTPS for an https URLcurl -fsSL https://raw.githubusercontent.com/kucukkanat/bunker/master/install.sh | sudo BUNKER_URL=https://bunker.example.com sh
# Dockerdocker run -p 8080:8080 -v bunker:/data ghcr.io/kucukkanat/bunkerWindows (PowerShell): irm https://raw.githubusercontent.com/kucukkanat/bunker/master/install.ps1 | iex
More detail: Docker and Compose, Linux installer and systemd.
After you deploy
Section titled “After you deploy”-
Open the URL. Azure shows it under Deployment → Outputs. Render, Railway, Fly and Koyeb show it on the service page.
-
Find the setup code. It’s printed in the logs when Bunker starts for the first time:
┌──────────────────────────────────────────────┐│ Bunker is ready to set up. ││ ││ Open: https://bunker.example.com/setup ││ Code: BKRT-WXQP │└──────────────────────────────────────────────┘- Azure: Outputs → setupCode
- Render: Environment →
BUNKER_SETUP_CODE - Linux installer: printed at the end, and in
/var/lib/bunker/setup-code.txt - Everywhere else: the service logs
Opening
/setupfrom the machine itself (localhost) doesn’t need the code. -
Create your account. Choose Just me or my team, enter your email, name and a password. You’re the admin. Invite people with one-time links.
-
Optional: company sign-in. Connect Entra ID, Google Workspace or OIDC, then turn built-in accounts off if you want.
Health check: GET /healthz (inside the container: bunker healthcheck). Every setting is in the configuration reference.