Service · Web development

Custom data centre software.

Custom DCIM, colocation client portals, capacity planning and sustainability reporting. For data centre operators, hyperscaler partners and enterprise owners who can no longer fit their facility workflow into a standard Sunbird or Schneider package.

Custom DCIMColocation portalCapacity planningPUE & sustainability

A data centre is not a server room.

The combination of property, energy, cooling, network fabrics and client SLAs makes a data centre a discipline of its own. Generic DCIM suites such as Sunbird, Schneider EcoStruxure IT, Vertiv Trellis, Nlyte, Cormant-CS, iTRACS and Patchmanager cover the basics, but every serious operator sooner or later hits their limits: the role model does not fit how your colocation team works, the client portal is an afterthought, and sustainability reporting comes from three systems that each have their own version of the truth.

At the same time, the demands on data centre operations are changing faster than vendors can update their roadmaps. AI workloads call for cooling models that no longer respect the classic PUE assumptions of six years ago. Edge sites want a fraction of the DCIM overhead but still need full multi-site visibility. Clients ask for scope 3 reporting that your supplier does not yet deliver off the shelf. And the EU Energy Efficiency Directive requires publication-ready energy and water use reports, whether or not your current tooling is prepared for that.

We build custom software for data centre environments where off-the-shelf tools no longer fit. Sometimes as a fully white-label colocation portal, sometimes as a layer on top of NetBox or GLPI, and sometimes as an integration platform that brings together DCIM, ITSM, ERP and facility monitoring. Always tailored to your workflow, never the other way round. Often alongside our cloud-native platform development when the stack becomes hybrid, or in tandem with our high-availability practice for mission-critical components.

The audiences we serve: colocation providers in the style of Equinix, Interxion, NorthC or EvoSwitch; enterprise data centre owners at banks, telecom companies and retailers running their own on-premises facilities; hyperscaler partners with a regional office or MSP role; carrier-neutral facilities; edge data centre operators; modular DC suppliers; data centre builders and consultancies needing custom tooling; and MSPs with multi-site data centres. Different worlds, one common thread: standard tooling forces a workflow that your customers never pay you for.

Three flavours of data centre software.

Depending on where your facility stands and which part of the operation is hitting a wall. We'll advise which direction fits during an initial conversation.

Compact project · fixed sprint budget

Colocation customer portal

A white-label self-service portal where your colocation customers can view their rack overview, submit remote-hands tickets, request badge access and download invoices. Single sign-on against their own identity provider, role-based access per organisation and an audit log at rack level. Branded with your own identity and domain, so customers never click through to a vendor portal. Built for operators who want to demonstrate their service level in everyday touchpoints, not just in the sales meeting.

Self-service rack overviewRemote-hands ticketingSSO & role managementBilling export
Mid-sized project · fixed sprint budget

Capacity and sustainability layer

A planning and reporting layer on top of your existing DCIM or NetBox. Capacity models for rack units, kVA and cooling per zone, real-time PUE and WUE per customer, and automated reporting for the EU Energy Efficiency Directive, ISO 14001 and customer Scope 3. Includes forecasting models that link your sales pipeline to available capacity, so sold space and actual space stop drifting apart. Ideal if your current DCIM works well for asset inventory but falls short on planning and compliance.

Capacity modelsPUE / WUEScope 3 exportEU EED reporting
Larger project · fixed sprint budget

Fully bespoke DCIM platform

The complete package for operators who can no longer fit their workflow into standard DCIM: asset and cable tracing, capacity, monitoring, ticketing, customer portal, billing and compliance in one coherent platform, with integrations to your ITSM, ERP and facility monitoring. Suited to multi-site operations, edge distributions and sector-specific compliance (financial DC, carrier hotel, healthcare data). Designed to preserve your operational logic, even if you consider a new DCIM vendor several years from now.

Asset and cable tracingERP integrationMulti-site and edgeAudit per rack

What you get at the end.

