Home / Website monitoring for freelance developers
Know before the client does, on every site you maintain, without building your own cron-and-curl setup.
The problem
You maintain a dozen sites for a dozen clients on a dozen hosts. Each one can fail in its own way, and the first you hear of it is a message at 23:00.
What you get
Telegram, Slack, Discord, e-mail, push or your own webhook. E-mail alerts work on the Free plan; chat channels from Solo.
HTTP, keyword, API, DNS, ping, port, heartbeat for cron jobs, SSL and domain expiry, blacklist. The incident names which one it was.
Ten monitors free with no time limit; Solo covers fifty sites for the price of one hour of your time a month.
HTTP monitor · checked every 30s
Current status
OPERATIONAL
HTTP 200
Avg. response (24h)
29ms
Fast
Last check
36ms
AVG 24H 29 ms · 2026-08-10 15:23:30
Speed pulse
Last 7 days
Auto-scaled to 145ms · 2488 checks
Alert channels
Downtime, SSL and keyword alerts go to every connected channel the moment a check fails — and again on recovery.
SSL certificates
soonest firstCertificate expiry status for all monitored endpoints
Screens are rendered from markup with sample data, not screenshots of a customer account.
Which plan
Fifty monitors, 60-second checks, every monitor type, chat alerts, custom-domain status pages. Every number is on the plan table; start on Free and upgrade when you need it.
Yes: a heartbeat monitor gives you a URL to ping from the job. If the ping is late, you get an issue alert; a late job is never counted as website downtime.
Usually. If the firewall blocks the check, the incident says so ("blocked by a firewall or bot filter") instead of pretending the site is down, and the fix is to allowlist the one monitoring address.
Yes, on paid plans: list, create, update and delete monitors with the same validation as the form, using read or write keys that can be limited to one monitor. Incidents and status pages are not in the API yet.