Product Features Who it is for How it works White-label About Pricing FAQ
B2B Platform for the EV charging business

A charging network under your own brand - without building software

OCPP core, billing, a driver app and an operator back office in one platform. You install chargers and sell kilowatt-hours. Protocols, money and customer support are on us.

We demo on a live charger simulator - you do not need hardware for the call

OCPP 1.6J and 2.0.1 Your brand on App Store and Google Play A separate database per operator ru · uz · en
Network monitor · Demo operator
Live
Chargers online
24/26
Active sessions
7
Energy today
412kWh
CP-0142 · Chilanzar
DC 120 kW · CCS2 · connector 1
41.2 kW
Charging
CP-0117 · Yunusabad
DC 60 kW · GB/T · connector 2
28.6 kW
Charging
CP-0098 · Mirzo Ulugbek
AC 22 kW · Type 2 · connector 1
-
Available
Network utilisation today OCPP events in real time
The whole stack, covered OCPP gateway Billing and payments Driver app Operator back office Analytics and reports Security
Product

Three products, one subscription. One party accountable.

Operators usually assemble this from three vendors: charger software, a payment layer and a mobile app. Here it is a single connected product - a charger event turns straight into money and into a clear screen for the driver.

Driver app

Your brand, your domain, your store accounts. iOS, Android and web from one codebase.

  • Charger map with live connector status
  • Start and stop charging in the app, QR scan at the charger
  • Wallet, top-ups, history and a receipt for every session
  • Phone number and SMS code sign-in, biometrics
  • Push notifications, three languages, dark mode

Operator back office

A workplace for your team: dispatch sees the network, finance sees the money, support sees the customer.

  • Chargers, connectors, groups, remote commands
  • Tariff and discount builder - no developer needed
  • Live session monitor, forced stop, incident review
  • Customers, RFID cards, wallets, refunds
  • Roles, two-factor sign-in, staff activity log

OCPP core and billing

The engineering layer nobody sees - and the one that makes the numbers add up.

  • OCPP 1.6J and 2.0.1 gateway, security profiles 1/2/3
  • Guaranteed processing of charger events
  • Double-entry accounting and immutable session records (CDR)
  • Payment layer in UZS, prepaid and postpaid
  • API and webhooks for 1C, ERP and partner services
The problem

Chargers are hardware. The business starts with software.

A charger without a platform is a socket you cannot account for. Here is what changes on day one.

Chargers on their own
  • Payment on trust. Card transfers, cash, a notebook. Revenue cannot be reconciled with the energy actually delivered.
  • Nobody knows the charger state. You hear about a fault from an angry customer, not from the system.
  • One tariff for everyone. No night rate, no corporate pricing, no idle fee after charging ends.
  • The customer is not yours. No app means no customer base, no repeat visits, no brand.
  • Vendor lock-in. Software from the charger manufacturer only works with their hardware.
A network on V3 Charge
  • Every kilowatt-hour accounted for. The charger meter is the source of truth; the output is an immutable receipt and a ledger entry.
  • The whole network in view. Live status for every connector, alerts on faults and lost connections.
  • Tariffs become a tool. Price per kWh and per minute, idle fees, night rates, group discounts and promo codes.
  • The customer base is yours. An app under your brand, a wallet, push campaigns, RFID cards.
  • Any hardware. OCPP is an open standard - chargers from different vendors in one network and one price list.
Features

Everything an operator needs, already built in

Not a checklist, but the functions that save or earn money every day.

Tariffs that do the maths for you

Combine rules freely: energy, time, a start fee, a minimum charge, an idle fee after charging ends and different pricing by hour. A tariff can be assigned to the network, a group of chargers, a single charger or a customer segment.

Energy, DC1,800 UZS / kWh
Night, 23:00-07:001,300 UZS / kWh
Idle after charging500 UZS / min
Corporate group-15%

No charger event is ever lost

A charger is acknowledged only after its event has been durably stored. If the link drops, the charger buffers sessions offline and replays them on reconnect, while the platform recognises duplicates and never bills twice.

Double-charge protection Offline session replay Retry queue Failed event review

Remote charger control

Start and stop a session, reboot, unlock a connector, take a unit out of service, reserve - straight from the back office or the app.

Remote Start / Stop Reset Unlock Reserve

RFID cards and corporate customers

Issue and block cards, assign them to employees, set a shared company limit, prevent concurrent sessions on one card.

Card issuing Customer groups Limits Postpaid

Reports, not guesswork

