Enterprise DNA

Instead of MaintainX

Stop renting MaintainX. Own your maintenance system.

We build your version around your plant and maintenance routines, bring your MaintainX data across and run it for you. Your service history stays in a database you own.

MaintainX Premium is US$65 per user per month billed annually, or US$75 billed monthly. Enterprise pricing is quoted privately.

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 recurring bill

Your maintenance records, priced by user and plan

MaintainX Essential is US$20 per user per month billed annually, or US$25 billed monthly. Premium adds parts, purchasing and meter-based maintenance. The decision is whether to keep renting the package or own a system shaped around your plant.

paid

Paid access for the team

MaintainX charges per user. Requester accounts are free, so count full users when checking your bill.

event_repeat

Recurring work in the paid plans

Essential includes unlimited repeating work orders. In your version, the service schedule and its source belong to your business.

inventory_2

Parts in Premium

Parts inventory is included in Premium. Your stock, usage and reorder levels can live beside the maintenance history you own.

shopping_cart

Purchasing in Premium

Premium includes purchase orders. Keep the supplier, expected delivery and committed cost together in your own records.

speed

Operating-hour triggers in Premium

Premium includes meter-based maintenance. Your version can apply the service thresholds agreed for each asset.

query_stats

Reporting by plan

Premium includes unlimited access to advanced analytics. Enterprise adds Report Builder. Owning the records lets you change the questions and calculations with your business.

What your version does

Run the maintenance week from your own records

Plan the work

A backlog that names the next decision

Bring requests, due services and repair jobs into one weekly review.

  • check See overdue, unassigned and quiet work together
  • check Create one active job per preventive schedule
  • check Compare remaining planned hours with each technician’s weekly capacity
  • check Change your priority rules and weekly questions around the plant

Protect the history

Evidence stays with the equipment

See the inspection date, its source and the work behind each asset.

  • check Flag missing inspection dates and interval references
  • check Record the site’s technician authorisation evidence
  • check Require recorded isolation references and completed procedure checks before closing work
  • check Adapt record checks to your site, with sources retained for review

Know the spend

Parts, labour and downtime together

Follow recorded costs without mixing currencies or treating ordered parts as consumed stock.

  • check Keep stock from falling below zero
  • check Receive a purchase once and update the stock balance
  • check Compare recorded reactive work and downtime by asset
  • check Change the cost analysis around your production lines and local priorities

Own the routine

Your paperwork, your questions

Get the week’s work and plant service history in your business’s name.

  • check Create branded job cards and service records
  • check Draft purchase paperwork and shift handovers for review
  • check Read weekly dashboards built from the same records
  • check Add your fields and reports without waiting for a vendor reporting plan

Make it yours

Design your own MaintainX replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your MaintainX 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 MaintainX data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real command results from fictional maintenance records, shown as a conversation. Your team asks in plain words and gets the records behind the answer.

forum

Maintenance for Claude Code

Connected to your own database

Which maintenance jobs need my attention today?

60000...

Title
Hoist safety inspection
Asset
Warehouse Hoist
Technician
Alex Chen
Status
open
Priority
high
Reason
no due date

60000...

Title
Replace conveyor bearing
Asset
Packing Conveyor
Technician
Mere Taylor
Status
On hold
Priority
urgent
Due date
2026-09-23
Reason
overdue; quiet over 7 days; on hold

60000...

Title
Investigate compressor leak
Asset
Air Compressor
Status
open
Priority
high
Due date
2026-09-27
Reason
unassigned

Ask it anything

Ten maintenance questions your records can answer

These answers run on the demo today. Change the questions and calculations around your own plant.

chat_bubble Which overdue jobs are unassigned, on hold or quiet for a week?
chat_bubble Which services are due by date or by operating hours?
chat_bubble Which technicians have more planned work than weekly capacity?
chat_bubble Which assets have repeat reactive jobs and recorded downtime?
chat_bubble What has each job consumed in parts and labour, by currency?
chat_bubble Which parts are below the stock level we chose?
chat_bubble Which ordered parts are late and what is still committed?
chat_bubble Which inspections lack a date, a source or current evidence?
chat_bubble Which completed jobs were on time and how long did they take?
chat_bubble What changed on a work order before the next shift took over?

