blurple eMobility OS sits on top of the charging platform and the driver app you already run. It keeps drivers coming back with games, rewards and loyalty, shows what that does to retention and revenue, and puts the market in front of your growth team. It doesn't replace your CPMS; it works on top of it.
From the team behind the Snake game 700,000+ Zes drivers play.
CONCEPT SCREENS · ILLUSTRATIVE VALUES
An API bridge to your charging platform and app: sessions, stations and driver IDs.
Games, streaks, rewards and seasons, inside your own driver app through a light SDK.
Tiers, wallet cards and win-back journeys for drivers who drift away.
Drivers who took part against those who didn't, before and after.
Store ratings, reviews, social mentions and competitors, next to your charging data.
↺ Every result shapes the next season.
In Türkiye, charging sessions nearly doubled in the first half of 2026, yet public DC chargers are in use less than 5% of the time, against more than 20% in mature markets, and revenue still rests almost entirely on selling kWh. The operators that do well will be the ones drivers choose again and again. That's the layer we build.
Sources: EPDK Charging Service Market Report, July 2026; ODMD.
Each module switches on for your team on its own, without a new install. Most operators start with Engagement & Loyalty.
Keeps drivers in your app, and brings them back.
Shows what the experience layer does to retention and revenue.
Reaches your drivers, and keeps an eye on the market.
The pictures are illustrative.
The full list we're building. Engagement & Loyalty comes first, then Analytics & Attribution, then Marketing & Growth; the AI features switch on as your data builds up.
We built Snake inside the Zes app: drivers play while their car charges, and come back for the next season. Engagement & Loyalty brings games like it into your app, in your brand.
Read the Zes case →The real game, shrunk to fit: arrow keys on a keyboard, swipe on a phone.
The driver side arrives inside the app you already have, through a light SDK your team can embed in days: games, rewards, streaks, push messages and wallet cards, in your brand. Your devices, payments and roaming stay exactly where they are.
Stays exactly where it is: your devices, payments and roaming.

For three years we've designed and built for Zes and Electrip: the driver apps, the charging-station screens, and the Snake game more than 700,000 Zes drivers play while they charge. eMobility OS is what we learned there, built as a product for every operator.
It connects to the charging platform and app you run today. Nothing you already rely on has to move.
We process your drivers' data to run the service; we never own it or sell it. Each operator's data is kept separate and hosted in the EU, under KVKK and GDPR.
Where the effect can be proven (taking part, coming back, retention) we say it plainly. Where revenue can't be pinned on one cause, we say that too.
Personal offers, churn alerts and forecasts switch on once there's enough data. Until then, clear rules do the work, and the panel says so.
Growth teams run the experience modules; viewers see the dashboards. Everyone sees only what their role allows.
Panels and driver screens work in Turkish and English from day one, with more languages as you grow.
Operators on the early-access list try it with their own drivers first, on terms we agree at the start. Analytics & Attribution and Marketing & Growth follow, each built on what the first module shows.
We're opening eMobility OS to a small group of operators first. Tell us about your network, and we'll be in touch about early access.
← All our productsNo. It works on top of the charging platform and the driver app you already run, through an API bridge and a light SDK.
Yes. Each module switches on separately; most operators start with Engagement & Loyalty.
It depends on your systems. We scope the API bridge and the SDK with your team at the start, so you know the effort before you begin.
We'll share pricing with operators on the early-access list, after they've tried it.
In the EU, kept separate for each operator, under KVKK and GDPR. The data is yours; we only process it to run the service.