Enterprise DNA

Instead of ConductorOne

Stop renting ConductorOne. Own your access review system.

We build your version around who approves access and how you prove a removal. We bring your ConductorOne review records across and run the system for you through Omni by Enterprise DNA.

ConductorOne, now C1, scopes platform pricing by managed identities, platform level and modules. Usage pricing is also available. Ask the vendor for your 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 subscription buys

An access review is a set of decisions you need to keep

Compare the breadth of your C1 contract with the work your team needs to do each week. This free base covers the review record. We scope the connections and wider controls around your business.

people

A scope based on identities

Platform pricing starts with the number of managed identities. Decide which people and accounts your review process actually needs to cover.

layers

Platform levels

C1 offers Pro and Advanced platform choices. Match the features in your contract to the controls your business needs.

extension

Selected product modules

The platform quote also depends on the modules selected. Your own review record can start with the decisions and evidence you use.

paid

Usage as another billing route

C1 also offers usage pricing. Check which model your contract uses before comparing ongoing costs.

fact_check

Review progress and outcomes

C1 provides campaign reporting. The same review meeting still needs named owners, unfinished decisions and evidence of completed removals.

folder

History you can carry forward

C1 documents a task export. Moving the record requires matching its fields and checking current access, rather than treating every historical decision as current.

Your version

Decisions, evidence and the next person to act

Certification

Finish the reviews that are holding the week up

See pending decisions with their reviewer and overdue days. Keep the approval rules close to the records they protect.

  • check Assign each review to a named person
  • check Prevent a person reviewing their own access
  • check Require current evidence before keeping access
  • check Combine your freshness rule with staff status and privilege classification

Removals

Track the gap between agreed and done

A removal decision stays unfinished until someone records evidence from the owning application.

  • check List agreed removals with missing verification
  • check Record who checked the removal and when
  • check Flag verification as invalid if access is later observed again
  • check Keep campaign closure blocked while removal evidence is missing

Control checks

Bring stale and uncertain records into the meeting

Checks flag recorded inactivity, departed staff and missing classification. Each check identifies its source or your own operating policy.

  • check Find departed people with access still recorded
  • check Surface accounts with old or missing usage evidence
  • check Separate unknown privilege from ordinary access
  • check Review current findings alongside historical decisions

Evidence

Keep a record you can explain

Produce a review pack and removal worklist in your business name, with the original imported values retained.

  • check Retain source outcomes without granting fresh approval
  • check Produce branded review documents and read-only summaries
  • check Keep an activity history of local changes
  • check Export the full record whenever you need it

Make it yours

Design your own ConductorOne replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Access Reviews for Claude Code

Connected to your own database

Which departed staff still have access recorded?

tama@example.test

Application
Ledger
Entitlement
Administrator
Ended on
2026-10-11
Observed status
present

Ask it anything

Ten questions your access review can answer

These are real questions the free version answers today. The examples show your own review rules at work, without claiming the vendor lacks configurable reports.

chat_bubble Which reviews are overdue and who owns them?
chat_bubble Which departed people still have recorded access?
chat_bubble Which accounts have no recent use or current evidence?
chat_bubble Which removal decisions still lack verification?
chat_bubble Which privileged accounts need attention?
chat_bubble Which applications have the most unfinished reviews?
chat_bubble How many decisions has each reviewer made and how long did they take?
chat_bubble On which days were keep and removal decisions recorded?
chat_bubble Which control checks fail on the current records?
chat_bubble What evidence supports the decisions in this campaign?

Switching

How to switch from ConductorOne

