Enterprise DNA

Instead of Infrahub

Replace your Infrahub Enterprise bill. Own your address planning workflow.

We build your version around address allocation, ownership reviews and change handovers, bring your Infrahub records across, and run it for you.

Infrahub Enterprise starts at $40,000 a year. The vendor does not label the currency. Infrahub Community is free.

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 licence covers

Check whether you need the whole infrastructure platform

Infrahub Enterprise charges for processing capacity and enterprise capabilities. Its Community edition already provides the core platform for free. Compare the part your team uses with the version you actually need.

paid

An annual Enterprise licence

The published starting price is $40,000 a year. Check your actual contract and currency before comparing costs.

database

Capacity for infrastructure records

Enterprise packages allocate processing capacity for infrastructure data. The package is broader than an address register.

settings

Capacity for automation work

Workers handle actions such as generating artifacts and running checks. Those requirements affect the package you need.

verified

Production scale and releases

Enterprise includes high availability, performance work and hardened releases. Include those needs in the comparison.

lock

Advanced access controls

Enterprise adds advanced permissions. A shared replacement needs access rules designed and tested for your team.

support_agent

Support and optional services

Standard support is included. Expanded support and implementation services are available separately.

Your address desk

The weekly network review, built around your rules

Capacity

See where the next address will come from

Keep the address plan and its remaining capacity in one review.

  • check Separate networks can reuse the same private addresses
  • check Count held and active addresses against each range
  • check Track address space assigned to child ranges
  • check Find the next free address in your recorded inventory

Accountability

Put an owner beside every range

Turn missing ownership and overdue evidence into a practical work list.

  • check Find ranges without an owner
  • check Review held addresses before their next-review date passes
  • check Record who checked the evidence and when
  • check Attach a follow-up and due date to the network it affects

Decisions

Keep the reason behind each reservation

Review proposed reservations against current records before saving a decision.

  • check A second named operator records the decision
  • check Availability is checked again at approval
  • check Competing approvals cannot reserve the same address twice
  • check Keep a snapshot of the record that supported the decision

Handover

Give the next operator the whole picture

Produce a handover from the same records used in the weekly review.

  • check Your business name and colours on the documents
  • check Address ranges, ownership and follow-ups together
  • check A separate record of each change decision
  • check Add your own fields and review rules to the owned version

Make it yours

Design your own Infrahub replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Network Addresses for Claude Code

Connected to your own database

Which office ranges are running out of addresses?

capacity

Harbour Office

Name
Office aggregate
Subnet
10.20.0.0/16
Used_percent
0.01
Available
65528

Harbour Office

Name
Office printers
Subnet
10.20.1.0/29
Used_percent
83.33
Available
1

Harbour Office

Name
Office uplink
Subnet
192.0.2.0/31
Used_percent
0.00
Available
2

Harbour Office

Name
Office IPv6
Subnet
2001:db8:10::/64
Used_percent
0.00
Available
18446744073709551615

Ask it anything

Ten questions your address desk can answer

These questions run against the free version today. They demonstrate the owned workflow, without claiming that Infrahub cannot answer them.

chat_bubble Which ranges have less than a fifth of their addresses left?
chat_bubble Which held addresses need another ownership review?
chat_bubble Which addresses have no containing range?
chat_bubble Which identical addresses belong to separate networks?
chat_bubble What is the next recorded free address in the printer range?
chat_bubble Which change decision is overdue?
chat_bubble What evidence supported an approved reservation?
chat_bubble Which follow-up belongs to the warehouse operator?
chat_bubble Who changed a record, and what did it say before?
chat_bubble How much space is assigned to child ranges without counting nested ranges twice?

Switching

How to switch from Infrahub

