NodX vs Sunbird dcTrack
Different tools for different questions. dcTrack = asset CMDB, change management, Power IQ. NodX = adaptive anomaly detection & capacity intelligence. Most colo teams run both — here is the honest map.
Last verified: 2025-01. Sources
TL;DR
Choose NodX if…
- You need adaptive anomaly detection (hour-of-day baselines, not static thresholds)
- You want stranded-power recovery (p95 headroom, node-fit math) out of the box
- You prefer flat per-rack pricing with no seat/device/metric meters
- You want a 2-week pilot, not a 6-month implementation
- You need alert lifecycle (fire → ack → escalate → resolve) with HMAC webhooks
Choose dcTrack if…
- You need asset lifecycle management (procurement → decommission workflows)
- You need change management with approval chains, scheduling, impact analysis
- You need contract / lease / warranty tracking per asset
- You need Power IQ for detailed what-if power/thermal simulation
- You have budget and timeline for a professional-services-led rollout
Feature Matrix
| Capability | dcTrack | NodX |
|---|---|---|
| Primary question answered | Where is asset X? What changed? | What is anomalous right now? |
| Data model | CMDB / asset-first | Time-series telemetry-first |
| Deployment model | Professional services, 6–12 month rollout | Binary + container, 2-week pilot |
| Pricing | Per-asset / per-user / module | Flat per-rack ($5 / $12 / Custom) |
| Capability | dcTrack | NodX |
|---|---|---|
| Redfish / SNMP / MQTT ingest | Via connectors / adapters | Native, first-class |
| Adaptive per-device baselines (24 hourly) | ❌ Threshold-only | ✅ Z-score, hour-of-day |
| Stranded-power / capacity math | Add-on module (Power IQ), manual | Built-in: p95, headroom, node-fit |
| Alert lifecycle (fire → ack → escalate → resolve) | Workflow engine, config-heavy | Native, HMAC webhooks, presets |
| Capability | dcTrack | NodX |
|---|---|---|
| Users & sites included | Per-seat licenses | Unlimited at every tier |
| Data retention | Configurable, storage-dependent | 30d raw / 1yr hourly / 2yr daily (Pro) |
| Export & webhooks | API + custom integration | Included (Pro+): Slack, Teams, Discord, PD |
| SSO / SCIM / Audit | Enterprise module | Enterprise (scoped per deal) |
| Capability | dcTrack | NodX |
|---|---|---|
| Asset import (CSV / JSON / NetBox / Device42) | Professional services | Self-serve dry-run, skip/merge/replace |
| Run both simultaneously | Possible, dual maintenance | Designed for it: NodX → DCIM webhook/API |
| NodX as intelligence layer on dcTrack | N/A | Recommended: dcTrack = system of record, NodX = system of intelligence |
Coexistence (The Real Answer)
"Most colo teams run both. dcTrack remains the system of record for assets, contracts, change management, and Power IQ simulation. NodX becomes the system of intelligence for live operations — anomaly detection, alert lifecycle, and operational capacity math."
dcTrack owns
- Asset CMDB (location, owner, warranty, lease)
- Change management workflows
- Contract / vendor management
- Power IQ: what-if power/thermal simulation
- Connectivity / cabling management
NodX owns
- Live telemetry ingestion (Redfish, SNMP, MQTT)
- Adaptive anomaly detection (24 hourly baselines)
- Alert lifecycle: fire → ack → escalate → resolve
- Operational capacity math: stranded power, p95, node-fit
- HMAC-signed webhooks to dcTrack / ServiceNow / Jira
Integration pattern: NodX incident.fire → webhook → dcTrack ticket / ServiceNow incident / Jira issue. Bi-directional asset sync via REST (NodX ←→ dcTrack) on a schedule or webhook trigger.
Frequently Asked
Can we keep Sunbird dcTrack and add NodX?
Yes — this is the most common path for colocation operators. dcTrack remains your asset CMDB, change management, and contract system. NodX ingests Redfish/SNMP/MQTT, runs adaptive anomaly detection and capacity math, then forwards incidents to dcTrack (or ServiceNow, Jira) via webhook. No rip-and-replace.
What does migration look like?
Export assets from dcTrack (CSV/JSON) → NodX import dry-run (preview conflicts, choose skip/merge/replace) → approve → live. The dry-run is mandatory; nothing writes until you confirm. Round-trip export back out any time.
Does NodX do Power IQ style capacity planning?
NodX has built-in stranded-power math: per-rack power_capacity_watts reconciled with p.demand_watts, p95 profiling, headroom calculation, node-fit (how many average nodes fit in remaining headroom). Power IQ is a separate licensed module in dcTrack with more what-if simulation; NodX focuses on live operational math.
Pricing difference at 200 racks?
dcTrack: typically $200k–$500k/yr depending on modules (Power IQ, Connectivity, CMDB), users, assets. NodX Pro: 200 × $12 = $28,800/yr flat. No per-user, per-device, or per-metric meters.
Implementation timeline?
dcTrack: 6–12 months with professional services. NodX: pilot in 2 weeks (binary + container, guided import), production in 4–6 weeks. We measure in days, not quarters.
Sources & Verification
All dcTrack data from public product pages, data sheets, and sales conversations. NodX data from shipped product (docs.nodx-ops.com).
- Sunbird dcTrack product overview
- Sunbird Power IQ module
- Sunbird pricing (contact sales)
- Sunbird data sheets (PDF)
- NodX docs — import / export
- NodX docs — webhooks / integrations
Sunbird® and dcTrack® are registered trademarks of Sunbird Software, Inc. NodX is not affiliated with, endorsed by, or sponsored by Sunbird Software.
Running dcTrack today? Add the intelligence layer in two weeks.
Pilot with your real telemetry. No professional services contract. No rip-and-replace. Export your dcTrack assets, dry-run import, go live.