Enterprise DNA

Instead of Dataedo

Stop renting Dataedo. Own your data catalogue.

We build your version around the definitions your business relies on, map your Dataedo export and run the review process with you. Your owners, your evidence and your rules.

Dataedo lists Essentials at US$18,000, Data Lineage at US$24,000 and Data Quality at US$32,000 per year, with three editors.

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

The annual catalogue bill

What the Dataedo subscription covers

Dataedo combines documentation, governance and optional lineage and quality capabilities. Compare what your team actually uses with the work your own version needs to do.

payments

An annual plan

The published Essentials starting point is US$18,000 per year. The decision begins with which parts of that plan your team uses.

group

A minimum editor package

Pricing starts with three editors. Additional editors or an unlimited-editor plan change the purchase.

visibility

Viewers already included

Dataedo includes unlimited viewers and community users. The comparison is about owning your process, not charging every reader.

account_tree

A separate lineage tier

Data Lineage lists at US$24,000 per year. Automatic discovery and recorded dependencies are different capabilities to assess.

fact_check

A quality tier

Data Quality lists at US$32,000 per year. Running source checks and recording their results are separate pieces of work.

support_agent

Vendor updates and support

Dataedo includes updates and support. A system you maintain yourself needs an owner for both.

Your own catalogue desk

Definitions with someone responsible for them

Stewardship

Put the overdue decisions in front of their owners

Combine review dates, unresolved actions and missing definitions in one weekly review.

  • check An owner and review date for each record
  • check A queue for changed or overdue definitions
  • check Workload grouped by the responsible person
  • check Unassigned archives shown before they disappear from attention

Change impact

Ask which reports depend on a record

Follow the dependencies your team has recorded and see who needs to review a proposed change.

  • check Links with an evidence reference
  • check Downstream reports across several recorded steps
  • check Owners shown beside affected reports
  • check A printable change-impact brief for the review meeting

Evidence

Keep the decision beside the definition

Quality observations and steward reviews stay connected to the records they describe.

  • check Observed failures as a share of records checked
  • check The date and evidence behind each observation
  • check The definitions preserved at the time of review
  • check Missing retention rationale and accuracy-review evidence flagged

Your version

Change the questions when your business changes

Keep the definitions and checks together, with your own rules for the next review.

  • check A business glossary linked to relevant records
  • check Your Dataedo asset and field export mapped and checked
  • check Private dictionaries and review documents in your brand
  • check An editable weekly review combining owners, issues and quality evidence

Make it yours

Design your own Dataedo replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Data Catalog for Claude Code

Connected to your own database

Which definitions need their owners to review them?

Demo Archive

Name
Customers archive
Review required
true
Open issues
0
Next action
assign owner

Demo ERP

Name
Customers
Owner
Aroha
Review due
2026-10-04
Review required
true
Open issues
1
Next action
review changed records

Demo BI

Name
Revenue dashboard
Owner
Aroha
Review due
2026-10-09
Review required
false
Open issues
1
Next action
review overdue

Ask it anything

Questions Dataedo cannot answer

Every one of these is a real question the demo answers today. Yours will be different, and that is the point.

chat_bubble Which overdue definitions belong to the same owner as a failed quality check?
chat_bubble Which customer-data records lack a retention rationale?
chat_bubble Which reports are downstream of a customer register with unresolved issues?
chat_bubble Which personal-data fields still have no definition?
chat_bubble Which definitions changed after the last steward review?
chat_bubble Which business terms have no linked records?
chat_bubble Which owners carry the most overdue reviews and open actions?
chat_bubble Which recorded quality rules have the highest failure rate?
chat_bubble Which unassigned archives need an owner before review?
chat_bubble Which evidence and operator support the latest review decision?

Switching

How to switch from Dataedo