A move usually involves exporting prefixes and addresses, mapping your fields and rules, checking the imported records, then running both systems side by side before you stop using Infrahub.

  1. 1

    Export your address records

    Use Infrahub’s documented object-list CSV export, or the standard prefix and address list exports available to your account, to take out your prefixes and addresses. Include any available ownership or review data you want to reconcile. If you are unsure which records your account can export, check with Infrahub. Keep the original export as a backup.

  2. 2

    Preview and load the records

    Load the prefixes and addresses using the replacement’s Infrahub import. Start with its test preview, which shows what it would bring in without changing the database. Review the preview before running the import for real. The import keeps original columns for reconciliation, and skips identical repeat imports. Keep your authorised export and original backup unchanged.

  3. 3

    Reconcile flagged records

    Work through the import’s flagged rows and reconciliation issues before treating the data as ready. Check invalid rows, hierarchy problems, and changed duplicates, which need an explicit decision. Verify owners and review dates because imported values start unverified. Custom fields and relationships need mapping, and the namespace label must uniquely identify each network. Compare the imported records with your saved export.

  4. 4

    Run both systems side by side

    Keep Infrahub available while operators check the new records and carry out address reviews in both systems. Compare prefix and address records, reservation decisions, ownership, and evidence against the current Infrahub records. A reservation in the new database is a planning record only, so operators still need to verify live network state and follow the approved deployment process.

  5. 5

    Stop using Infrahub

    Once the records are reconciled and operators agree the new workflow meets their needs, make the new database the place they use for address planning and stop using Infrahub for that work. Keep the original export as a backup. Before ending Infrahub access or a contract, check what your team still depends on. This is a smaller address planning workflow, not a replacement for the entire Infrahub platform.

construction

Where the real effort goes

Most of the work is mapping your custom fields, relationships, ownership and review rules, then deciding which history to bring across. The import covers base IPAM attributes for prefixes and addresses, not arbitrary Infrahub models, automation code, device credentials, branch history or permissions. Enterprise DNA handles the mapping and import checks when it installs and runs your custom version.

Not ready for a call?

Get your Infrahub switch plan by email

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

Start with the free version or have your version built and run

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and ask for the weekly review
  3. 3 Export Infrahub prefix and address lists, then preview each import
  4. 4 Check your records and review evidence before using a separate database for real work
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your network boundaries, ownership fields and review rules
  • check Your Infrahub export mapped and reconciled
  • check Shared screens and connections built for your operators
  • check A different underlying technology when your environment needs it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access and backups set up for your team
  • check Address reviews and handover documents prepared from your records
  • check Connections and controls tested before operational use
  • check Kept working through Omni by Enterprise DNA
Talk to Sam

Questions

Instead of Infrahub, answered

Infrahub already has a free edition. Why consider this? expand_more

Infrahub Community is free and includes the core infrastructure data platform. This is a smaller address planning workflow with ownership reviews, reservation decisions and handovers. We compare the Community edition, your Enterprise contract and your actual requirements before recommending a change.

Can our existing Infrahub records come across? expand_more

The free version imports the standard prefix and address list exports, preserving the original columns for reconciliation. Custom fields and relationships need mapping. Owners and review evidence must be verified after import. Enterprise DNA handles the mapping and checks in your custom version.

Does an approved reservation change the network? expand_more

No. It records a reservation in your database. Operators still verify live network state and use their approved deployment process. Discovery, address services and device connections are custom work that we build and test before they take over an operational job.

Can several operators use it with different access? expand_more

The free version is for trusted operators. A named reviewer is recorded with a decision, but it is not a sign-in service. We build authenticated access, permissions and shared screens into your version around the people who need to use it.

How do we compare the cost? expand_more

Bring your actual invoice and the work your team needs done. Enterprise starts at $40,000 a year on the vendor page, which does not label the currency. Community is free. Hosting and agent usage have separate costs. Our version is built for a setup fee and then run on a retainer, with the scope agreed from your requirements.

Bring your Infrahub invoice and one address review

Spend 30 minutes with Sam. Show the ranges you manage, a recent change decision and the parts of Infrahub your team uses. We will work out what your own version needs, including the controls and connections that make it useful.

Book 30 minutes with Sam Get the free version

Network Addresses for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Infrahub?

Get your version built