Uptime monitoring, on-call and status pages for SaaS teams

What SaaS teams need from uptime monitoring

A SaaS product needs monitoring that matches what customers experience: can they reach the app, log in, use the core feature, and find out what is happening when they cannot. Uptime Tracker's Team plan covers each of those layers.

The Team plan includes 50 standard monitors and 50 heartbeat monitors, which is enough to cover production, the key staging checks and the main third-party endpoints of a typical early-stage SaaS. Use projects, up to 10, to separate environments or product lines.

All checks use failure confirmation: two consecutive failures before a monitor is marked down, two successes before it is up. Probe-side errors are never counted against your availability, which matters when you publish uptime numbers to customers. Checks currently run from one probe location, with additional regions planned.

Testing the login and core workflow

The most valuable SaaS monitor is one that logs in and does something real, because that is the failure customers report first. Uptime Tracker's multi-step API workflows, on the Team plan, chain up to 10 HTTP requests and pass extracted values such as an access token between steps.

A typical SaaS workflow:

1. POST test-account credentials, stored as encrypted secrets, to your token endpoint, and extract the token.
2. GET the current user or workspace and assert on a known ID with JSONPath.
3. Call the endpoint behind your main feature, such as listing projects or running a search, and assert that results come back.

Use a dedicated test account with limited permissions and no billing, so the monitor cannot affect real customers. Prefer read-only steps; if a step must create data, delete it in a later step.

Team includes 50,000 workflow request units per month. A three-step workflow every 5 minutes uses about 3 × 288 × 30 = 25,920 requests in a 30-day month, leaving room for a second workflow of similar size. Pair workflows with simple 30-second HTTPS checks on your health endpoint for fast detection of total outages. See API monitoring for assertion options.

Status pages, SLOs and customer trust

A public status page on your own domain is expected by most SaaS buyers, and Uptime Tracker's Team plan includes 10 of them with 2,000 email subscribers and 20,000 status emails per month. Pages are driven by monitors, so component status changes automatically, and your team posts plain-text updates from the incident view.

Uses SaaS teams get out of multiple pages:

• One public page at status.yourproduct.com for all customers.
• Private, password-protected pages for enterprise customers who want a view of the components they use.
• An internal page for support and sales staff with more detailed components.

SLOs and error budgets on Team let you set an availability target per monitor, such as 99.9%, and see how much downtime budget remains. Availability is time-weighted, backdated to the first failed check and adjusted for maintenance windows, so the number is defensible when a customer asks about your track record. Aggregated history is kept for 395 days, which covers a full year for annual reviews.

If you offer contractual SLAs, the uptime calculator converts targets into allowed downtime per month and year. Availability reports can be exported as CSV.

On-call and incident response for a small engineering team

Uptime Tracker's Team plan covers on-call for teams of up to 10 engineers without a separate paging product: rotations, escalation policies, PagerDuty when you already use it, and incidents that open automatically.

• On-call rotations with weekly-style handoffs at a local time, correct across daylight-saving changes, and an iCal feed for calendars.
• Escalation policies with sequential steps that repeat up to 5 times and stop on acknowledgement or recovery.
• PagerDuty via Events API v2, US or EU, de-duplicated.
• Monitor dependencies that suppress child alerts when a shared dependency such as the database or API gateway is down.
• Deployment markers from GitHub Actions, GitLab CI or Jenkins, shown next to incidents as possibly related.

The incident view keeps acknowledgement, assignment, a runbook link, internal notes and public updates on one timeline, and incident history is retained for 365 days. The audit log records changes to monitors and settings, which helps when customers' security questionnaires ask who can change alerting.

Ten login seats cover a small team; up to 20 read-only guest viewers can be limited to a project, for example for a customer success manager. See incident management.

Security and data handling

SaaS teams often need to answer vendor questionnaires, so it helps to know how Uptime Tracker handles access and data. Sign-in is passwordless by email, with TOTP two-factor authentication and recovery codes on every plan, and active sessions can be listed and revoked.

• API tokens are scoped to a workspace with read or write access.
• Secrets used in API monitors are encrypted at rest and dropped on cross-origin redirects.
• Payments are handled by Stripe; Uptime Tracker does not store card data.
• Continuous backups with tested restores; no advertising trackers, and data is not sold.

Monitors cannot be pointed at private or internal network addresses, which prevents the service from being used to probe internal networks. On Team, members have roles, guest viewers are limited to a project, and an audit log records changes.

Where data is stored and how it is protected is described on the security page and in the privacy policy.

Which plan fits a SaaS team?

Team is designed for SaaS; Starter suits a solo founder pre-launch.

Starter works for a solo founder who needs 60-second checks, a status page on the product domain and authenticated API checks before launch. Once there are paying customers and more than one engineer, Team adds what customers and investors start asking about: tested login flows, on-call coverage, SLO reporting and an audit trail. The 14-day Team trial needs no card, and the workspace returns to Free automatically if you do not subscribe.

Team is $490 per year billed annually, about $40.83 a month. Need more than Team offers? Contact support; larger plans are planned. See pricing.