Enterprise DNA

Instead of incident.io

Paying for incident.io reviews? Own the review workflow.

We build your incident review system around your services and team rules, map your incident.io records and run your version. Your urgent paging service stays in place while we move the review work.

incident.io Pro response lists US$25 per user per month. That is US$300 per user over twelve months, before the separate on-call add-on.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

Separate the review work from the response bundle

incident.io sells response software per user, with on-call priced separately. Decide which work needs a live response service and which records you want to own. Figures below come from <a href="https://incident.io/pricing">the vendor pricing page</a>, checked 16 October 2026.

paid

Pro response seats

Pro response is US$25 per user per month. The per-person charge follows the people using the service.

notifications

On-call is a separate item

Pro lists on-call at an additional US$20 per user per month. Our free review desk does not deliver pages.

assignment

A post-incident process

Pro includes a configurable post-incident process and post-mortems. The owned version records your review decisions and evidence.

insights

Advanced insights

Pro includes advanced insights and custom dashboards. The free version answers the record questions shown below.

lock

Private incidents and policies

These appear in the Pro offer. Restricting sensitive records in your version needs a deployment designed for your team.

support_agent

Enterprise service commitments

Enterprise uses a custom proposal. Review its service commitments separately from the cost of keeping your review records.

The owned review desk

An outage is resolved. The follow-up work still has an owner.

Review deadlines

Know which reviews need finishing

A resolved incident stays visible until someone records the review and finishes its corrective actions.

  • check Name the affected service and accountable owner
  • check Set the review date using your own policy
  • check See overdue reviews beside unfinished actions
  • check Keep resolved, reviewed and closed as separate states

Corrective work

Keep the promised fix attached to the incident

Every follow-up has an owner and due date. Completion needs evidence; an open action prevents closure.

  • check List actions in due-date order
  • check Record the evidence behind each completion
  • check Find repeated incidents on services with overdue work
  • check Read the incident history before drafting a review brief

Evidence

Carry the facts into the review pack

Dated events, the recorded cause and the lessons stay together. Produce internal documents in your business name.

  • check Retain the original imported row for comparison
  • check Record who made each local change
  • check Produce a review pack and corrective action brief
  • check Flag missing chronology and overdue retention reviews

Your rules

Ask questions across your own records

Review the week across services, incidents and actions. Change the fields and rules when your operating process changes.

  • check Compare recorded resolution times by service
  • check Find the service with repeated incidents and late fixes
  • check Read three reports in your own colours
  • check Keep a complete archive of records and local change history

Make it yours

Design your own incident.io replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from incident.io. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your incident.io replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your incident.io data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Incident Reviews for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Incident Reviews for Claude Code

Connected to your own database

Which incident reviews still need finishing?

DEMO-103

Me se
Daily report delayed
Rvice ow
Reporting
Ner st
Theo
Ate re
reviewed
View_due da
2026-10-03
Ys_overdue op
13
En_actions
1

DEMO-101

Me se
Order queue stalled
Rvice ow
Order gateway
Ner st
Mira
Ate re
resolved
View_due da
2026-10-13
Ys_overdue op
3
En_actions
2

DEMO-102

Me se
Order retries growing
Rvice ow
Order gateway
Ner st
Mira
Ate re
open
View_due da
2026-10-23
Ys_overdue op
-7
En_actions
0

Ask it anything

Ten questions your review records can answer

Each question is supported by the working free version. These are examples from your records, not a claim that incident.io cannot report the same facts.

chat_bubble Which resolved incidents missed their review date?
chat_bubble Which corrective actions are overdue, and who owns them?
chat_bubble Which service has multiple incidents in the last 30 days and overdue actions?
chat_bubble Which imported incidents still need a local owner and classification?
chat_bubble Which review cycles are unfinished even after a written review?
chat_bubble Which services have the longest recorded average resolution time?
chat_bubble Which records lack any local timeline evidence?
chat_bubble Which incident records have passed their retention review date?
chat_bubble Who recorded a resolution, review or action completion?
chat_bubble What did the old system say before local verification?

Switching

How to switch from incident.io

