Enterprise DNA

Instead of Backup Radar

Stop renting Backup Radar. Own your backup assurance system.

We build your version around your client reviews, bring your Backup Radar evidence across and run it for you. Start with the free evidence review, then add the connections your service team needs.

Backup Radar lists $8 per client per month, with a 30-client minimum and $495 onboarding. Monthly billing has a 12-month term; the vendor page does not specify currency.

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 is on the bill

A subscription for keeping the backup picture together

Backup Radar combines results, missing-result checks and service workflows. Compare the service you use with the evidence review you want to own.

group

A charge for each client

The published rate is $8 per client per month with a 30-client minimum. Your client count is part of the buying decision.

event

An annual subscription commitment

The vendor describes monthly billing on a 12-month term. Check your own contract dates before planning a switch.

settings

Onboarding

The vendor lists $495 onboarding. Its activation process covers source connections and monitoring workflows.

database

Results gathered from your backup tools

Vendor connections bring backup observations together. Your own version needs tested collection connections for the tools you actually use.

notifications

Exceptions routed to service work

Alerting and ticket connections turn findings into action. We scope and test the required delivery paths in your custom version.

description

Reports for client reviews

Backup performance and recovery objectives become review evidence. The free version produces branded reports from your stored records.

The system you own

Start with the evidence your team needs every morning

Morning review

Find a failed result and a silent job in one review

Check the latest recorded evidence against the recovery interval agreed for each job.

  • check Keep clients, devices and backup jobs together
  • check Distinguish a fresh success from failure, warning and missing evidence
  • check Leave imported jobs unconfigured until their owner records the targets
  • check Add your own service-tier rules to your version

Restore exercises

Keep recovery evidence beside backup evidence

A successful backup observation does not establish that a restore works. Record the actual exercise and its outcome.

  • check Record the exercise date and reported recovery duration
  • check Keep the evidence reference and the person recording it
  • check Show failed, overdue and never-tested jobs
  • check Use your own exercise cadence and acceptance rules

Accountability

Carry every exception into owned follow-up work

Keep the action, deadline and completion evidence alongside the affected job.

  • check Give each follow-up a named owner
  • check Surface overdue work in the weekly review
  • check Require evidence before an action closes
  • check Record who changed the recovery policy and what they recorded

Client reviews

Produce the review in your business name

Bring the stored backup position, restore evidence and open work into a report for each client.

  • check Generate branded backup reviews and restore records
  • check Keep vendor daily assessments separate from local review rules
  • check Show missing security review and retention decisions
  • check Add the questions and report sections your clients ask for

Make it yours

Design your own Backup Radar replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Backup Assurance for Claude Code

Connected to your own database

Which backup results need attention this morning?

C-ARCHIVE

Client
Cedar Wholesale (demo)
Name
Legacy archive
State
unconfigured

C-ERP

Client
Cedar Wholesale (demo)
Name
Orders database
State
failure
Last_result
2026-11-09T21:47:51.226Z
Last_success
2026-11-07T22:47:51.226Z
Owner
Leon

H-DESIGN

Client
Harbour Design (demo)
Name
Design archive
State
stale-results
Last_result
2026-11-06T22:47:51.226Z
Last_success
2026-11-06T22:47:51.226Z
Owner
Mina

H-FILES

Client
Harbour Design (demo)
Name
File server nightly
State
current-success
Last_result
2026-11-09T20:47:51.226Z
Last_success
2026-11-09T20:47:51.226Z
Owner
Mina

Ask it anything

Ten questions your own evidence review answers

These questions are supported by the free version. Add your own exercise evidence and policy decisions to make the review specific to your clients.

chat_bubble Which jobs have no result or an old result?
chat_bubble Which failed result needs attention this morning?
chat_bubble Which jobs have never had a restore exercise?
chat_bubble Which latest restore exercise failed despite an earlier pass?
chat_bubble Which client has the most backup and restore exceptions?
chat_bubble Which imported jobs still need an owner and recovery target?
chat_bubble Which follow-up actions are overdue?
chat_bubble Which client lacks security review or retention evidence?
chat_bubble What did the original vendor assessment say on a given day?
chat_bubble Who changed a recovery policy, and what evidence did they record?

Switching

