Your building data is scattered.
ninezero collects it all.
Utility portals, meter vendors, manual spreadsheets — building energy data lives in dozens of disconnected systems. ninezero connects them into a single, structured, queryable layer you control.
Connected to the Danish utility landscape
Pre-built adapters for the systems Danish municipalities actually use — Energinet DataHub (Eloverblik), Kamstrup READy, eForsyning (150+ utilities), Kredsløb and Aalborg Forsyning — plus MQTT/M-Bus for gateways. We handle the protocol differences so you don't have to.
Your provider has an API but no ninezero adapter yet? Tell us — connecting new Danish sources is what we do.
Know when a building misbehaves
ninezero watches every meter and surfaces abnormal consumption, data gaps and dead meters as concrete action items — an inbox, not another dashboard you have to remember to check. Weather-normalized baselines separate a real problem from a cold week.
Prove you’re compliant — EPBD & EED
See exactly where your public buildings fall short of EPBD 2024 and EED — expired energy labels, the label-B-by-2040 gap, the 3%/yr renovation rate, savings vs a 2021 baseline — each with a recommended action, a deadline, and the meter data that proves it.
Built for consumption data
A purpose-built time-series warehouse (ClickHouse) optimized for utility data. Columnar, partitioned by time, pre-aggregated hourly to yearly — designed for the read patterns that matter: aggregation across meters, buildings and time ranges.
Portable by design
Run ninezero EU-hosted in Denmark or on your own infrastructure, under your full control. Standard formats, open APIs, complete data export at any time. Your data never gets locked in.
Developed and operated from Aarhus, Denmark, and hosted within the EU — keeping your data in-region and under your control.
Semantically classified, not just stored
Every entity in ninezero — organizations, properties, buildings, meters — is classified with a Brick Schema URI, an open standard instead of a proprietary one. JSON-LD (REC/Brick) export is available today; broader ecosystem tooling on top of it is still early.
GET /api/meters/1042/measurements?from=2026-01-01
Authorization: Bearer nz_...
{
"meter": {
"id": 1042,
"meterType": "electricity",
"brickClassUri": "https://brickschema.org/schema/Brick#Electrical_Meter",
"building": { "id": 87, "name": "Rådhuset" },
"property": { "id": 12, "name": "Rådhuskvarteret" }
},
"measurements": [
{ "timestamp": "2026-01-01T00:00:00Z", "value": 42.7, "unit": "kWh" }
]
}Agent-ready API
A documented REST API for developers — structured JSON with an OpenAPI spec and interactive docs at /docs. Every response carries Brick URI references, so your own tooling can build on an open standard instead of a proprietary one.
The same API that powers your dashboards is available to every tool in your stack.
Ask your buildings anything
Pulse answers in plain language, grounded in your actual meter data — never invented. It reads energy reports and operations documents too, so building facts fill themselves in instead of being typed by hand.
Three schools are up year-over-year, weather-corrected:
See where your portfolio stands
Book a demo to see your own buildings scored against EPBD and EED, or explore the live platform.