Enterprise DNA

Instead of IBM watsonx.governance

Stop renting IBM watsonx.governance for reviews. Own your review desk.

We build your version around who reviews each model, what evidence they need and how exceptions get resolved. We bring your agreed IBM inventory records across and run the system for you.

IBM lists Risk & Compliance Advanced from US$6,450 monthly, or US$77,400 over twelve months. Indicative pricing, before taxes; country and package affect the quote.

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 bill buys

Separate the review desk from the wider platform

IBM lists Risk & Compliance Basic from US$3,500 monthly and Advanced from US$6,450 monthly. The annualised starting amounts are US$42,000 and US$77,400. Its wider platform also provides evaluation and monitoring. Start by identifying the review work your team actually needs to own.

paid

A continuing plan charge

Risk & Compliance is sold as a monthly package. The public figures are starting prices and vary by country.

person

Concurrent access

The listed Basic and Advanced starting packages each include one concurrent user. Extra concurrent users are optional add-ons.

layers

Modules

Each listed starting package includes one module. Additional modules are optional.

dns

Instances

The starting packages include one instance. Additional instances are listed separately as options.

fact_check

Review and risk workflows

The plan packages use-case onboarding and risk assessment. Your owner assignments, evidence references and decisions can live in your own database.

query_stats

Services beyond the register

Model evaluation and monitoring are broader services. We scope those needs separately when designing your version.

What you own

The records behind the next review decision

Review queue

Start the week with a named owner

See missing owners, late reviews and the actions due next. Combine them to find where one person has both a review backlog and unresolved work.

  • check An accountable owner and purpose for every use case
  • check Current and previous model versions kept together
  • check Review dates and action deadlines in one weekly pack
  • check Find owners with overdue reviews and overdue actions together

Evidence

Know when an approval has gone stale

A review decision belongs to a specific version. Its supporting evidence has its own expiry, so an old approval cannot hide a missing check.

  • check Validation, privacy and human oversight evidence references
  • check Approval periods limited by the supplied evidence
  • check A new version starts unassessed
  • check Find operating records whose evidence has expired

Remediation

Close the exception with a reason

Assign an owner and due date to each action. High-severity actions block approval until a resolution is recorded.

  • check Severity and responsibility on every action
  • check A written resolution before an action closes
  • check History of changes and recorded decisions
  • check Find retired systems that still have unresolved work

Your version

Keep your policy in a database you own

Make the review rules fit your business. Read-only reports show your register, evidence and deadlines in your own branding.

  • check Model cards, assessment records and remediation plans
  • check Your review dates and risk thresholds
  • check Export your records with their original imported fields
  • check Ask for a combined evidence-and-review report when your policy changes

Make it yours

Design your own IBM watsonx.governance replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Model Governance for Claude Code

Connected to your own database

Which model reviews need attention this week?

DOC-02

Me ow
Document classifier
Ason
Owner missing

SUP-01

Me ow
Support reply drafts
Ner ne
Mara Chen
Xt review re
2026-10-23
Ason
Review overdue

DEM-03

Me ow
Demand forecast
Ner ne
Ari Patel
Xt review re
2026-11-18
Ason
Review within 30 days

Ask it anything

Ten questions from your model review records

These answers combine your owners, review dates and evidence. Each runs on the demo today; your version can use your own policy.

chat_bubble Which operating models have no current approval?
chat_bubble Which owners have both an overdue review and overdue actions?
chat_bubble Which suppliers have unassessed use cases?
chat_bubble Which departments have no accountable owner recorded?
chat_bubble Which approvals depend on evidence expiring within 30 days?
chat_bubble Which current versions have never had a review?
chat_bubble Which high-severity actions are overdue and who owns them?
chat_bubble Which imported use cases still need assessment?
chat_bubble Which retired systems still have unresolved actions?
chat_bubble Which planned reviews arrive before their evidence expires?

Switching

How to switch from IBM watsonx.governance

