01
Create a read-only credential
Create the credential in Better Stack with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
Read-only checks on Better Stack confirm monitoring is actually in place: the token connects, monitors are configured, and coverage doesn't silently go dark.
4 read-only checks, run on a schedule. Each failure becomes a finding linked to a control — every check is listed, none are “coming soon”.
Confirms the API token authenticates via GET /api/v2/monitors (HTTP 200).
token-connectivity
Fails if the Better Stack team has no monitors, so nothing is being watched. Walks the full monitor list via GET /api/v2/monitors (page-number pagination).
monitors-configured
Fails if the team has no monitors, or if every monitor is paused. Walks the monitor list via GET /api/v2/monitors and counts monitors whose `attributes.paused_at` is null (active).
monitors-active
Fails if the Better Stack team has no on-call calendars, so alerts would have no one to route to. Walks the on-call list via GET /api/v2/on-calls (page-number pagination).
on-call-configured
Bring your current platform's test list — we'll map it against these checks, gap by gap
Setup is minutes, not a migration project — and every step stays on your side
Create the credential in Better Stack with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
The first run starts right after connecting, then repeats on a schedule. Results are timestamped, so your evidence has a history, not a snapshot.
Passing results attach as evidence to the controls they support; failures become findings you triage. When the audit comes, the proof is already connected.
Open any page for its full check register.
You create and scope every credential yourself, and you can revoke it at any time. Checks only read; results and evidence are stored in Switzerland and stay exportable.
Yes. The checks authenticate with a credential you create and scope yourself, and only ever read configuration. devguard holds no write access to Better Stack and remediates nothing silently.
A failed check becomes a finding linked to the control it supports, with the evidence attached. You decide the treatment — nothing pages your engineers and nothing is auto-remediated.
Checks run from Swiss infrastructure, and results and evidence are stored in Switzerland. Everything is exportable — your evidence stays yours.
20 minutes on how you run certification today. Bring your current test or control list and we'll map it against these checks — honestly, gap by gap.