Enterprise
DPPAN Enterprise is the same binary as the public build, run with a different configuration: a self-hosted master orchestrator, authentication enabled, and clusters isolated to your network. Nothing leaves your infrastructure.
What you get
- Self-hosted master — your own orchestrator. The public DHT is disabled (
public_dht = false) andinclavate.iois never contacted. Data never leaves your network. - Join-token auth — only devices presenting the correct per-cluster token can register.
- User API tokens — control who can submit inference requests.
- Cluster isolation — clusters are scoped to your master by default; federate explicitly when you want cross-site routing.
- Audit log — metadata per inference call (no prompt content, no generated text), written as JSONL.
- Admin API — manage the device allowlist, rotate tokens, revoke access.
- Air-gap compatible — runs fully offline behind your firewall.
Deployment models
| Model | Setup | Suitable for |
|---|---|---|
| Cloud master | Master on your AWS / GCP / Azure VM | Multi-site, remote workers |
| On-prem master | Master behind the corporate firewall | Strict data residency, air-gap |
| LAN-only | dppan host --standalone + mDNS | Pilots, conference-room demos |
Verifiable data residency
With public_dht = false, no traffic goes to inclavate.io — the master acts as the sole bootstrap/relay peer. This is verifiable by inspecting the config and running dppan doctor.
For a deployment walkthrough or a pilot, reach out at [email protected].