Platform footprint
The platform's own compute, power and water draw, published as a report.
We audit ourselves the same way
Watermark's own hosting, storage, and inference costs are read from billing exports and published with the same evidence tags used for every other domain — modeled, not metered.
Static pages cost less to serve
Because most pages are static documents rather than a live dashboard, the platform's own compute footprint is a small fraction of a comparable data-driven app.
The report updates, it doesn't reset
Each publication cycle appends to the running report rather than replacing it, so the platform's footprint can be read as a trend, not a snapshot.
A hosting draw read from the cloud billing export is [reference] ; the associated water footprint, modeled from the provider's published PUE, is [inference] .
The platform reports its own footprint with the same discipline it asks of every site it covers.