Enterprise DNA

Instead of Atlassian Statuspage

Paying for Atlassian Statuspage? Own your service updates.

We build your version around your services and update rules, bring across your agreed Statuspage records and run it for you. Hosting and notification connections are scoped and tested as part of your version.

Statuspage Enterprise lists US$1,499 a month. Twelve months at that rate is US$17,988. Lower plans are available.

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 record work from the delivery service

The <a href="https://www.atlassian.com/software/statuspage/pricing">Statuspage pricing page</a> lists Enterprise at US$1,499 a month, checked 23 October 2026. Choose the service you need, then decide which records and rules you want to own.

paid

A recurring plan

Enterprise is billed as a service subscription. Your own version has an agreed setup and ongoing operating cost.

group

Subscriber capacity

Plans carry subscriber allowances. The free base keeps your contact records with an explicit review step.

badge

Team access

Team allowances sit inside the plan. We scope the access each person needs in your version.

notifications

Notification channels

Available delivery channels depend on the plan. Your custom version needs tested connections for the channels you use.

monitoring

Service metrics

Plans include metric allowances. The base reports recorded service conditions; monitoring connections are separate work.

calendar_month

Incident and maintenance records

Statuspage includes incidents, components and scheduled maintenance. Own the records behind those routines and the rules for preparing updates.

What the working base does

Make the next communication a recorded commitment

Promises

Know which update is due next

Each open event has an owner and a next update promise. Missing information stays visible.

  • check See overdue update promises
  • check Find incidents with no named owner
  • check Record verified wording as work progresses
  • check Close incidents with a recorded resolution note

Maintenance

Catch two changes on the same service

Check maintenance windows against shared services before the team starts work.

  • check Record start and finish times
  • check Find overlapping windows on the same service
  • check Track work through verification
  • check Prepare a branded maintenance notice

Subscribers

Keep the purpose beside the contact

Bring subscriber records across for review. A migration does not create permission to contact someone.

  • check Review imported contact records
  • check Record purpose and supporting evidence
  • check Keep opted-out contacts excluded
  • check Count reviewed subscribers by affected service

History

Bring the weekly review together

Combine update promises, service health, maintenance conflicts and subscriber review in one working report.

  • check Read the recorded incident timeline
  • check See workload by owner
  • check Prepare incident briefs from the records
  • check Add the fields and reports your business needs

Make it yours

Design your own Atlassian Statuspage replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Service Status for Claude Code

Connected to your own database

Which services need attention?

API

Name
Customer API
Status
Degraded performance
Owner
Mara
Open_incidents
1
Maintenance_windows
0

FILES

Name
File delivery
Status
Partial outage
Open_incidents
1
Maintenance_windows
0

PORTAL

Name
Customer Portal
Status
operational
Owner
Jules
Open_incidents
0
Maintenance_windows
2

Ask it anything

Ten useful questions for your service desk

Each is supported by the working base. These are examples from your records, not a claim that Statuspage cannot answer them.

chat_bubble Which promised updates are overdue?
chat_bubble Which open incidents have no owner?
chat_bubble Which maintenance windows overlap on one service?
chat_bubble Which degraded services have open incidents?
chat_bubble Who owns the largest communication queue?
chat_bubble Which services have not been reviewed recently?
chat_bubble Which subscribers need a purpose or retention review?
chat_bubble How many reviewed subscribers match this affected service?
chat_bubble What wording did we record during the incident?
chat_bubble Who changed a record and what was their note?

Switching

How to switch from Atlassian Statuspage

