Self-hosting is first-class.
Danbyte is built to be run by you. You get 100% of the features, on your own hardware, with no phone-home and no expiring license — and it runs fully air-gapped if that's your world. Stand it up on a single server in an afternoon.
The whole platform, nothing withheld.
Self-hosting Danbyte is not a limited edition. It is the product.
100% of the features
Every capability on this site is in the open-source release. No enterprise tier, nothing paywalled.
Air-gapped capable
Runs fully offline with no external calls, so it fits classified and isolated networks.
Your data, your hardware
The database lives on your server. Nothing leaves your network unless you send it.
No phone-home, no telemetry
No accounts, no license server, no usage beacons.
No license expiry
Run the version you have for as long as you like. Upgrade on your schedule.
Plugin-friendly
A codebase built to extend, with hooks to add your own models and behavior.
A boring, dependable stack you already know how to run.
Danbyte runs as a few small processes anywhere Django runs; the production processes install as user-level systemd units.
- Python 3.13
- Managed with uv in a project venv.
- Django 5.2 LTS
- Served by gunicorn (WSGI) and daphne (WebSockets).
- PostgreSQL 17-18
- The single source of truth for all your data.
- Redis + RQ
- Background job queues and scheduled work.
From bare server to running instance.
A start-to-finish install on a fresh Ubuntu or Debian box. The full guide generates your secrets in the browser and walks each step; this is the shape of it.
# 1. System packages (Ubuntu/Debian)sudo apt install -y postgresql redis-server git curlcurl -LsSf https://astral.sh/uv/install.sh | sh # 2. Get the code + Python 3.13 depsgit clone …/danbyte ~/danbyte && cd ~/danbyteuv venv --python 3.13 .venvVIRTUAL_ENV=$PWD/.venv uv pip install -r requirements.txt # 3. Migrate + first-run bootstrap.venv/bin/python manage.py migrate.venv/bin/python manage.py bootstrap # 4. Build the frontend, then run the systemd unitsmake frontend-build && make collectstaticYou own the operations.
Self-hosting means you hold the levers — and the responsibility. Here's what that covers.
- 01
Updates & upgrades
Pull a new release, run migrations, restart the units. On your schedule.
- 02
Backups
Back up PostgreSQL (and your media) with whatever you already use.
- 03
Infra & processes
Provision Postgres, Redis and the gunicorn / daphne / worker processes, sized to your load.
- 04
TLS & access
Terminate TLS at your reverse proxy and wire up LDAP / MFA to taste.
- 05
Monitoring
Keep an eye on the units and the queues; Danbyte's own checks help.
- 06
Documented throughout
The docs cover install, the nginx proxy, settings and day-two operations.
Would rather not run it yourself?
Danbyte Cloud runs the exact same open-source software as a private instance for you — same features, no lock-in, export anytime. You're paying for operations, not software.