A production-ready platform running in your cloud, on-premises, or in a hybrid setup, plus everything around it so you can manage and extend it yourself.

  • The platform itselfProduction and staging environments running in your cloud (GCP/AWS/Azure), your on-premises cluster, or a hybrid setup where sensitive data stays within your facility.
  • Codebase and architecture documentationFull source code, build instructions, infrastructure as code and an architecture document that enables your IT team to continue developing the platform independently.
  • Operations runbookWritten for your facility team: how to add roles, how to import sensor data, how to use the audit log during an ISO audit, and how to validate failover scenarios.
  • Compliance packageDPIA, threat model, hardening report and mapping to ISO 27001, EN 50600 and, where relevant, NEN 7510 or PCI-DSS, so your auditor can get started straight away.
  • Managed services contract (optional)Ongoing monitoring, security patches, telemetry tuning and feature development. Fixed monthly fee, with four response-time levels depending on mission-criticality.

When bespoke development is the right choice.

Five situations where standard DCIM falls short and a bespoke platform, or a custom layer on top of it, becomes the more economical choice.

Colocation

Customer portal as a brand carrier

Your customers log in to a portal bearing your brand, not a generic Sunbird skin. Self-service onboarding, remote-hands orders and rack overviews are fully white-labelled, with a user experience that matches your service level.

Edge & modular

Non-standard workflow

Edge data centres, modular units and carrier-neutral facilities have workflows that the large DCIM packages model poorly. Custom development lets you run operators, technicians and customers according to your own logic.

Multi-system

Three sources of truth, one report

Capacity sits in DCIM, tickets in ServiceNow, contracts in ERP and sensors in a separate BMS. A custom platform brings these together so you have one report, not three versions of the truth.

Sustainability

Reporting pressure

The EU Energy Efficiency Directive, customers' Scope 3 questions and internal ESG targets call for PUE, WUE and carbon reporting per customer and per rack. This isn't available out of the box in a standard suite, but it can be built into a bespoke reporting layer.

AI data centres

GPU workloads & liquid cooling

AI clusters disrupt the PUE assumptions of classic data centres. Direct liquid cooling, immersion and high rack densities call for capacity models that vendors have not yet built in. We model them with you.

Compliance

Sector-specific

Carrier hotels with telco requirements, financial-sector data centres subject to PCI-DSS, and healthcare data under NEN 7510 each impose additional logging, segmentation and audit requirements that standard DCIM does not cover on its own. See also ISO 27001-compliant software.

How a data centre software project works.

1

Introductory meeting and facility walk-through

A conversation in which we establish which flows the platform needs to support — operations, customer portal, capacity, billing, compliance — and how your facility is physically organised. What is tied to a BMS, what to a DCIM, what lives in your ERP, and which processes still run on spreadsheets. For multi-site operations we visit at least two locations to understand the variation between sites.

2

Scope, architecture & data audit

Workshops with your operations and IT teams, plus an audit of the data sources: PDUs, CRAC units, sensors, badge system, ITSM and ERP. We establish where the source of truth lives, which integrations should be one-way or two-way, and which data must stay within your facility versus which can be sent externally. At the end: a concrete scope, an architecture choice (replace versus layer on top), a risk register and a sprint-by-sprint plan.

3

Building in sprints

A working build at the end of every sprint, tested against your own sensor and ticket data, not a demo dataset. Operators and colocation customers can take part early on a staging environment, so feedback feeds straight into the next sprint. We work with feature flags so that new modules are first enabled for a single facility or customer group before rolling out more broadly.

4

Hardening, audit preparation & rollout

Penetration testing by an external party, a hardening pass and mapping to ISO 27001 / EN 50600. Phased rollout per facility or per customer segment, training for key users and a short video tutorial for external colocation customers. Thereafter ongoing management for security patches, telemetry tuning and further development, depending on whether you prefer to handle this yourselves or entrust it to us.

Frequently asked questions.

What data centre operators usually want to know before we begin.

