Pricing for one project, ten, or fifty
One plan per organisation covering uptime monitoring, cron monitoring, privacy-oriented analytics and error tracking, organised around the same projects. Allowances are enforced, not aspirational: going over blocks the next create with an upgrade prompt instead of appearing on your invoice.
Uptime, cron, errors, analytics. $5 a month.
Flat, per organisation. No seats, no meters, no surprise line on the invoice.
Try PostDeploy free for 30 days
No card required. Every feature on Pro limits from the first minute, then keep going from $5/month.
Then Indie $5 a month, Pro $29 a month, Scale $99 a month.
Indie
Most picked$5/ per month
Flat, per organisation.
The permanent entry point: monitoring, analytics and error tracking for everything you build, on one small bill.
One developer, personal projects, small production apps, tiny SaaS
- 3 projects, 1 member
- 20 uptime and API monitors
- 20 cron and heartbeat jobs
- 5 minutes checks
- 100k analytics events a month
- 10k error events a month
Pro
$29/ per month
Flat, per organisation.
Faster checks, more monitors and longer retention, so the product your customers depend on stays watched.
A product with customers
- 10 projects, 5 members
- 100 uptime and API monitors
- 200 cron and heartbeat jobs
- 1 minute checks
- 500k analytics events a month
- 50k error events a month
Scale
$99/ per month
Flat, per organisation.
Room for the whole team and the traffic that comes with growth: more projects, members and events across the board.
A growing team and a higher-volume product
- 50 projects, 20 members
- 300 uptime and API monitors
- 1,000 cron and heartbeat jobs
- 30 seconds checks
- 2 million analytics events a month
- 250k error events a month
Every allowance, one table
Every enforced allowance, in one table. If a capability is not listed here, it is not part of the product today.
| Feature |
Indie
$5
|
Pro
$29
|
Scale
$99
|
|---|---|---|---|
| Organisation | |||
|
Projects
|
3 | 10 | 50 |
|
Members
|
1 | 5 | 20 |
| Monitor | |||
|
Uptime and API monitors
HTTP and HTTPS, API endpoint, keyword and response, TCP port, and SSL expiry on a monitored endpoint.
|
20 | 100 | 300 |
|
Cron and heartbeat jobs
A scheduled job pings a URL on success; PostDeploy alerts you when the ping is late.
|
20 | 200 | 1,000 |
|
Fastest uptime interval
|
5 minutes | 1 minute | 30 seconds |
|
Detailed uptime samples
Individual check results. Older results are folded into daily uptime history.
|
7 days | 30 days | 90 days |
| Observe and Measure | |||
|
Analytics events per month
Accepted Measure pageviews and analytics API events. Known bots, rejected payloads, retries and filtered events are not counted.
|
100,000 | 500,000 | 2 million |
|
Error events per month
|
10,000 | 50,000 | 250,000 |
| Alerts and access | |||
|
Email, Slack and Discord alerts
|
Yes | Yes | Yes |
|
Webhook and Telegram alerts
|
Yes | Yes | Yes |
|
API requests per minute
|
60 | 300 | 600 |
|
Audit log retention
|
30 days | 90 days | 365 days |
What those plans buy
Everything on the plan is live
Monitor, Observe and Measure are all live today, on the same plan. The table above is the whole offer.
Pricing questions
What does a paid plan cost?
Indie is $5 a month, Pro is $29 and Scale is $99. Each is one flat price per organisation: no seats, no meters and no overage line on the invoice.
What happens after the 30 days?
Without a subscription the organisation becomes read-only: every chart, incident and error stays visible, but writes and ingest stop. Data is kept 30 more days, then purged. Subscribing at any point restores everything.
What counts as an uptime monitor?
One polled check: HTTP or HTTPS, an API endpoint, a keyword or response check, or a TCP port. SSL certificate expiry is checked as part of an https monitor rather than counting as its own monitor. Browser and multi-step transaction checks are not part of the monitor allowance and are not offered.
What counts as a cron job?
One scheduled job you are watching. The job pings a heartbeat URL when it finishes successfully, and PostDeploy alerts you when an expected ping does not arrive. Cron jobs have their own allowance, so watching a scheduled task never uses up an uptime monitor.
What counts as an analytics event?
Accepted pageviews and custom events. Known bots, rejected payloads, retries and filtered events are not counted against your allowance.
How long is data kept?
Detailed uptime samples, meaning individual check results, are kept for 7 days on Indie, 30 on Pro and 90 on Scale. Beyond that window checks are folded into daily uptime history rather than kept sample by sample.
What happens if I go over an allowance?
Creating a monitor, job, project or member beyond your plan is blocked with an upgrade prompt rather than billed as overage. Existing resources keep running.
What does PostDeploy not do?
No on-call rotations, no SMS and no voice escalation, and no logs, traces or session replay. Checks run from one region. PostDeploy tells you what broke and when, on email, Slack and Discord on every plan, including the trial, plus webhooks and Telegram.
Where do the checks run from?
One AWS region. There is no multi-region confirmation of a failure, so a network problem between that region and your server can read as downtime.
Ship your next project with one toolkit, not three.
Start on the trial, then pick Indie, Pro or Scale when a project outgrows the one before it. No credit card to start.
Start your 30-day free trial