Enterprise DNA

Instead of PagerDuty

Stop renting PagerDuty. Own your on-call planning.

We build your coverage and handover system around your team, bring your PagerDuty assignments across and connect the services you need. We run your version through Omni by Enterprise DNA.

PagerDuty lists its PD Reliability Platform Plus plan at $48,000 a year. Confirm the dollar currency and your own entitlements against your quote.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The subscription under review

Separate the duty records from the wider platform bill

The <a href="https://www.pagerduty.com/pricing/" target="_blank" rel="noopener noreferrer">Plus plan lists $48,000 per year</a>. It includes more than planning. These are bundled capabilities and allowances, not separate charges or a claim that the free version replaces them all.

paid

An annual platform subscription

Plus is a recurring plan. Compare the records you need to own with the live services you still need operated.

group

An included seat allowance

Plus lists 50 seats. Your owned planning database has no per-person licence charge.

event

On-call schedules

PagerDuty includes schedules. Your version starts from the resolved assignments for the period you export.

route

Escalation policies

PagerDuty connects services to people and schedules. Your version checks the recorded coverage at each level.

notifications

Notification delivery

PagerDuty delivers urgent notifications. Required replacement delivery must be built and tested before a live switch.

monitoring

Event capacity

Plus lists an included event allowance, with credits for extra capacity. Your planning review works from prepared records.

Your own operating records

Make the next handover a known plan

Coverage

Find the exact uncovered interval

Inspect the duty plan across every expected escalation level.

  • check Show gaps at the start, middle and end of the review period
  • check Check the exact moment one assignment hands over to the next
  • check Show empty policies as uncovered
  • check Keep inactive responders out of coverage

Workload

See when one person carries competing duties

Review assignment hours without counting the same hour twice.

  • check Combine overlapping intervals for each responder
  • check Show simultaneous duties across different policies or levels
  • check Keep all comparisons in a consistent time reference
  • check Apply your own threshold for a fatigue review

Handover

Leave the next person a checked record

Put the owner, due time and completion evidence beside the work.

  • check List overdue handovers and follow-up actions
  • check Require evidence before marking work complete
  • check Produce duty plans and handover records in your business colours
  • check Draft a private handover with the outstanding coverage gaps

Your rules

Ask across duty and review evidence

Connect your assignments to the review dates and business rules you choose.

  • check Flag imported assignments that still need verification
  • check Review retention dates for responder records
  • check Keep the previous assignment when its times are revised
  • check Add your own fields and questions without waiting for a plan upgrade

Make it yours

Design your own PagerDuty replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your PagerDuty 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 PagerDuty 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 On-call Coverage for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

On-call Coverage for Claude Code

Connected to your own database

Where does Storefront have no first responder?

Storefront

Level
1
From
2026-11-09T00:00:00.000Z
To
2026-11-10T00:00:00.000Z
Hours
24
Responders
R-01
State
covered

Storefront

Level
1
From
2026-11-10T00:00:00.000Z
To
2026-11-10T02:00:00.000Z
Hours
2
State
GAP

Storefront

Level
1
From
2026-11-10T02:00:00.000Z
To
2026-11-11T00:00:00.000Z
Hours
22
Responders
R-02
State
covered

Storefront

Level
2
From
2026-11-09T00:00:00.000Z
To
2026-11-11T00:00:00.000Z
Hours
48
Responders
R-03
State
covered

Ask it anything

Ten questions your own coverage review answers

These examples run against the working demo. They are not claims that PagerDuty cannot answer them.

chat_bubble Where are the uncovered intervals at each escalation level?
chat_bubble Who is assigned at the exact handover boundary?
chat_bubble Which responder has simultaneous duties across policies?
chat_bubble How many unique on-call hours does each responder carry?
chat_bubble Which imported assignments still need verification?
chat_bubble Which policy has no named owner or an overdue review?
chat_bubble Which handover is late and who owns it?
chat_bubble Which responders have overdue retention reviews?
chat_bubble What changed when an assignment was revised?
chat_bubble How many records arrived in each import batch?

Switching

How to switch from PagerDuty

