OEM Reach

Device manufacturers expose telemetry and control through proprietary clouds. kWh gives OEMs a single path to reach aggregators, utilities, and energy platforms.

Book a Demo

OEM Path

One integration surface, from first connection to verified outcome.

Step 1: Connect your cloud

Connect your device cloud once. kWh detects your telemetry and control endpoints and confirms scopes.

iManufacturer-sanctioned APIs only.
Connect your cloud
API credentialsverified
cloud.your-oem.com
1
Telemetry endpoint
detected · 5 metrics
2
Control endpoint
detected · 3 commands

Step 2: Map fields once

Your native fields map to the canonical model. Units, timestamps, and enums are normalized at ingestion.

iMap once; every downstream app benefits.
Field mapping
# your schema        canonical
battery_soc_pct   → state_of_charge
tstat_setpoint_f  → target_temperature
dev_uid           → oem_device_id
units normalizedUTC timestampsenums mapped

Step 3: Reach downstream apps

Once mapped, your devices are reachable by aggregators, utilities, and platforms through one connection.

iNew partners connect to kWh, not a new project.
Connected apps
Connected via kWh4 live
VPP operator · West
Utility DR program
Energy platform
Financier portfolio

Step 4: Nothing is lost

OEM-specific fields are preserved under oem_extensions, so your unique data survives normalization.

iFields with no canonical match are never dropped.
Preserved data
{
  "device_id": "dev_8f2c1a",
  "target_temperature": 51.7,
  "oem_extensions": {
    "eco_mode": true
  }
}
OEM-specific fields preserved
Connect your cloud
API credentialsverified
cloud.your-oem.com
1
Telemetry endpoint
detected · 5 metrics
2
Control endpoint
detected · 3 commands
Field mapping
# your schema        canonical
battery_soc_pct   → state_of_charge
tstat_setpoint_f  → target_temperature
dev_uid           → oem_device_id
units normalizedUTC timestampsenums mapped
Connected apps
Connected via kWh4 live
VPP operator · West
Utility DR program
Energy platform
Financier portfolio
Preserved data
{
  "device_id": "dev_8f2c1a",
  "target_temperature": 51.7,
  "oem_extensions": {
    "eco_mode": true
  }
}
OEM-specific fields preserved

Why Teams Choose kWh

Downstream Reach

One integration mapping layer instead of bespoke connectors per partner.

Preserve Data

Fields without a canonical equivalent are kept in oem_extensions.

Edge Option

Pair cloud APIs with the Edge Gateway for site-level open standards.

Faster Onboarding

New downstream applications connect to kWh, not a new OEM project each time.

Edge Gateway

Software license or palm-sized hardware for edge protocol translation.

Explore Edge Gateway →

Talk to the kWh team

Request a demo tailored to your use case and buyer segment.

Book a Demo