Install · 1.3.1 · Apache-2.0

Run it on machines you already operate.

OpsKnight is self-hosted. Compose is the shortest path. Helm is the production path. After boot, open port 3000 and create the first admin on /setup. Full steps live in the docs — this page is the checklist.

You need

  • Docker Engine 20+ and Compose 2+, or a Kubernetes cluster
  • PostgreSQL 14+ (Compose can start this for you)
  • NEXTAUTH_SECRET and ENCRYPTION_KEY
  • A stable HTTPS base URL in production (auth callbacks)

OpsKnight requires PostgreSQL, NEXTAUTH_SECRET, and ENCRYPTION_KEY. The bundled Docker Compose configuration starts both PostgreSQL and OpsKnight automatically.

Docker Compose

Clone the repo, copy env.example to .env, set the secrets, then start.

compose

git clone https://github.com/opsknight-labs/OpsKnight.git
cd OpsKnight
cp env.example .env
# set DATABASE_URL, NEXTAUTH_URL, NEXTAUTH_SECRET, ENCRYPTION_KEY
docker compose up -d

Generate secrets with openssl rand -base64 32 and openssl rand -hex 32. Then open http://localhost:3000.

Helm

For repeatable Kubernetes installs. Chart source is in the product repo and a dedicated charts repo.

helm

git clone https://github.com/opsknight-labs/OpsKnight.git
cd OpsKnight
helm install opsknight ./helm/opsknight \
  --namespace opsknight \
  --create-namespace

Helm deployment docs

What this is not

There is no OpsKnight Cloud signup. Native voice paging is not in this release. SAML is not in this release (local accounts and OIDC are). After install, the canonical reference is the installation guide.