Uptime monitoring for SaaS teams who promise uptime in their contracts
Your customers pay for a product that is supposed to be there when they need it. UptimePilot watches your app, your API, your background workers and your certificates every 30 seconds from two regions, alerts the right engineer, keeps customers informed on a status page with your domain, and turns the month into an SLA report you can attach to an enterprise renewal.
What downtime costs a SaaS company
For a SaaS product, an outage is rarely a single number. It is support tickets that pile up while the team investigates, a churn risk on the accounts that noticed, a credit owed under an SLA, and a sales call where the prospect asks about reliability. The worst version is the one where a customer tells you first.
- Customers learn about the outage before your team does
- Support is flooded with "is it down?" messages during an incident
- Nobody can say what the uptime was last quarter when a contract asks for it
- A background worker stops and data is quietly late for days
- Certificates on API hosts expire while the main site looks fine
What a SaaS team should monitor
| Layer | Monitor type | What it catches |
|---|---|---|
| Marketing site and login | HTTP with keyword | Errors, slow pages, a login page without the login form |
| App dashboard | HTTP with keyword | A blank app shell after a bad deploy |
| Public API | API checks with JSON assertions | Wrong status codes, missing fields, slow responses |
| Auth and token endpoints | API checks with credentials | Broken sign in for every new session |
| Queue workers and scheduled jobs | Heartbeat | Jobs that stop running or never finish |
| Database and cache hosts | Port | A service that stops accepting connections |
| Every customer facing hostname | SSL and domain | Expiring certificates and domains |
Start with api monitoring on the endpoints your product depends on and cron job monitoring for the workers behind them.
Alerts that reach the engineer on call
A failure in one region triggers an immediate recheck from the other, and only a confirmed failure sends an alert. That keeps a single network hiccup from paging anyone at three in the morning. Alerts go by email, SMS, Slack, Microsoft Teams or webhook, and escalation moves the alert to the next person when the first one does not acknowledge it within the minutes you set.
Maintenance windows silence planned work, so a scheduled migration does not open an incident. Read more on website downtime tracker settings and on how to reduce false alarms in uptime monitoring.
A status page on your own domain
When something breaks, customers want to know that you know. Publish a status page on status.yourdomain.com with your logo and colors, components such as App, API and Webhooks, and incident updates written by your team. Monitors linked to components switch them to an outage as soon as the failure is confirmed, and subscribers get email updates, so support does not have to answer the same question a hundred times.
Team includes 5 status pages with custom domains. Business adds password protected pages for internal tools or enterprise customers with a private page.
Uptime numbers for contracts and renewals
Enterprise customers ask for an uptime commitment and a way to verify it. From Team upward, UptimePilot produces a monthly SLA report as a PDF with the uptime percent, response time percentiles, every incident with its start, end and duration, and the maintenance windows that were excluded. Send it to the account that asks, or attach it to a security questionnaire. See uptime monitoring service reports in detail and 99.9 uptime explained in minutes per month.
Built into how the team ships
- REST API on Business and Enterprise to create monitors and incidents from your deployment pipeline
- Groups of monitors per product, environment or region of your own infrastructure
- Members and roles, so support can read and engineers can change
- Audit log and SSO (SAML) on Enterprise for teams with access reviews
- Members included in the plan, priced per team and not per seat, so adding the whole on-call rotation does not change the bill
Which plan fits a SaaS team
- Starter, $49 a month or $24 a month billed yearly: 50 monitors, 1 minute checks, 10 heartbeats, 1 status page, 3 members, for a founder with a first product
- Team, $99 a month or $49 a month billed yearly: 200 monitors, 30 second checks, 50 heartbeats, 5 status pages with custom domains, 10 members, monthly SLA PDF
- Business, $249 a month or $124 a month billed yearly: 1,000 monitors, 250 heartbeats, 20 password protected status pages, 25 members, REST API
- Enterprise, $599 a month or $299 a month billed yearly: 3,000 monitors, 1,000 heartbeats, 50 status pages, 100 members, SSO (SAML), audit log, invoicing
Compare every limit on uptime monitoring pricing.
01
Can we monitor staging and production separately?
Yes. Put each environment in its own group with its own alert rules, so staging failures go to a channel and production failures page the on-call person.
02
Do status page components update automatically?
Yes. Link monitors to components, and a confirmed failure switches the component to an outage. Your team writes the incident updates.
03
Is the SLA report suitable for enterprise customers?
The monthly SLA PDF shows uptime percent, response time percentiles, incidents with durations and excluded maintenance windows, which is the information enterprise contracts usually ask for. It is included from Team upward.
04
Can we create monitors from our deployment pipeline?
Yes, on Business and Enterprise through the REST API for monitors and incidents.
05
Do we pay for every engineer who receives alerts?
No. Team members are included in the plan up to its limit, from 3 on Starter to 100 on Enterprise.
Know about the outage before your customers write in
Add your app, your API and your workers, publish a status page on your domain and send the first SLA report at the end of the month.