Pricing
Per-seat pricing for on-call and incident response.
Five plans, one baseline platform. Prices are list prices per user per month, and only a few features are tied to plan.
Trial
$0/ user / mo
up to 5 seats
Starter
$9/ user / mo
up to 10 seats
Pro
$15/ user / mo
up to 50 seats
Business
$29/ user / mo
up to 200 seats
Enterprise
Custom
seats negotiated
Five plans
Evaluation
$0/ user / mo
no card required
Evaluation · 14 days · up to 5 seats · no card
- Seats
- 5
Pro
$15/ user / mo
list price
For teams that want API access and related-incident insights.
- Seats
- 50
Business
$29/ user / mo
list price
For a growing organisation. The first paid plan with email-to-alert: an inbound alert address per workspace.
- Seats
- 200
Enterprise
Custom
negotiated
For multiple teams or workspaces, with seat caps and terms arranged individually.
- Seats
- Custom
Paid plans are activated directly by the CallHeim team. Seat caps are the published plan limit: adding a user beyond a plan’s seat limit is refused (Trial 5, Starter 10, Pro 50, Business 200); existing users and paging are not affected.
Included everywhere
What every plan includes.
Alert ingest, noise reduction, escalation, scheduling, incident response, the status page and analytics are on every plan, not sold as an upgrade.
- HTTPS alert ingest. Send alerts to your integration URL over HTTPS, in the CallHeim alert format or through a field mapping you define. Accepted alerts are queued durably and processed asynchronously.
- Alert sources. A catalogue of alert sources (early access), each with a payload mapping for that tool’s webhook format and its own setup page, ready to connect.
- Duplicate collapse. Repeats of the same alert collapse onto one incident while they keep arriving within five minutes of each other. The thresholds behind the noise handling are published: a 300-second dedup window, a flap threshold of 4 state changes in 600 seconds, and title-similarity grouping at a default of 0.6.
- Escalation policies. Up to 8 tiers with per-tier timeouts from 1 to 240 minutes and a mandatory fallback. An unanswered tier times out and advances.
- On-call schedules. Layers, overrides, weekday and hours restrictions, follow-the-sun templates, time off, approved shift swaps and coverage-gap detection, in any IANA time zone.
- Incident lifecycle and timeline. Four states and five severities, role-gated actions, and a timeline with no edit or delete in the product.
- Public status page. Every workspace has a public status page that your team updates by hand.
- MTTA and MTTR analytics. MTTA and MTTR (mean, p50, p90) computed from each incident’s own timestamps, on every plan.
- Severity suggestions. A suggested severity with the matched terms shown; a person applies it. Suggestions never change severity or page anyone.
- E-mail paging. Live in early access. Incident pages go out by e-mail with an acknowledge link, and sent and delivered status is recorded on the incident.
Tied to plan
A few features are tied to plan.
Some features are tied to plan: the REST incident API and related-incident insights on Pro and above; email-to-alert (per-workspace inbound alert e-mail addresses) on Trial, Business and Enterprise, not Starter or Pro.
| Feature | What it is | Included on |
|---|---|---|
| REST incident API | List and get incidents, and acknowledge, resolve or close them through the API, with API keys. | ProBusinessEnterprise |
| Related-incident insights | Related-incident and responder insights, drawn from your own incident history. | ProBusinessEnterprise |
| Per-workspace inbound alert address | Each workspace gets its own inbound e-mail address; mail sent to it becomes an alert. | TrialBusinessEnterprise |
How we price
Noise handling and analytics are not add-ons.
Every plan is priced per seat, not per event or per alert. The features that cut noise and the analytics that measure your response are baseline on every plan.
Alerts are not metered or billed. Seat caps are the only published plan limits.
Questions
About pricing and buying.
How are paid plans activated?
Paid plans are activated directly by the CallHeim team.
What happens when the trial ends?
Once the trial ends, adding users is refused until a paid plan is in place; existing users keep working and webhook alerts keep paging. Email-to-alert keeps working for 14 days, then new alert e-mail is refused.
Are alerts metered?
Alerts are not metered or billed. Seat caps are the only published plan limits.
Is there an annual discount?
List prices are per user per month, and no annual discount is published. Paid plans are activated directly by the CallHeim team.
Which plan do I need?
Start by seat count: Starter covers up to 10 seats, Pro up to 50, Business up to 200. Move up for the REST incident API and related-incident insights (Pro). Email-to-alert, a per-workspace inbound alert address, is on the Trial, Business and Enterprise plans; a Trial that moves to Starter or Pro does not keep it.
Try it on one service, and page yourself before you page your team.
CallHeim helps teams stay in control when critical systems are not. Explore the platform, connect one source, and send yourself a test page by e-mail.
Early access · every workspace starts with a 14-day trial for up to 5 seats, no card required