Marketplace SaaS uptime monitoring guide
Marketplace apps live in two worlds. The listing may be visible in Atlassian, Google, Shopify, or another marketplace, while your own backend is where installs, webhooks, and user actions succeed or fail.
That split makes a public status page useful. It gives reviewers and buyers one place to check whether your app is healthy.
Quick answer
For a marketplace SaaS, StillOnline should monitor the backend endpoints behind install, auth, API, and webhook flows; Free gives one owner alert channel and Pro/Ultimate add email, Telegram, and Slack on pricing. Marketplace programs such as Atlassian Marketplace and Google Workspace Marketplace document app listing requirements separately from your service uptime. Treat the listing as discovery and your StillOnline status page as the operational source of truth.
What buyers expect
Buyers do not need your whole observability stack. They need a clear answer when the app fails inside the host platform.
| Area | Check | Status component |
|---|---|---|
| Install | OAuth or install callback | App installation |
| API | read-only health URL | API |
| Webhook | receiver health | Webhook processing |
| Dashboard | login/session check | App dashboard |
Review team angle
Marketplace reviewers may ask how incidents are communicated. A public status page answers that without promising enterprise-grade observability.
Link the page from docs, support replies, and security questionnaire answers. Avoid broad claims like “99.99% SLA” unless your contract and monitoring actually support it.
Webhooks and host dependencies
If your app depends on events from the host platform, separate “host platform down” from “our webhook receiver down.” StillOnline can monitor your receiver; the host’s own status page explains their side.
Webhook-heavy marketplace apps also benefit from a dedicated Webhooks component — the same pattern as in webhook platform status page.
Related guides
- Webhook platform status page
- Status page security questionnaire
- B2B SaaS status page trust
- API-only SaaS uptime checks
FAQ
Does a marketplace SaaS need StillOnline if the host marketplace is up?
Yes, if your own backend can fail independently. The marketplace listing can be available while your install callback, API, or webhook receiver is down.
Should I link a StillOnline status page from the marketplace listing?
Use the listing support or documentation fields if the marketplace allows it. A status page link is especially helpful for B2B buyers and reviewers.
Can StillOnline monitor Atlassian or Google Marketplace itself?
StillOnline should monitor endpoints you own. For host outages, link to the host platform’s official status page and explain the dependency in your incident update.
What should marketplace app components be called in StillOnline?
Use buyer language: App installation, API, Webhooks, Dashboard, and Billing if relevant. Avoid internal service names that customers cannot map to impact.