Cron monitor, managed by CoreHost

Sign in with the email address you gave when you ordered and the password shown on your app page on CoreHost. The owner account was created for you before the app first started and sign-up is off, so nobody else can create one. Change the password under Account Settings once you are in.

Create a check, copy its ping address, and add a request to that address at the end of the job, for example curl -fsS -m 10 --retry 5 -o /dev/null followed by the address. Add /start to the address at the beginning of the job to measure how long it runs, and /fail to report a failure. Set the schedule and grace time on the check to match the job.

Yes, on purpose: your cron jobs have to reach it from anywhere. The address contains a long random secret, so treat it like a password. Anyone who has it can send a ping for that check, but cannot read or change anything. If one leaks, delete the check and create a new one, or rotate the project's ping key.

Yes, once you add your own mail server under the app's settings on CoreHost (Email server, port, username and password). Until then no email is sent, and you sign in with your password only. Slack, Discord, Telegram, ntfy, Gotify, Matrix, Teams, PagerDuty, Pushover and webhooks work without a mail server. Port 25 is blocked, so use 587 or 465.

Alert targets are checked every time they are used, and any address that is not on the public internet, including this server, its neighbours and private networks, is refused. A webhook to a public address works as normal. Put a service you want to notify on a public address (with its own authentication) or use one of the built-in integrations.

Pinging by email is not available because the server cannot receive mail. Sign-up is closed by default; you can switch on open sign-up in the app's settings on CoreHost once you have added a mail server, or invite colleagues to a project from inside the app.

We do. Curated updates roll out shortly after upstream releases and are tested on our platform first; security fixes move fast. If an update changes behaviour in a breaking way, we email you before it lands.

Take a final export or SFTP copy any time before you cancel. After termination we keep your data for 14 days (in case you change your mind), then purge it, backups included.

Yes. Point a CNAME at your instance, prove ownership with a TXT record, and TLS certificates are issued automatically. Cloudflare-proxied domains work; if you use CAA records, allow letsencrypt.org.