The move involves exporting your register, mapping its fields, checking the imported records and running both systems side by side before you switch.

  1. 1

    Export your IBM records

    Use the export options available in your IBM watsonx.governance account. IBM documents exports of governance objects and configurable spreadsheet exports from grid results. Export your model or use-case register and the fields you need to continue your reviews. If your account allows it, use CSV or Excel, and check with IBM watsonx.governance if you are unsure which export path to use.

  2. 2

    Map fields and preview

    Match the headings in your export to the fields in Model Governance for Claude Code, then run a test import preview before loading the records. The import keeps the original fields, but imported records start unassessed. Treat the preview as a chance to check how your records will map before you make them part of the new register.

  3. 3

    Check import warnings

    Review what the preview flags and correct problems before importing for real. Pay attention to records or fields that do not map as expected, and confirm that important details such as owners and review dates are present. Imported records start unassessed, so plan for your reviewers to check them and record decisions in the new system.

  4. 4

    Run both systems side by side

    Keep IBM watsonx.governance available while you use the new database and Claude Code for a short period. Compare key register records and review work in both systems, and resolve discrepancies before you rely on the new one. This gives you a chance to check that your mapped fields and review rules work for your team.

  5. 5

    Switch off IBM

    Once you have checked the imported records and are ready to use the new system, stop using IBM watsonx.governance for this review work. Keep any exports or records you need for reference or retention, and protect them because they contain business records. Make sure your team knows where the current register and review decisions now live.

construction

Where the real effort goes

The main work is usually mapping your own fields and review rules, then deciding how much history to bring. The basic import brings across register records, but historical decisions, attachments and relationships need a separate migration scope. If you have Enterprise DNA install and run the system, Enterprise DNA handles this migration work with you.

Not ready for a call?

Get your IBM watsonx.governance switch plan by email

We will send you the step-by-step plan for moving your business off IBM watsonx.governance, 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, MIT licence

  1. 1 Clone the repo, run npm install, then npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Map your IBM inventory export, preview the import and reconcile the records
  4. 4 Set up your database, access controls and backups
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your fields, evidence requirements and review rules
  • check Your agreed IBM export mapped and checked with your team
  • check A web front end or different stack where wanted
  • check The reports and connections your reviewers need
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installation, agreed migration and team handover
  • check Access controls, backups and maintenance for the agreed system
  • check Support as your review policy changes
  • check Run inside Omni by Enterprise DNA with the rest of your business
Book a discovery call

Questions

Instead of IBM watsonx.governance, answered

Are we replacing the whole IBM platform? expand_more

This free version handles the model register, version-specific reviews, evidence references and remediation. If you rely on live evaluation, monitoring or automatic discovery, Enterprise DNA scopes the connections and services your custom version needs before any switch.

Can we bring our existing inventory across? expand_more

Yes. IBM documents object exports and spreadsheet exports from its governance records. The free import takes an inventory export after its headings are mapped. Original fields are retained, but imported records start unassessed. Historical decisions, attachments and relationships need a separate migration scope.

Does it certify compliance or decide whether a model is safe? expand_more

No. It checks recorded ownership, dates and evidence against your local policy, with references to the voluntary NIST framework. Your reviewer checks the evidence and records the decision. It does not test model behaviour or control a running service.

What will our reviewers see? expand_more

They can read branded model cards, assessment records, remediation plans and weekly dashboards. Enterprise DNA can build the shared screens and access controls your team wants. Your decision history stays with your database.

What does Enterprise DNA charge? expand_more

One setup fee, then a retainer for the agreed customisation and operation. We scope your record migration, evidence rules, connections and support with you. The free version carries an MIT licence; running costs depend on how you host and operate it.

Put your model review desk on your own terms

Spend 30 minutes with Sam. Bring your IBM bill and one review that takes too much chasing. We will identify the records, evidence and connections your version needs, then agree what Enterprise DNA builds and runs.

Book a discovery call Get the free version

Model Governance for Claude Code is free and open source, published by Enterprise DNA.

Done paying for IBM watsonx.governance?

Get your version built