The move is a staged records migration: export campaign task history, map your fields, validate the import, and run both systems side by side before switching.

  1. 1

    Get your campaign task export

    Ask ConductorOne for the campaign Tasks CSV. The material does not specify how your account exports it, so export what your account allows, usually CSV or Excel, and check with ConductorOne if needed. The import guidance calls for the campaign Tasks CSV, not the separate Excel report, so confirm any alternate format before loading it. Check that the export includes each task’s person, application, entitlement and stable source task ID.

  2. 2

    Test the import first

    Have your operator test the import using the campaign Tasks CSV before loading it for real. Choose the local campaign name, due date and operator identity for the new review. Check that each task maps to a person, application, entitlement and stable source task ID. The importer can preserve every source column, so map unfamiliar headings rather than dropping them.

  3. 3

    Check the import results

    Review the test results for unmatched fields, missing required values and rejected rows before proceeding. A bad row rolls back the whole import, so correct the source or mapping and test again. Confirm that original values are preserved. Imported decisions stay as history only: local reviews start pending, new access records start unknown, and a source removal label does not prove that access was removed.

  4. 4

    Run both systems side by side

    For a short, agreed period, keep ConductorOne available while you use the new database for local review work. Compare the records, reviewer decisions and removal evidence, and resolve differences before relying on the new register. The import brings task history, not an approved local review. Make sure your team knows which system is the record for new decisions during this overlap.

  5. 5

    Switch off ConductorOne

    Retire ConductorOne only after you have reconciled the imported history and current work. Confirm your replacement scope first: this base covers review records, decisions, removal evidence and documents. Live application connections, access enforcement and authenticated reviewer sign-in are separate implementation work. Make sure those needs have an agreed solution, then tell reviewers where new decisions and evidence belong and follow your organization’s process to end or disable ConductorOne.

construction

Where the real effort goes

The main work is matching your report headings to required records, deciding which review history to bring, and reconciling differences without treating old decisions as current approvals or removal proof. The free version preserves source values and starts fresh local reviews. If you have Enterprise DNA install and run it, they handle mapping and reconciliation as part of the build.

Not ready for a call?

Get your ConductorOne switch plan by email

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

Choose who builds and runs your version

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install
  2. 2 Run npm run demo to inspect fictional records
  3. 3 Open it in Claude Code, Codex, OpenCode or Cursor
  4. 4 Read the replacement guide, map your task CSV and test the import
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your reviewer rules, fields and evidence requirements
  • check Your ConductorOne data mapped and reconciled
  • check A web front end and a different technology choice when your team needs them
  • check Connections and access controls built to the agreed scope
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check We install your version and bring the records across
  • check We operate it inside Omni by Enterprise DNA
  • check We maintain the agreed connections, backups and review rules
  • check You have someone to call when the process changes
Book a call

Questions

Instead of ConductorOne, answered

Does the free version replace the whole ConductorOne platform? expand_more

It covers access review records, decisions, removal evidence and review documents. Enterprise DNA scopes live application connections, reviewer sign-in and access enforcement as part of your custom version. We agree that scope before you change systems.

Can we bring our review history across? expand_more

Yes. Start with the campaign task export and match its headings to the required records. The free version preserves the original values and starts fresh local reviews. Enterprise DNA handles mapping and reconciliation when we build your version.

Will a decision here actually remove access? expand_more

The free version records a removal decision and the evidence supplied after the application owner acts. Enterprise DNA can build the agreed connections for your managed version. A historical removal label is never treated as proof of current access.

Will the checks make us compliant? expand_more

The checks identify selected account-control gaps in your records. They show the source of each rule and separate it from your own operating policy. Your responsible owner still checks the evidence and decides which standards apply.

What do we pay Enterprise DNA? expand_more

One setup fee, then a retainer for the agreed work. We look at your applications, approval rules and migration before setting the scope. The free version remains available for you to install and run yourself.

Own the record behind your access decisions

Book 30 minutes with Sam. Bring your ConductorOne scope, one review export and the controls your team needs. We will work through the migration, connections and what your own version would look like.

Book a call Get the free version

Access Reviews for Claude Code is free and open source, published by Enterprise DNA.

Done paying for ConductorOne?

Get your version built