Enterprise DNA

Instead of Sunbird dcTrack

Stop renting Sunbird dcTrack. Own your rack records.

We build your version around your cabinets, review procedures and site paperwork. Enterprise DNA maps the agreed dcTrack exports, brings your records across and runs the system for you.

Sunbird lists dcTrack at US$19.50 per cabinet per month, US$234 per cabinet annually. This published offer is US-only, with annual payment up front. Get an ANZ quote before comparing your own bill.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

Read the renewal

The cabinet count drives the subscription

Sunbird sells a complete operations product. Compare the parts your team uses with the records and weekly work you need to own.

paid

A licence for each cabinet

The published dcTrack subscription is US$19.50 per cabinet per month. Adding cabinets changes the licence count.

calendar_month

An annual commitment

Sunbird lists US$234 per cabinet annually and requires the subscription year to be paid up front.

groups

Unlimited people already included

dcTrack includes unlimited users, sites and assets. This comparison is about ownership and cabinet licensing, not removing a per-person charge.

inventory_2

The asset and capacity layer

The operations product covers asset, capacity and change management. Those are the records this free base starts with.

settings

Services around the software

Sunbird offers installation, migration, training and integration services with deployment-specific pricing.

monitoring

Monitoring is a separate decision

Sunbird also sells Power IQ for power, energy and environmental monitoring. Agree the monitoring connections your custom version needs.

The weekly work, in your system

Start with the records that decide the next job

Capacity review

Find contiguous room before booking a move

Use recorded dimensions and declared power allocations to find possible placements. Missing facts stay visible.

  • check Check consecutive free rack units
  • check Count installed and planned allocations
  • check Block a fit when cabinet or device inputs are unknown
  • check Add your own approval limits to the same review

Asset audit

Bring overdue checks into the Monday conversation

See which devices lack a recent audit, a business owner or a usable warranty date.

  • check Review audits older than your chosen interval
  • check Keep serial numbers beside cabinet positions
  • check Separate unknown power from recorded allocations
  • check Record the evidence and person behind each check

Change paperwork

Keep the request, review and completion together

A move has a due date, a reason and a rollback plan. Record the review before recording completed work.

  • check Require a reviewer different from the requester
  • check Recheck recorded capacity when completing a move
  • check Flag missing practitioner references on electrical requests
  • check Produce branded draft work orders and asset audit sheets

Your review rules

Ask questions across your own records

Combine asset ownership, direct connections, audit gaps and planned work without waiting for a product release.

  • check See the recorded neighbours of a server being moved
  • check Trace who changed an operational record
  • check Preserve original imported item fields
  • check Add a report that combines your own exceptions and site policy

Make it yours

Design your own Sunbird dcTrack replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Data Centre Operations for Claude Code

Connected to your own database

Which cabinets are over their declared power budget?

Auckland

Cabinet
AKL-A01
Units
42
Budget_w
4000
Occupied_units
5
Allocated_w
2050
Incomplete_assets
0
Free_units
37
Headroom_w
1950

Auckland

Cabinet
AKL-A02
Units
42
Budget_w
6000
Occupied_units
4
Allocated_w
2000
Incomplete_assets
0
Free_units
38
Headroom_w
4000

Wellington

Cabinet
WLG-B01
Units
42
Budget_w
3000
Occupied_units
2
Allocated_w
3200
Incomplete_assets
0
Free_units
40
Headroom_w
-200

Ask it anything

Ten questions the free version answers today

These examples run against the fictional demo. They show what this build does, without claiming that Sunbird cannot produce similar reports.

chat_bubble Which cabinets can take a four-unit device with a declared 1200-watt allocation?
chat_bubble Which capacity answers are blocked by missing facts?
chat_bubble Which installed devices have gone more than 90 days without a recorded audit?
chat_bubble Which change requests are overdue or awaiting review?
chat_bubble Which directly connected devices need a review before we move this server?
chat_bubble Which business owners have unknown power allocations?
chat_bubble Which warranties have expired or end within 60 days?
chat_bubble Which electrical change records lack practitioner evidence?
chat_bubble Who changed a record and when?
chat_bubble What belongs in the Monday capacity and change review?

Switching

How to switch from Sunbird dcTrack

