Self-host with Korvu Core

Korvu Core is the open-source review engine that powers Korvu Cloud. You can run it yourself if you'd rather keep diff traffic on your own infrastructure, or use it as a hybrid worker that the Cloud control plane dispatches to.

Two ways to self-host

Standalone. Run Korvu Core on your own VPS or Kubernetes cluster, point your GitHub or GitLab webhooks at it, and supply your own LLM key. No Korvu Cloud account required.

Hybrid. Keep using Korvu Cloud for the UI, policies, billing, and observability — but run a Core worker inside your network. Cloud dispatches review jobs to your worker over an authenticated long-poll channel. Diff content never leaves your perimeter.

Hybrid is Enterprise-only Standalone is free. The hybrid worker requires an Enterprise plan, since Cloud has to maintain a per-customer dispatch tenant. See pricing.

Run with Docker

The fastest way to try Core is the published image. You need a Postgres database, a Redis instance, and an LLM key.

docker run --rm -it \
  -e DATABASE_URL=postgres://... \
  -e REDIS_URL=redis://... \
  -e LLM_API_KEY=sk-... \
  -e GITHUB_APP_ID=... \
  -e GITHUB_APP_PRIVATE_KEY="$(cat key.pem)" \
  -p 8080:8080 \
  ghcr.io/rsych/korvu-core:latest

Once it's up, point your GitHub App webhook at https://<your-host>/webhooks/github and open a PR.

Run on Coolify or a VPS

Korvu Core ships a docker-compose.yml and is tested on Coolify. Clone the repo, copy .env.example, fill in secrets, and run docker compose up. Full guide in the Core repo.

What you give up vs. Cloud

Self-hosting Core gets you the review engine. You're responsible for:

• Hosting Postgres, Redis, and the worker itself
• Webhook secret rotation and TLS termination
• Backups and uptime
• Multi-tenant identity and SSO (Core is single-tenant by design)
• Billing and metering (Core has no billing layer)

If you don't want to operate that stack, Korvu Cloud will handle it for you — it's pre-GA and on a waitlist.