Self-hosted
Run Sekeye inside your perimeter.
Same binary as our SaaS. Docker Compose for ≤ 2,000 endpoints, Helm beyond that. Air-gap capable with an Ed25519 offline license.
Why buyers choose self-hosted.
Data residency
Snapshots, findings, and catalog imports stay inside your country and your VPC.
Regulated procurement
Fits CERT-In 180-day log retention in India, NIS2 data sovereignty in the EU, and NESA / NCA rules in the Gulf.
Air-gap capable
Ed25519 offline license. Signed catalog bundles you import on your schedule. No outbound calls required.
Same binary as SaaS
One codebase. Never a fork. SaaS is us operating the self-hosted distribution, multi-tenant.
Install
Four steps to a running fleet.
Step 01
Provision a VM
2 vCPU / 4 GB is enough for 1,000 endpoints. Ubuntu 24.04 LTS. Postgres and Redis colocated for smaller fleets.
Step 02
Install the compose file
curl the compose.yaml, set your admin email, drop your license file, and bring the stack up.
Step 03
Enrol Drig
The console prints an enrolment token. Deploy the Drig binary via MDM, Ansible, or a signed installer package.
Step 04
Ingest signed catalog bundles
Air-gapped installs pull signed catalog bundles from a mirror on your schedule. Signature verification is mandatory.
Sizing
What a self-hosted fleet costs to run.
A single VM handles most mid-market deployments. Postgres and Redis colocate. Backups are pg_dump.
| Endpoints | Backend | Ingress | Storage / mo |
|---|---|---|---|
| ≤ 500 | 1 vCPU / 2 GB | Compose | ~ 2 GB |
| ≤ 2,000 | 2 vCPU / 4 GB | Compose | ~ 8 GB |
| ≤ 10,000 | 4 vCPU / 8 GB | Helm | ~ 40 GB |
| > 10,000 | Horizontal Helm | Helm | Design review |