01
Login flow
Validates sign-in with MFA, SSO, and session establishment.
Managed status pages for scenario checks
Turn scenario checks into public status signals
Guardus helps teams monitor what matters and communicate status to customers without operating the underlying infrastructure.
1{2 "service": "Payments",3 "status": "operational",4 "updated_at": "2026-05-29T00:15:30Z",5 "scenarios": [6 {7 "name": "Checkout flow",8 "status": "operational"9 }10 ]11}
From checks to clear customer communication
Guardus turns scenario checks into public status pages with customer-ready updates, so your team can stay focused on building.
Scenario checks
Validate the journeys and dependencies users rely on, then publish only the signal customers need.
See all check typesSynthetic
02
Checkout flow
Runs end-to-end checkout across payment methods.
03
Webhook delivery
Verifies outbound webhooks are delivered and acknowledged.
04
API dependency chain
Checks upstream APIs your service depends on.
05
TLS / Domain
Monitors certificate validity, expiry, and domain resolution.
Console later
Same checks, cleaner ownership.
Public status stays simple. Operator context, run history, alert routing, and team controls belong in the future Console.
Condition engine
Define readable YAML conditions that trigger on status, content, response time, headers, and custom signals.
View docsMulti-step conditions
Time windows and thresholds
Per-step or overall results
Noise reduction built in
1name: Checkout flow healthy2type: scenario3entity: suites/checkout4conditions:5 all:6 - step: "4. Checkout"7 ok:8 status: [200, 201]9 response_time_ms:10 p95: "< 1500"11 error_rate:12 rate: "< 1%"13 - step: "5. Webhook"14 ok:15 delivered: true
Supports
- status, headers, body
- JSONPath assertions
- regex and content checks
- latency p50, p95, p99
- error rate and budgets
- multi-step all/any logic
Suites and transaction flows
Model real user journeys as suites. Each step depends on the previous step and shares context.
Learn more1. Login
200
180 ms
2. Browse
200
210 ms
3. Add to cart
200
240 ms
4. Checkout
500
1.82 s
5. Webhook
Pending
waiting
Context and cookies carried forward
Assertions at each step or end-to-end
Fail fast or continue on failure
Public and internal signals
Share clear status with users while keeping sensitive details private.
Explore integrationsPublic status page
Web / App operationalok
API operationalok
Checkout degradedwatch
Auth operationalok
Status badges
All systems operationalok
Checkout degradedok
Response time 412 mswatch
Uptime and metrics
Last 30 days stableok
Latency budget watchedok
Prometheus readywatch
Integrations
PagerDuty incidentsok
Slack updatesok
Datadog eventswatch
Custom webhooksok
A managed platform so your team can focus on building.
Guardus is planned as the hosted Console for teams that want scenario templates, shared status ownership, and incident workflows without operating monitoring infrastructure.
Globally distributed monitoring
Built-in incident and maintenance flows
Console-ready RBAC, audit logs, and SSO roadmap
Join the managed waitlist
Be first to get early access to the Guardus Console, private beta, and launch updates.
Static preview only. The live waitlist backend will be connected with Console.
Questions engineers ask first
How is Guardus different from a normal status page?
The status page is an output. The source of truth is active scenario checks that validate workflows, dependencies, and conditions.
Is the managed Console available now?
Not yet. This draft routes interest to the managed waitlist while the Console surface is planned separately.
Can internal details stay private?
Yes. The product model separates public status signals from protected operator details and future Console collaboration.