Self-hosted & air-gapped
Your infrastructure, your rules
Eidon was built to run entirely inside your own network — no phone-home telemetry, no cloud dependency, and a licensing model designed from the ground up to work with zero network access at all.
Deployment
Deploy however your environment requires
Docker Compose
One docker-compose.yml stands up the API, frontend, Postgres and Redis together — the fastest path for a single-server deployment.
Kubernetes / Helm
A versioned, packaged Helm chart for a real cluster deployment — network policies, F5/AS3 integration for BIG-IP-fronted environments, and an external-database option for pointing at infrastructure you already run.
Bring your own cloud
If "self-hosted" means your own cloud account rather than on-prem hardware, the same container images and chart deploy there too — you're never locked into a specific hosting model.
Licensing
Offline activation, no network required either way
Every Eidon deployment starts with the full suite unlocked for evaluation. For production use, a license is a small signed token — generated entirely offline by whoever holds the private signing key, no call home, no activation server, no network involved in minting or applying it.
The token is cryptographically signed (Ed25519 or RSA) and verified locally against a public key you configure — it carries which modules and features are unlocked, seat count, and an expiry date, applied in Settings by an admin in seconds.
Why this matters for air-gapped environments
- No license server to reach — the token itself is the whole proof
- Nothing in the product needs outbound internet access to function
- AI features are entirely opt-in and per-workspace — bring your own provider, or don't configure any
- Renewing or changing entitlements is a new token, applied the same way — no reinstall
Data
Your data stays where you put it
A self-hosted deployment's data lives entirely in the Postgres instance you run — there's no external service it's copied to, synced with, or otherwise dependent on. Secrets (SSO/LDAP credentials, connector API keys, TOTP seeds) are encrypted at rest with a key you control. Backups, retention and audit logging are all part of the standard deployment, not a separate add-on.
Talk to us about your environment
Air-gapped, regulated, or just prefer to run your own infrastructure — tell us what you're working with and we'll help you plan the deployment.