Step 1 of 4
Create an account
Sign up — you get a personal workspace. Create an organization from the Team page to share monitors with teammates.
Connect Perch to what you run
Perch can watch things from the outside, wait for your jobs to check in, or read health data from your servers. Pick the option that needs the fewest changes for you — you can mix them.
Website / APINo changes on your sideHeartbeatAdd one line to your jobHealth endpointAdd a small JSON endpointServer agentRun one install command
Which one should I use?
| You want to know… | Use | What you change |
|---|---|---|
| Is my website / API up? Is the SSL certificate or domain about to expire? | Website / API | Nothing |
| Did my cron job, backup or queue worker run — and did it succeed? | Heartbeat | Add one curl line |
| Is my server alive, even behind a firewall? | Heartbeat ("server alive") | One crontab line |
| How busy are CPU, memory and disk? Which processes / containers are running? Is my database reachable? | Health endpoint | Add a small endpoint (copy-paste) or run one Python file |
| Continuous metrics and logs without opening a port | Server agent | Run one install command |
| Alert me when CPU or disk crosses a limit, or errors pile up in the logs | Server agent + alert rules | Nothing more — create a rule |
Get started in 4 steps
- Step 2 of 4Add a monitorClick Add monitor and choose how Perch should watch it — or Add a server for the server agent.
- Step 3 of 4Follow the setup on the monitor pageURLs, secrets and install commands are already filled in for you.
- Step 4 of 4Get alertedAdd an alert channel (email, Slack, Discord, Telegram, SMS, webhook) under Alert Channels and attach it to the monitor.
Everything inside an organization — monitors, projects and alert channels — is shared with its members according to their role (owner, admin, editor, viewer).