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

• 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 (by email, and to Telegram, Slack, or a webhook to your own tools — see Notifications) with a plain-language explanation of what happened.

Create your first monitor

1. Sign up or sign in with Google or GitHub — your first sign-in creates a free account (no card). See Account & sign-in. You land on Monitors.
2. Click New monitor.
3. Pick what you want to watch — for a website, choose Website / HTTP and enter the URL you want checked (e.g. https://example.com).
4. Choose how often to check it. Free accounts check every 5 minutes; paid plans can check more often.
5. Choose where to check it from, under Where we check from. Website, Port, Ping, and UDP monitors run from a checkpoint — pick one of CuliPulse’s shared probe locations (Singapore, Frankfurt, or Montreal) with no setup, or your own agent if the target is only reachable from inside your network. (Domain, DNS, and Vendor checks run from CuliPulse directly and skip this step.)
6. Save. CuliPulse starts checking right away. (A heartbeat is different: it starts being watched after your job’s first check-in.)

See Monitors for the full list of what you can watch, and Check types for the settings each one offers.

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.

See Alerts & states for what “up”, “down”, “degraded”, and “unknown” each mean.

Get notified

A monitor on its own just watches — to hear about problems, connect a notification destination (Telegram, Slack, or a webhook). New accounts get email alerts to their sign-in address automatically. Don’t see an Email row? Turn it on under Add destination → Email (details). Head to Notifications to connect one; it takes under a minute.

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.