The issue hides
between the tabs.
You find the uptime alert. Then the certificate email. Then the DNS change. Now you have to work out what matters.
Bring the context into one workspace.For product teamsThe first alert
The first alert
shouldn’t be
a customer.
Your team ships every week and shares the pager. Bring uptime, certificates, DNS and scheduled jobs into one place, page whoever is on call when a failure is confirmed, and keep customers informed while you fix it.
On-call and escalation from Starter (€29/month).
Pro adds unlimited team members and SSO.
INCIDENT / ESCALATIONIllustrative flow
checkout.relay.examplePaged in order.
Paged in order.
Stopped by a person.
01 / AT 0 MIN
On call
Paged in Slack
02 / AT 10 MIN
Backup
Not paged
Acknowledged after 4 minutes. Escalation stops.
The person on call takes the incident. No further step fires, and the incident shows who acknowledged it.
One incident, one ownerAcknowledged · Remaining steps skipped
Example behavior only. No live checks or notifications.
Try both scenarios. See when the next person is paged.
On-call & escalation from StarterAdmin, operator, member & viewer rolesSlack · Teams · PagerDutyEU-hosted
Shared responsibility, scattered signalsLess time chasing signals.
01 / LOST TIME 02 / ALERT FATIGUEEvery ping feels
03 / NO CLEAR OWNEREveryone saw it.
Less time chasing signals.
More time fixing things.
When the uptime alert, the certificate email and the DNS change arrive in different places, someone has to connect them before anyone can act.
The issue hides
Every ping feels
like an emergency.
A noisy connection can look like an outage. Repeated false alarms make the next notification easier to ignore.
Confirm failures before paging.Everyone saw it.
Nobody took it.
An alert in a busy channel reaches the whole team and belongs to no one. By the time someone asks who is on it, a customer has already written in.
Page one person, then the next.Share the pager, not the chaosOne incident.
Explore on-call and escalation
One incident.
One owner.
Decide who hears about a confirmed failure first, who comes next if nobody answers, and where everyone else follows along.
01
Verified before anyone is paged.
A failed HTTP uptime check is re-tested from a second region first. That filters most single-location connection problems before they wake anyone up.
02
The person on call first, then the next.
On-call schedules work out who is on duty in the schedule’s own timezone. Escalation policies page the next step after the wait you set, and an acknowledgement stops them.
03
One message per channel, not twenty.
Each channel gets a confirmed incident once. A check that keeps flipping sends one flapping notice, and each channel can keep its own quiet hours.
Check intervals describe how often scheduled checks run. They are not a guarantee of detection or notification time, and verification does not eliminate every false alert.
Relay.Illustrative status page
Web appOperational
Checkout APIDegraded
Fictional service and incident.
Keep customers in the loopFewer tickets.
Fewer tickets.
Clearer updates.
Support should not have to guess while engineering investigates. A status page shows the affected service and your updates, and subscribers hear about them without asking.
- Confirmed uptime and SSL failures open the incident and flag the affected component.
- Visitors subscribe by email or follow the RSS, Atom and JSON feeds.
- Maintenance windows keep planned work from opening incidents or paging anyone.
Starter includes five status pages on your own domains. Pro has no limit.
Explore status pagesWatch the whole productThe services customers use.
Uptime monitoring Application health Cron monitoring Server monitoring SSL monitoring DNS monitoring
The services customers use.
The jobs they never see.
Start with the endpoints and background work your product depends on, then add the deadlines that catch teams out.
Are the app and its API reachable?
Monitor availability and response time. A failure is re-tested from a second EU region.
Is it healthy behind the login?
Read your app’s own health endpoint: queues, failed jobs, disk space, third parties.
Did the nightly job actually run?
Use heartbeats to spot a missing or late check-in.
Is the server running out of room?
Watch CPU, memory and disk with a lightweight agent.
Will a certificate expire on a Friday night?
Watch certificate health and approaching expiry.
Did someone change a record?
See every record change, with the old value next to the new one.
Coverage and limits vary by plan. Compare plan details
Fits the tools you already useAutomate it.
REST API WEBHOOKS MCP
Automate it.
Or just ask.
What you do in the dashboard, you can also do over the API, and AI assistants can read your monitoring through Hoppla’s MCP server.
Script your setup.
A documented REST API with an OpenAPI description. Read-only on Free, full access from Hobby.
Read the API docsFeed your own systems.
Send incidents and warnings to your own endpoint as JSON, signed with HMAC-SHA256 once you set a secret.
Explore notificationsAsk your assistant.
Connect Claude, Cursor or another MCP client to ask about monitors and incidents. Read-only by default; acting on an incident needs a write scope you grant.
Set up the MCP serverSwitching from another tool?Run both side by side.
Run both side by side.
Switch when you trust it.
Import your monitors from one of eight tools, then run Hoppla alongside your current tool for 24 hours or 7 days. Compare the results as a team before you move the pager.
Discuss migration in early accessTools Hoppla can import from
- Oh Dear
- Uptime Robot
- Better Stack
- Pingdom
- StatusCake Beta
- Cronitor Beta
- Healthchecks.io Beta
- Statuspage
Check which monitor types, schedules and history your provider’s import covers before moving. Beta importers follow the provider’s documented API and are not yet proven on a live account.
Plans for teamsShare the response.
Teams sharing the response More people, more services
Share the response.
Keep the bill simple.
Starter brings on-call and every channel. Pro removes the member limit when more of the company shares the pager.
Early access
Compare every plan These are planned prices. Join the waitlist for onboarding; access follows as places open.
Starter.
€29/ month
Billed monthly. No per-seat pricing.
- 50 monitors
- 30-second checks
- 5 team members
- On-call & escalation policies
- 5 status pages + custom domains
- 183 days of data history
Pro.
€99/ month
Billed monthly. No per-seat pricing.
- 250 monitors
- 30-second checks
- Unlimited team members
- SSO / OIDC
- Unlimited status pages
- 365 days of data history
Just you for now?
See plans for founders Free and Hobby cover the first few services for one person, with email, Slack, Discord and webhooks.
Monthly prices shown. Starter is €278 when paid yearly (€23.17/month), Pro €950 (€79.17/month). Every paid plan starts with a 14-day free trial. All prices are total prices. No VAT is charged or shown, under the German small-business rule (§ 19 UStG). See the pricing page for the full comparison.
Questions teams askClear answers.
Clear answers.
Then back to shipping.
Which plan includes on-call?
On-call schedules and escalation policies are included from Starter, with five team members. Pro removes the member limit and adds SSO / OIDC. The pricing comparison lists every allowance.
How does an escalation stop?
When someone acknowledges or resolves the incident, no further step fires. If nobody answers and the policy runs out of steps, it can start again from the top, up to ten times.
Do we still need PagerDuty?
Not to page your own team: Hoppla has its own on-call schedules and escalation, with no per-seat pricing. If PagerDuty already routes your alerts, connect it as a channel from Starter.
Can someone help without changing settings?
Yes. The operator role manages monitors, incidents, maintenance and status pages, but not the team, its settings or billing. The viewer role can read everything and change nothing.
Does a second region prevent every false alarm?
No. A failed HTTP uptime check is re-tested from a second region before anyone is paged. That filters most single-location connection problems, but it cannot rule out every false alarm or detect a failure the moment it starts.
Where is our data hosted?
In the EU. Checks run from Germany and Finland. The security page and privacy policy have the details.
Know before your customers doGive the next incident
Get early access Give the next incident
a clear owner.
Bring your team’s monitoring, paging and customer updates into one place.
Plan details as of September 2026. See current plans