Self-hosted deployment

1. Minimum requirements

Requires 64-bit Linux with Docker Engine 24+ and either a domain with TLS or internal DNS. Disk grows with attachments only — text conversations are negligible.

2. License

Request an evaluation via the self-hosted form. After review you receive a license bound to your domain, your capacity tier and an expiration (for eval) or your paid term. The license is a signed file loaded at first startup.

3. Deploy with Docker

# 1. Place your license file and env at /opt/onsites
# 2. Set your domain and timezone in .env
# 3. Start:
docker compose -f /opt/onsites/compose.yaml up -d
# 4. Confirm health:
curl -fI https://support.yourcompany.com/health

The stack ships as a set of images with no external dependencies. After startup, create the admin account, connect channels and invite users exactly as in the cloud setup.

4. AI endpoints

• Bring your own API key: configure an OpenAI-compatible endpoint in Settings → AI.
• Internal model: point Harness/Copilot at a model served inside your network.
• Air-gapped: the software runs fully disconnected; enable AI only when an endpoint is available.

Credit accounting is the same as cloud (see billing); in self-hosted mode you provide the AI (your own API key, an internal or air-gapped model) and the storage on your own disks — no credit packs or storage packs are sold on this track.

5. Backups

docker exec onsites-backup /backup.sh   # writes an encrypted archive
docker exec onsites-backup /restore.sh recent.tar.gz

Run the backup script daily via cron. The archive contains settings, conversations, documents and contact data.

6. Upgrades

docker compose pull
docker compose up -d

Upgrades are backward compatible within the supported major version. Updates are part of your plan — we test and release upgrade paths for your review before applying.

7. Localization

The interface ships in English today. All mainstream languages are on the roadmap and will be selectable per user as they land.