Basic
- 10 monitors
- 60-second check interval
- 1 status page, SSL checks included
- Email and Slack alerts
Start on Basic, move up when you need more monitors or faster checks. Upgrade or downgrade any time from your account.
| Feature | Basic | Team | Business |
|---|---|---|---|
| Monitors | 10 | 100 | Custom |
| Fastest check interval | 1 min | 30 s | Custom |
| Check types: HTTP(S), keyword, ping, port, SSL, heartbeat | |||
| Confirmation re-checks before alerting | |||
| SSL expiry warnings at 30, 14 and 7 days | |||
| Email, Slack, Discord, Teams, Google Chat and webhook alerts | |||
| Incident timeline, acknowledgement and comments | |||
| Maintenance windows | |||
| Status pages | 1 | Unlimited | Unlimited |
| Custom domains for status pages | – | ||
| Team members with roles | Owner only | Unlimited | Unlimited |
| Notify-only alert contacts | |||
| REST API | |||
| MCP server for AI agents | – | ||
| Raw check history | 7 days | 7 days | Custom |
| Priority support and onboarding | – | – |
Upcertain is in early access. Billing is not enabled yet, so plans are assigned from your account settings. We will announce prices before any billing starts, and nothing is charged without your agreement.
Yes. Switch between Basic and Team any time from Account, Plan & usage. Before the change applies we show exactly what happens: on a downgrade, monitors over the limit are paused (oldest first) and faster intervals are raised to the plan's minimum; upgrading again restores the intervals.
Each URL, keyword, ping, port, SSL or heartbeat check you create is one monitor. Paused monitors do not count toward the active limit.
When a check fails, Upcertain re-checks before opening an incident, so a single dropped request does not alert anyone. You can set how many failed checks in a row are needed per monitor.
Business is for agencies and platforms that need more monitors, faster intervals or other custom limits. Tell us what you need and we set the limits on your account.
Account data is stored in a Supabase Postgres database in the Seoul (ap-northeast-2) region, with every account separated by row-level security. See the privacy policy for details.
Something else? Talk to us.