Add a monitor
Open Monitors and choose Add monitor. Give it a name and the address to check, then choose how often. Your plan sets the fastest: every 5 minutes on Free, every 1 minute on Solo and Team.
A monitor can be an HTTP or HTTPS check (the status code you expect, redirects, and a response time above which it counts as slow), a keyword or API check (a word that must appear, a header, or a value in a JSON answer), or a certificate check.
Before a monitor is created you tick a box: “I own this website or service, or I am authorised to test it, and I will not use this monitor in a way that overloads it.” You can only point a monitor at an address you enter yourself. See the Terms of Service (G8).
What is checked, and what is kept
Checks run from more than one place (see the Terms of Service, G8, and the Privacy Policy). A failure is confirmed from a second place before it opens an incident, and a recovery is confirmed the same way. Checks cannot reach private or internal addresses.
For each check AperioFlow keeps the time, whether it passed, how long it took, the status code and a short fixed reason. It does not keep the page or API response.
How long things are kept: individual check results 30 days (14 on Free); hourly totals, resolved incidents and alert records for the plan history period (14 days Free, 90 Solo, 12 months Team); alert webhook delivery records 30 days.
Incidents and alerts
When a check fails and the failure is confirmed, AperioFlow opens an incident and an issue on the monitor’s project. A failure is confirmed by a second look about a minute later; you can ask for more failed checks in a row (up to 10) on a monitor, to avoid being told about a brief blip. When it recovers, both close. You can be told by email, by web push and by a signed webhook: once when it goes down and once when it recovers. Alert emails are service messages to members of your organisation and carry no marketing.
An alert webhook address is outside AperioFlow, so add only one you control or trust (Terms, G8).
Use a maintenance window to silence alerts while you work.
Heartbeats: cron jobs and backups
Create a monitor of type Heartbeat. It gives you a secret address. Have your job call that address when it finishes, for example by adding curl -fsS <the address from the monitor> > /dev/null as the last line of the script.
Set how often it should call and a grace period. If a call does not arrive in time, an incident opens; the next call closes it. Treat the address like a password. Only a hash of it is stored.
Coolify
Give AperioFlow a read-only Coolify API token and it can find your applications and databases, watch their state, and spot a container that keeps restarting. The token is stored encrypted, is not shown again, and is used only to read state. Create it with read-only permission. Coolify checks are included on Solo and Team.
Coolify only tells AperioFlow what Coolify itself reports about a container, so a container that is running can still be serving errors. Add a web monitor for the same service as well: it checks the address your visitors use. If AperioFlow cannot reach Coolify for a while, that is shown as a single incident about the connection, not as every one of your applications being down.