Enterprise DNA

Instead of Ardoq

Stop renting Ardoq. Own your application portfolio.

We build your version around the software decisions your business makes, bring your Ardoq application records across and run it for you. See what depends on a system before you decide to replace it.

Ardoq quotes privately by application, with unlimited users. Your version starts with one setup fee, then a retainer.

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

Your application count sets the bill

Ardoq packages enterprise architecture around the applications you manage. Start by comparing the work you actually need each week with the scope of your contract.

apps

An application-based licence

Ardoq prices by the number of applications in your workspace. Its pricing page asks you to request a quote.

groups

Unlimited people included

Ardoq includes unlimited users. Adding colleagues is not the per-seat cost argument for switching.

visibility

Visibility across the business

The Business & IT Optimization module covers the application landscape and opportunities to rationalise it.

route

Transformation planning

The Strategic Planning module covers future states and change initiatives. Decide how much of that scope your team uses.

policy

Governance reviews

The Governance, Risk & Compliance module covers risks, controls and architecture reviews.

extension

Additional services and options

Professional services are purchased separately. Ardoq also lists optional additions such as a sandbox.

The version your business owns

Start with the decisions, then follow the records

Ownership

Put a name beside every application

Find the records nobody owns before the next renewal arrives.

  • check Assign an accountable owner and a business capability
  • check See missing review dates beside overdue reviews
  • check Keep unknown costs visible instead of turning them into zero
  • check Review recorded annual costs separately for each currency

Dependencies

Find the people affected by a change

Trace the applications that consume a service, including indirect connections.

  • check Record the direction and evidence for each connection
  • check Follow several steps through the dependency chain
  • check List connections whose evidence needs refreshing
  • check Block a retirement decision while active consumers remain

Decisions

Make the approval match the current facts

A decision against an old application record needs a fresh review.

  • check Propose retention, investment, migration or retirement
  • check Record the rationale, evidence and person approving it
  • check Mark decisions stale when the application or its connections change
  • check Prepare an internal decision brief from the current record

Evidence

Keep reviews open after software retires

Retiring an application does not dispose of the information it held.

  • check Find missing security and retention evidence reviews
  • check Keep retired applications in the personal-information checks
  • check Render review paperwork in your business name
  • check Change review rules around your actual policy, with a record of the change

Make it yours

Design your own Ardoq replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Application Portfolio for Claude Code

Connected to your own database

Which applications are near or past the end of support?

APP-01

Name
Harbour orders
Owner
Aroha
Support_end
2026-09-25
Days_left
-15
Dependent_apps
1

APP-03

Name
Legacy orders
Support_end
2026-10-30
Days_left
20
Dependent_apps
1

Ask it anything

Ten questions your application review can answer

These answers run on the fictional demonstration records below. Ardoq also offers configurable analysis. The difference here is owning the database and the rules behind your review.

chat_bubble Which applications lack an owner or a current review?
chat_bubble Which support deadlines arrive within ninety days, including missed dates?
chat_bubble What would be affected indirectly if Harbour orders stopped?
chat_bubble Which recorded connections have not been verified for ninety days?
chat_bubble Which application renewals are due within ninety days or already late?
chat_bubble Where do two active applications serve the same business capability?
chat_bubble What is the recorded annual cost by capability and currency?
chat_bubble Which application costs are still unknown?
chat_bubble Which decisions became stale after an application record changed?
chat_bubble Which retired applications still need a personal-information evidence review?

Switching

How to switch from Ardoq

