Plans and capabilities
How Uptime, On-call, and Status pages are enabled and enforced in a workspace.
One workspace, three capabilities
HowlOps separates product access into three capabilities:
| Capability | Covers |
|---|---|
| Uptime | Monitors, heartbeats, check frequency, regions, screenshots, and history |
| On-call | Schedules, escalation, inbound alerts, and paging methods |
| Status pages | Public or restricted pages, domains, branding, and subscribers |
A workspace can use a different plan for each capability. The API resolves the effective limits on the server before a resource is created or changed. The browser does not decide whether an operation is allowed.
Prices, included usage, and plan comparisons change independently of this documentation. Use the pricing page as the commercial source of truth.
What a capability check affects
Capability checks can control a numeric quota, such as the number of active monitors, or a feature flag, such as multi-region checks or private status pages. A rejected API request returns an error instead of silently changing the requested configuration.
Some values are shown directly in the product. For example, the monitor form reads the current minimum interval and the plan screen reads the live capability catalog. Prefer those values over numbers copied into scripts or runbooks.
Upgrades and downgrades
An upgrade is applied after checkout succeeds. A downgrade is normally scheduled for the end of the current billing period, so the already-paid capability remains available until then.
When a lower entitlement takes effect, HowlOps reconciles resources against the new limits. Excess monitors or heartbeats can be paused, and features that are no longer entitled stop being effective. The resources are not deleted. Review the impact shown in Settings → Plan before confirming the change.
Was this page helpful?