Enterprise DNA

Instead of Nobl9

Stop renting Nobl9. Own your reliability review system.

We build your version around your services, bring supported Nobl9 exports across and run the review process for you. Your targets, evidence and decisions stay in a database you own.

Nobl9 Teams lists US$14,950 per year. Professional and Enterprise are quoted privately. The free base handles recorded measurements and reviews; we scope live monitoring connections around your business.

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 buys

An annual platform bill around your reliability targets

An error budget is your agreed allowance for failed requests. Nobl9 packages the measurement and reporting around those targets into subscription plans.

banknotes

Teams: US$14,950 a year

The published Teams price is an annual subscription. It is a vendor list price, not a customer invoice.

chart-bar

Objective units

Teams includes 50 units. Each objective consumes a unit, including additional objectives within one service target.

link

Data-source allowance

Teams includes up to 10 data sources. Professional lists unlimited sources.

clock

Stored measurement history

Teams lists two years of retention. Decide how long your own review evidence needs to be kept.

bell

Alert methods

The Teams package includes all alert methods. Your custom version needs its notification routes scoped and tested.

users

Larger plans by quote

Professional starts with 200 objective units and Enterprise with 500. Both require a sales quote.

Your owned version

The evidence behind the next service decision

Targets and counts

Separate a healthy service from a missing measurement

Read complete daily counts against the target you approved.

  • check Keep each service and its accountable owner together
  • check Compare successful and failed requests over your chosen window
  • check Show missing days beside the result
  • check Treat zero traffic as unknown evidence

Decisions

Put your policy beside the numbers

Record the owner decision with the evidence that supported it.

  • check Hold when the failure allowance is exhausted
  • check Require a current written service policy
  • check Block a proceed record while recovery work is overdue
  • check Retain the measurement and policy snapshot with the decision

Recovery work

Make Monday about the work still owed

Bring missing evidence, overdue reviews and recovery actions into one conversation.

  • check Assign each recovery action to an owner
  • check Record the due date and completion evidence
  • check See open and overdue work by owner
  • check Ask which service combines missing evidence with an overdue policy

Your records

Keep the review portable

Use a database you own for the records your team needs to explain a decision.

  • check Retain original columns from supported Nobl9 exports
  • check Keep imported results separate from daily count calculations
  • check Prepare branded service reviews and policy drafts
  • check Review the purpose and retention of names and decision notes

Make it yours

Design your own Nobl9 replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your Nobl9 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 Nobl9 data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Three real runs on fictional demo records. The answers show an exhausted budget, missing measurements and the evidence needed for an owner decision.

forum

Reliability Objectives for Claude Code

Connected to your own database

Which services have exceeded their allowance for failed requests?

CHECKOUT-OK

Name
Successful checkout requests
Basis
daily-counts
Remaining pct
-100.00
State
exhausted

PORTAL-OK

Name
Successful portal requests
Basis
daily-counts
Remaining pct
80.00
State
within budget

SYNC-OK

Name
Successful sync jobs
Basis
daily-counts
Remaining pct
0.00
State
incomplete

Ask it anything

Questions you can answer with your own records

Each question is demonstrated by the commands in the free version. Your version can use your own service rules and records.

chat_bubble Which service has used more than its allowance for failed requests?
chat_bubble Which result is missing days of measurements?
chat_bubble Which service is ready for an owner decision today?
chat_bubble Which recovery action is overdue, and who owns it?
chat_bubble Who has the largest open recovery workload?
chat_bubble Which service needs its reliability policy reviewed?
chat_bubble Which imported result is too old to rely on?
chat_bubble What measurements supported the last proceed decision?
chat_bubble Which services need a review of their record-retention purpose?
chat_bubble Who changed the policy, and what did it say before?

Switching

How to switch from Nobl9

