Supercheck

Open-source testing, monitoring, and AI SRE — as code.

Supercheck brings Playwright test automation, k6 performance testing, uptime and synthetic monitoring, incident investigation, and public status communication into one platform. Use the web application, manage resources from the CLI, and record browser tests with the Supercheck Recorder.

What Supercheck includes

• Test automation: browser, API, database, custom, and k6 performance tests, with AI-assisted creation and failure analysis.
• Monitoring: HTTP, website and SSL, ping, port, and scheduled synthetic browser checks across configured execution locations.
• Investigation: run logs, screenshots, traces, linked artifacts, and read-only AI SRE investigation over Supercheck evidence and configured connectors.
• Communication: alerts through email, Slack, Discord, Telegram, Microsoft Teams, and webhooks, plus public status pages and subscriber notifications.
• Governance: organizations, projects, six RBAC roles, API keys, audit trails, requirements traceability, and coverage snapshots.
• Secure execution: ephemeral Kubernetes Jobs, gVisor isolation, network policies, and resource limits for Playwright and k6 workloads.

Competitive landscape

Supercheck combines capabilities that are commonly split across test automation, synthetic monitoring, load testing, status communication, and incident-investigation products. The comparison below describes each product's primary, natively documented scope; integrations or adjacent products may extend it.

Platform	Primary focus	Pricing	Test automation	Synthetic / uptime	Load testing	Status pages	AI SRE
Supercheck	Unified reliability	Open source	✅	✅	✅	✅	✅
Checkly	Synthetic monitoring & testing	Free + paid	✅	✅	—	✅	Partial
Datadog	Observability & synthetics	Usage-based SaaS	Partial	✅	—	—	Partial
Better Stack	Observability & incident management	Free + paid	—	✅	—	✅	Partial
UptimeRobot	Uptime monitoring	Free + paid	—	✅	—	✅	—
BrowserStack	Browser & device cloud	Capacity-based SaaS	✅	Partial	—	—	Partial
Sauce Labs	Browser & device cloud	Capacity-based SaaS	✅	Partial	—	—	Partial
Cypress Cloud	Cypress orchestration	Free + paid	✅	—	—	—	Partial
Grafana k6	Performance & load testing	Free + usage-based	—	Partial	✅	—	Partial
Azure	Cloud test execution	Usage-based	✅	—	✅	—	—
Statuspage	Status communication	Free + paid	—	—	—	✅	—
Instatus	Status pages & uptime	Free + paid	—	✅	—	✅	Partial
HolmesGPT	AI SRE investigation	Open source	—	Partial	—	—	✅
PagerDuty	Event intelligence & response	Commercial SaaS	—	—	—	—	✅
Resolve AI	AI production ops	Commercial	—	—	—	—	✅

Get started

Self-host Supercheck

Production self-hosting requires a Linux server with Docker Compose v2. Supercheck uses local K3s and gVisor for isolated test execution; macOS, Windows, and WSL2 are not supported deployment targets.

git clone https://github.com/supercheck-io/supercheck.git
cd supercheck/deploy/docker
./init-secrets.sh
sudo bash setup-k3s.sh
KUBECONFIG_FILE=/etc/rancher/k3s/supercheck-worker.kubeconfig docker compose up -d

Open http://localhost:3000, or follow the self-hosting guide to configure HTTPS, optional integrations, backups, and multi-location workers.

Install the CLI

The CLI requires Node.js 20 or later.

npm install -g @supercheck/cli
supercheck init

Create a token under Organization Admin > CLI Tokens, then authenticate:

supercheck login --token sck_live_...
supercheck pull
supercheck diff
supercheck deploy

On-call engineers can also work with AI SRE from the terminal:

supercheck incident list
supercheck sre triage <incident-id>
supercheck sre investigate <incident-id> --live-connectors
supercheck sre ask "Summarize the strongest evidence" --incident <incident-id>

See the CLI guide and command reference for resource management, local execution, and CI/CD usage.

Install the recorder

Record browser interactions and save Playwright tests directly to Supercheck:

• Chrome Web Store
• Microsoft Edge Add-ons
• Source and build instructions
• Recorder documentation

Architecture

