🔢 Track every dependency in your stack
Free watches 5 vendors. Pro watches 50. Most stacks depend on 20+ third-party services, and you don't get to pick which one breaks first.
Pricing
Free for solo devs. Pro for teams that own production.
No sales calls, no contracts. Pro trial requires no card and rolls to Free if you don't add one.
Free
$0 forever
For solo devs. Fast setup, no card.
- 5 monitors
- 1 team seat
- 15 notifications per month
- 30 days of incident history
- Email, Slack, Discord, webhooks
- Component-level filtering
- Notification groups + severity filters
Most popular
Pro
$15 / month
For teams that get paged when their vendors break.
- 50 monitors (10× Free)
- Unlimited notifications
- 1 year of incident history + exports
- MCP endpoint for Claude, Cursor, Cline
- 10 team seats
Why teams upgrade to Pro
🔔 No notification cap during a busy week
Free caps at 15 alerts per month. Fine for a quiet vendor. Not fine when AWS, Stripe and Datadog all have a bad Tuesday. Pro is uncapped.
📒 1 year of history for the retro
Free keeps 30 days. Pro keeps a year, so when the postmortem asks "did Stripe have issues last quarter?", you can answer. CSV or JSON exports for your runbook.
🤖 AI assistants that know what's broken
Pro unlocks the MCP endpoint. Plug it into Claude or Cursor and ask "is GitHub down?". Real-time answers across 6,000+ providers.
What's in each plan
Side-by-side breakdown. Every feature listed is on both plans unless explicitly limited.
| Feature | Free | Pro |
|---|---|---|
Monitors One per provider, with optional component filter | 5 | 50 |
Team members Users on the same account | 1 | 10 |
Notifications per month Email, Slack, Discord and webhook combined | 15 | Unlimited |
Incident history For postmortems, retros, SLA reports | 30 days | 1 year |
Email alerts Sent from a verified domain. No spam folder. | ✓ | ✓ |
Native Slack app OAuth install, Block Kit messages, /pingoru slash command | ✓ | ✓ |
Native Discord integration Rich embeds, no OAuth required | ✓ | ✓ |
Generic webhook POST signed JSON to Teams, Mattermost, anywhere | ✓ | ✓ |
Notification groups Bundle recipients and filters into one routing unit | ✓ | ✓ |
Component-level filtering e.g. "only alert when EC2 us-east-1 degrades" | ✓ | ✓ |
Per-event severity filters Opened, updated, resolved by severity | ✓ | ✓ |
Maintenance calendar Scheduled work across every monitored vendor | ✓ | ✓ |
CSV + JSON exports For your data warehouse, BI tool, or audit | Last 30 days | Full 1 year |
Per-incident notification preferences Different recipients for different vendors or severities | ✓ | ✓ |
MCP endpoint Pingoru in Claude Desktop, Claude Code, Cursor, Cline, Zed, Goose | — | ✓ |
Priority email support Direct line during incidents. Same-day reply. | — | ✓ |
Pricing FAQ
What is a "monitor"?
A monitor is one provider you watch, plus your alert preferences for it. Free includes 5, Pro includes 50. You can point two monitors at the same provider with different filters. For example, one for AWS EC2 us-east-1 alerting on anything, and another for AWS EC2 eu-west-1 alerting only on major outages.
How does the 15-notification-per-month limit on Free work?
Each alert that goes out (email, Slack message, Discord embed, or webhook POST) counts as 1 toward the cap. The counter resets at the start of each calendar month. If one incident fires opened, two updates, and a resolved, that's 4 notifications. Most vendors have far fewer than 15 incidents a month, so a single-monitor Free user rarely hits the cap.
What happens when I hit the notification cap on Free?
Pingoru keeps watching providers and recording incidents in the dashboard. It just stops sending alerts for the rest of the month. The cap resets at the start of next month, or you can upgrade to Pro any time for unlimited notifications.
What's a "team seat"?
One user account on the team. Free includes 1 seat (the account owner). Pro includes 10. Invite teammates by email and they set their own password. Everyone on the team sees the same monitors, notification groups, and incident history. Useful for on-call rotations where "who saw the alert?" matters.
How is "incident history" different between Free and Pro?
Free retains 30 days of incidents. Pro retains a full year, so you can answer postmortem questions like "how often has Stripe had issues this year?" or compile vendor-reliability reports for an audit. CSV and JSON exports follow the same window.
Can I upgrade or downgrade anytime?
Yes. Upgrades take effect on the next page load. Downgrades to Free take effect at the end of your current billing period; you keep Pro features through the period you've paid for. No annual contract.
Do you offer annual billing?
Not yet, monthly only. We may add annual with a small discount later. If you'd prefer to pay annually now, email [email protected] and we'll set it up.
What payment methods do you accept?
All major credit and debit cards via Stripe. Account billing lives at /app/plan once you're signed up.
Can I add more than 50 monitors on Pro?
If you need to track more than 50 vendors, email [email protected] and we'll work out a custom tier. There's no published Enterprise SKU. We'd rather size it to your use case than guess.
Evaluating Pro for a team? Email [email protected].
Happy to walk you through it, answer questions, or set up a
longer trial.
Other questions? [email protected]