The move usually involves exporting your subscriber and service records, mapping the fields and rules you use, then checking the replacement before customer communications move.

  1. 1

    Export your Statuspage records

    Use Atlassian Statuspage’s export steps to get your subscriber records as CSV or JSON. Also obtain the public API JSON responses for components, incidents and scheduled maintenance. Check Atlassian’s instructions for the exports your account supports, and decide which history you need to bring across.

  2. 2

    Test and load the records

    Start with the import’s test run to check how your records will be read before loading them. Then load the subscriber export and the service records you chose to bring across. Import components before incidents and maintenance linked to them, or provide a combined JSON bundle. The import keeps the original fields and checks the file as a whole.

  3. 3

    Review what the import flags

    Check any rows or mappings the import flags, and confirm that incidents and maintenance are linked to the right components. Review the imported subscriber records too. New subscribers start in review, and existing opt-outs stay excluded. An export alone does not prove permission to contact someone, so check purpose, evidence, review date and service selection before making a contact active.

  4. 4

    Run both services side by side

    Keep Atlassian Statuspage running while you check the imported records, reports and draft notices against your current process. The base prepares records and drafts but does not send or publish messages. Test the agreed hosting, access and notification delivery for the replacement before moving customer communications. Use this short overlap to resolve gaps without interrupting your existing service.

  5. 5

    Switch off Atlassian Statuspage

    Once the replacement has been checked and customer communications can move, switch off Atlassian Statuspage. Confirm that the records and history you agreed to bring across are present, and that the replacement is ready for the work you expect it to handle. Keep in mind that private incident history, audience permissions, Slack subscribers, metrics and integrations need separate migration work.

construction

Where the real effort goes

The real work is usually mapping your fields and rules to the new records, then deciding how much history to bring across. Private incident history, audience permissions and integrations may need separate migration work. If you have Enterprise DNA run it, they map your actual export, reconcile the agreed history and handle the additional records agreed for your version.

Not ready for a call?

Get your Atlassian Statuspage switch plan by email

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

Start with the base, or have your version built and run

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install
  2. 2 Run npm run demo, then open it with Claude Code, Codex, OpenCode or Cursor
  3. 3 Try the reports, notices and command recipes
  4. 4 Export your Statuspage records, preview the import and reconcile the results
Get it on GitHub

Built around your business

We customise it

An agreed setup fee

  • check Your service names, fields and update rules
  • check Your Statuspage records mapped and checked with you
  • check A web front end or a different stack when you need it
  • check Hosting, access and notification connections scoped for your business
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Your agreed connections tested before the switch
  • check Your reports and notices kept useful as the business changes
  • check Your database and history stay under your control
Talk to Sam

Questions

Instead of Atlassian Statuspage, answered

Can we stop paying Statuspage immediately? expand_more

First agree what your replacement must do. The free base handles records, local reports and draft notices. Enterprise DNA scopes and tests hosting, access and delivery before the customer communication service moves. Keep your current service running until that cutover is checked.

What happens to our existing records? expand_more

The free version reads subscriber exports and downloaded service, incident and maintenance records. Imports preserve the original fields and start new subscribers in review. Enterprise DNA maps your actual export, reconciles the history and handles the additional records agreed for your version.

Does a subscriber export include permission to send? expand_more

An export alone is not treated as permission. The system requires a recorded purpose, supporting evidence, a review date and a service selection before a contact becomes active. Opted-out contacts stay excluded. Nothing in the free base sends messages.

Will we get our own branded status experience? expand_more

Enterprise DNA builds the customer experience and delivery connections you agree, including a web front end when needed. The free base already produces branded incident briefs, maintenance notices and private reports. A production service is tested as part of the custom implementation.

How do the costs compare? expand_more

Statuspage Enterprise lists US$1,499 a month, or US$17,988 over twelve months at that rate. Lower plans exist. The free base has no licence fee, while hosting, delivery and operation still cost money. Enterprise DNA agrees one setup fee, then a retainer for running your version.

Bring your Statuspage bill and one recent incident

Book 30 minutes with Sam. We will look at your update routine, the records to bring across and the hosting and delivery your business needs. Then agree the version Enterprise DNA can build and run for you.

Book 30 minutes with Sam Get the free version

Service Status for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Atlassian Statuspage?

Get your version built