Revenue, energy, hourly charger utilisation, top customers, CSV export of session records for accounting.

Revenue and energy Utilisation CDR export

Security at payment-system level

Each operator has a separate database - not a shared table with a filter on one column. Chargers connect only over a secure channel with their own key, which can be revoked and reissued. Staff access is role-based, admin sign-in requires two-factor authentication, and every action is logged.

Separate database per operator OCPP security profiles 1/2/3 Charger key rotation 2FA and roles Activity log Encrypted payment credentials

Staying in touch with drivers

SMS, Telegram and push: sign-in codes, session start and end, low balance, auto-stop. Templates are editable, in three languages.

SMS Telegram Push Templates
Who it is for

Four scenarios - one platform

Pick yours and see exactly what you get.

You are building a public charging network

The job is not installing chargers. It is making sure a driver finds yours, pays within thirty seconds and comes back - while you see every kilowatt-hour and every som.

  • An app under your brand in the stores - the entry point for drivers and your retention channel.
  • One price list across mixed hardware - chargers from any OCPP-capable vendor in a single network.
  • A dispatch desk. Live map, fault alerts, remote restart without sending a crew.
  • Tariff flexibility per location: one price at a mall, another on the highway, a third at night.
  • Settlements with site owners - a transparent per-charger export for any period.

You own a mall, hotel, petrol station, car park or restaurant

Charging is not your core business - it is the reason a guest comes to you and stays for forty minutes. Running software and supporting drivers was never part of the plan.

  • Charging pays for the parking space. An energy tariff plus an idle fee so the bay is not blocked after charging ends.
  • Free for guests, paid for everyone else - promo codes and customer groups on a zero tariff.
  • No support burden on your side. The driver resolves things in the app, not at your reception desk.
  • A report for the owner - how much energy, how much revenue, which hours are busy.
  • Or work through an operator. If you would rather not run it yourself, we can bring in a partner operator for your chargers.

You sell or import charging hardware

The customer asks "and what software comes with it?" - and the deal stalls. Building your own platform costs more than a year of your hardware margin.

  • Sell hardware bundled with the platform under your own name - software stops being an objection.
  • Each of your customers gets an isolated workspace and their own app, while you keep the overview across all of them.
  • Recurring revenue instead of a one-off box sale: the software subscription goes to you.
  • Compatibility testing for your charger model on our bench before you start selling.
  • Reseller terms - partner pricing on the platform, not end-customer pricing.

You run an electric fleet: taxi, delivery, logistics

Vehicles charge at the depot and around town. The question is not how to charge them, but knowing who charged, where, how much and on whose budget.

  • A card per driver. Every session is tied to an employee and a vehicle - no more arguments about expenses.
  • Limits and restrictions. Caps by amount and time of day, card blocked in one click.
  • Postpaid invoicing per period instead of a wallet - the familiar model for a legal entity.
  • The depot under control. Charging queue, status of every bay, energy consumption report per vehicle.
  • Export to 1C through API and webhooks - data reaches your accounting system on its own.
How it works

From a meter pulse to a line in the ledger

The path of a single kilowatt-hour through the platform. Every step is designed so an event cannot be lost or counted twice.

Step 1
Charger
Any OCPP-capable vendor. Connects over a secure channel with its own key.
Step 2
Gateway
Receives the event, validates format and permissions, stores it durably - and only then acknowledges the charger.
Step 3
Processing
Events are handled in order and exactly once. Duplicates and offline replays are recognised automatically.
Step 4
Billing
Tariff, VAT, commission, wallet deduction. Every movement is a balanced ledger entry.
Step 5
Result
A receipt for the driver, a line in the accountant's report, an event in your system via webhook.
Data isolation
Every operator has its own database. A neighbour's breach cannot reach you - technically, not just by policy.
Acknowledge after storing
The charger treats an event as delivered only once it is stored. Otherwise it replays it itself.
Double-count protection
Redelivery of the same event never creates a second receipt or a second deduction.
Scaling
Gateway, workers and API scale horizontally - network growth does not require rewriting the platform.
White-label

The platform is ours. The brand is entirely yours.

A driver never encounters our name. They download your app, open your domain and see your colours. Tap a colour to see how it looks.

  • Your own app in the stores. Published in your App Store and Google Play accounts - which means the app belongs to you.
  • Your own domain. The portal and web version run on your address, not on a contractor's subdomain.
  • Logo, palette, splash screen, icon - changed in the back office, with no rebuild and no developers.
  • Your own copy and documents. Terms, privacy policy, support contacts - yours, in three languages.
  • Your own senders. SMS arrives from your name; the Telegram bot and campaigns are yours too.
