Documentation

Small enough to learn before lunch.

up4 has eight concepts and one price formula. This page is the map; the guide, the recipes and the full API reference are one click deeper. If something does not answer your question, a human will — contact us.

The guide

Every part of the product, one page each.

Getting startedAccount → monitor → alerts → status page → API key, in one sitting. MonitorsTypes, intervals, keyword checks, degraded state, maintenance windows. Alerting & on-callChannels, alert plans, rotations — and why one blip never pages. Scheduled jobsHeartbeats for cron jobs and backups; silence becomes an incident. Status pagesAutomatic component states, subscribers, translations and hosted public URLs. Incidents & playbooksThe lifecycle, severities, and shared step progress at 4 a.m. Agency modeClient partitions, share links, white-label, templates. BillingThe meter, the wallet, quotas — and grace mode instead of a blackout.

Prefer working examples? Five recipes cover batch import, CI deploy hooks, webhook consumers, backup heartbeats and monitors-as-code.

Getting started

From zero to monitored, in four steps.

Create an account

€3 of starting credit, no card required. Every released feature is available from the first minute — including client accounts — and the product shows the usage-based runway.

Add your first monitor

Paste a URL, pick an interval down to 10 seconds. The form shows the monthly cost before you save; every monitor-region execution is metered or budgeted.

Wire the alerts

Connect an alert channel, group channels into an alert plan, optionally add an on-call rotation. Three consistent observations trigger it — the failed check plus two instant confirmation checks; one blip never does.

Publish a status page

Pick monitors, choose a slug, publish. Subscribers get notified on incidents; the page is served from a stable up4 URL.

Start monitoring

Concepts

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, updates and a stable up4-hosted URL.
Client	An agency-mode partition. Monitors, incidents, pages and reports scoped per client — see the agency tour.

Scheduled jobs

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.

API & webhooks

Everything the interface does, the API does.

REST, versioned, keyed. Create an API key under Settings → API tokens, then talk to https://app.upfour.io/v1 — 130+ endpoints, the same ones the product itself uses. The full reference documents every one, with an in-browser Try-It console on each endpoint.

Webhooks, signed. Subscribe to events and verify each delivery with the X-Up4-Signature header — copy-paste verification in Node and Go, so nobody can forge an “all clear”.

Sandbox included. Test keys run against your own sandbox organization: real checks, suppressed notifications. Break things safely.

# list your monitors
curl -s https://app.upfour.io/v1/monitors \
  -H "Authorization: Bearer $UP4_API_KEY"

The contractEnvelope, errors, cursors, idempotency, rate limits — what we promise not to break. QuickstartKey to running monitor in five curl commands. ReferenceEvery endpoint, grouped by resource, each with a Try-It panel. WebhooksEvents, signatures, verification snippets.

Set up before the coffee gets cold.

Start monitoring See pricing

€3 credit · no card · no negative balance