A move usually involves exporting application records, mapping your headings, checking the import and reconciling Ardoq data that does not come across automatically.

  1. 1

    Export application records

    Use Ardoq’s report export to export only your application records. The importer accepts Ardoq JSON exports or a CSV saved from an Excel report. Check which export options are available in your account with Ardoq, and keep the original export unchanged. Relationships, permissions, attachments and decision history are not included in the application record import.

  2. 2

    Map and test the import

    Map the headings in your export to the application fields, including any custom headings you use. Run the import as a test first so you can review the proposed changes without saving them. Imported applications start in planned status. They need ownership, capability and personal information classification before reviews can be activated.

  3. 3

    Review import issues

    Check the test results for records or values that need attention, including duplicate IDs and headings that did not map as intended. The importer rejects duplicate IDs and changed repeats rather than applying them. Resolve mapping problems, then review the imported records for missing owners, capabilities and personal information classifications before relying on them for reviews.

  4. 4

    Run both side by side

    Keep Ardoq available for a short period while you check the new register against it. Compare application records, ownership, costs and decisions, and reconcile connections and other information that needs a separate migration. Use this period to confirm the records and review process fit your team’s work. Do not assume the application register import replaces Ardoq’s wider modelling and collaboration scope.

  5. 5

    Switch off Ardoq

    Before cancelling Ardoq, confirm that the agreed migration scope covers the business views and connections your team depends on. Reconcile permissions, surveys, attachments and decision history separately if you need them. Once the new register and agreed workflows have been checked, follow your Ardoq contract and internal process to end the subscription. The import itself does not cancel services or contracts.

construction

Where the real effort goes

The main work is usually mapping your own fields and review rules, then deciding which history and related records to bring across. The application register import does not automatically bring over relationships, permissions, surveys, attachments or decision history, so those need separate reconciliation. If you have Enterprise DNA install and run your version, Enterprise DNA handles the agreed mapping and migration.

Not ready for a call?

Get your Ardoq switch plan by email

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

Run the free version or have yours built

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and install the dependencies
  2. 2 Run npm run demo and try the fictional portfolio
  3. 3 Open it with Claude Code, Codex, OpenCode or Cursor
  4. 4 Map your Ardoq application export and test the import before using real records
Get it on GitHub

Built around your business

We customise it

A setup fee, then a retainer for ongoing work

  • check Your application fields, ownership rules and decision paperwork
  • check Your Ardoq records mapped and reconciled with the original export
  • check A web front end and business connections scoped around your team
  • check A different technical foundation if your business needs one
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 Connected to the agreed records and evidence archive
  • check Access controls, backups and recovery checks for shared use
  • check Ongoing changes when your software estate or review process changes
Book a call

Questions

Instead of Ardoq, answered

What would we own instead of our Ardoq subscription? expand_more

The free base covers the application register, ownership, costs, dependencies, decisions and evidence reviews in a database you own. We agree the scope of your version against the work your team actually does. Your licence has no application limit. Hosting, support and agent use have their own costs.

Can we bring our existing Ardoq records across? expand_more

Yes, for application records. Ardoq supports report exports, and the free version imports the application records after their headings are mapped. Imported records wait for an owner and classification review. Connections, permissions, attachments and decision histories need separate reconciliation. Enterprise DNA handles the agreed mapping and migration in your version.

Will this give us the diagrams and connections our team uses? expand_more

We scope your business views and connections before the switch. The free base provides read-only review snapshots and paperwork. Your custom version can include a web front end and the connections you need. Compare the full migration scope with your Ardoq contract before cancelling it.

Does a passed evidence review mean we are compliant? expand_more

No. The checks identify missing or overdue security and retention reviews, including records for retired applications. A responsible person must assess the actual safeguards and legal duties. Evidence references record what your operator supplied. They do not inspect the underlying system or certify compliance.

What does Enterprise DNA charge to build and run our version? expand_more

One setup fee, then a retainer for the agreed ongoing work. In a 30-minute call, Sam reviews your current bill, application records and must-have workflows before scoping the build. There is no Enterprise DNA price per application on this page.

Make the next renewal a decision about your business

Book 30 minutes with Sam. Bring your Ardoq contract, one application export and the questions your next review needs to answer. We will scope the version Enterprise DNA can build and run for you.

Book a call with Sam Get the free version

Application Portfolio for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Ardoq?

Get your version built