Charging networks and operators
Your own stations and the owners you onboard — in one portal under your brand, with your tariffs and your commission.
White-label CSMS · the Apostol CSMS platform
A charging station management system under your brand: Your own charging platform. Your brand. Ready to launch.
The Apostol CSMS platform that runs OCPP CSS — as a dedicated installation under your name: for charging networks, energy companies, station makers and fleets. Owner portal, operator workplace, driver app, QR payment and station onboarding — on your domain, with your clients and your commission.
Portal demo ↗operator / operatorDriver app demo ↗driver / driver
One platform, one release — two brands
- Dedicated installationits own server, database and domain for every brand
- Your domain and brandon every screen — from the portal to QR payment, no development
- OCPP 1.5 · 1.6 · 2.0.1a mixed fleet in one portal; OCPI roaming
- With us or with youhosted on our platform or on your servers
Who it is for
For companies that need their own charging brand
OCPP CSS serves station owners directly. When the network, the clients and the brand are yours, the same platform runs as your own installation.
Energy retailers
Charging as part of your energy offer: customers charge under a brand they already know, and the stations live in your system.
Station makers and distributors
Ship hardware together with a management platform under your own name — no third-party logo in your customer's app.
Fleets, leasing, taxi
Charging your vehicles, drivers and partners by your rules — with invoices and RFID access, under your name.
Developers, car parks, retail chains
Charging as part of every property you build or run: residents, tenants and visitors in one network under your brand.
A few stations of your own?
You don't need your own installation — connect them to OCPP CSS yourself in about 15 minutes, no account managers.
OCPP CSS for station owners →Live example
OCPP CSS is a brand on this platform
What OCPP CSS gives its clients, you get under your own name: owner portal, driver app, QR payment, sign-in and API. Not a demo build but a working business with real drivers and money. Open it and look before talking to us — the demo logins are right here.
In productionAuthorized YooKassa Partners API partner
What you get
A complete charging platform, not a module
Everything OCPP CSS runs on is in your installation: from the station protocol to the money flow and the apps your clients use.
Workspaces for every role
Owner portal with a station map, sessions, tariffs and invoices; an operator workplace; an engineer console with direct station commands; support; a partner with their own sub-network and revenue; administration of the whole platform.
Driver app and QR payment
A web app that installs on a phone in one tap, no app stores: map, charging, wallet, saved cards, RFID tags. A one-off payment by the QR code on the station — no sign-up.
OCPP 1.5, 1.6 and 2.0.1
Three versions on one pipeline: station commands are built in one form and translated to the station's version. Remote commands, firmware updates, a security event log.
YooKassa Partners API and 54-FZ
Every station owner has their own YooKassa shop: drivers' money goes to them directly, funds are held until charging starts, the 54-FZ receipt carries their details. The platform commission accrues to your legal entity.
Organizations, partners and roles
Many operators in one installation, each with their own network, staff and data boundary. A partner sees only their part of the tree.
Tariffs and settlements
Prices per kWh, minute, waiting, idle and reservation; wallet, invoices and double-entry for every payment. The settlement model with owners — agency, operating or revenue share.
OCPI roaming
OCPI 2.2.1 and 2.3.0 in the charge point operator (CPO) and e-mobility service provider (eMSP) roles, hub connection, partners' remote commands. The contract with a roaming hub is on your side.
AI assistant for drivers
An in-app chat explains the station, the session and the charge, checks and performs a start, unlock or reboot — with the driver's own rights — and hands the conversation over to a human. Prompt, model and tools are set per network.
A documented REST API
Every platform function is available through a REST API described in OpenAPI; the reference is open on this site. App interfaces come in a dozen languages.
Your brand everywhere
Configuration, not development
A brand is made of four layers that never mix. All brands share one platform codebase: nothing is forked for you, so nothing falls behind.
01 · LicenceYour details: brand, legal entity, tax ID, domain. Signed with the platform key and verified by it at startup.
02 · EnvironmentPasswords, keys and secrets — only in your installation.
03 · SettingsCurrency, country, payment system and operating rules — in your database's registry.
04 · Brand manifestThe look of every app. Changed by an administrator without a release, and it survives every update.
What the manifest sets
Logos and iconTheme and coloursLanguageSign-in with Google and YandexPayment keyMapsSupport emailLinks to your terms
Your installation
Separate data, a shared release
Data stays in your installation
Every brand has its own server and its own database, and the database is not connected to any external network. Clients, sessions and payments never share a database with another brand.
One release for all brands
What is built for one brand, all receive. The version is pinned with image checksums; an update is one command, and if a database migration fails it stops while the running version stays as it was.
With us or on your servers
We run the installation — or you deploy it on your own Linux server with Docker from the same packages, with the same install, update and health-check tools.
How a launch goes
From the first conversation to your own platform
Briefing
Your network, regions and stations; hosting with us or on your servers.
Licence and details
Legal entity, brand name and domain go into a signed licence.
Domain and accounts
DNS records and certificates for your addresses, a YooKassa contract, email, Google and Yandex sign-in, a maps key.
Installation and checks
The whole stack is installed, the database is created, every service passes a health check.
Launch
Your owners connect stations, your drivers charge and pay — under your brand.
Choose your path
OCPP CSS or your own brand
| Criterion | OCPP CSS | White-label CSMS |
|---|---|---|
| For whom | Sole proprietors and companies with their own charging stations | Charging networks, energy companies, station makers, fleets, developers |
| Brand and domain | OCPP CSS, ocpp-css.com | Yours, on your own domain |
| Installation | The shared OCPP CSS service | Your own — with us or on your servers |
| Your clients | You manage your stations and drivers | You also onboard station owners — the commission on their receipts is yours |
| Getting started | Self-service: a station connects in about 15 minutes | A briefing, then an assisted launch |
| Price | Published tariffs — see «Pricing» | An individual offer after a briefing |
Who does what
A clear boundary from day one
We provide
- The platform and its regular releases
- Apps under your brand: portals, the driver app, the QR payment page, sign-in
- OCPP 1.5/1.6/2.0.1, OCPI, YooKassa Partners API and 54-FZ receipts
- Installation, updates and monitoring — if we host
- Technical support and notes for every release
On your side
- Legal entity, brand and domain
- A YooKassa contract, outgoing email, Google and Yandex sign-in, a maps key
- Contracts with roaming hubs — if you need roaming
- Attracting station owners and drivers, marketing
- First-line support for your clients
- The server — if you host it yourself
Questions
White-label: frequently asked questions
Is it a separate installation or an account inside OCPP CSS?
A separate installation: its own server, database and domain. OCPP CSS is a brand next to yours, not a layer above it.
What carries your brand?
Owner portal, operator workplace, engineer console, driver app, QR payment page and sign-in — on your domain, with your name, logo and colours.
Where is the data stored?
In your installation's database — on a server we run or on your own.
Which charging stations are supported?
Stations with OCPP 1.5, 1.6 or 2.0.1. Versions are translated automatically, so a mixed fleet works in one portal.
Which payment system can be connected?
In Russia — YooKassa via the Partners API with 54-FZ receipts; in Europe — Stripe. The payment system is a brand setting; you sign the contract with the provider.
How much does it cost?
Terms are individual: they depend on whether we or you host the installation and on the size of the network. We prepare an offer after a briefing.
Briefing
Let's talk about your network
The first conversation is a briefing: your stations, regions and how you want to receive the platform. We reply within one business day.
Terms
Individual — they depend on the hosting model and the size of the network. We prepare an offer after a briefing.