Skip to main content
Platform

Nine modules. One resource operating system.

AquaWatt DC OS is not a collection of point tools. Each module shares the same telemetry, the same digital twin, and the same safety and approval model — so power, cooling, water, and compute are finally optimized as one system.

Resource Command Center
Platform simulation
Facility power
—MW
Cooling load
—MW
Water use
—L/kWh
IT utilization
—%
Carbon intensity
—gCO₂/kWh
Open recommendations
—
Facility power trend
Cooling load trend

Illustrative platform demonstration. Layout and metric types shown are representative of the command center interface; values are not from a live or historical deployment.

Explore the modules.

Select a module to see what it does, what it needs, and what it produces.

Resource Command Center

A single live view of the facility, so operators no longer stitch together separate dashboards to understand what is happening right now.

Key capabilities
  • Real-time power, water, cooling, and carbon state
  • Workload and IT load visibility alongside facility data
  • Cost and resource trends in one timeline
  • Alerting on abnormal operating conditions
  • Drill-down from facility to hall to equipment
Consumes

Telemetry from BMS, DCIM, SCADA, meters, and workload schedulers

Produces

Live operational picture and prioritized alerts

Key workflows

What the platform actually does, step by step

Modules are only meaningful in sequence. These are the five end-to-end workflows AquaWatt DC OS is being built around — each one ending in a human decision, a measured result, or both.

Facility onboarding

From first connection to a trusted baseline

Nothing is optimised until the data is proven. Onboarding ends in observation mode, where the customer validates every dashboard and calculation before AquaWatt recommends anything.

10 steps
  1. 1Administrator creates the organization and facility.
  2. 2Engineering team installs or registers the edge gateway.
  3. 3AquaWatt discovers or imports equipment and data points.
  4. 4User maps sensors to the facility hierarchy.
  5. 5Data-quality tests are completed.
  6. 6Operating limits and policies are configured.
  7. 7Historical data is imported.
  8. 8Baseline models are created.
  9. 9Facility enters observation mode.
  10. 10Customer validates dashboards and calculations.

Workflows describe intended platform behaviour under development. Some steps depend on capabilities scheduled for later releases — see the first release scope below.

First release scope

What ships first — and what deliberately does not

We would rather be precise than impressive. The first release proves that AquaWatt can integrate securely with a live facility, establish accurate resource baselines, forecast electricity and water demand, surface optimisation opportunities and verify measurable savings — without taking direct control of critical equipment.

Release objective. Every capability below exists to serve one outcome: a verified, defensible savings number that an operator, a CFO and a sustainability lead can all agree on.

In the first release

26 capabilities
  • Organization and facility management
  • Edge gateway
  • BMS and DCIM ingestion
  • Power-meter ingestion
  • Water-meter ingestion
  • Server or cluster telemetry
  • Weather ingestion
  • Data-quality monitoring
  • Real-time resource dashboard
  • Historical analytics
  • PUE and WUE reporting
  • Power forecasting
  • Cooling-demand forecasting
  • Water forecasting
  • Power anomaly detection
  • Water anomaly and leak detection
  • Cooling inefficiency detection
  • Baseline creation
  • Recommendation engine
  • Human approval workflow
  • Action audit log
  • Predicted-versus-actual savings
  • Monthly sustainability report
  • Role-based access control
  • Notifications
  • Initial AI copilot for read-only analysis

Intentionally excluded

Later phases
  • Fully autonomous control
  • Geographic workload shifting
  • Direct battery dispatch
  • Automated demand-response participation
  • Advanced liquid-cooling control
  • Heat-reuse marketplace
  • Cross-portfolio autonomous scheduling
  • Unsupervised reinforcement-learning control

These capabilities are on the roadmap but are held back until trust, data quality and safety envelopes are proven in operation. See the release roadmap on the company page.

Scope describes planned first-release functionality and is subject to change as development and pilot deployments progress. Nothing here represents a generally available product today.

See the platform against your own facility.

We’ll walk through which modules matter most for your systems and operating goals.