Your telemetry, under your control.
Observability data is some of the most sensitive you hold — it describes exactly how your systems work. backwork is built so it stays yours, isolated, and honest.
Self-hosted by default
backwork runs on your own infrastructure. Logs, metrics and traces are stored on your disk and never traverse a third party — the strongest data-residency guarantee there is.
Per-tenant isolation, to the byte
Every organization's data is scoped by an enforced org_id: injected into log stream labels, metric series and trace spans at ingest, and filtered server-side on every query. A tenant can never read another's telemetry.
Encryption & hashing at rest
Alert-channel secrets are sealed with AES-256-GCM (HKDF-derived keys). Ingest tokens are stored only as SHA-256 hashes. Passwords use argon2id with a server-side pepper.
Hardened sessions
Signed, HttpOnly, Secure cookies with server-side revocation via a token version — logging out or changing a password invalidates captured cookies everywhere. Per-IP and per-account rate limiting throttles brute force.
Safe by construction
Same-origin (CSRF) checks on every state-changing action, SSRF guards that block alert webhooks from reaching internal or metadata endpoints, and path-only redirects that can't be hijacked.
Honest by design
A missing or failed data source reads as “no data,” never “healthy.” Outages in the telemetry path are surfaced, not masked — so the dashboard is trustworthy precisely when you need it most.
Found something?
We take security reports seriously. Responsible disclosures are reviewed promptly — please don't open a public issue for vulnerabilities.
Report a vulnerabilityReady to own your observability? Start free →