How to switch from Backup Radar

The move involves exporting your device history, checking how it maps to your records, and keeping your current controls running until the replacement checks are complete.

  1. 1

    Export your device history

    Ask Backup Radar for a complete device-history export covering the period you want to bring across. The import uses the latest results and daily vendor assessments for that period, so make sure the export includes all its pages. It does not contain every historical backup run. Check with Backup Radar about the export available to your account and decide whether the history it includes is enough for your review.

  2. 2

    Preview, then load the records

    Use the import preview before adding records to the database. It lets you review the export and reconcile issues before the import is applied. Once you are satisfied with the preview, load the records. If you are having Enterprise DNA run the system, they bring your records across and reconcile the inventory as part of the custom setup.

  3. 3

    Resolve the import findings

    Review anything the import flags before relying on the new records. It rejects incomplete export pages, duplicate device and job keys, unknown statuses, and conflicting observations. Imported jobs also need an owner, a recovery interval, and a restore cadence before they are configured. Check these against your own records and rules, then correct the source information or agree how to handle each finding.

  4. 4

    Run both side by side

    Keep Backup Radar and its existing controls running while you check the replacement against your actual backup evidence and review process. The base system reviews stored evidence. It does not collect backups, poll vendors, send alerts, or create service tickets. If your replacement needs collection, alert delivery, or service connections, keep the current controls until those paths have passed end-to-end checks.

  5. 5

    Switch off Backup Radar

    Turn off Backup Radar only after you have checked the imported records, resolved the findings you need to address, and confirmed that the replacement paths your business relies on work end to end. Make sure you have retained the history you decided to bring across and that your team knows where to review results, restore exercise evidence, and follow-up work. Keep any separate controls you still need.

construction

Where the real effort goes

The work is usually in matching your fields and rules to the new records, then deciding how much history to bring. The export contains latest results and daily assessments, not every historical run, so check that against what your review needs. New jobs also need owners and recovery and restore settings. If you have Enterprise DNA run it, they reconcile the inventory and build the fields and rules for your setup.

Not ready for a call?

Get your Backup Radar switch plan by email

We will send you the step-by-step plan for moving your business off Backup Radar, 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 Backup Radar device-history export, reconcile it and import it
  4. 4 Record your policies and restore exercises, then render your reports
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your client records brought across and reconciled
  • check Your recovery targets, restore rules and review documents
  • check Your collection connections and a shared web view if you want 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 and tested recovery
  • check Your required collection and delivery connections built and tested
  • check Backup reviews and follow-up work prepared for your team
  • check Operated through Omni by Enterprise DNA alongside your other systems
Talk to Sam

Questions

Instead of Backup Radar, answered

What am I comparing with my Backup Radar bill? expand_more

Backup Radar lists $8 per client per month and $495 onboarding, with a 30-client minimum and a 12-month subscription term. The published page does not identify currency. Bring your invoice and contract to the review so we compare the actual service and commitment you have.

Can you bring my Backup Radar history across? expand_more

Yes. The free version imports a complete device-history export containing the latest results and daily vendor assessments for the requested period. We reconcile the inventory and bring your evidence across in the custom version. That export does not contain every historical run, so we check what your review needs before switching.

Does the free version collect backups and send alerts? expand_more

It reviews stored evidence and records restore exercises. We build and test the live collection, alert delivery and service connections required for your version. Keep your current controls running until the replacement paths have passed end-to-end checks.

Does a green result prove that we can recover? expand_more

A recent successful result is one piece of evidence. The review also tracks the outcome of actual restore exercises and flags missing or overdue tests. Your team performs the exercise and records its evidence. The review does not certify recoverability or legal compliance.

Who looks after the system and what does Enterprise DNA charge? expand_more

You can operate the free version, have us customise it, or have us run it through Omni by Enterprise DNA. We agree one setup fee and a retainer around your requirements. Hosting, connections, access and ongoing operation are part of that discussion.

Bring your Backup Radar invoice to a 30-minute review

Spend 30 minutes with Sam. Bring your invoice, client count and the backup review your team prepares today. We will identify the evidence, connections and operating work your own version needs.

Book a 30-minute Backup Radar review Get the free version

Backup Assurance for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Backup Radar?

Get your version built