Enterprise DNA

Instead of ConfigCat

Review your ConfigCat bill. Own your feature flag release desk.

We build your version around your release process, bring your ConfigCat configuration across and run the agreed system for you. Application connections and delivery are scoped before you switch.

ConfigCat lists Dedicated at US$4,500 a month, equivalent to US$54,000 over twelve months. Enterprise is US$900 a month. These are public USD list prices, not a quoted saving.

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

Separate your release records from the service delivering them

ConfigCat sells hosted configuration delivery as well as a control panel. Your own release desk holds the records and review process. We agree the application delivery you need before replacing any service.

payments

A plan sized for your usage

Dedicated lists US$4,500 a month. Enterprise lists US$900. The free version has no licence fee, while hosting and operation remain part of your own system.

group

Unlimited seats already included

ConfigCat includes unlimited seats. This comparison is about owning your release process and configuration, rather than a claimed saving on seat licences.

cloud_sync

Configuration downloads and network usage

ConfigCat plans include different download and network allowances. We scope how approved versions reach your applications and who operates that delivery.

rule

Targeting rules and percentage rollouts

ConfigCat includes targeting capabilities across its plans. Your exported configuration retains its rules, with local tests before a recorded release.

history

The history you need to retain

ConfigCat lists different audit-log retention by plan. Your own desk records imported baselines, proposed changes, tests, supplied decisions and releases from the point you start using it.

support_agent

Hosting and support responsibilities

Dedicated offers hosted or on-premise options. We agree your access, backups, application connections and operating support as part of the managed version.

What you own

A release process you can change around your team

Ownership

A reason and an owner for each flag

Put review work next to the configuration it concerns. An unowned flag or a missed review stays visible.

  • check Named owners and a plain-language purpose
  • check Review dates and an overdue list
  • check Owner workloads across environments
  • check Default-value differences between staging and production

Change review

Tests and evidence before a recorded release

Each proposal starts from a known version, with its impact and rollback plan recorded.

  • check Test cases for changed flags and affected prerequisites
  • check A failed latest test blocks approval
  • check A different named reviewer supplies the decision
  • check An older proposal must be recreated after the baseline changes

Owned history

Keep the change and its explanation together

Ask about your own review rules, ownership changes and release evidence in the same place.

  • check Who changed an owner and what was there before
  • check Which supplied review approved each change
  • check The source fingerprint and count for each import
  • check Earlier release snapshots available for reviewed rollback proposals

Working documents

A handover that uses your records

Generate the register and release handover in your business name, then adapt the fields and checks to fit.

  • check Environment registers with active flags and owners
  • check Release handovers with tests and rollback plans
  • check Read-only weekly and control reports
  • check Private exports and review drafts for a person to inspect

Make it yours

Design your own ConfigCat replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Feature Flags for Claude Code

Connected to your own database

Which flags and changes need attention now?

Kauri production

Item
CHECKOUT-01
Issue
change overdue
Due_on
2026-10-26

Kauri production

Item
Legacy banner
Issue
owner missing
Due_on
2026-10-18

Kauri production

Item
Legacy banner
Issue
review overdue or missing
Due_on
2026-10-18

Kauri staging

Item
Legacy banner
Issue
owner missing
Due_on
2026-10-18

Kauri staging

Item
Legacy banner
Issue
review overdue or missing
Due_on
2026-10-18

Ask it anything

Ten questions this working version answers

These are answers from the owned release record. ConfigCat also provides reporting. Your version lets us connect your ownership history, review policy and release evidence in the way your team needs.

chat_bubble Which flags have no owner and an overdue review?
chat_bubble Which change is overdue before its first release?
chat_bubble Which proposals were prepared against an older revision?
chat_bubble Which owner has the most reviews due?
chat_bubble Where do staging and production defaults differ?
chat_bubble Which named reviewer approved a change and why?
chat_bubble Did the latest test run fail after an earlier pass?
chat_bubble Which recorded version is available for a rollback proposal?
chat_bubble Who changed a flag owner and what was there before?
chat_bubble Which imported environment came from this configuration digest?

Switching

How to switch from ConfigCat

