# critlab documentation

> What critlab is, how it is built, and where to start — as a user or as the team running it.

Source: https://critlab.app/docs

critlab is a feedback platform for prototypes built with AI coding agents. You publish a prototype — a zip, a folder, a single HTML file, or a staging URL — and share a link. Reviewers click any element and leave a pinned, threaded comment; no account needed. Each comment carries a screenshot, the element's selectors and the browser environment, and your coding agent reads all of it over MCP and ships the fix.

The cloud service and the self-hosted edition are one codebase. Everything in these docs applies to both, except where a page says otherwise.

## Where to start

| If you want to… | Read |
| --- | --- |
| Use critlab: publish, share, comment, connect an agent | [Getting started](/docs/getting-started) |
| Publish a React, Angular, Vue or other framework project | [What you can publish](/docs/what-you-can-publish) |
| Understand what you would be running | [Architecture and trust boundaries](/docs/self-hosting/architecture) |
| Try it on one machine | [Evaluate with Docker Compose](/docs/self-hosting/evaluation) |
| Run it in production | [Requirements and sizing](/docs/self-hosting/requirements), then [Production install with Helm](/docs/self-hosting/helm) |
| Look up an environment variable | [Configuration reference](/docs/self-hosting/configuration) |
| Connect your identity provider | [Single sign-on](/docs/enterprise/sso) and [Directory sync](/docs/enterprise/scim) |
| Review the security model | [Security overview](/docs/enterprise/security) |

## What a self-hosted install is

Three small Node.js services and three stateful dependencies:

- **web** — the Next.js app: dashboard, viewer, API, sign-in, SAML and SCIM.
- **sandbox** — serves uploaded prototype files from a separate, cookieless origin. Every prototype version gets its own origin.
- **realtime** — a WebSocket service for presence, cursors, follow mode and live comment updates.
- **Postgres**, **Redis** and any **S3-compatible object store** (SeaweedFS is bundled for self-hosted installs).

Optional: an SMTP relay for sign-in codes, a SAML or OIDC identity provider, and a local speech-to-text binary for voice comments.

## Editions

A self-hosted install runs without a licence key. Uploading, sharing, commenting, voice notes, presence and the agent round-trip all work. A licence key from Supermode unlocks the Team and Enterprise features — SAML SSO, SCIM, audit export, your own bucket per workspace, custom share domains, integrations and members-only access. See [Licence](/docs/self-hosting/license).

> **Enterprise features are on request**
>
> Self-hosted licences and Enterprise plans are issued by Supermode, the company behind critlab. Contact us for a key, a trial, or help planning an install.

## Docs for agents

Every page is also available as plain Markdown: add `.md` to the URL, for example [/docs/self-hosting/helm.md](/docs/self-hosting/helm.md). An index of all pages for language models lives at [/docs/llms.txt](/docs/llms.txt).