A move usually involves exporting selected Dataedo documentation, mapping it into the catalogue, checking exceptions, and running both systems until you are ready to retire the workflows you have replaced.

  1. 1

    Export your documentation

    Export the Dataedo documentation you want to bring across, using its Excel export and selecting the content you need. Dataedo workbooks can be configured, so check the sheets and headings in your export. If you are unsure what your account allows, check with Dataedo. Include asset and field definitions, and keep a copy of the export to compare against the imported records.

  2. 2

    Map and load the records

    Match the headings in your export to the catalogue’s asset and field definitions. The import supports configurable Excel workbooks and CSV sheets saved from Excel. Ask for a test run first so you can preview the mapping and results before records are loaded. Once the mapping is right, load the records and keep the original export for reference.

  3. 3

    Review the import findings

    Check the import results and compare the record counts with your export. The import flags missing parent records, duplicate identities and changed records that need review. It rolls back the whole file if it fails, and repeating an identical import makes no changes. Resolve the flagged issues and review changed records before you rely on the catalogue.

  4. 4

    Run both systems together

    Keep Dataedo available while your team uses the new catalogue for the workflows you have moved. Compare definitions, owners and recorded dependencies, and make sure stewards can complete their reviews. The catalogue does not automatically scan sources or discover lineage, so check that any Dataedo workflows relying on those capabilities still have a plan before you move them.

  5. 5

    Retire replaced workflows

    Switch off Dataedo only after you have checked the imported records and your team is ready to use the new process. The import does not bring across permissions, connector configuration, profiling samples, existing reviews or automatic lineage. Decide how to handle each of these separately, and keep Dataedo for any workflow you have not replaced yet.

construction

Where the real effort goes

Most of the work is mapping your own fields and rules to the catalogue, then deciding what history and other Dataedo details you need to retain. Existing reviews, permissions, connector settings and automatic lineage are not included in the import and need separate decisions. If you have Enterprise DNA run your version, they do the record mapping and configure the agreed parts.

Not ready for a call?

Get your Dataedo switch plan by email

We will send you the step-by-step plan for moving your business off Dataedo, 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, customise it, or have us run it

Open source

Do it yourself

Free, open source

  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 Ask for /weekly-review and inspect the synthetic catalogue
  4. 4 Map your Dataedo Excel export, preview the import and reconcile the records
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your definitions, approval rules and business priorities
  • check Your Dataedo records mapped and reconciled
  • check A web front end and source connections scoped for your team
  • check A different technology foundation when that suits 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 review routine and agreed connections maintained
  • check Private access, backups and report delivery configured
  • check Support for the owners who maintain your business definitions
Book a call

Questions

Instead of Dataedo, answered

Are we replacing every Dataedo feature? expand_more

The free version covers recorded definitions, owners, reviews, dependencies and quality evidence. Automatic source scanning, automatic dependency discovery and a team portal are separate work. We scope and build the parts your team needs before you retire the corresponding Dataedo workflow.

Does our documentation come across? expand_more

Dataedo offers an Excel export with selectable content. We map the asset and field definitions, preserve the original exported details and check the counts. Permissions, existing review history and automatic connections need separate mapping. Changed records return to the review queue.

Does Dataedo already let us keep our own data? expand_more

Yes. Dataedo supports on-premises deployment and documentation exports. This choice is about owning and changing the catalogue process itself. It is not a claim that Dataedo prevents access to your records.

Can we trust the compliance and quality results? expand_more

The checks show missing governance evidence and the quality observations your team records. They do not certify compliance or test the source records automatically. Each observation carries a date and an evidence reference for a steward to examine.

Who runs it, and what do we pay Enterprise DNA? expand_more

You can run the free version yourself. For your own managed version, we agree a setup fee and then a retainer. We map the records, configure private access, connect the agreed sources and maintain the review process through Omni by Enterprise DNA.

Keep your definitions. Choose how to run them.

Book 30 minutes with Sam. Bring your Dataedo plan and an example of the review your team repeats every week. We will look at the records to move, the connections to build and the version your business needs.

Book a call Get the free version

Data Catalog for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Dataedo?

Get your version built