Skip to content
IncidentBot

Enterprise incident management software with the controls your security team asks for

IncidentBot holds some of the most sensitive operational data a company has: who is on call and how to reach them, what broke, when, and what was said while it was broken. This page describes how access is controlled, how data is protected and stored, how paging keeps working, and what the Enterprise plan adds.

Audit log

TimeActorEvent
09:12:40Workspace adminSAML single sign-on required for the domain
09:20:05Workspace adminEscalation policy checkout-api updated
10:02:18SCIMUser deactivated
14:12:30CommsStatus page update published: Checkout

Single sign-on with SAML

On Business and Enterprise, responders and stakeholders sign in through your identity provider with SAML 2.0 single sign-on. You prove your email domain with a DNS TXT record and keep your own multi-factor policy in the identity provider. Once an admin requires SSO, people removed from your directory can no longer sign in.

  • SAML 2.0 SSO with identity providers such as Okta, Microsoft Entra ID and Google Workspace.
  • Optional enforcement: an admin can require SSO for members in your verified domain. The workspace owner and members with other addresses keep email code sign-in.
  • No passwords anywhere: without SSO, people sign in with a one-time code sent by email.

SCIM provisioning on Enterprise

SCIM 2.0 keeps the user list in step with your directory. New people are created, their details stay up to date, and people who leave are deactivated without anyone opening a ticket.

Roles and permissions

Every plan has three roles. Admins manage the workspace, responders can be on call and act on incidents, and stakeholder viewers follow along read-only and are never billed.

An audit log for every change that matters

On Business and Enterprise, the audit log records who did what and when. Entries cannot be edited by anyone, including administrators.

  • Schedules, overrides and escalation policies.
  • People, role changes and SSO sign-ins.
  • Integration secrets set or cleared.
  • Status pages, incidents and billing.

How we protect incident data

Security practice is described here in plain terms, so you can check it against what the product does.

  • Encryption in transit: connections to the application use TLS.
  • Integration secrets (Slack, Jira, Linear, Twilio and SAML settings) are stored encrypted and are not shown again after saving.
  • Customer data is separated per workspace, and every request is checked against the workspace it belongs to.

What data IncidentBot holds

Alert payloads your monitoring tools send, on-call schedules and escalation policies, contact details used for paging (email, phone number for SMS and voice, mobile push tokens), incident records and timelines, status page content, postmortems and action items. In Slack, the bot reads messages only in the incident channels it creates or is invited to, so it can build the timeline. It does not read the rest of your workspace.

Where your data is stored

Workspace data is stored on servers in the European Union (Germany), on every plan. That covers incident records, timelines, schedules, alert payloads and status page content.

Custom retention

By default, incident history is kept for as long as your subscription is active, because trends in incident tracking depend on it. Enterprise can set one retention period, from 30 to 3650 days. Resolved incidents older than that period are deleted, together with their timeline and raw alerts.

Paging that does not depend on one channel

Paging is the part of incident management software that cannot fail quietly, so it never relies on chat alone.

  • Paging does not depend on Slack. If Slack is unavailable, push and email still reach the on-call engineer, and so do SMS and voice through your own connected Twilio account.
  • Engineers acknowledge from wherever the page reaches them, including by replying ACK to the SMS or pressing 1 during the call.
  • Escalation policies keep moving when nobody acknowledges, tier by tier, until someone does. The detail is on on-call management.

Enterprise pricing and setup

Enterprise is bought like every other plan, by card, with nothing to negotiate.

  • 398 USD per user per month, or 199 USD per user per month billed annually.
  • Everything in Business, plus SCIM provisioning and custom data retention.
  • Invoices and receipts are in the billing portal.
  • Schedules, overrides and escalation policies import from PagerDuty and Opsgenie under Integrations, on every plan. See the Opsgenie alternative page for the migration steps.

Questions from security reviews

Which plan includes SSO?

SAML single sign-on and the audit log are included in Business and Enterprise. SCIM provisioning and custom data retention are on Enterprise. Every plan and price is on the pricing page.

Do stakeholders need accounts with the same controls?

Stakeholder viewers sign in the same way as everyone else, through SSO when your workspace uses it. They are read-only and are not billed as seats.

Can we evaluate before a security review is finished?

Yes. The incident simulator demo runs in your browser on a sample scenario and needs no account and no company data, so engineers can evaluate the workflow while the review runs.

Where do we send security questions?

Send them to [email protected] with the plan you are evaluating.

Bring your security questions

Enterprise is 398 USD per user per month, or 199 USD billed annually, and starts by card on the pricing page. Send your security questions to [email protected] and the answers come back by email.

See pricing