Small enough to learn before lunch.
up4 has eight concepts and one price formula. This page covers all of them. If something here does not answer your question, a human will — contact us.
From zero to monitored, in four steps.
Create an account
15 trial days, €3 of credit, no card. Everything is unlocked from the first minute — including client accounts.
Add your first monitor
Paste a URL, pick an interval. The form shows the monthly cost before you save — 10-second checks, if you want them, from day one.
Wire the alerts
Connect an alert channel, group channels into an alert plan, optionally add an on-call rotation. Two consistent failed checks trigger it; one blip never does.
Publish a status page
Pick monitors, choose a slug, publish. Subscribers get notified on incidents; custom domains come with Team and Agency.
The vocabulary, in plain language.
| Term | What it means here |
|---|---|
| Monitor | One thing we check: a URL, a TCP port, a ping target, a DNS record or an API call. Has an interval, a cost preview and a state — up, degraded or down. |
| Alert channel | A place alerts go: email, Slack, Telegram, PagerDuty and eight more. Connect once, reuse everywhere. |
| Alert plan | The rules between a monitor and its channels: who is told, in what order, after how long. Other tools call this an escalation policy; we think plans should read like plans. |
| On-call rotation | Whose phone buzzes tonight. Schedules, overrides for holidays, and a “who is on call right now” answer in one glance. |
| Scheduled job | A cron job or backup that must call us before a deadline. If the ping does not arrive, that silence becomes an alert — monitoring for the things that have no URL. |
| Playbook | The steps you actually take when something breaks, attached to the monitors they belong to, with shared progress during an incident. No wiki archaeology at 4 a.m. |
| Status page | The public (or client-facing) view of your uptime, with subscribers and updates. Custom domain and SSL included from the Team plan. |
| Client | An agency-mode partition. Monitors, incidents, pages and reports scoped per client — see the agency tour. |
Monitor the things that have no URL.
Backups, cron jobs, nightly exports — the failures nobody notices until restore day. Create a scheduled job, get a unique ping URL, and add one line at the end of the script:
#!/bin/sh
pg_dump mydb | gzip > /backups/nightly.sql.gz
# tell up4 the backup actually ran
curl -fsS https://app.upfour.io/v1/heartbeat/<your-slug>If the ping misses its window, the silence becomes an incident — with the same alert plans, playbooks and status pages as everything else.
Everything the interface does, the API does.
REST, versioned, keyed. Create an API key under Settings → Developer, then talk
to https://app.upfour.io/v1. Monitors, incidents, status pages,
reports — the same endpoints the product itself uses.
Webhooks, signed. Subscribe to events and verify each delivery with the
X-Pulse-Signature header, so nobody can forge an “all clear”.
Batch import. Post a list of URLs and get a fleet of monitors — the same mechanism the migration flow uses.
# list your monitors
curl -s https://app.upfour.io/v1/monitors \
-H "Authorization: Bearer $UP4_API_KEY"Set up before the coffee gets cold.
€3 credit · no card · cancel by simply stopping