The move involves exporting a chosen period of resolved assignments, checking and reconciling the imported records, then testing replacement paging before you switch off PagerDuty.

  1. 1

    Prepare a complete export

    Ask an authorised PagerDuty administrator for a complete export of resolved on-call assignments for the period you want to bring across. The documented path is an authorised on-calls JSON export with complete pagination metadata. Decide how much history you need before exporting. This brings recorded assignments, not repeating schedule rules, contact methods or notification configuration.

  2. 2

    Load the records safely

    Have the export loaded into the new database, starting with the import preview. Review the preview before completing the import, then load the records. The importer checks the page sequence, keeps the original records as evidence and refuses partial exports. Use a complete export for the period you chose so the review is based on the records you intended to bring across.

  3. 3

    Review flagged records

    Imported assignments start unverified and are flagged for review. Check the records against your actual expected escalation levels and future schedule requirements, and resolve anything the import flags before relying on the review. The import does not bring across repeating schedule rules, contact methods or notification configuration. A recorded assignment shows who is assigned, not that they can be reached.

  4. 4

    Run both systems side by side

    For a short period, keep PagerDuty's paging service operating while you use the database for assignment planning, coverage reviews and handovers. Check uncovered intervals, handover boundaries, competing duties and unfinished handovers against your expectations. Use this period to verify the imported assignments and identify what still needs attention. The database does not send urgent notifications.

  5. 5

    Switch off only after testing

    Do not turn off PagerDuty just because the records have moved. Keep it operating until any required replacement connections, notification delivery, monitoring and recovery have been built and tested. On-call Coverage does not send urgent notifications, so you need a separate replacement paging arrangement if you still require them. Switch off PagerDuty only when that replacement is ready and verified.

construction

Where the real effort goes

The import is only part of the work. Most effort usually goes into mapping your own fields and rules, reconciling expected coverage levels and future schedules, and deciding how much history to bring across. When you have Enterprise DNA run the system, they handle this mapping and reconciliation with you as part of the scoped setup.

Not ready for a call?

Get your PagerDuty switch plan by email

We will send you the step-by-step plan for moving your business off PagerDuty, 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

Do it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and run /weekly-review
  3. 3 Preview a complete PagerDuty on-calls export, then reconcile and import it
  4. 4 Set expected levels, verify assignments and render your duty documents
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your escalation levels, handover rules and review dates
  • check Your PagerDuty assignments mapped and reconciled
  • check Your delivery connections and a shared screen if you need one
  • check Your preferred database and technology choices
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with controlled access, backups and tested recovery
  • check Coverage reviews, handovers and follow-up work prepared for your team
  • check Your required connections and screens built, tested and maintained
  • check Operated through Omni by Enterprise DNA alongside the rest of your business
Talk to Sam

Questions

Instead of PagerDuty, answered

Can we turn off PagerDuty as soon as the records move? expand_more

The free version handles assignment planning, coverage reviews and handover records. It does not deliver urgent notifications. Keep your current paging service operating until the required replacement connections, delivery, monitoring and recovery have been built and tested. Enterprise DNA scopes that work with you.

Can we bring our existing on-call assignments across? expand_more

Yes. An authorised administrator prepares a complete export of resolved on-call assignments for a stated period. The free version imports those records, checks the page sequence and keeps the original evidence. It does not bring across repeating schedule rules, contact methods or notification configuration. We reconcile the actual expected levels and future schedule requirements with you.

Will the coverage report tell us someone can be reached? expand_more

It tells you that an active responder has a recorded assignment during an interval. Imported assignments start unverified and are flagged for review. Successful notification delivery and fitness for duty need separate checks. The workload report counts assigned on-call time, not hours actually worked.

What happens when a shift changes or a handover is missed? expand_more

Revise the recorded assignment and attach the reason. The previous record stays in the change history, and the revised assignment needs verification again. Missed handovers and overdue actions remain visible with their owners until completion evidence is recorded.

Who maintains the system and what do we pay Enterprise DNA? expand_more

You can run the free version yourself, have us customise it, or have us operate it through Omni by Enterprise DNA. The managed options start with one setup fee and then a retainer. We agree the required records, live services, access and operating responsibility before scoping your version.

Bring your PagerDuty bill and the next duty plan

In a 30-minute call, Sam will work through your assignments, handovers and live service requirements. You will see what belongs in your own version and what must be tested before a switch.

On-call Coverage for Claude Code is free and open source, published by Enterprise DNA.

Done paying for PagerDuty?

Get your version built