Checks and heartbeats
Checks look at your apps from outside. Heartbeats work the other way round: your job tells Fidiba it ran, and Fidiba notices when it goes quiet.
Checks
Fidiba visits your site from 3 regions, as often as your plan allows. A check fails only when more than one region agrees, so one bad network path doesn't wake anyone. Checks also watch certificates and domains, and warn before either runs out.
Heartbeats
Give each scheduled job or backup a heartbeat, and say how often it should arrive.
# Every night at 02:00, then tell Fidiba it worked. 0 2 * * * /usr/local/bin/backup.sh && curl -fsS https://in.fidiba.dev/hb/backup-KEY
To say a run failed, rather than waiting for it to be late, add /fail:
/usr/local/bin/backup.sh \ && curl -fsS https://in.fidiba.dev/hb/backup-KEY \ || curl -fsS https://in.fidiba.dev/hb/backup-KEY/fail
Your app's own keys
Fidiba never asks for your Stripe, mail or AI keys. If you want to know a key still works, let your app check it and send a heartbeat: "works" or "fails".