Security
Last updated:
1. Overview
This page describes the security controls built into Supercheck and how we run Supercheck Cloud. Supercheck Cloud is coming soon; signups are not open yet. Sections marked “Cloud” describe how the hosted service is set up for launch. Self-hosted operators run their own infrastructure and control those parts themselves.
2. Encryption
- Secrets: secret project variables, notification provider settings, AI SRE connector credentials, and heartbeat monitor tokens are encrypted with AES-GCM authenticated encryption before they are written to the database.
- In transit: traffic to Supercheck Cloud is served over HTTPS/TLS.
3. Access control
- Roles: organization roles (owner, admin) and project roles (admin, editor, viewer) limit what each member can see and change.
- Sign-in: email and password, or OAuth sign-in with GitHub or Google.
4. Audit log
Supercheck records an audit log of security-relevant actions. By default, audit entries are kept for 12 months, and after 30 days email addresses in them are replaced with a keyed hash.
5. Isolated test runs (Cloud)
On Supercheck Cloud, test runs execute in short-lived pods sandboxed with gVisor, and a network policy restricts their outbound traffic.
6. Backups (Cloud)
Supercheck Cloud keeps backups in off-host storage, separate from the servers that run the service.
7. Infrastructure providers (Cloud)
Supercheck Cloud relies on providers including:
- Hetzner: compute servers
- Cloudflare: DNS and object storage
- PlanetScale: managed PostgreSQL database
- GitHub and Google: OAuth sign-in, when you choose it
- AI model providers: AI-assisted features you use
- Payment processor: subscription billing
See the Privacy Policy for the data shared with AI, authentication, payment, and notification providers.
8. Self-hosting
If your data must stay in your own environment, you can self-host Supercheck. Self-hosted operators choose where their data lives and which integrations are enabled.
9. Reporting a vulnerability
Please report vulnerabilities privately through GitHub private vulnerability reporting or by email to [email protected] with the subject “Security report”. Do not open a public issue. Our full policy is in SECURITY.md.