StackPulse monitors the apps and services you operate. The model is intentionally small: create an app, add services, then attach checks that prove those services are healthy.
Use these docs when you need a precise setup path or a safe example for a specific provider.
What to read first
- Start with Getting Started to understand the core workflow.
- Use Website Uptime Check for public pages and marketing sites.
- Use API Health Check for structured
/healthendpoints. - Use Authenticated API Check when an endpoint requires headers.
- Use Supabase REST Check for a low-impact Supabase REST probe.
Core concepts
| Concept | Meaning |
|---|---|
| App | A product, site, or system you want to monitor. |
| Service | A component inside an app, such as an API, frontend, database, worker, or auth service. |
| Check | A configured probe that StackPulse runs on a schedule. |
| Alert | A notification created when a check opens or resolves an incident. |
Minimal by design
StackPulse is built for operational clarity. It does not need access to your source code, deployment pipeline, or private customer data to run uptime and health checks.
Deployment notes
This docs site is static. It can be deployed separately from the StackPulse product app and served at https://docs.stackpulsehq.dev.