Website Monitoring for SaaS Teams
You get an alert when login or the API fails a check, and weeks before a certificate expires. Uptime, SSL, DNS and domain checks for your app, API, docs and marketing site sit in one workspace.
No credit card required·Nothing to install·Free plan with no time limit
Downtime
Your customers shouldn't be the first to tell you
Customers work inside your app, so when it stops answering, their work stops too. The first sign is often a support ticket or a post that tags you, and by then the outage has been running for a while.
WebPixie checks the app, the API and the marketing site from multiple global locations, such as London and New York, on an interval you set per monitor, from 30 seconds to 24 hours depending on your plan. When a check finds a monitor down you get an alert, and another one when it recovers. From the Starter plan, each outage is also kept as an incident with how long it lasted.
A 99.9% uptime target still allows about 43 minutes of downtime a month. If you multiply that by the customers who are logged in at the time, you see what it means for you. The free Uptime Calculator turns any percentage into minutes.
Incidents
Last 7 days
- CriticalResolved
app.example.com
Uptime · Timeout · Tue 14:02 · 23 min
- CriticalResolved
api.example.com/v1/health
Uptime · Status code mismatch · Sat 02:41 · 9 min
Down and recovery alerts sent by email and Slack
Login and API
The app loads, but login or the API is broken
A homepage check stays green while the login page throws an error or the API answers 200 with an error message inside. Customers cannot sign in, integrations fail, and your dashboard still says everything is up.
You can add the routes customers depend on, such as /login or /v1/health, as their own uptime monitors. Each one can send the method, headers, request body and Basic, Token or Digest auth the route needs. You choose which status codes count as up and a keyword that must or must not appear, so a 200 that says "error" counts as down.
Every check records its location, status code, response time and response headers, so you can see what the route actually returned.
WebPixie sends a request and checks the answer. It does not click through a sign-up in a browser.
Uptime monitors
Production
api.example.com/v1/healthStatus 200 · must not contain "error"
Found
Downapp.example.com/loginMust contain "Sign in"
Found
Upapi.example.com/v1/meToken auth · accepts 200
200
Up
Alert sent for api.example.com/v1/health
Certificates
The certificate on the subdomain nobody remembered
Auto-renewal covers the subdomains someone set it up for. The docs site, an old status page or the landing page from launch week can fall outside it. When that certificate expires, browsers show a warning and API clients fail their TLS handshake.
The Certificates Manager lists the certificates seen for your domain and its subdomains in Certificate Transparency logs, so a subdomain you forgot shows up with an Add Site action. Once it is a site, SSL monitoring checks the served certificate every day, warns you 15 days before it expires by default and raises the severity as the date gets closer.
It also checks whether every IP behind the name serves the same certificate, and shows a mismatch behind a load balancer as a finding to review.
Renewal still happens with your certificate provider or host. WebPixie tells you in time.
Certificates · example.com
Daily check
- Add site
launch.example.com
Seen in CT logs, not monitored
docs.example.com
SSL certificate expires
5 days
Highapi.example.com
Valid and trusted
61 days
OK
Alerts
Two people on call can't wake up for every blip
On a small team, the person who gets the alert is also the one who has to ship tomorrow. After a few false alarms at night the alerts get muted, and then a real outage lands in silence.
A timeout or connection error is retried in place before it counts. On paid plans, if it still fails, WebPixie checks from the monitor's other selected locations. If the app answers there, no incident opens and the check stays out of your uptime figures, so the monitors that wake people up should have at least two locations.
For a route that flaps, you can set the monitor to alert only after several failed checks in a row. Either way, you get one notification when the incident opens and one when it closes: by email on every plan, in Slack from Starter and through webhooks from Pro, so alerts can reach the on-call tool you already use.
app.example.com/login
Alert settings
- Locations
LondonNew York- On timeout
Retry, then verify- Alert after
2 failed checks in a row- Notify
EmailSlack
Timeout from London
Reachable from New York · no incident opened
Domain and email
A lapsed domain takes the app, the API and your emails down
When the domain lapses, the app and the API go down together, and invite and password-reset emails stop arriving. Auto-renewal can fail quietly when the card on file expires and the reminder goes to a founder's old inbox.
Domain monitoring checks the registration every day, warns you 30 days before expiry by default and alerts you if the registrar puts the domain on hold.
Product emails also depend on SPF and DMARC records. DNS monitoring reads them every day, lists any that are missing or set up incorrectly, and keeps every DNS change with its old and new value. After a move to a new email provider, you can see exactly what changed.
WebPixie cannot see whether a particular email reached the inbox, but a missing or broken record is one of the first things to rule out.
Domain and email · example.com
Daily check
Domain registration
Renew at your registrar
24 days
Medium- Found
SPF
Includes your email provider
- Missing
DMARC
No record found
MX record changed
Old and new value kept
Yesterday
Change
Proof
A bigger customer asks for your uptime and your security setup
The first larger customer often wants an uptime figure for the contract and asks how the product is secured. Every monitor shows its uptime rate, how many times it went down and a response-time chart, and each check is kept with its time, location and error. Paused time and failures dismissed by cross-location verification are left out, so the figure reflects real downtime. How far back you can look depends on your plan's data retention.
WebPixie's analysis of your security headers and SSL setup looks at what your sites send, such as HSTS, CSP and the TLS versions you accept. Each finding is ranked from Critical to Info with fix guidance, so you can tighten things before a customer's security review asks about them.
Public status pages are coming soon. Until then, Slack and webhook alerts help you update customers through your own channels.
app.example.com
Last 30 days
Uptime
99.96%
Went down
1 time
Avg response
286 ms
Response time
Uptime by day
Search and AI
Can search engines and AI assistants still reach your site?
New signups often start with a search or a question to an AI assistant. One line left over from staging in robots.txt can keep search engines such as Google and Bing, or AI crawlers, away from the marketing site or the docs, and nothing looks wrong to visitors.
WebPixie reads robots.txt and llms.txt line by line, shows which AI crawlers, such as GPTBot and ClaudeBot, have their own rules, and checks that robots.txt points to your sitemap. The Link Crawler lists broken links and marks pages that robots.txt blocks, and from the Starter plan, Sitemap Monitoring shows pages missing from your sitemap.
These checks cover access, not rankings.
robots.txt · docs.example.com
Daily analysis
- # copied from staging
- User-agent: *
- Disallow: /
- User-agent: GPTBot
- Allow: /
What WebPixie reports
Syntax
ValidAI crawlers with explicit rules
GPTBotSitemap line
Missing
One workspace
Five tools for a three-person team
A pinger for uptime, a script for certificates, a calendar reminder for the domain and nothing for DNS. Each one is another login, another bill and another thing to hand over when someone leaves.
In one WebPixie workspace, the uptime monitors, certificates, DNS records and domain data for every subdomain sit together. You can sort sites into folders for the product and the website, tag monitors by environment, and give cofounders and engineers workspace-wide roles.
As you ship, the GraphQL API from the Starter plan lets your deploy pipeline create a monitor for a new service, pause it during the deploy and resume it afterwards. The MCP server is open on every plan, so AI assistants such as ChatGPT and Claude can answer "what is down right now?" from your workspace.
Sites
Product
- app.example.comproductionScore88
- api.example.comproductionScore91
- auth.example.comproductionScore74
Website
- example.comproductionScore86
- docs.example.comproductionScore67
You can start monitoring in three steps
Nothing to install and no DNS change. Works wherever your app is hosted.
- 1
You add your product
You add the app, the API, the docs and the marketing site as sites, and routes such as /login as uptime monitors. Monitoring begins right away.
- 2
You set what counts as working
You pick the status codes, keywords, auth, locations and check interval for each monitor.
- 3
Alerts go where your team is
Alerts go to email on every plan, to Slack from Starter and to webhooks from Pro. Paid plans let you invite the rest of the team.
The free plan covers 1 site and 3 uptime monitors with email alerts, with no time limit, which is enough to watch the app and its login route before launch. Once customers rely on the product, paid plans add faster checks, cross-location verification, incident history, Slack alerts and the API. You can compare them on the pricing page.
Frequently Asked Questions
Common questions from SaaS founders and engineers.
A good place to start is what customers would notice first: the login page, a health route on your API and the app itself, plus the certificates and domain behind them. Each route can be added as an uptime monitor with a keyword or status rule, so a page that loads with an error still counts as down. Then the app, the API, the docs and the marketing site can be added as sites, which turns on daily SSL, DNS and domain checks for each one. The Certificates Manager lists subdomains seen in Certificate Transparency logs, which helps you find the ones you forgot, such as an old launch page. After that, the pages that bring in signups, such as pricing and the sign-up form, are worth their own monitors. The free plan covers 1 site and 3 uptime monitors, which is enough for the most important routes. The pricing page shows how far each paid plan goes.
Before launch or with a handful of users, the free plan is often enough, and it has no time limit. It covers 1 site and 3 uptime monitors at 15-minute check intervals, with email alerts and SSL, DNS, domain and link checks for that site. The MCP server works on the free plan too. What changes once paying customers rely on the product is speed and confirmation. Paid plans check more often, verify network failures from the monitor's other locations before alerting, keep each outage as an incident with its duration, add Slack alerts and the GraphQL API, and let you invite teammates. They also cover more sites, which matters once the app, the API, the docs and the marketing site each need their own certificate and DNS checks. You can start free and upgrade later without setting anything up again. You can compare the plans on the pricing page.
Yes, at the request level: each route you add is called with the method, headers, body and auth you set, and judged by its status code and content. You can point a monitor at your login page with a keyword that must appear, such as "Sign in", or at an API health route with a keyword that must not appear, such as "error", so a 200 response carrying an error counts as down. Monitors can send Basic, Token or Digest auth, custom headers and a request body as form data, raw text or JSON, which lets you check a protected endpoint such as /v1/me with a test account's token. You also choose which status codes count as up. Every check keeps its status code, response time and response headers in the uptime monitoring history. WebPixie sends one request per check and does not click through a multi-step sign-up in a browser, so each important step's route needs its own monitor. On paid plans, failures become incidents that close on their own when the route recovers.
Once you add each subdomain as a site, WebPixie checks its certificate every day, while the Certificates Manager helps you find the subdomains you forgot. SSL monitoring validates the served certificate and its chain, warns you 15 days before expiry by default, and raises the severity at 7 and 3 days on the same incident. A certificate that is expired, untrusted or issued for the wrong name fails the check, which sends an email alert on every plan and opens an incident on paid plans. The Certificates Manager pulls Certificate Transparency logs for your domain and lists the certificates seen for it and its subdomains, with an Add Site action for each subdomain you are not watching yet. WebPixie also checks whether every IP behind a name serves the same certificate and shows a mismatch, such as one node behind a load balancer, as a finding. Renewal still happens with your certificate provider or host. The free plan covers 1 site, so a product with several subdomains needs a paid plan; the pricing page has the details.
WebPixie retries network failures, confirms them from other locations on paid plans and sends one notification per incident, so a two-person team hears about real outages without every blip. A timeout or connection error is first retried in place with backoff. On paid plans, if it still fails, it is checked from the monitor's other selected locations; if the site answers there, no incident opens and the check stays out of your uptime figures. A monitor with a single location has nowhere else to verify from, so important routes need at least two. For a route that flaps, each uptime monitor can wait for several failed checks in a row before alerting. When an incident opens you get one notification, and one more when it closes, by email on every plan, in Slack from Starter and through webhooks from Pro. Notifications can be switched off per resource, so staging can stay quiet while production alerts. Email goes to every workspace member by default.
You can pause monitors before a deploy and resume them after, by hand or from your pipeline; on paid plans the GraphQL API can also create monitors for new services. A paused monitor runs no checks and opens no incidents, and paused time is left out of the uptime percentage, so a planned deploy does not count as downtime. With the API integration, available on Starter, Pro, Enterprise, the pipeline that ships a new service can add its uptime monitor with tags such as production. API keys can be read-only and limited to specific sites and uptime monitors, so a CI job only touches what it needs. The MCP server is open on every plan: with read and write access, you can ask an AI assistant such as ChatGPT or Claude to pause a monitor before a release, or ask what is down right now. For short blips during a rollout, the uptime monitoring setting that waits for several failed checks in a row before alerting also helps.
Everything WebPixie can watch on your product
You can turn on the checks each site and endpoint needs.
Related Solutions
You can put your app, API and every subdomain under watch
Free plan, no credit card required.