Teams & billing
Monitors belong to a team, not a person. Plans buy reach: pages, speed, and seats. Nothing is priced per check or per alert.
Roles and permissions
- Members do the daily work: create and edit monitors, run checks, set up notification channels, and read every timeline.
- Admins do all of that, and can also delete monitors, manage invitations and member roles, and create or revoke API keys.
- Owners do everything admins do, plus billing. Every team has one from the moment it is created.
Invitations go out by email with a link that expires. Monitors, alert history, channels, and API keys all belong to the team, so nothing is lost when someone leaves.
Plans and limits
| Plan | Price | Monitors | Fastest checks | Team members | Check tiers |
|---|---|---|---|---|---|
| Free | $0 | 3 | Daily | 2 | Exact diff, semantic |
| Pro | $25/mo | 25 | Every 15 minutes | 5 | All three |
| Scale | $49/mo | 100 | Every 5 minutes | 15 | All three |
| Business | $99/mo | 500 | Every 2 minutes | 100 | All three |
Checks, alerts, and evidence are never metered. No credits, no “AI actions”, no per-check pricing on any plan. Full pricing detail and FAQ: /pricing.
Upgrades, downgrades, cancellation
- Upgrading charges right away and unlocks the new limits immediately. Plan changes run through the Stripe customer portal (Settings → Billing) and prorate automatically.
- Downgrading deletes nothing. Monitors keep running, with check intervals clamped to the new plan's fastest. If you end up over the new monitor limit, the monitors you have keep running, but you cannot create new ones until you are back under it. A monitor on a tier the new plan does not include keeps its configuration and starts again once the plan allows it.
- Canceling keeps your access through the end of the paid period, then drops you to Free limits. Account deletion removes data from active systems within 30 days and from backups within 60. See the terms and privacy policy.
API keys
Owners and admins create named API keys in Settings → API. A key is scoped to one team, shown once when you create it, stored hashed, and revocable at any time. Revoked keys stay in the list so there is an audit trail. Full reference: API documentation.