Do you replace Sunbird, Schneider EcoStruxure or Vertiv Trellis?
For a full enterprise DCIM replacement, that is rarely the most sensible choice. Those packages have years of asset inventory, sensor integrations and floor-plan tooling built in, which we don't want to rebuild from scratch. More often we build a custom layer on top (customer portal, capacity models, sustainability reporting) or replace specific modules where the standard falls short. For edge and modular data centres, where enterprise suites are overkill, we can deliver a complete platform, often using NetBox or GLPI as an open-source foundation for IT asset and IPAM data. The advice comes from the first workshop, based on your existing tooling and the gaps you experience in practice.
Can the customer portal be fully white-label?
Yes. In practice, this is one of the most common reasons to choose custom development. Your brand, your domain, your email templates, your UX. The portal layer pulls data from your DCIM, ITSM and billing systems and presents it in an environment that customers experience as part of your service, not as a link through to a vendor. Multi-tenant branding (for example, a reseller layer in which your partners serve their own customers) can also be built in, with separate themes per organisation and separate subdomain routing.
How do you handle custom capacity planning?
We model rack units, kVA, BTU cooling and network ports as separate capacity domains, link your customer contracts and SLAs to them, and build forecasting models for both sales pipeline and operational planning. AI data centre and liquid-cooling scenarios require additional models because the classic PUE assumptions no longer hold there, and we factor those into the design. Anomaly detection on power and temperature curves is a logical extension once the data pipeline is in place; we apply ML models trained on your historical telemetry, not on a generic dataset.
What about sustainability reporting (EU EED, Scope 3, PUE/WUE)?
Since the EU Energy Efficiency Directive, large data centres are required to report on energy and water use. We build real-time PUE and WUE per zone and per customer, map them to EN 50600 and ISO 14001, and deliver Scope 3 exports that your customers ask for. The reports come from a single source, not from three spreadsheets that contradict each other. For publicly shared sustainability reports, we also support DCiE, carbon footprint and renewable energy mix overviews, with an audit trail showing when each measurement arrived and which calculation it went through.
How do we connect ITSM, ERP and facility monitoring?
For ITSM we typically work with ServiceNow, Jira Service Management or TopDesk via webhook and REST integrations. On the ERP side, usually SAP, Microsoft Dynamics or Exact via an integration layer. Facility monitoring via Modbus, BACnet or SNMP, depending on the PDUs and BMS vendor. We can integrate maintenance workflows with a CMMS maintenance management system or build them as a module within the platform itself.
Which compliance frameworks do you cover?
As standard: ISO 27001, EN 50600 (data centre design and operations), ISO 14001 (environmental), ISO 22301 (business continuity) and GDPR. On request: NEN 7510 for healthcare data, PCI DSS for card data, SOC 2 for international customers, and TIA-942 where the data centre builder already applies it. For each project we explicitly map the relevant controls so that your auditor or customer CISO can work through them quickly. The platform itself is not the bottleneck: data classification, segregation of duties and logging are built into the architecture from sprint one.
How do you work together with our facilities and IT departments?
Almost always in the same sprints. Your facility engineers supply the domain knowledge on PDUs, CRAC units, badge systems and the quirks of your site; your IT team handles the IdP, ITSM and ERP integrations; we bring the software engineering and architecture. In the final sprint we run knowledge transfer, deliver an incident runbook and agree clear responsibilities so your team can manage the platform itself once it is live.
What determines the cost of a custom project?
The number of flows in scope (customer portal only, or also capacity and compliance), the number of systems to integrate, whether we build on an existing foundation (NetBox, GLPI, your current DCIM) or from scratch, and the level of compliance rigour your customers require. A bounded customer portal for a single facility is a far smaller project than a full multi-site platform with scope 3 reporting and ITSM integration. We work with fixed sprint budgets so you can steer each sprint: no open-ended commitments, no surprises after a few sprints.
What about high availability and mission-criticality?
For mission-critical components (customer portal, ticketing, billing) we design by default with a multi-AZ setup, automatic failover and thorough observability. For the sharper edges, such as active-active across multiple regions or sub-second failover, we work alongside our high-availability system development and the wider enterprise software practice.

Talk to us about your data centre software.

A thirty-minute introductory call, no obligation. Send us a rack diagram, a ticket export or simply a description of where things are hurting, and we will come to the conversation prepared and give you direction you can act on.

Edit content