Plans, limits and retention
Three plans. Pro and Business differ only in numbers, never in which capabilities exist, which is a rule the build enforces rather than a promise. Everything below is generated from the same table the server checks permissions against, so this page cannot disagree with what your account actually does.
Prices
Free
Free
3 monitors, 7 days of history.
Pro
£7 /month
25 monitors, 30 days of history.
Business
£19 /month
100 monitors, 90 days of history.
Everything, side by side
| Capability | Free | Pro | Business |
|---|---|---|---|
| Monitors | 3 | 25 | 100 |
| Fastest uptime check | every 5 min | every 1 min | every 1 min |
| History retention | 7 days | 30 days | 90 days |
| Latency analytics window | 7 days | 30 days | 90 days |
| Metric rules per monitor | 2 | 5 | 5 |
| Run-log excerpt | 4 KB | 16 KB | 64 KB |
| Fleet monitors | no | no | yes |
| Fleet instances | — | — | 500 |
| Cron expression schedules | no | yes | yes |
| SSL expiry alerts | no | yes | yes |
| Keyword checks | no | yes | yes |
| Degraded threshold | no | yes | yes |
| Repeat alerts while down | no | yes | yes |
| Delay before first alert | no | yes | yes |
| Escalation | no | yes | yes |
| Maintenance windows | no | yes | yes |
| Signed webhooks | no | yes | yes |
| Slack & Discord formatting | no | yes | yes |
| Incidents | no | yes | yes |
| Publish incidents | no | yes | yes |
| Public status page | no | yes | yes |
| Status badges | no | yes | yes |
| Metric baselines | no | yes | yes |
| Schedule-aware baselines | no | yes | yes |
| Baseline overrides | no | yes | yes |
| Error grouping | no | yes | yes |
| REST API write access | no | yes | yes |
| Support assistant | no | yes | yes |
| Assistant questions per day | — | 30 | 100 |
| Assistant questions per month | — | 400 | 1,500 |
| Assistant history kept | 7 days | 30 days | 90 days |
Retention
Pings, run records and uptime check results are pruned at the retention length for your plan: 7 days on Free, 30 on Pro, 90 on Business. Pruning is automatic and cannot be turned off.
Rolled-up daily uptime and latency survive longer, for a year, so the 90-day history on a status page keeps working after the individual pings behind it are gone. Incidents, state changes and alert history are also kept for a year.
One exception is worth knowing: if a monitor or fleet has a completion budget with a window longer than your retention, the run history the budget is computed from is kept for the whole window. A 90-day budget on a 30-day plan would otherwise measure 30 days and report the number as if it covered 90.
Upgrading
- Open Billing and choose a plan. Checkout is handled by Lemon Squeezy; card details never reach PulseWatch.
- The new entitlements apply within about half a minute of the payment confirming.
- Confirm it worked: the billing page names your plan and where it came from, and controls that were previously unavailable become editable.
Monitors that were auto-paused by a previous downgrade are resumed automatically, and only those. Monitors you paused deliberately stay paused.
Downgrading and cancelling
Nothing is deleted when you drop to a smaller plan. What happens instead:
- If you are over the monitor cap, the oldest active monitors are paused until the count fits and the newest keep running. They are marked so an upgrade resumes exactly those.
- Channels the new plan does not include stop receiving alerts. They are not deleted.
- Status pages and badges stop serving. The slug is kept.
- History beyond the shorter retention is pruned on the next housekeeping pass. Export first if you need it.
- Cancelling leaves the account on Free rather than closing it. Deleting the account is a separate, explicit action in settings.
Export before you need it
Settings has an export of your monitor configuration, and the REST API can read pings and check results on every plan, including Free. Writing needs Pro or above.
curl -fsS -H "Authorization: Bearer <api-key>" \ "https://pulsewatcher.up.railway.app/api/v1/monitors" > monitors.json
What can go wrong
Monitors paused themselves
A downgrade took you over the cap. Upgrade to resume them, or delete the ones you no longer need and unpause the rest.
Alerts stopped after a plan change
A Telegram or webhook channel is attached to a monitor and the plan no longer includes it. Attach an email channel, which every plan has.
Older history disappeared
Retention. It applies from the moment the plan changes, not at the next renewal.
The billing page shows a plan you are not paying for
An operator granted it. The page says so explicitly, and your purchased plan is tracked separately, so removing the grant returns you to what you actually pay for rather than to Free.
The check interval will not go below five minutes
That is the Free floor. Pro and Business allow 60 seconds.
Related
- FAQ for questions about billing and the product in general.
- REST API for exporting your data.
- Troubleshooting when something stopped working after a plan change.