The network software running your chargers decides how drivers interact with them, how you get paid, and how you manage the system over its life. It is also one of the stickier vendor choices you will make, because switching platforms later can mean reconfiguring or even replacing hardware. Getting the evaluation right up front is cheaper than unwinding the wrong choice in year three.
What commercial charging software does
A commercial charging platform (sometimes called a Charging Station Management System, or CSMS) typically handles:
- Session management. Starting, stopping, and metering sessions, and logging energy delivered and duration.
- Billing and payment. Collecting from drivers via app, RFID card, or credit-card tap, and distributing revenue shares to the host in third-party arrangements.
- Access control. Restricting use to employees, residents, or members, or opening it to the public.
- Load management. Allocating limited electrical capacity across multiple ports so the site does not trip its service or spike its billed demand.
- Remote monitoring and diagnostics. Detecting faults, tracking uptime, and alerting you to outages before a driver complains.
- Reporting. Revenue by site, utilization trends, downtime, and energy data for sustainability reporting.
- Driver app. A consumer-facing app to find, activate, and pay for charging.
The first four determine your operating experience; the last three determine whether you can manage and prove the value of the asset over time.
These are categories and capabilities, not endorsements. We do not have referral arrangements with any platform, and you should verify current terms directly before signing.
| Platform | Orientation | Notes (as of Q2 2026) |
|---|
| ChargePoint | Largest North American network | Strong consumer app and reporting; per-port cloud subscription model; introduced added per-session service fees in 2026 |
| Blink Charging | Long-established network | Hardware-plus-software and software-only options; reliability reputation varies by market |
| EVgo | DCFC-focused operator | Public fast-charging network; less oriented to host revenue-share deals |
| Shell Recharge (formerly Greenlots) | Utility and fleet focus | Enterprise and fleet strength; less property-owner-revenue oriented |
| EV Connect | Property-manager focused | OCPP-based; works across hardware brands; common in multifamily and hospitality |
| AmpUp | Software-first, hardware-agnostic | OCPP-based; markets flexibility and load management for workplace and multifamily |
| Driivz | Enterprise CSMS | Used by large charge-point operators; powerful but more complex than host-focused tools |
| Tesla (commercial) | NACS-centric | Tooling for sites serving primarily Tesla vehicles; connector ecosystem is the main consideration |
The meaningful differences among these are less about feature lists, which converge over time, and more about business model (do they want a revenue share, and how big?), support quality, and how locked-in their hardware is.
The OCPP question: open vs. proprietary
OCPP (Open Charge Point Protocol) is the open standard for communication between a charger and its management software. OCPP-compliant chargers can, in principle, be moved to any OCPP-compatible platform, which is what gives you leverage to switch software without throwing away hardware.
- OCPP 1.6J is still the most widely deployed version in the field.
- OCPP 2.0.1 adds stronger security, better device management, and a more capable smart-charging and load-management specification. NEVI-funded sites are required to use OCPP 2.0.1, and specifying 2.0.1 compatibility is the safer choice for new private projects too.
Proprietary systems, where a charger only talks to one company's software, lock you to that vendor. If they are acquired, raise prices, or let service quality slip, your options shrink. "OCPP-compliant" also varies in practice: some vendors implement the standard partially or layer proprietary extensions on top, so confirm the specific version and ask whether all the features you care about (especially smart charging and remote diagnostics) work over standard OCPP rather than a proprietary channel.
Practical rule: require OCPP 1.6J at minimum, prefer OCPP 2.0.1, and put the requirement in the contract. Ask the vendor to confirm in writing that core management and load-management functions operate over standard OCPP.
Load management and demand-charge control
For any multi-port site, load management is no longer a premium add-on; it is close to a baseline requirement. Commercial customers pay demand charges based on their highest sustained kW draw in a billing period, and several chargers ramping up together can set a new monthly peak that costs far more than the energy itself.
Good platforms support dynamic load management: the software continuously reallocates available power across active ports based on real-time site demand, vehicle state of charge, and your configured priorities, keeping the site under a set ceiling. Under OCPP 2.0.1 this is done with structured charging profiles the platform sends to each charger. Some platforms can also shift charging toward off-peak, lower-cost hours and participate in utility demand-response programs.
When evaluating a platform, ask specifically:
- Can it cap total site draw to a configured kW ceiling and dynamically share power across ports?
- Can it shift charging to off-peak windows on a time-of-use schedule?
- Does load management run over standard OCPP, or does it require this vendor's hardware?
Understanding the full cost
Platform cost is more than a sticker subscription. Account for all of these (figures as of Q2 2026):
- Per-port network subscription. Commonly $300–$475 per port per year on a major network; some vendors quote a monthly per-port fee instead (often $15–$40/port/month, which lands in a similar annual band).
- Payment processing. A per-transaction cost on every paid session, sometimes a percentage of the transaction, sometimes a flat per-session fee. Unlike subscriptions, these rarely get volume discounts and can quietly erode margin on small sessions.
- Per-session service fees. Some networks now add a service fee to driver-paid sessions on top of your rate. Confirm whether this comes out of your revenue or is passed to the driver.
- Revenue share. In host or turnkey arrangements, the platform keeps a slice of revenue. Know the percentage and what it covers.
- Roaming markups. If your site appears on partner networks, those transactions may carry an added markup.
A platform that looks cheap on the subscription line can be expensive once transaction and service fees are added, especially at low utilization where fixed costs dominate. Model your real session mix, not just the headline per-port price.
| Criterion | What to ask for |
|---|
| Interoperability | OCPP version supported; whether key functions run over standard OCPP |
| Reliability | Documented network uptime; target 99%+ |
| Support quality | Fault-resolution SLA and response times; local or regional support presence |
| Total cost | Per-port fee, transaction/service fees, revenue share, roaming markups |
| Load management | Dynamic load sharing, site kW cap, TOU shifting, demand-response support |
| Reporting | Revenue by site, utilization, downtime events, energy data for ESG reporting |
| Access control | Granular user groups (employee/resident/public) and pricing per group |
Support quality, not features, is the most common source of regret among commercial operators. A platform with a rich feature list and slow fault resolution will still leave you with dead chargers and unhappy users.
Red flags
- Lock-in contracts with no exit for poor performance. Five- to ten-year terms are common; an exit clause tied to uptime or support failures is worth negotiating.
- Per-port fees that break the economics at your utilization. At a low-traffic site, a high monthly per-port fee can consume most of the revenue. Run the math at conservative utilization.
- No or partial OCPP support. If the hardware will not talk to anything but one vendor's cloud, ask why, and weigh the long-term flexibility cost.
- Uptime guarantees with no penalty. A 99% uptime promise that carries no financial consequence when missed is marketing, not a commitment.
- Opaque fee structure. If the vendor cannot give you a clear all-in cost (subscription plus transaction plus service plus revenue share), assume the total is higher than the part they led with.
Decision checklist before you sign
The right platform is the one whose business model, support, and interoperability fit your site, not the one with the longest feature list. Decide what you need it to do, insist on open standards so you keep the option to leave, and price the total cost at the utilization you actually expect rather than the one the sales deck assumes.
Last factually verified: 2026-05-24 against Open Charge Alliance OCPP documentation, EV Connect and AmpUp 2026 platform guidance, ChargePoint published per-port pricing and 2026 service-fee changes, Driivz EV billing reference, and Ampeco transaction-cost guidance.
