CAYNMARS is designing and developing NEXUS OS, proprietary software for operating on-site power at AI data centres. Rather than delegating power control, availability measurement and carbon accounting to separate commercial tools, the objective is to handle them within a single control layer.
The functional structure on this page is a design basis. The development status of each module is stated separately in the table below. Unverified performance is not published.
Each layer operates independently while sharing a common data model, so the same structure can be applied repeatedly as additional sites are developed.
Development data standard
Site, power, permitting and procurement deliverables are managed under a single data model, so each project accumulates into a reusable standard rather than starting from scratch.
Control layer
Fuel cells, storage and the grid interface are operated from one control layer. The objective is to handle rapid AI load variation through rules and prediction rather than operator judgement.
Availability and SLA measurement
A measurement and reporting layer that evidences contracted availability and power quality. Measurement points and formulas are aligned with the contract schedule.
Carbon accounting and evidence
Hourly carbon intensity and capture performance are measured continuously and retained in a form that supports third-party verification, derived from operating data rather than annual estimation.
| Layer | Current status | Verification method | Verification point |
|---|---|---|---|
| Site Model | Design complete · in development | Internal data migration and consistency check | Applied during Project Nexus development |
| Power Orchestration | Design complete · in development | Power quality demonstration and integrated testing | Joint demonstration stage |
| Assurance | Design in progress | Alignment of measurement points with contract schedule | After Pre-FEED |
| Carbon Ledger | Design in progress | Mass balance reconciliation and third-party protocol | After FEED |
There is no commercial operating record to date, and no performance figures are presented before demonstration is complete.
We state what the software does not do, as this is more useful for technical review.
GPUs, servers, network fabric, security and workloads remain under customer control and are outside the control scope of this software.
Protective systems of generation and cooling equipment remain under the manufacturer's native control. This software operates above that layer for dispatch decisions.
It does not replace commercial EMS, DCIM or BMS. It integrates through standard protocols and APIs and provides the integrated decision and evidence layer.
Control logic is confirmed through demonstration and integrated testing. No performance is claimed before verification, and results are submitted as deliverables.
Intellectual property in NEXUS OS is held by CAYNMARS rather than by a project company. Land, generation assets and project finance sit in a separate company for each site, while the standard specification and operating software remain with the firm and are applied to the next site. This is the basis on which we pursue a repeatable energy business rather than one-off development.
Information on this page includes plans and targets, stated separately from confirmed facts. Detailed architecture, data models and integration specifications are provided after a non-disclosure agreement.