Getting started

From signup to a live status page in a few minutes. This walks the same guided wizard you'll see in the dashboard — nothing here needs a separate setup step outside it.

1. 1. Create your account

   Sign up with your email, or continue with Google. Confirm your email address before continuing — the link is in your inbox.

2. 2. Pick a plan

   The wizard's first step. Free works fine to try things out — you can upgrade later from Billing in the dashboard without losing anything you've already set up.

3. 3. Add your first service

   A service is the thing you're monitoring — give it a name and an endpoint (a URL we'll check on a schedule). You can add more endpoints and assertions (expected status code, response time, headers, body content) once it exists; the wizard only asks for the essentials to get one running.

4. 4. Add more services (optional)

   Most people are only watching one or two things at first. Add the rest now or later — from Services in the dashboard at any time.

5. 5. Confirm your check configuration

   Review the check interval and region(s) before anything goes live — which regions are available depends on your plan.

6. 6. Preview your status page

   A live render of what your customers will see, using your actual configuration — not a mockup. See setting up your status page for the full set of branding options once you're past the wizard.

7. 7. Publish

   That's the wizard done — you land in the normal dashboard from here. Checks run on the schedule you set, and your status page stays current automatically as they report in.

8. 8. Add a notification channel (optional)

   From Notification Channels in the dashboard, send a webhook, a Slack message, or an email when an incident is created or a degradation is detected. Building your own receiving endpoint? See the payload reference for the exact JSON shape and how to verify a delivery's signature.

9. 9. Automate it (optional, Business plan)

   From API Keys in the dashboard, mint a key to manage services and incidents from a script, CI pipeline, or your own infrastructure-as-code tooling. See the API reference for authentication and the full endpoint list.

10. 10. Invite your team (optional)

    From Members, add teammates by email — if they don't have a HeimPulse account yet, we'll send them an invite to set one up. An org owner can remove a member or force-log-out an individual session at any time.