Support
Cadence is a native iOS client for Healthchecks, the open-source monitoring service you run on your own server.
Yes. Cadence has no backend of its own. It connects to a Healthchecks instance you host. If you'd like to see the app first, tap Try the demo on the setup screen — it runs on bundled sample data with no server and no network access.
Yes, over plain HTTP as well as HTTPS. Enter the host, and the port and path if you use them. iOS will ask permission for local network access the first time — Cadence can't reach a LAN address without it.
In your Healthchecks project, under Settings → API Access. A read-write key enables pausing, editing and creating checks; a read-only key gives you the dashboard and detail views, with editing hidden.
Cadence checks your server in the background on iOS's schedule, and iOS decides when that happens. An alert can arrive some minutes after the event. Keep your server's own notification channels enabled — Cadence is built to sit alongside them, not replace them.
The widget fetches on its own, but iOS budgets how often. When it can't reach your server — off your home network, usually — it shows the last known state and says so rather than pretending to be current.
Never for notifications. Whatever you have configured on your server — email, Slack, ntfy, a webhook — is left exactly as it is. Cadence reads your checks, and pauses, resumes, creates or edits them only when you ask it to.
Settings → Disconnect. That removes the stored server address and deletes the API key from the Keychain. Deleting the app does the same.