flowchart TB
    Users[Users / CI/CD] --> T[Traefik Proxy<br/>SSL / Load Balancer]
    T --> App[Next.js App<br/>UI + API]
    App --> DB[(PostgreSQL<br/>Primary DB)] & Redis[(Redis + BullMQ<br/>Queue + Cache)] & S3[(MinIO<br/>Artifacts)]
    App --> SRE[AI SRE Engine<br/>Read-only investigations]
    SRE -.-> Private[Private Agents<br/>Outbound HTTPS only]

    Redis --> W_EU
    Redis -.->|Internet| W_US
    Redis -.->|Internet| W_APAC

    subgraph PRIMARY["Primary Server"]
        W_EU[Worker EU<br/>NestJS + BullMQ<br/>WORKER_LOCATION=eu-central] --> K3S_EU[K3s + gVisor<br/>Sandboxed Execution]
    end

    subgraph US["US Server"]
        W_US[Worker US<br/>NestJS + BullMQ<br/>WORKER_LOCATION=us-east] --> K3S_US[K3s + gVisor<br/>Sandboxed Execution]
    end

    subgraph APAC["Asia Pacific Server"]
        W_APAC[Worker APAC<br/>NestJS + BullMQ<br/>WORKER_LOCATION=asia-pacific] --> K3S_APAC[K3s + gVisor<br/>Sandboxed Execution]
    end

    style Users fill:#6366f1,stroke:#4338ca,color:#fff
    style T fill:#0ea5e9,stroke:#0369a1,color:#fff
    style App fill:#3b82f6,stroke:#1e40af,color:#fff
    style DB fill:#f59e0b,stroke:#b45309,color:#fff
    style Redis fill:#ef4444,stroke:#b91c1c,color:#fff
    style S3 fill:#8b5cf6,stroke:#6d28d9,color:#fff
    style SRE fill:#0ea5e9,stroke:#0369a1,color:#fff
    style Private fill:#8b5cf6,stroke:#6d28d9,color:#fff
    style W_EU fill:#10b981,stroke:#047857,color:#fff
    style W_US fill:#10b981,stroke:#047857,color:#fff
    style W_APAC fill:#10b981,stroke:#047857,color:#fff
    style K3S_EU fill:#059669,stroke:#047857,color:#fff
    style K3S_US fill:#059669,stroke:#047857,color:#fff
    style K3S_APAC fill:#059669,stroke:#047857,color:#fff
    style PRIMARY fill:none,stroke:#3b82f6,stroke-width:2px
    style US fill:none,stroke:#64748b,stroke-width:2px,stroke-dasharray: 5 5
    style APAC fill:none,stroke:#64748b,stroke-width:2px,stroke-dasharray: 5 5

Loading

The application stores platform data in PostgreSQL, schedules work through Redis and BullMQ, and keeps execution artifacts in S3-compatible storage such as MinIO. Workers consume location-aware queues and run Playwright or k6 workloads as ephemeral Kubernetes Jobs in a restricted execution namespace. Deploy one local worker or add workers for other configured locations.

Repository layout

Path	Purpose	License
app/	Next.js web application and API	AGPL-3.0-only
worker/	NestJS orchestration and execution worker	AGPL-3.0-only
cli/	@supercheck/cli source and documentation	AGPL-3.0-only
recorder/	Browser recorder based on Playwright CRX	Apache-2.0
docs/	Product and deployment documentation	AGPL-3.0-only
deploy/	Docker Compose deployment assets	AGPL-3.0-only

Documentation

• Welcome
• Deployment
• Automate: tests, jobs, and runs
• Monitor
• Investigate with AI SRE
• Communicate: alerts and status pages
• Administration
• CLI
• Recorder

Contributing and security

Contributions are welcome. Before opening a pull request, read CONTRIBUTING.md and follow the Code of Conduct. Governance and release expectations are described in GOVERNANCE.md, and help is listed in SUPPORT.md.

Use the issue chooser for reproducible bugs, documentation fixes, and feature requests, and GitHub Discussions for proposals and questions.

Please report vulnerabilities privately as described in SECURITY.md.

Community integrations

Integration	Description
Azure DevOps	Community-maintained pipeline tasks and dashboard widget

Community integrations are maintained outside the core Supercheck repository. If you have built one, open a Discussion to share it.

License

The Supercheck app, worker, CLI, documentation, and deployment assets are licensed under the GNU Affero General Public License v3.0 only. The recorder remains Apache-2.0; see recorder/LICENSE, recorder/NOTICE, and its retained upstream attribution.

Community