ColoView records what your datacenter actually delivered and checks it continuously against what the lease requires. Power, temperature, capacity, and delivery dates, with the evidence assembled before the claim window closes.
You negotiated availability, an ASHRAE envelope, a PUE target, delivery milestones, and notice periods. Then the building went live and the only record of performance became a monthly PDF written by the counterparty.
Notice periods commonly run 30 days from the event. A breach nobody recorded is a credit nobody claims, and the clock does not wait for the quarterly review.
Their instruments, their measurement boundary, their number, delivered a month after the fact. It is the only evidence in the room, and it was written by the party being measured.
Some obligations in your lease have no telemetry behind them at all. A breach would go unrecorded. Nobody currently tells you which ones.
Compliant, exception, or unverifiable. The third one is not a failure mode. It is the most useful thing the product will tell you before a renewal.
Availability, capacity, envelope, efficiency, redundancy, and notice obligations, each with its clause reference, target, evaluation window, and remedy basis. Evaluated against measurement, not against a report.
| Obligation | Basis | Exposure | Window | State |
|---|---|---|---|---|
| CEDAR RIDGE CR-1MERIDIAN BTS · 5 OBLIGATIONS | ||||
| Critical power availability | Lease 7.1 | — | — | COMPLIANT |
| Rack inlet temperature | Sch. 4 | $21,600 | 14 DAYS | EXCEPTION |
| Design PUE | Sch. 4 | — | — | UNVERIFIED |
| GRANITE FALLS GF-1NORTHLAKE · 4 OBLIGATIONS | ||||
| Capacity delivery milestone | Lease 4.4 | $184,000 | 3 DAYS | EXCEPTION |
| Telemetry access | Exh. F | — | — | EXCEPTION |
Each breach opens a notice period derived from the lease. ColoView starts the clock at the measured event, escalates as it closes, and assembles the notice pack: what was measured, at which points, under which clause.
On build to suit, delay remedies are the largest numbers in the lease and the easiest to lose by accepting a date nobody independently confirmed. ColoView records when capacity actually became available.
Where an obligation has no telemetry behind it, ColoView says so and names the exact point that would fix it. That list is generated from the gap between your lease and your mapping, and it lands as an exhibit amendment when you need it.
| Obligation | Site | Point required | Status |
|---|---|---|---|
| Design PUE | CR-1 | Utility service entrance meter | NOT EXPOSED |
| Generator load test | CR-1 | Run state, load, fuel points | NOT EXPOSED |
| Rack inlet temperature | GF-1 | Per rack inlet sensors | DUE UNDER EXH. F |
| Cabinet inlet temperature | DA11 | Cabinet level, not cage level | NOT EXPOSED |
Because the evidence requires continuous measurement, you also get the top down view of every building: load against contracted capacity, A and B balance at the whip, inlet conditions, and the operator's alert feed, normalized across providers.
The access this needs is not something a tenant should route through a vendor cloud. ColoView runs entirely inside your environment, and the collector is written so that it cannot do anything but read.
One Docker Compose stack on your own VM. Air gapped installs supported with loadable image tarballs.
No write, command, or setpoint code path is compiled or shipped. Verifiable by reading the source, not by trusting a setting.
No inbound ports on the source network. Your team keeps the firewall rule and the segmentation.
No license check, update check, or analytics call leaves the stack. Licensing is an offline signed file.
SNMP, REST, Modbus, BACnet, MQTT, or a scheduled CSV drop. New operator APIs are configuration, not code.
Collector, gateway, schema, and adapters published under Apache 2.0, with an SBOM per release.
ColoView is delivered against the lease lifecycle, because that is when the evidence is worth something.
The point list, transports, refresh rates, and interface obligations written into the deal, along with recognition of tenant side measurement as valid evidence. A lease signed without it is a building you can only half instrument.
Capacity milestones confirmed from measurement rather than from a certificate. Finite, high value, and where the ROI case for everything else gets made.
Continuous obligation monitoring, claim window management, quarterly evidence packs, and a full term performance record to bring to the next negotiation.
Open the demo and look at a portfolio of five buildings, twenty obligations, and four operators, with the evidence already assembled.
ColoView asserts what was measured, with provenance, and names the obligation it bears on. It does not compute an amount owed, issue a claim, or determine entitlement.