A move usually starts with a test import of cabinet and item records, followed by checking gaps, mapping any extra history and validating the new records before you cut over.

  1. 1

    Export your dcTrack records

    Start with the item-list CSV export, which is the supported import route for cabinet and item records. Export the fields and records your dcTrack account allows, usually CSV or Excel, and check with Sunbird dcTrack if you need help finding the export. Connections, previous changes, attachments and monitoring history are not part of that import, so decide which of those records you need separately.

  2. 2

    Test the item import

    Use the import's test run before writing records. It previews what the item-list data will bring in and lets you address mapping questions before loading the full set. Run the real import into an empty database, not the fictional demo database. The import keeps original item fields, leaves unknown dimensions and power unknown, and rejects malformed rows without partially applying them.

  3. 3

    Review flagged records

    Check every issue the import flags, including missing inputs and rows it cannot accept. Confirm cabinet and item names, locations, dimensions, power allocations and ownership against your source records. The import does not fill unknown dimensions or power with guesses. Resolve errors or document what remains unknown, then repeat the import and verify the resulting records before relying on capacity answers.

  4. 4

    Run both systems side by side

    Keep Sunbird dcTrack available while you use the new database for a short period. Compare asset and cabinet records, review planned allocations and change paperwork, and have site staff verify physical conditions. Treat discrepancies as follow-ups, not as proof the system has discovered hardware or measured power. This is a records and planning base, so keep your existing monitoring and physical site procedures in place.

  5. 5

    Switch off dcTrack

    Once the agreed records are checked and people know where new records belong, stop creating operational records in dcTrack and retire it under your own retention and access requirements. Keep any history you chose not to import available according to your records policy. Reconcile the records you agreed to bring across before you switch.

construction

Where the real effort goes

The import covers cabinet and item records, but the real work is usually mapping your own fields, cabinet rules and review practices, then deciding how much history to bring. Connections, previous changes, attachments and monitoring history need separate exports and mapping. Plan time with the people who know those records and site rules. If Enterprise DNA runs it for you, Enterprise DNA handles the agreed mapping, import and reconciliation before cutover.

Not ready for a call?

Get your Sunbird dcTrack switch plan by email

We will send you the step-by-step plan for moving your business off Sunbird dcTrack, 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, then npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Preview your dcTrack CSV export with import sunbird-dctrack --dry-run
  4. 4 Reconcile the records, set your cabinet limits and run your weekly review
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your fields, cabinet rules and review procedures
  • check Your agreed dcTrack records mapped and reconciled
  • check A web front end or different stack when required
  • check Reports and paperwork in your business name
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 Agreed monitoring and business-system connections
  • check Controlled access, backups and operating support
  • check Regular review of the rules as your sites change
Book a call with Sam

Questions

Instead of Sunbird dcTrack, answered

Does this replace our monitoring and physical site procedures? expand_more

The free version handles operational records, declared capacity and change paperwork. Your site team still verifies the real conditions. Enterprise DNA scopes monitoring connections and any phone or web workflow into your custom version before a cutover.

Can we bring our Sunbird dcTrack history across? expand_more

The free import takes cabinet and item records from the item-list CSV export, keeps the original item fields and flags missing inputs. Connections, previous changes, attachments and monitoring history need separate exports and mapping. Enterprise DNA agrees that scope with you and reconciles the records before you switch.

How does the price compare with Sunbird? expand_more

The vendor publishes US$234 per cabinet annually for dcTrack, with unlimited users, sites and assets. Its public offer is US-only. Use your own renewal or ANZ quote for the comparison. The free version has no software licence fee. Hosting and assistant usage have their own costs. Enterprise DNA charges one setup fee, then a retainer for the agreed service.

Will this certify electrical work or approve a physical change? expand_more

It records review evidence and flags missing New Zealand practitioner or certificate references. It does not issue certificates or decide that work is safe. Your qualified people determine the requirements for each site. Enterprise DNA configures your review rules and access controls as part of the custom version.

Who owns the records and controls access? expand_more

You own the database and can take a full copy of its records. The free version is an operator tool, with actor names supplied by the operator. Enterprise DNA sets up the agreed authenticated access, backup and approval arrangements when building and running your version.

Bring your cabinet count and your renewal

Spend 30 minutes with Sam. Show him the dcTrack work your team relies on, the reports you keep rebuilding and the site procedures that must carry across. Agree what your owned version needs and who will run it.

Data Centre Operations for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Sunbird dcTrack?

Get your version built