One platform for your customers, your partners, and your engineering team.
Model every service in your stack — public-facing, partner-only, or internal-only — with dependency chains that roll up vendor health automatically. Show each audience exactly what they need to see.
What you get
Three visibility tiers
Mark each service public, authenticated (passcode or SSO), or private (internal only). One status model, multiple audiences.
My Services — your internal source of truth
Engineers see the full picture: every service, dependency chain, component-level vendor status, and runbook links — without exposing internals to customers.
Dependency-aware rollups
Link services to the vendors they depend on. If Stripe degrades, your Payments API shows degraded — automatically, on every tier that should see it.
Audience-aware maintenance
Schedule maintenance for public customers only, internal teams only, or both — without duplicating windows or posting the wrong message to the wrong audience.
Vendor incident promotion
When a tracked vendor declares an incident, ServicePulse can suggest posting to your status page — so customer comms stay in sync with what you already know.
Service map visualization
See your architecture as a live graph: services, vendors, and health coloring in one view — built from the same dependency model.
How it works
Model your services
Add your APIs, pipelines, and product surfaces in My Services. Set visibility: public, authenticated, or internal-only.
Wire up dependencies
Link each service to the vendors it depends on — optionally filtered to specific regions or components.
Status rolls up automatically
Vendor outages propagate through your dependency graph. Your status page and internal views stay current without manual updates.
Share the right view
Customers get your public page. Partners use the secure tier. Engineers use My Services and the service map for the full technical picture.
Common use cases
SaaS with a public API and internal batch jobs
Customers see API health on your public page. Your data team sees ETL pipeline status internally — without exposing batch infrastructure to the world.
Partner integrations
Give integration partners a passcode-protected status tier that shows more detail than the public page — including vendor names if you choose.
On-call triage
During an incident, engineers open My Services to see which dependency chain is red — Stripe → Payments API → Checkout — in seconds.
Frequently asked questions
What's the difference between My Services and the status page?
My Services is your internal architecture view — all services, all visibility levels, full dependency detail. The status page is what you publish externally (public and/or secure tiers).
Can I hide vendor names on the public page?
Yes. Public services can show operational status without naming third-party vendors. Secure and internal tiers can show full vendor detail.
Does this work with ping monitors and push endpoints?
Yes. Services can be tied to ping monitors or receive push status from your pipelines — and those feed the same rollup model.
Internal & External Status is included on every paid plan.
Start free. Upgrade when you need more.