Deploy G8KEPR in your VPC

G8KEPR runs where your traffic and data already live. You can start on our hosted platform and move into your own VPC later — the software is the same in both places.

Where G8KEPR can run

• ▸Community — hosted only. No install: generate an API key and use the dashboard on g8kepr.com.
• ▸Starter and Pro — hosted, or self-hosted in your VPC.
• ▸Enterprise — VPC, on-prem, or fully air-gapped.

What gets deployed

Self-hosted G8KEPR is the same stack we run:

• ▸Backend — FastAPI (Python)
• ▸Frontend — Next.js 14 / React
• ▸Database — PostgreSQL 15
• ▸Cache & sessions — Redis 7
• ▸Edge — Nginx, TLS 1.3 (TLS 1.2 disabled)
• ▸Observability — Prometheus + Grafana, Jaeger tracing, Loki logs, Sentry errors

It ships as Docker Compose (dev, production, monitoring, and HA configurations) and as a Kubernetes / Helm bundle (Deployment, HorizontalPodAutoscaler, PodDisruptionBudget, NetworkPolicy, ExternalSecrets, and PrometheusRule manifests).

Network isolation

Containers are split across four isolated Docker networks so the data tier is never reachable from the internet:

• ▸database-net — PostgreSQL + Redis, marked internal (no outbound route)
• ▸app-net — backend, frontend, tracing
• ▸public-net — Nginx and the frontend edge
• ▸monitoring-net — metrics and dashboards

All containers run non-root with no-new-privileges and hard CPU / memory limits.

Bringing up production

# 1. Fill in real secrets
cp .env.example .env && $EDITOR .env

# 2. Bootstrap TLS certificates before Nginx starts
./scripts/init-letsencrypt.sh

# 3. Start the stack
docker compose -f docker-compose.production.yml up -d

High availability (optional)

For deployments that need it, the HA configuration adds PostgreSQL failover (Patroni + etcd + HAProxy), Redis Cluster with Sentinel, multiple uvicorn workers (2 x vCPU + 1), and zero-downtime blue-green releases with automatic TLS renewal.

Sensor licensing in your VPC

Self-hosted installs carry a cryptographically signed license that sets your max_sensors. The install wizard rejects sensors over your cap, and tampering invalidates the license.

Tenant isolation is enforced in the application layer (every query is scoped to your organization); database row-level security sits underneath as defense-in-depth.