OCPP charging platform for station owners
The EV Armenia platform is software for people who run EV charging networks: an OCPP server for 1.6J, 2.0.1 and 2.1 chargers, driver payments with Idram, IDBank/ArCa cards and Fastshift, a double-entry wallet, an admin panel and driver apps in Armenian, Russian and English. It is the software behind the EV Armenia app. You can have us host it or install it on your own server; contact us for a quote.
What the platform includes
OCPP charging station server
Chargers connect over WebSocket with a password. OCPP 1.6J, 2.0.1 and 2.1 are accepted; remote start and stop, reset, unlock, availability, configuration and raw OCPP commands work from the admin panel. Details: OCPP CSMS platform.
Armenian payments
Idram, bank cards through the IDBank (ArCa) gateway and Fastshift, with reconciliation. See payment integration.
Wallet and guest checkout
A double-entry ledger records every top-up, charge and refund. Drivers can charge as guests: prepay with refund or prepay with credit, plus a card hold where the bank enables two-stage payments.
Promotions and corporate accounts
Promo codes, top-up packages, cashback rules and referrals; organisation accounts with prepaid or postpaid billing, driver limits and monthly invoices.
Admin panel
Stations, tariffs, live sessions, finance, users, team roles with two-factor sign-in, an audit log, the OCPP message log and station photos.
Driver apps
A web app that installs like an app (PWA) and native Android and iOS apps built from the same code, with push notifications. See white-label app.
Three languages
Apps, admin panel and e-mails in Armenian, Russian and English. Receipts and notifications go out in the driver’s language.
Migration tools
Legacy-account import lets existing drivers claim their old balance and history after a switch.
How it is built
- One language end to end. TypeScript on Node 22 for the OCPP gateway, API, workers, admin and apps, with shared contracts between server and clients.
- Data. PostgreSQL 16 for transactions and the ledger, Redis 7 for station presence, commands between instances and rate limits.
- No lost meter readings. Incoming OCPP messages are written to a durable queue before the charger gets its answer, then applied in order. A restart does not drop data.
- Operations. Prometheus metrics, health checks, rate limits, a strict content security policy, configurable data retention. Deployed with Docker Compose behind your reverse proxy.
A measured number, labelled as a simulation
In a simulated load test of 200 virtual OCPP 1.6 stations sending 150 messages per second on a shared 2-vCPU machine, the server acknowledged MeterValues in about 2 ms (median) and 4 to 6 ms (95th percentile) with the durable queue enabled. This is a synthetic test on shared hardware, not a production figure, and the stations were simulated. We publish no uptime, customer count or revenue figures.
What is not included yet
| Area | Status |
|---|---|
| Automatic load management | The platform can send raw OCPP smart-charging commands (SetChargingProfile) from the admin panel. Automatic balancing of a site’s power between connectors is not built. |
| OCPP 2.1 specific features | Connections are accepted and the core transaction flow runs through the 2.0.1-compatible handlers. V2X, DER control and battery swapping messages are acknowledged but not acted on. |
| OCPI roaming | A roaming module for OCPI 2.2.1 (CPO and eMSP roles) exists, is off by default and has been tested between two instances of our own platform. It has not yet been run against a third-party network. |
| Telcell, Apple Pay, Google Pay | Not supported. Telcell needs a contract and the merchant API specification from Telcell. |
| Saved cards and auto top-up | Built but switched off until the bank confirms recurring payments. |
| Fiscal receipts (e-CRM) | Invoices are settlement documents, not fiscal documents. Whether charging needs an e-CRM receipt is an open question for your accountant; see licence, tax and e-CRM. |
Scroll sideways to see the whole table
Ways to work together
- Hosted by us. We run the platform: updates, monitoring, backups. You manage stations, tariffs and drivers.
- On your server. We install it on your VPS or Docker host. You own the infrastructure and the data.
Pricing is a licence plus setup, quoted per project; we do not publish a price list. The platform author is Andrew Boiko. If you are planning a network, start with how to start an EV charging network in Armenia and OCPP explained.
Questions and answers
Which OCPP versions does the platform support?
OCPP 1.6J, 2.0.1 and 2.1 over WebSocket. For 2.1 the core transaction flow works; 2.1-only features such as V2X are acknowledged but not acted on yet.
Can I host it myself?
Yes. It runs with Docker Compose on a modest server with PostgreSQL and Redis, or we can host it for you.
Does it work with chargers from any manufacturer?
It speaks standard OCPP, so chargers that implement 1.6J, 2.0.1 or 2.1 can connect. We recommend testing your charger model when you write to us; we do not publish a list of certified models.
Which payment methods are supported?
Idram, IDBank (ArCa) cards and Fastshift, plus the in-app wallet. Telcell, Apple Pay and Google Pay are not supported.
Can I move my existing drivers over?
Yes, legacy-account import lets drivers claim their old balance and history.
How much does it cost?
A licence plus setup, quoted per project. Write to us with your network size and we will send a quote.
Talk to us about your charging network
Tell us about your stations and payments. We reply within one business day.