Skip to content
critlab
Log inGet started

Self-hosting

Evaluate with Docker Compose

Run critlab on one machine from a source checkout, with Postgres, Redis, SeaweedFS and Caddy in Docker Compose.

The fastest way to try self-hosted critlab is on one machine: Docker Compose runs Postgres, Redis, SeaweedFS and Caddy, and the three critlab services run from a source checkout. Plan on about fifteen minutes.

Prerequisites

  • Docker with Compose (Docker Desktop, Colima or plain Docker Engine).
  • Node.js 22.23.4 or newer (the repository pins the line in .nvmrc) and pnpm 9 through Corepack.
  • Git, and free local ports 3000, 4000, 4001, 4010, 5432, 6379 and 9000.
  • Chrome or another browser that resolves *.localhost to your machine (the sandbox zone defaults to s.localhost:4000).

1. Get the code and configure it

bash
git clone https://github.com/critlab/critlab.git
cd critlab
cp .env.example .env

Two secrets in .env are blank. Generate a value for each and paste it after the = on the matching line, AUTH_SECRET= and SANDBOX_TOKEN_SECRET=:

bash
openssl rand -base64 32
openssl rand -base64 48

.env already points every service at the Compose defaults: Postgres on 5432, Redis on 6379, SeaweedFS's S3 API on 9000 with bucket critlab, the sandbox zone at s.localhost:4000, realtime at ws://localhost:4010. The configuration reference explains every variable.

2. Start the infrastructure

bash
corepack enable
pnpm install
pnpm infra:up

pnpm infra:up runs docker compose up -d with:

ServiceImageHost portNotes
postgrespostgres:16-alpine5432user, password and database are all critlab
redisredis:7-alpine6379
seaweedfschrislusf/seaweedfs:4.479000S3 API only; credentials from infra/seaweedfs/s3.json
seaweedfs-initamazon/aws-cli—creates the critlab bucket, then exits
caddycaddy:2-alpine4000the sandbox origin, proxying to the sandbox service on 4001

3. Migrate and run

bash
pnpm db:migrate
pnpm dev

pnpm dev starts web on http://localhost:3000, the sandbox service on 4001 (reached through Caddy on 4000) and realtime on 4010.

4. Sign in

Open http://localhost:3000/signup and enter any email address. With no mail transport configured, the six-digit code is printed in the pnpm dev output inside a box marked [critlab:mail] console transport. Enter it and you have a workspace.

Upload a build folder, open its share link, press C and click something to leave the first comment.

5. Try the features a licence unlocks

An unlicensed install caps each workspace at the Free plan's limits. To lift the limits for evaluation:

bash
pnpm --filter @critlab/db set-plan <workspace-slug> pro

Team and Enterprise features (SSO, SCIM, audit export, your own bucket, custom domains, integrations, members-only access) need a licence key; ask us for an evaluation key. See Licence.

Stop and reset

bash
pnpm infra:down

Data survives in the Compose volumes critlab_postgres_data and critlab_seaweedfs_data. Remove them with docker volume rm after infra:down to start over.