If you run between 10 and 200 chargers, Driivz is sized for the network you don't have yet. We publish our price (€29/charger/month + 3%/session), ship the white-label app in a week, and let you walk away month-to-month. Below: every claim, dated and sourced.
Last updated May 2026
Read this row by row. If two cells are functionally equivalent we say so. We don't pretend Driivz is a worse product than it is — we explain why it's the wrong shape for a small or mid CPO.
| EnerGo Connect | Driivz | |
|---|---|---|
| Public pricing | Yes — €29/charger/mo + 3%/session, on the page. | No — sales-led, NDA-gated. |
| Typical contract length | Month-to-month, no exclusivity. | Multi-year enterprise contracts. |
| Time from kickoff to first live charger | 24 hours once OCPP credentials are in. | Weeks to months (implementation project). |
| Implementation cost | €0 — self-serve onboarding, optional paid pilot. | €100k+ implementation projects reported (third-party). |
| Target segment | 10–200 chargers. | 500+ chargers; utilities; OEMs; multi-country networks. |
| OCPP versions | 1.6 + 2.0.1 (production). | 1.6 + 2.0.1 (OCA-certified). |
| OCPI roaming | 2.2 — Hubject, Gireve, custom hubs. | 2.2 — Hubject, Gireve, broad coverage. |
| White-label driver app | Included; live in a week. | Available; multi-month integration typical. |
| Multi-tenant model | From the first table — sub-brands and franchises native. | Enterprise add-on; partner mode. |
| Hardware support | Hardware-agnostic (any OCPP charger). | Hardware-agnostic (any OCPP charger). |
| Public changelog | Yes — per-release, with issue keys. | No — release notes are customer-only. |
| Hosting regions | EU default; UK/UAE/KSA/Brazil/India on request. | Global; sovereign-cloud on request. |
| Sandbox / self-serve trial | Two-week paid pilot on your real chargers. | Sales-led demo on staging tenants. |
| Walk-away terms | Month-to-month, full data export, no fee. | Contract-term obligations apply. |
Five concrete reasons, all of them downstream of one decision: we sized this product for the segment Driivz doesn't actually serve.
Driivz negotiates per deal. We publish €29/charger/month + 3%/session as a single global number, with volume discounts at 200 and 1,000 chargers and emerging-market parity. A CFO can model 12 months of Connect spend in a spreadsheet. They cannot do that with Driivz.
Driivz implementations are projects — scoping, contracting, integration, go-live. Connect's onboarding is operational: hand us OCPP credentials in the morning, your first charger is live by end of day. The two-week paid pilot puts you on production with up to 5 of your real chargers.
Driivz supports sub-brands as an enterprise feature. In Connect, every operator is a tenant from the schema up. That means franchise networks, partner programmes, and multi-brand portfolios work without bespoke configuration.
Driivz contracts are multi-year. Connect is month-to-month, with a full data export on exit (CDRs, users, tariffs, audit log) at no charge. The economic argument we have to make is 'stay because it works,' not 'stay because you signed.'
We ship every release publicly with the same EG-### issue keys we use internally. You can verify what shipped, when, and why. Driivz's release notes are gated to customers. We think the public posture is a feature, not a marketing risk.
If we don't tell you the cases where Driivz is the right call, you won't trust the rest of the page. Here they are.
If you're a utility-affiliated CPO with deep ties into grid-operator systems (load-balancing across thousands of DC chargers, demand-response programmes, ancillary-market participation), Driivz's enterprise heritage and ABB ownership are real assets. Connect doesn't compete in that frame.
Our pricing model and architecture is sharp for 10–200 chargers, fine for 200–1,000, and at 1,000+ you should at least benchmark Driivz alongside us. Their unit economics get more attractive as scale rises; ours stay flat.
Driivz carries an OCA-certified OCPP 2.0.1 implementation. Our 2.0.1 implementation is production-tested but not OCA-certified. If certification is a procurement requirement (rare outside enterprise RFPs), that's a Driivz win.
We use real session volumes from our own production network. Driivz figures are derived from public third-party reports — we'll happily replace them with a published price the day Driivz publishes one.
Connect is roughly break-even on monthly run-rate and meaningfully cheaper in year one once implementation is included.
Driivz crosses ahead on monthly run-rate at this scale; once implementation, integrations, and multi-year commitment cost are included, Connect remains lower year one and competitive thereafter.
This is the upper edge of Connect's sweet spot. We'll model your real session distribution on the demo call.
Real timeline from our last Driivz-to-Connect migration (40 chargers, Q1 2026). We do the import. You verify and approve each step.
Total: 9 working days, end-to-end
We map your Driivz fleet, tariffs, user database, and roaming connections. Read-only — no production change. We deliver a written audit report by end of day.
Your EnerGo Connect tenant is provisioned in EU-Frankfurt (or your chosen region). Charger metadata, tariffs, and user database are imported. Driver app branding is applied to the staging build.
Your chargers' OCPP endpoint is switched to EnerGo's backend, one cabinet at a time, during off-peak hours. Each cabinet is verified live within 30 minutes of switch.
Both systems are live for 48 hours. We reconcile sessions, payments, and roaming events row-by-row and surface any discrepancies.
Driver app is published to App Store and Play. Driivz tenant is decommissioned. Archive snapshot is delivered to you. We stay on-call for the first session of every new day for two weeks.
Yes. Connect is the same software powering our own production network in Armenia, with sessions, payments, and roaming running 24/7. The public changelog (with EG-### issue keys) is the audit trail. If you want a reference call with a customer who migrated off an enterprise CPMS, we'll arrange one.
If you run between 10 and 200 chargers — yes, this is exactly the segment we built for. If you run 1,000+ across multiple countries with utility-grade grid integrations, Driivz's heritage is more aligned. Our two-week paid pilot is the cleanest way to find out — same production stack, your real chargers, real sessions.
Zero. OCPP re-pointing happens during off-peak windows and per-cabinet. In-flight sessions complete on the old endpoint; the next session starts on the new one. Driver-app cut-over is a separate, scheduled day where the new app goes live in App Store / Play Store and drivers update via standard auto-update channels.
OCPI 2.2 is a clean handshake. We swap your party ID's endpoint, your roaming partners re-handshake (typically <24 hours), and roaming sessions continue. We coordinate the handshake with each partner — you don't have to chase Hubject or Gireve yourself.
You take everything with you. Full export of CDRs, users (with consent), tariffs, audit log, and roaming history. Month-to-month means month-to-month — no termination fee, no data hostage.
It can be. Above 1,000 chargers in a single tenant, with multi-year commitment and enterprise leverage, Driivz's per-port economics can win. Below that — and especially in year one when Driivz's implementation cost is amortising — Connect's published price is usually lower in total cost of ownership. Bring your last 12 months of session data to the demo; we'll model both.
AmpUp's 2024 EV charging software buyer guide; the 2025 EVMagazine CPMS landscape report; softwarefinder.com vendor listings. Driivz does not publish a price publicly. If Driivz publishes a different number, email us — we update this page within a business day.
Bring your last 12 months of session data to a 30-minute call. We'll model your Connect bill against your current Driivz spend on the call. If the maths doesn't work, we'll say so and you walk away with the model.