A move usually involves exporting each environment, checking and mapping its configuration, then testing the replacement beside ConfigCat before changing application delivery.

  1. 1

    Export each environment

    Export the native configuration for each ConfigCat environment you plan to move. The import accepts this environment export, including its v6 targeting rules, segments, prerequisites and percentage assignments. A whole-product backup is a different format and will not work for this import. If you are unsure which export your account allows, check with ConfigCat.

  2. 2

    Trial the import

    Start with an empty replacement database and import one environment at a time. Run the import's trial first so you can see what it would bring across before loading it. The import preserves the exported configuration, but it does not deploy changes to your applications or contact ConfigCat. Keep your existing service running while you prepare and test the replacement.

  3. 3

    Review the import findings

    Check the trial results, including the import counts and source details, then inspect the imported flags and targeting rules. Resolve anything that needs attention before relying on the new records. Configuration exports do not include everything: historical approvals, team permissions and other records need separate mapping. Decide which of those records you need to bring across.

  4. 4

    Run both side by side

    For a short period, keep ConfigCat running while you test the imported configuration and its local evaluations against the cases that matter to your team. Check customer groups and boundaries in your targeting rules. Have application owners test the separate delivery of approved local configuration. Recording a release in the replacement does not change a running application.

  5. 5

    Switch off ConfigCat

    Only switch off ConfigCat after the replacement and rollback have been tested and your team has agreed how applications will receive the approved local configuration. Coordinate the application change with the people who own delivery, since the replacement does not deploy to applications by itself. Keep your rollback plan available as you make the change.

construction

Where the real effort goes

The import itself is only part of the work. Most effort usually goes into mapping your own fields and rules, then deciding which history to bring, since approvals, permissions and other records are not in the environment export. You also need to verify the configuration and test application delivery. If Enterprise DNA installs and runs the replacement, it handles the record reconciliation as part of the agreed setup.

Not ready for a call?

Get your ConfigCat switch plan by email

We will send you the step-by-step plan for moving your business off ConfigCat, 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 and run npm install
  2. 2 Run npm run demo with the fictional release records
  3. 3 Open the folder in Claude Code, Codex, OpenCode or Cursor
  4. 4 Preview a native ConfigCat v6 environment import, then test application behaviour before switching
Get it on GitHub

Built around your business

We customise it

An agreed setup fee

  • check Your flag ownership, review rules and handover documents
  • check Your ConfigCat configuration mapped and checked
  • check A web front end or a different stack if agreed
  • check Application delivery 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 retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Your agreed application connections maintained
  • check Backups and operating responsibilities agreed from the start
  • check Your release reports and controls adapted as the business changes
Talk to Sam

Questions

Instead of ConfigCat, answered

Does this replace the whole ConfigCat service? expand_more

The free version gives you an owned release record and local evaluation of your imported targeting rules. Recording a release does not change a running application. Enterprise DNA scopes delivery, access controls and the application connections into your version. Keep your current service running until the replacement and rollback have been tested.

Can we bring our existing flags and targeting rules? expand_more

Yes, from the native configuration export for each environment. The free version preserves those values and rules, offers a trial import and rejects a different configuration over an existing environment. A whole-product backup is a different format. Historical approvals, team permissions and other records need separate mapping. We reconcile the required data before a switch.

How does the price compare? expand_more

ConfigCat lists Enterprise at US$900 a month and Dedicated at US$4,500 a month. Twelve months at the Dedicated rate is US$54,000. Confirm your currency, term and actual usage with ConfigCat. The free version has no licence fee. Enterprise DNA charges an agreed setup fee, then a retainer for the managed service. Hosting and application delivery are included in the scope discussion.

What happens if a proposed change fails its tests? expand_more

A failed latest test blocks approval. The proposal needs passing tests and a different named reviewer before it can become a recorded release. Changing the baseline makes earlier proposals stale. Returning to an older version follows the same review process. The tests prove the supplied examples, so your team must include the customer groups and boundaries that matter.

Who controls our configuration and review history? expand_more

You own the database and can export the records. The free version records supplied actor names rather than verifying identities, and a database owner can edit history. Enterprise DNA agrees authenticated access, record protection, retention and backup operation for your managed version. Your team remains responsible for the release decisions it supplies.

Bring your ConfigCat bill and one release handover

Book 30 minutes with Sam. We will look at your environments, review process and application delivery, then agree what your version needs and how it should be run.

Book 30 minutes with Sam Get the free version

Feature Flags for Claude Code is free and open source, published by Enterprise DNA.

Done paying for ConfigCat?

Get your version built