EcoVolt
Balance
148 500
Charger No. 4 DC 120 kW
Start charging
EcoVolt
Wallet balance
148 500
Chilanzar DC 120 kW 41 kW
Yunusabad AC 22 kW Available
Stop charging
EcoVolt
Session complete
37 400
24.8 kWh 42 min · VAT incl.
View receipt
The money

A balance that cannot be quietly "adjusted"

In most in-house systems a customer balance is just a number in a table: any bug or crash changes it silently and irreversibly. Here money moves only through paired entries, the way real accounting works.

  • Every movement is visible

    A balance is not a field in a database but the sum of all entries. Any figure can be traced down to a specific session, payment or refund.

  • Session records are immutable

    When charging ends, a record is created that cannot be edited afterwards - not by the operator, not by support.

  • Nightly reconciliation

    The system reconciles ledger entries against session records and payments on its own. A mismatch triggers an alert instead of a surprise at month end.

  • Prepaid and postpaid

    Retail customers get a wallet with top-ups and a hold at session start. Business customers get a credit limit and an invoice per period.

Ledger entries for one session TX-4417 · 24.8 kWh
Customer wallet Debit -37,400
Operator revenue Credit +31,460
VAT payable Credit +4,488
Platform commission Credit +1,452
Hold released Debit 0
Debits and credits balance Σ = 0 · reconciled
Integrations

Fits into what already works for you

The platform does not require you to change your accounting, your hardware or how you talk to customers.

Charging hardware
OCPP 1.6J and 2.0.1 - the standard supported by most chargers on the market. We test your specific model on our bench before any contract.
Available
Payment acceptance
Payme is connected and live. Click, Uzum and other providers plug in as drivers, with no changes to billing. Merchant credentials are yours and stored encrypted.
Payme · others on request
SMS, Telegram, push
Eskiz for SMS, your own Telegram bot and in-app push. You control templates and message language.
Available
API and webhooks
Network events reach your systems: session start and end, receipt, payment, charger status. Signed requests, retries on failure, manual redelivery.
Available
Accounting and 1C
Export session records and invoices to CSV, or push them automatically over the API. VAT is calculated at your rate and included in the receipt.
Export and API
Languages and currency
Russian, Uzbek and English across every interface and notification. Settlement in UZS; the architecture is ready for other currencies.
ru · uz · en
Analytics
A separate analytical store for history: revenue and energy charts over long periods never slow down the operational database.
Available
Roaming between networks
Session records are already shaped to the industry interchange standard - when the market is ready for roaming, the data will not need reworking.
On the roadmap
Where we are

The platform is ready. Public case studies are not.

We will not show you logos and testimonials we do not have. It is more honest to say plainly where we are - and what that means for someone joining early.

  • Direct access to the people writing the code. No scripted first line: your questions go to the team building the product.
  • You shape what gets built next. While there are few partners, your requirements land in upcoming releases rather than on a "under consideration" list.
  • We come from this market. V3 is our live EV project in Uzbekistan. We see charging through the eyes of a driver, a dealer and an importer, not through industry reports.
What works right now ready in progress planned
OCPP 1.6J and 2.0.1 Ready
Billing, tariffs, session records Ready
Operator back office Ready
Driver app, web version Ready
Branded app builds for iOS and Android Ready
Reports and session record export Ready
Webhooks and API for your accounting system Ready
Payment acceptance - Payme Ready
Payment acceptance - Click, Uzum On request
In-app push notifications In progress
Roaming between charging networks Planned

Money flows and charger event handling are covered by automated tests. Before launch the platform went through a dedicated security audit - findings were fixed and locked down with tests.

Pricing

The platform pays for itself out of revenue, not before it

We do not sell an expensive box up front. The subscription combines a base fee, a per-charger fee and a share of revenue - we tune the mix to your case.

Start
First chargers, a pilot at one site, testing demand
from 650 000 UZS per month A base fee of 500 000 UZS plus 150 000 UZS per connected charger. No revenue share during the pilot.
  • Up to 5 chargers - 1 250 000 UZS/month for all five
  • Web app for drivers on a subdomain
  • Back office, tariffs, monitoring, reports
  • Wallet and payment acceptance
  • Support by email and Telegram
