Every rack, every port, every IP — in the same database as the invoice.
FluxBilling ships a real DCIM. Rack and U-position model, per-rack power budgets, IPMI and Redfish out-of-band, SNMP health polling, patch-panel cabling, and IPAM — one schema, no EasyDCIM-to-WHMCS sync to babysit.
What DCIM software does — and what changes when it lives in the billing schema
DCIM software — data center infrastructure management — tracks the physical layer of a data center: racks, devices, power circuits, cabling, and IP addresses. In FluxBilling the DCIM tables share one Postgres schema with billing, so a device assignment, a suspension, and the recurring invoice reference the same rows. There is no sync between two products to configure or reconcile.
One schema for racks, ports, IPs, and customers.
Inventory queries, power roll-ups, and IP allocations all run against the same Postgres database as billing — one query, no joins across vendors.
- Rack U-position
- integer start/end on every device
- Power budget
- kW + amps + voltage per rack
- Health polling
- SNMP v2c/v3 + Redfish
- IPAM
- IPv4 + IPv6 in the billing schema
Eight objects, one schema.
The DCIM isn’t a side panel that mirrors billing. Devices, ports, patch panels, IPs, and customers are joined directly — the activity log is the same activity log that records your invoice changes.
- Rack & U-position
- Each device records its rack, U-position start, and U-position end as integer values. The rack view aggregates devices by position, so reordering writes a single update on the device row.
- Power budget per rack
- Racks carry a power budget in kW, a circuit amperage, voltage, and a redundancy label (N+1 by default). Allocated draw is summed from per-device watts and colocation power_kw, and the headroom view rolls that against the rack budget.
- BMC & out-of-band
- IPMI 2.0 and Redfish 1.x are first-class. Power state, hardware inventory (CPU, memory, NICs, drives), and reset actions go through one Redfish client that resolves Dell, HPE, Lenovo, and Supermicro system paths.
- IPAM cross-reference
- Subnets, VLANs, and per-IP assignments live in the same database as rack inventory. Allocating an IP to a service records the assignment alongside the device, rack, and customer in one place — no second product to reconcile.
- Patch panels & cabling
- Patch-panel ports are first-class objects with front and rear connection types, port labels, cable type (Cat5e–Cat7, OM3/OM4/SM fibre, DAC, twinax) and cable colour. Front side links to switch/router/device ports; rear side links to server NICs, cross-connects, or other panels.
- Asset lifecycle
- Serial number, asset tag, manufacturer, model, and warranty expiry are stored on every physical device. Disposition states (available, allocated, reserved, maintenance, decommissioned, faulty) drive the inventory workflow.
- Switch & VLAN management
- Switch ports are polled via SNMP for status, speed, and traffic counters (32-bit and 64-bit). Admin status can be set from the UI via SNMP, and port connections are tracked against patch-panel and device endpoints.
- Activity log
- Inventory and admin actions write to the activity_log table with actor, action, entity, and JSON detail. Available in the admin UI for review; not a tamper-evident chain.
Hardware protocols supported on day one.
Vendor-neutral first, vendor-specific second. Anything outside this list ships as a plugin against the same OOB and polling abstractions.
Billing a colocation customer for a rack.
The DCIM is not a separate product you reconcile against. The customer reference, the device, the U-position, and the recurring price live in the same row.
Two products, one sync, drift watch.
Define the rack and customer in EasyDCIM, configure the WHMCS sync module, create the matching service in WHMCS, then issue the invoice. When the sync queue hangs, you reconcile manually.
Place the device, attach the customer, set the price.
Open the rack, assign the device to a U-position, attach the colocation service with its power_kw allocation, set the recurring price. Recurring invoices generate from the same record on schedule.
EasyDCIM has the deepest hardware-vendor BMC catalog on the market. If you need a niche vendor extension today, it’s still the leader. Our angle: one schema with billing.
Try it on your own data. Refund inside 14 days if it’s not the fit.
Pick a tier and provision a tenant in under two minutes — isolated K3s namespace, your own database, the full product. If FluxBilling isn’t the right fit inside 14 days, open a ticket and we’ll refund the subscription. No sales call, no qualification gate.
- 01.< 1 minPick a tierLite from €4.95/mo. Upgrade later, no migration.
- 02.< 2 minProvision the tenantIsolated K3s namespace + your own PostgreSQL database. Full product, your data.
- 03.d0 — d14Refund inside 14 daysNot the fit? Open a ticket within 14 days and we refund the subscription. No questions, no qualification gate.