A move usually involves exporting incident summaries, mapping your fields and review rules, then checking the imported history before you switch workflows.

  1. 1

    Export your incident summaries

    Export the incident summaries from incident.io in CSV format. The available export options depend on your account, so check with incident.io if you cannot find the right export. Decide which history to bring across. Keep private incidents out of the initial export if you are using the free version, which has no individual access controls. Timelines, attachments, follow-ups and post-mortem contents need separate mapping.

  2. 2

    Map and preview the import

    Match the column headings in your export to the fields used by Incident Reviews for Claude Code. Preview the import before loading records, then reconcile the counts so you know what will come across. The import retains each original row, skips identical repeats and stops if it finds changed rows or reference collisions. Imported records start unverified, so an old status is not proof that a review is complete.

  3. 3

    Review the import checks

    Check the imported records for missing classification, chronology and review evidence, as well as missed review dates. Resolve changed rows and reference collisions before trying the import again. Assign local owners and classifications where needed, and verify the evidence against your own records. These checks flag gaps for your team to assess. They do not certify compliance or decide reporting duties.

  4. 4

    Run both workflows briefly

    Keep incident.io available while your team works through reviews and follow-ups in the new database for a short period. Compare the records, owners, review dates and evidence, and note anything that is missing or mapped incorrectly. Keep your paging and alert services operating too. Incident Reviews for Claude Code handles incident records, reviews and follow-ups, not urgent alerts or on-call schedules.

  5. 5

    Switch off the old workflow

    When your team has checked the imported history and can complete its review work in the new workflow, stop using incident.io for that work. Confirm separately that paging, alert delivery and any other services you rely on remain covered. Keep the exported records protected, since exports and other incident documents contain incident data.

construction

Where the real effort goes

The real work is usually mapping your own export fields and review rules, then deciding how much history to bring across. Incident summaries can be imported after the headings are mapped, but timelines, attachments, follow-ups and post-mortem contents need separate mapping. Imported records also need local verification. If you have Enterprise DNA run the replacement, they do this mapping and configure the agreed fields and rules.

Not ready for a call?

Get your incident.io switch plan by email

We will send you the step-by-step plan for moving your business off incident.io, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Use the free version, have yours built, or have it run

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and open it in Claude Code, Codex, OpenCode or Cursor
  2. 2 Install dependencies and run npm run demo
  3. 3 Export incident.io summaries, map the CSV headings and preview the import
  4. 4 Reconcile the records, then classify them and start your review workflow
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check We map your incident.io export and check the records with you
  • check Your services, owners, review dates and evidence rules
  • check A web front end and agreed connections where your team needs them
  • check A different stack and access arrangements when your business needs them
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check We install your review system and bring across the agreed records
  • check We connect it with the tools your team uses
  • check We operate backups, access and the agreed review process
  • check It runs inside your Omni Command Centre alongside the rest of your business
Book a call with Sam

Questions

Instead of incident.io, answered

Does this replace the service that wakes someone up? expand_more

The free version handles incident records, reviews and follow-ups. It does not deliver urgent pages or run on-call schedules. Keep those services operating. Enterprise DNA scopes the connections and service requirements for your version before any switch.

What happens to our incident.io history? expand_more

The free version imports incident summaries from your CSV export after the headings are mapped. It preserves each original row, skips identical repeats and stops changed rows for reconciliation. Imported records start unverified. Full timelines, attachments, follow-ups and post-mortem contents need separate mapping, which we scope with you.

Will it prove that we complied with our incident policy? expand_more

It checks that records have classification, chronology and review evidence, and flags missed dates. The review dates are your policy. These checks do not certify compliance or decide reporting duties. Your team still judges the evidence and any obligations.

Can we keep sensitive incidents private? expand_more

The free version is for one trusted team and has no individual access controls. Exclude private incidents from the initial export. Enterprise DNA can build and operate the access arrangements your version needs before sensitive records move across.

What do we pay Enterprise DNA? expand_more

One setup fee, then a retainer for the agreed ongoing work. We look at your records, review process, connections and operating needs before scoping it. The free version has no licence fee; hosting, agent subscriptions and operating time remain costs.

Own the review work after the outage

Book 30 minutes with Sam. Bring your incident.io bill and one example of an unfinished review. We will look at the records you need, the response service you keep and the version Enterprise DNA can build and run for you.

Book 30 minutes with Sam Get the free version

Incident Reviews for Claude Code is free and open source, published by Enterprise DNA.

Done paying for incident.io?

Get your version built