Discuss a pilot
Most popular
Business
A live network, your own brand, your own customer base
Base fee + per charger + revenue share The percentage drops as revenue grows
  • Mobile apps for iOS and Android under your brand
  • Your own domain and full brand customisation
  • No limit on the number of chargers
  • RFID cards, customer groups, postpaid and invoicing
  • API, webhooks, exports into your accounting system
  • SMS and Telegram from your own name
  • Priority support
Get a quote
Partner
Hardware suppliers and operators with several independent customers
Custom terms Reseller pricing and revenue sharing
  • Several isolated workspaces for your customers
  • A single overview across every connected network
  • A separate app for each customer
  • Compatibility testing for your hardware
  • Joint go-to-market and training for your team
  • Second-line support on our side
Discuss partnership

Exact figures depend on the number of chargers, their power and your monetisation model. On the demo call we price your specific case and follow up with a written proposal.

Getting started

From the first call to the first paid session

A clear path with no surprises: at any point you know which step you are on and what is needed from you.

Demo and pricing

We show the platform on a live charger simulator, work through your scenario and run the numbers. From you: forty minutes and details of the planned network.

40 minutes

Pilot on your chargers

We connect the hardware, configure tariffs and verify a real session from start to receipt. Running on our subdomain - no branding spend yet.

Pilot

Branding

Your logo, palette and domain. We build the iOS and Android apps, help publish them in your accounts, and connect payments and SMS.

Your brand

Operation and growth

We train your team, hand over the back office and stay on support. From there we keep developing the platform and connecting chargers as the network grows.

Support
Questions

What people usually ask

If the charger supports OCPP 1.6J or 2.0.1, almost certainly yes - it is the industry standard. Quirks do appear in specific firmware, since manufacturers interpret some messages differently. That is why we test your model on our bench free of charge before any contract and give you a written compatibility assessment. If the charger is already connected to another system, switching is a matter of changing the server address in its settings.
Yes, and this is the most common case. We have a charger simulator that behaves like real hardware: it connects, reports statuses, sends meter readings, responds to remote commands and even simulates faults. On the demo you will see the full cycle - session start, live kilowatts, completion, deduction and receipt - without a single physical charger.
Yours. The customer base, session history and revenue belong to you, the app is published in your developer accounts and the domain is registered to you. Each operator's data lives in a separate database rather than a shared table. On request we export everything in machine-readable form - written into the contract, not promised verbally.
The charger keeps charging the vehicle and stores events locally, then replays them with their original timestamps once the link is back. The platform accepts that batch, recognises events it has already processed and creates no duplicate charges. While the link is down the operator sees the charger as offline and gets an alert. Offline RFID authorisation rules are configured on your side.
Acquiring is set up under your legal entity, the payment credentials are yours and money reaches you directly. The platform keeps the books: it records top-ups, deductions and refunds as paired entries, produces an immutable record for every session and reconciles daily against the payment provider. Any discrepancy shows up immediately rather than at month end.
A pilot on our subdomain starts quickly - most of the time goes into configuring chargers and tariffs. The longest part is publishing the apps in the stores: App Store and Google Play review is outside your control and usually takes from a few days to a couple of weeks. That is why we recommend starting to earn on the web version while the apps ship in parallel. We fix concrete dates in a plan after the demo.
You take your data and go. Chargers run on an open standard - they are not locked to us, and pointing them at another server address is enough. The apps in the stores are yours and so is the domain. We deliberately build the relationship on the platform being worth it, not on being impossible to leave.
Yes, that is a separate partner model. You get reseller pricing and sell hardware together with software; each of your customers works in an isolated workspace under their own brand, while you get a single overview across every connected network. The subscription turns a one-off hardware sale into recurring revenue. Terms are agreed individually.
Demo · 40 minutes

See how it works on your own scenario

This is not a slide deck. We open the live system, start a charging session on the simulator and run it from start to receipt - then work through the numbers for your network.

  • A live charging session - connector statuses, kilowatts, pricing and the receipt in real time.
  • The back office from the inside - we will build a tariff for your site during the call.
  • A check on your hardware - tell us the charger model and we will assess compatibility.
  • A written proposal priced for your charger count and monetisation model - within one business day.
Not a fan of forms - just message us
Request a demo

We will get back to you within one business day, agree a time and send a meeting link.

Please enter your name
Please enter your company
Please enter a valid number
Please check the address
Please choose an option

Request received

We will contact you within one business day to arrange the demo. If it is urgent, message us on Telegram.

Book a demo