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

The line under every rung is the baseline platform — alert ingest, noise reduction, escalation, scheduling, incident response, the status page and analytics are on every plan. The rungs above it are what changes: the price, the seat cap, and a small number of features tied to plan.

Five plans

  • Trial

    $0/ user / mo

    no card required

    14 days, up to 5 seats, no card required.

    Seats
    5
  • Starter

    $9/ user / mo

    list price

    For a small team that owns its own pager.

    Seats
    10
  • 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 organization: email-to-alert, audit-log export, an IP allowlist for administrative changes and private status pages.

    Seats
    200
  • Enterprise

    Custom

    negotiated

    For multiple teams or organizations, with seat caps and terms arranged individually.

    Seats
    Custom

Paid plans are invoiced and activated directly by the CallHeim team; ask from Billing in the app. 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 catalog of alert sources on every plan, each with a payload mapping for that tool’s webhook format and its own setup page.
  • Duplicate collapse. A repeat of the same alert attaches to its open incident in the same service with no new page: at any age when the sender supplies its own dedup key, and within 24 hours of the incident being triggered when the identity is only the e-mail subject or alert title. A P1 or P2 repeat on an open P3 to P5 incident opens a new incident and pages, and once an incident is resolved or closed the next repeat opens a new one. The rules behind the noise handling are published. A repeat attaches to its open incident, within 24 hours of the incident opening unless the sender supplies its own dedup key. A series that changes state 4 times in 600 seconds is treated as flapping. Near-identical titles from the same source and service group together at a similarity of 0.6. Title grouping can be switched off for your organization.
  • 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 for the next 7 days, in any IANA time zone, with a private calendar feed per schedule.
  • 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 organization has a public status page, and your team posts the updates. Additional pages for different audiences show only the services you add to them, with their posts and scheduled maintenance, and visitors can subscribe by e-mail or with a Slack webhook.
  • MTTA and MTTR analytics. MTTA and MTTR (mean, p50, p90) from each incident’s own timestamps, plus alert-volume heatmaps and on-call load and fairness reports, on every plan. Reports export as CSV or JSON.
  • Severity suggestions. A suggested severity with the matched terms shown; a person applies it. Suggestions never change severity or page anyone.
  • E-mail paging. Incident pages go out by e-mail on every plan, each with a signed acknowledge link, and sent, delivered and bounced status is recorded on the incident.

See the full platform →

Tied to plan

A few features depend on your plan.

Features tied to plan
FeatureWhat it isIncluded on
REST incident APIList and get incidents, and acknowledge, resolve or close them through the API, with API keys.ProBusinessEnterprise
Related-incident insightsRelated-incident and responder insights, drawn from your own incident history.ProBusinessEnterprise
Per-organization inbound alert addressEach organization gets its own inbound e-mail address; mail sent to it becomes an alert.TrialBusinessEnterprise
Audit-log exportDownload the audit log as a CSV or JSON file. The file goes straight to your device, and CallHeim keeps no copy.BusinessEnterprise
IP allowlist for administrative changesAccept administrative changes (role changes, invitations, deactivations, secret rotation, forced sign-out) only from the IP ranges you list. It does not restrict sign-in, the incident console or the REST API.BusinessEnterprise
Private status pageMake the status page visible only to the e-mail addresses you list, through an access link sent to them.BusinessEnterprise
Directory provisioning (SCIM)Your identity provider creates, updates and deactivates members through SCIM 2.0. Roles are set in CallHeim, not by the identity provider.BusinessEnterprise

Audit-log export is a CSV or JSON download of the audit log; the file goes straight to your device and CallHeim keeps no copy. The IP allowlist accepts administrative changes (role changes, invitations, deactivations, secret rotation, forced sign-out) only from the ranges you list; it does not restrict sign-in, the incident console or the REST API. A private status page is visible only to the e-mail addresses you list, through an access link sent to them.

Buying

How buying works.

  1. Start the 14-day trial. It needs no card and covers up to 5 seats.
  2. When you are ready, ask from Billing in the app, or open a request in Help Center with the Billing category. Say which plan and how many seats.
  3. The CallHeim team sends an invoice and activates the plan on your organization.
  • Prices are list prices per user per month. Read-only stakeholders do not take a seat.
  • Alerts are not metered or billed. Seat caps are the only published plan limits.
  • Seat changes, invoices and plan changes go through the same Billing request.
  • Enterprise seat caps and terms are agreed individually. Ask about Enterprise →

Trial

What the 14-day trial includes.

  • Up to 5 seats for 14 days, with no card.
  • Everything every plan includes, listed above, and inbound alert e-mail addresses.
  • Text and phone-call paging, once an organization admin turns SMS and voice on.
  • Help Center, for questions while you evaluate.
  • Not in the trial: the REST incident API and related-incident insights (Pro and above), and audit-log export, the IP allowlist, private status pages and SCIM (Business and above).
  • The importer’s dry run works on the trial. A live import that would take you over 5 seats is refused before anything is written.
  • To evaluate a feature outside the trial, or to take more time, ask from Billing in the app.

Get started in six steps →

How we price

Noise handling and analytics are not add-ons.

Alerts are not metered or billed. Seat caps are the only published plan limits.

Before you decide, see the security and data handling, the alert sources you can connect and the migration guide for PagerDuty and Opsgenie teams.

Questions

About pricing and buying.

How do I buy a paid plan?

Paid plans are invoiced and activated directly by the CallHeim team; ask from Billing in the app.

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, before tax, and no annual discount is published. Enterprise terms are agreed individually.

How do I add more seats?

Each plan has a seat limit (Trial 5, Starter 10, Pro 50, Business 200). To go above it, move up a plan or ask the CallHeim team from Billing in the app; read-only stakeholders do not take a seat.

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), and for audit-log export, an IP allowlist for administrative changes and private status pages (Business). Email-to-alert, a per-organization inbound alert address, is on the Trial, Business and Enterprise plans; a Trial that moves to Starter or Pro does not keep it.

CallHeim

Start on the trial, and page yourself before you page your team.

Start a 14-day trial, connect one alert source and send yourself a test page.

14-day trial · up to 5 seats · no card required