05 · Partners and OEMs
The energy data layer for your platform.
If you're an ESG software vendor, a sustainability consultancy, or an industrial OEM whose product needs energy data - you have two options. Build the IoT, ingestion and normalisation layer yourself, in every country your customers operate in. Or use Wia underneath, keep your engineering team on your core product, and ship faster.
Partners want their customer experience to feel like one product, not a Frankenstack. Wia is built to disappear: typed REST and webhook APIs, predictable schemas, hardware drop-shipped in your branding. Your salespeople don't sell 'a Wia integration'; they sell their platform with energy data already in it.
REST + webhooks
Or push to your warehouse
White-label
Your UI, your customer
Hardware
Drop-shipped or BYO meter
How a partnership comes on
Three steps. From contract to live in weeks.
01
Define the contract
We agree the data shape, the integration model (push or pull), the SLA and the commercial model. Most partnerships are productised - fixed per-meter pricing - but bespoke deals work too.
02
Connect
API keys provisioned, sandbox available the same day. Your engineering team integrates against the sandbox; we co-engineer through the shared Slack channel. Most partners are flowing live data within two weeks.
03
Scale
Roll out to your customers in their geographies. Wia handles hardware fulfilment, country-level connectivity, tariff data, regulatory shape. Your team stays focused on your product and customer relationship.
Inside Partners and OEMs
Everything Partners and OEMs brings, in one place.
Typed JSON schemas
Every endpoint documented with explicit, versioned schemas. Breaking changes ship behind new versions, never silent. Reading once is enough to integrate; you don't need to learn the energy domain.
Webhook event stream
Push, not pull. Subscribe to consumption events, anomalies, device-status changes and report-ready signals. Your platform reacts in real time without polling our API.
SSO & SCIM for your tenants
Your customers' users authenticate against your IdP, not ours. SCIM provisions and deprovisions automatically when your customers add or remove users on their end.
White-label hardware
Hardware drop-shipped to your customer in your branding or unbranded - your call. Configuration codes and onboarding flows can mention only your product. We're invisible to the end customer if that's what the partnership calls for.
SLAs on data freshness
Contracted SLAs on ingestion latency, uptime and incident response. If your platform commits 15-minute freshness to your customer, we commit it to you, in writing.
Co-engineered onboarding
A named technical contact and a shared Slack channel from kickoff. We co-design the integration with your engineering team, then keep the channel open as a working group, not a ticket queue.
Partners integrate Wia's data layer to give their customers meter-level granularity without building the IoT infrastructure themselves.
Architecture
Your platform, Wia’s data layer.
Wia handles everything below the data line: hardware, connectivity, ingestion, normalisation, tariffs, currencies, regulatory framing. Your platform consumes a typed energy dataset via API or warehouse-push and stays focused on what makes your product valuable. Where the partnership calls for it, the end customer never sees the Wia name at all.
You ship the energy data; we ship the layer underneath. Frictionless to your customer.
Built for
The platforms partners build on top of Wia.
Wia is most often the data layer for one of four partner archetypes - each integration shape is different, but the API contract is the same.
ESG software
- Carbon accounting
- CSRD / EPBD platforms
- Building certification (LEED, BREEAM)
- Reporting consultancies
Industrial & OEM
- Solar / EV charging OEMs
- BMS vendors
- Industrial automation
- HVAC manufacturers
Capital & advisory
- Real estate asset managers
- Infra & energy funds
- Sustainability consultancies
- Energy procurement advisors
FAQ
Common questions
Do our customers know it's Wia underneath?
Only if the partnership calls for it. Default is fully white-labelled - hardware in your branding, end-customer dashboards under your domain, support routed through you. Some partnerships expose Wia as a named component; we follow your lead.
Can we keep the customer relationship and contract?
Yes. Most partner deals are structured so you contract your customer, we contract you, and the end customer never sees a Wia contract. There are deal shapes where this differs - happy to walk through what fits.
What if you launch your own product in our segment?
We don't compete with partners in the segments we partner in - that's a deal-level commitment, not just a friendly assurance. Where there's any ambiguity, we paper it in the partnership agreement.
How do you handle data residency for our EU customers?
EU data is stored and processed in EU regions. Customers with specific residency requirements (UK, US, APAC) are routed to the right region automatically. Schrems-II compliant by default; SCC and DPA available.