Switching

How to switch from MaintainX

Moving off MaintainX means exporting your asset and work-order records, running a test import to see what carries over cleanly, and only then deciding what else needs mapping before you stop paying for the old system.

  1. 1

    Export your records from MaintainX

    In MaintainX, export what your plan allows, usually asset and work-order data as CSV. Work-order export needs a Premium or Enterprise administrator account, so check who on your team can run it. Keep the original export files and any supporting documents such as procedures or attachments separately, since you will want them later.

  2. 2

    Load the export as a test run

    Have your import run first as a test, not a live load. Nothing is kept as a real record until you say so. This lets you see how your assets and work orders come across before committing anything, and every original column from your export is kept rather than dropped or renamed without your say.

  3. 3

    Check what the import flags

    Look at what the test run brought across and what it did not. Asset and work-order records come in directly, but procedures, costs, recurrence and attachments need separate mapping before they count as working records. Decide what history you actually need rather than assuming everything should follow you across.

  4. 4

    Run both systems side by side

    Keep MaintainX active for a short period while the new records are in use. Compare open jobs, assets and technician assignments across both. This is where you catch missing fields, wrong mappings or gaps in inspection evidence before anyone relies on the new system alone for real work.

  5. 5

    Reconcile, then switch off MaintainX

    Once the team confirms the records match and nothing important was left behind, agree with them that the move is done. Cancel or downgrade the MaintainX account. Keep the original export files and supporting documents as your record of what moved and when, even after the licence ends.

construction

Where the real effort goes

The real work is rarely the export itself. It is deciding which fields, priorities and inspection rules should carry over as they are, and which need to change for your plant. Procedures, costs, recurrence and attachments always need separate mapping. Enterprise DNA does this reconciliation with your team when they install and run it for you.

Not ready for a call?

Get your MaintainX switch plan by email

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

Choose how you own it

Do it yourself, have it customised, or have us run it

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm run demo
  2. 2 Use Claude Code, Codex, OpenCode or Cursor
  3. 3 Test your MaintainX asset and work-order exports before applying the import
  4. 4 Set up your database, backups and access controls
Get it on GitHub

Built around your business

We customise it

Scoped around your plant

  • check Your fields and maintenance rules
  • check Your MaintainX data brought across
  • check A web front end if you want one
  • check A different stack if you want one
Get your version built

Omni by Enterprise DNA

We run it for you

Setup fee, then a retainer

  • check Installed, connected and operated inside Omni by Enterprise DNA
  • check Your records and agreed connections maintained with your team
  • check Backups and ongoing changes managed for the installation
  • check One partner to keep your maintenance system working
Get your version built

Questions

Instead of MaintainX, answered

Can we bring our MaintainX history? expand_more

Yes. The free version imports asset and work-order exports, with a test run before any records are kept. MaintainX work-order CSV export requires a Premium or Enterprise administrator. Keep the original files and supporting documents. We map additional procedures, costs, recurrence and attachments for your version.

Will technicians have phone entry and photos? expand_more

We can build the phone experience, photo capture and connections your team needs into your custom version. We agree the workflow and test it with the people doing the work.

Does a clear inspection report mean the plant is safe? expand_more

No. These checks identify missing or overdue records. Your competent people determine inspection intervals, assess equipment and control isolation. We keep the sources and evidence with the work.

Is this free to run, or do we need Omni? expand_more

The software is free and open source. Hosting and agent usage have their own costs. Choose to run it yourself, have Enterprise DNA customise it, or have us install and operate it through Omni by Enterprise DNA for a setup fee and retainer.

What can we change after moving? expand_more

Your fields, inspection reminders, priorities, documents and reports can change with the plant. You own the database and can export your records. We reconcile the migration with your team before you stop using MaintainX.

Build the maintenance system your plant needs

Book 30 minutes with Sam. Bring your MaintainX bill and one maintenance routine that is hard to keep on track. We will map the records, the migration and the version your team needs.

Book a call with Sam Get the free version

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

Done paying for MaintainX?

Get your version built