Deployment

Classifyre ships in two distributions, with the same features in both:

Docker — one image that runs on macOS, Windows, or Linux, with the database and scan workers inside it.
Kubernetes with Helm — for shared instances, production, high availability, and horizontal scaling.

A namespace export moves work from one to the other, so this is not a decision you are locked into.

Option 01 · Docker

Run it on your machine

One image · amd64 + arm64

PostgreSQL, the UI and the scan workers are all inside the image, so there is nothing to provision — and a bind-mounted folder is a source like any other.

docker run -d --name classifyre \  -p 3000:3000 \the only port it serves  --shm-size=1g \Postgres needs it; the default is too small  -v classifyre-pgdata:/var/lib/postgresql/data \your data  -v classifyre-data:/var/lib/classifyre \scan logs + credential key  -v classifyre-uv-cache:/cache/uv \survives upgrades  classifyre/all-in-one:0.5.6

Docker install guide →

Option 02 · Kubernetes

Or run it on a cluster

Helm, OCI-native · no repo add

The chart deploys the web UI, API, worker, and the ephemeral scan Jobs. PostgreSQL can be embedded for a trial or external for production.

helm install classifyre \
  oci://registry-1.docker.io/classifyre/classifyre-core \
  --namespace classifyre --create-namespace \
  --version 0.5.6

Kubernetes deployment guide →

Docker

The all-in-one image carries the API, the web UI, the Python scan workers, and PostgreSQL, so nothing else has to be provisioned. Bind-mount a directory and it becomes a source like any other.

Read the Docker install guide.

The official Helm chart deploys the web UI, API, background worker, ephemeral CLI scan Jobs, and the required Kubernetes services and RBAC. PostgreSQL may be provided by the chart for development or connected as external infrastructure for production. Object storage is optional.

Read the Kubernetes deployment guide.

Platform components

The supported deployments use the same application components:

Web UI: the user-facing Next.js application.
API and worker: orchestration, state, background queues, and automation.
CLI Jobs: isolated source extraction and detection runs.
PostgreSQL: application state and investigation data.
Object storage: optional logs and uploaded artifacts.