Getting started
CuliPulse watches the things your business depends on — your website, your servers, the services your team runs — and tells you the moment something needs attention. Instead of finding out from an angry customer, you find out first.
What CuliPulse watches
Section titled “What CuliPulse watches”- Your own stuff — a website, an API, a database port, a background job.
- Your vendors — the third-party services you depend on (GitHub, your cloud provider, your AI provider), so you know when a problem isn’t yours.
When something goes down, CuliPulse sends you an alert (Telegram, Slack, or a webhook to your own tools — see Notifications) with a plain-language explanation of what happened.
Create your first monitor
Section titled “Create your first monitor”- Sign in and go to Monitors (the page you land on).
- Click New monitor.
- Pick what you want to watch — for a website, choose Website / HTTP and enter the URL
you want checked (e.g.
https://example.com). - Choose how often to check it. Free accounts check every 5 minutes; paid plans can check more often.
- Save. CuliPulse starts checking right away.
See Monitors for the full list of what you can watch and how editing works.
Read the status
Section titled “Read the status”- The Monitors page lists every monitor with its current status — up, down, or degraded — at a glance.
- Click into a monitor to see its recent history and any past incidents.
- The Overview page rolls everything up into one summary if you’re watching a lot of things at once.
Get notified
Section titled “Get notified”A monitor on its own just watches — to hear about problems, connect a notification destination (Telegram, Slack, or a webhook). Head to Notifications to connect one; it takes under a minute.
Using the API
Section titled “Using the API”Everything you can do in the app — list monitors, check incidents, manage notification channels — is also available over a REST API, so you can script it or wire it into your own tools. Start with API authentication.