A move usually involves confirming export access, mapping your objectives and fields, importing the history you choose, and checking results before you retire Nobl9.

  1. 1

    Confirm and export your records

    Ask Nobl9 to confirm your account has access to the documented Enterprise measurement export. Export the measurement evidence and remaining-budget snapshots you want to bring across, along with the objective details needed for mapping. The configurable objective-list export is a different format, so do not assume it is ready for direct import. If your account does not offer the documented export, check with Nobl9 before setting the migration scope.

  2. 2

    Test the import first

    Provide the authorised export to whoever is handling the migration. Have them run the import as a test without saving changes, then compare the record counts with what you expected to bring across. The importer preserves original columns, so the source data remains available for review. Agree which history to include before loading it for real, especially if you do not need every available record.

  3. 3

    Review the import findings

    Check the import results for missing or stale snapshots, composite objectives, changed duplicate measurements, and any rejected records. Missing or stale snapshots and composite objectives cannot support a proceed decision. Ask for each finding to be explained and resolved, or recorded as an accepted limit, before relying on the imported history. Confirm the loaded objectives and measurement counts match the agreed scope.

  4. 4

    Run both systems side by side

    Keep Nobl9 in use while you compare its reviews with the new system over a short period agreed with your team. Check the objectives, evidence coverage, recovery actions, and recorded decisions against the same services and dates. Keep your operational monitoring in place until any replacement connections have been tested. Use this period to identify mapping or policy changes before making the new process your day-to-day review.

  5. 5

    Switch off Nobl9 reviews

    After the owners have checked the mapping, imported history, and side-by-side results, agree when to stop using Nobl9 for these reviews. Confirm that the records you chose to retain are available in the database you own and that your team knows where to record future decisions. Keep operational monitoring in place until its replacement has been tested, if replacing it is part of your plan.

construction

Where the real effort goes

The main work is usually mapping your own objective fields and rules, then deciding how much history to bring across and checking it. The documented export may not match your chosen objective format directly, so the mapping needs review. If you have Enterprise DNA run the system, they handle the export mapping, fields, and rules with you.

Not ready for a call?

Get your Nobl9 switch plan by email

We will send you the step-by-step plan for moving your business off Nobl9, 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 and run npm install
  2. 2 Run npm run demo in Claude Code, Codex, OpenCode or Cursor
  3. 3 Try the weekly review and a supported Nobl9 export with --dry-run
  4. 4 Reconcile the records and configure your own database
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your service targets, review rules and recovery process
  • check Your supported Nobl9 export mapped and checked
  • check Your monitoring connections and notification routes built and tested
  • check A shared web view or a different technology stack when you need it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access, backups and recovery checks
  • check Your reliability review prepared from current evidence
  • check Your connections and records maintained as services change
  • check Run through Omni by Enterprise DNA beside the rest of your business
Book 30 minutes with Sam

Questions

Instead of Nobl9, answered

Does the free version replace all of Nobl9? expand_more

It covers stored reliability targets, daily measurement counts, supported imported results, recovery actions and decision records. Live monitoring, alert delivery and advanced calculations are scoped as part of your custom version. Keep your current monitoring in place until those connections are tested.

Can we bring our Nobl9 history across? expand_more

The free version reads the documented Enterprise measurement export and retains its original columns. Confirm your account has that export before planning the switch. The configurable objective-list export is a different format; Enterprise DNA agrees its mapping with you before migration.

What stops missing measurements from looking like good service? expand_more

A daily-count result needs every day in its review window and some measured traffic before it supports a proceed decision. Imported results must be recent. The owner also needs a current policy and no overdue recovery actions. Recording a decision does not release software.

Can our team have its own screens and monitoring connections? expand_more

Yes. Enterprise DNA builds the shared views, data connections and notification routes your team needs around the owned database. We agree how each connection will be checked before it becomes part of day-to-day operations.

What does Enterprise DNA charge, and who owns the records? expand_more

One setup fee, then a retainer, scoped around your services and the work you want us to run. Your records remain in a database you own. The base is open source, and its exports include measurement evidence and change history.

Bring your Nobl9 bill and one service review

Book 30 minutes with Sam. We will look at the targets you track, the exports you can obtain and the monitoring connections your version needs. You leave with a clear scope for the records, reviews and operating work.

Book 30 minutes with Sam Get the free version

Reliability Objectives for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Nobl9?

Get your version built