Observe the service
Choose the endpoint, DNS record, certificate, port, or heartbeat that represents something users depend on.
Monitor websites, APIs, DNS, TLS certificates and background jobs from one workspace. See the check behind every status, then act on the evidence.
Overview
Workspace health and the checks behind each status.
Monitors
Checks today
Success · 24h
Median response
How it works
Monitoring is a sequence of small signals. Sraraa keeps each observation attached to the status it supports, so an alert starts with evidence instead of guesswork.
Choose the endpoint, DNS record, certificate, port, or heartbeat that represents something users depend on.
Each state keeps its latest result, check time, response time and failure detail beside it.
Use incidents, maintenance windows and supported alerts; publish only the monitors you intend to share.
No uptime percentage is invented; each figure links to a stated window and definition.
No invented uptime score and no mystery dashboards. Each screen answers a concrete operational question and keeps the evidence next to the claim.
A monitor state sits beside the latest result, its timestamp, and measured response time. Missing data is shown as unknown, never green.
Implemented behaviour, not a mockTrack active and resolved incidents with maintenance windows, updates and postmortems instead of a single changing colour.
Implemented behaviour, not a mockOwner, admin, member and viewer roles, page grants and per-monitor access. Admins manage; members see only what they were given.
Implemented behaviour, not a mockPublish selected monitors, current incidents and scheduled maintenance. Branding and custom domains are plan features.
Implemented behaviour, not a mockEmail down/recovery, supported webhooks and browser push. Test delivery before an outage.
Implemented behaviour, not a mockScoped API tokens, CLI and a Terraform provider for infrastructure-as-code workflows.
Implemented behaviour, not a mockCapabilities
Start with the signal you need and add depth as the service and team grow. Plan-dependent checks say so before you configure them.
Status codes, redirects, response time and supported content assertions for public endpoints.
Verify record answers and certificate validity, with expiry warnings before renewal becomes urgent.
Catch silent background jobs by requiring a check-in after successful completion.
Email down and recovery notifications, supported webhooks and browser push.
Publish selected monitors, incidents and maintenance; private monitors stay private.
Roles, page grants, monitor-level scope and an audit trail for workspace changes.
Latest result, response time, failure detail and maintenance state sit with the monitor.
Scoped API tokens, CLI, Terraform and agent/push checks for private networks on supported plans.
Principles
This is not a claim about a named competitor. It is the standard Sraraa holds itself to when it labels a service healthy or broken.
What is actually being checked?
A status colour with no visible evidence.
Latest result, response time and check timestamp sit beside the state.
Can a short outage hide between checks?
An uptime number with no stated window or interval.
Windows, intervals and failure thresholds are shown with the measurement.
Who can see private monitors?
One shared login with no monitor-level scope.
Roles, page grants and per-monitor access are enforced by the API.
What appears on the public status page?
Every monitor, or an unexplained green banner.
Only monitors explicitly made public, with incident and maintenance context.
Why did an alert fire?
A notification with no check detail.
Down/recovery alerts link back to the workspace and the failed check.
Pricing
Every plan is enforced by the same catalogue the dashboard uses. Start free; upgrade only when you need more monitors, history or team access.
Try the platform and monitor a small project.
$0/month
Individuals and small projects.
$9.99/month
Developers and growing products.
$15/month
Multiple services and operational teams.
$30/month
Teams managing production infrastructure.
$50/month
Compare every capability and limit · Prices in USD, billed monthly or yearly.
Here's everything you need to know before getting started.
Contact usHTTP(S) and keyword checks, DNS records, TLS certificates, domain expiry, TCP/ICMP/UDP checks, cron heartbeats, API assertions, page speed, synthetic flows, Docker/host agents and push agents, subject to your plan.
No. A check samples a specific endpoint from the configured probe path. It cannot represent every location, browser, dependency or user journey, and the dashboard shows missing or stale data as unknown.
Plan checkout and subscription management happen on the web dashboard. Subscription checkout is web-only.
Email is available on every plan. Webhooks, browser push and other routing depend on the workspace plan and deployment configuration.
Yes. Public status pages include only monitors explicitly marked public. Private monitors, workspace members and internal incident causes stay out of the public payload.
Use the contact form or the support page. Include the monitor name and approximate check time, but never send passwords, API tokens or workspace secrets.
Learn
Set up workspaces, monitors, alerting, incidents and status pages against the shipped product.
OpenStep-by-step paths for website, API, DNS and TLS monitoring with expected outcomes.
OpenPractical explanations of uptime, latency, DNS, certificates and scheduled work.
OpenStart with a signal
Create a free workspace, add your first monitor, and verify the alert path before you need it.