KERN — For VPP Platforms

Your platform is strong
above the asset layer.
KERN closes the gap below.

KERN integrates below your VPP as the asset management and connectivity layer. Your platform gets a clean, normalised API feed, confirmed dispatch and 24h flexibility forecasts — for every asset your clients have, including those currently unreachable.

Discuss API Integration

Where KERN fits in your stack

Market / TSO / Grid Operator
         ↓
┌─────────────────────────────────────────────┐
│         YOUR PLATFORM                       │
│  VPP optimisation · Bidding · Redispatch    │
│  Trading · Reporting                        │
└─────────────────┬───────────────────────────┘
                  │  Normalised telemetry feed
                  │  Dispatch commands + confirmation
                  │  24h flexibility forecast
┌─────────────────▼───────────────────────────┐
│         KERN                           │
│  Asset management · Autonomous dispatch     │
│  Real-time optimisation · Forecasting       │
└─────────────────┬───────────────────────────┘
                  │
         Zigbee Mesh  ·  MIOTY
                  │
┌─────────────────▼───────────────────────────┐
│  PV · BESS · Heat pumps · EV chargers       │
│  CHP · Controllable loads · Microgrids      │
└─────────────────────────────────────────────┘

Three gaps KERN fills

Problem
Assets with unreliable connectivity stay out of the portfolio
Rural sites, industrial premises, basements — LTE drops, WiFi is unstable. Your clients can't bring these assets into your platform. Potential stays on the table.
KERN
MIOTY (10km, IEC standard) and Zigbee Mesh make every asset reachable — your clients grow their portfolio without infrastructure investment.
Problem
No dispatch feedback — the loop is open
Your platform sends commands — but whether the asset responded stays unknown until the next meter reading. Deviations are detected too late, penalties hit your clients.
KERN
KERN confirms every dispatch at asset level and reports back in real-time. Your platform knows immediately whether the flexibility commitment is being met.
Problem
Heterogeneous assets increase integration overhead
Every new asset type, every new manufacturer, every new protocol means integration effort — for you or your clients. This slows onboarding and limits scale.
KERN
KERN normalises all asset types to a single data model. Your platform speaks to KERN — not to every asset individually.

What your platform gets from KERN

Clean, normalised API feed

Unified telemetry regardless of how many asset types, manufacturers or protocols are behind it. One integration, all assets.

Dispatch with confirmation

KERN receives your dispatch command, executes at asset level and reports back whether and how it was fulfilled.

24h flexibility forecast

Rolling 24h forecast per asset and portfolio — driven by live telemetry, weather-based PV models and historical load patterns. Continuously refined as delivery approaches. More precise bids, fewer penalties for your clients.

More assets in the portfolio

Assets currently excluded due to connectivity become available. Your clients grow their dispatchable portfolio without CAPEX.

Integration options

Model Description Effort
API integration KERN delivers normalised telemetry and accepts dispatch commands via REST/WebSocket. Your platform remains primary. Low
White-label KERN runs under your brand as an "Asset Connectivity Module" for your clients. Medium
Pilot One client, one asset class, defined scope — fast to start, low risk. Minimal

Let's discuss the API.

30 minutes to go through the spec and identify which of your clients' assets are currently excluded — and how quickly that changes with KERN.

Discuss API Integration Explore the Technology