Our Client
EVPassport is a B2B EV charging platform serving property owners, fleet managers, and hospitality operators nationwide.
How EVPassport Built a Platform the Electric Vehicle Industry Actually Demands and Reduced Infrastructure Costs 54%
When an electric vehicle (EV) charging session fails, the impact is immediate and personal. Drivers miss meetings. Fleet vehicles can’t complete routes. Hotel guests start road trips on empty batteries. For EVPassport — a business-to-business (B2B) end-to-end EV charging platform serving property owners, fleet managers, and hospitality operators — minimizing those moments is what drives every engineering and platform decision.
Their near-term target was 20,000 chargers; their horizon, 100,000. Reaching that vision meant evolving the platform they had built. This is how EVPassport did it.
The Problem
A Platform Ready to Scale to the Next Level
EVPassport entered the market with a clear value proposition: give property owners, fleet operators, and hospitality brands a single platform to manage EV charging at scale. The product vision was strong. Commercial traction was real. As the company scaled rapidly, the platform they had built needed to evolve to meet the demands of rapid growth.
Inside engineering, the team had built a platform well-suited to early-stage growth — but the architecture needed to mature alongside the business. The backend relied on polling cycles that created scaling constraints. Critical services lacked the failover redundancy that enterprise-grade uptime requires. Test coverage sat below the 70–80% threshold that production systems at scale typically target. Institutional knowledge carried much of the operational memory — a common pattern at startup speed that creates risk as teams and complexity grow.
Backlog ownership needed more structure. QA processes needed more rigor. The engineering team found much of its capacity absorbed by maintenance work, leaving limited runway for the product investment the business needed to accelerate.
Security represented another area ready for maturation. Web Application Firewalls (WAF) had not yet been deployed. External penetration testing had not been part of the roadmap. System and Organization Controls 2 (SOC 2) documentation was in early stages — and for enterprise buyers, a documented compliance posture is often the deciding factor in whether a procurement conversation moves forward.
The platform EVPassport had built carried them to this point. Now the moment called for evolving it to match the scale the market was demanding.
The Solution
Clarity Before Code: A Platform Rebuilt for Enterprise Scale
EVPassport’s first move was to establish clarity before acting. They commissioned a rigorous three-track assessment covering architecture, product process, and security — three weeks of stakeholder interviews, codebase deep dives, and security reviews conducted with SoftServe’s technical advisory team.
What surfaced gave the engineering team an independent, structured view of where to focus: the architectural constraints limiting scale, the process improvements that would accelerate delivery, and the security investments that would open enterprise conversations.
Choosing what to build and what to buy
With a clear diagnostic in hand, EVPassport made a strategic decision that redefined where their engineering capacity would go. They adopted a proven platform to handle core Charge Point Operator (CPO) capabilities — Open Charge Point Protocol (OCPP) server management, billing, and Open Charge Point Interface (OCPI) roaming — freeing their engineers to focus on what genuinely differentiates the product.
Selecting the right platform was a precise exercise. SoftServe led a structured evaluation, and four criteria drove the decision.
Application programming interface (API) depth and flexibility was non-negotiable.
Several evaluated platforms locked key capabilities behind proprietary interfaces inaccessible programmatically. EVPassport needed to consume and act on data without dependence on third-party tooling. The selected vendor delivered.
Data model fit for a multi-entity business was equally critical.
EVPassport’s commercial structure spans a layered hierarchy of partners, contracts, and locations — with tariff management and relationship structures that vary across entity types. The chosen platform accommodated this natively; several alternatives required workarounds that would have become technical debt within a year.
Partner-facing back-office flexibility mattered because EVPassport’s back office isn’t only internal.
Property managers, fleet operators, and other stakeholders need visibility into charger usage and performance from the same system. The selected vendor offered the permission model and customization depth to support that experience without sacrificing operational control.
Dual CPO and e-Mobility Service Provider (eMSP) coverage preserved long-term optionality.
Several competing platforms were built for one role or the other. EVPassport selected a vendor that spanned both — a decision that matters as much for where the business is heading as for where it stands today.
With the foundation set, EVPassport redirected engineering capacity toward differentiation. The driver-facing app received a complete rebrand. Custom features were built for fleet operators and property managers – capabilities tailored to how each segment actually uses the product. Backend billing logic was developed to match EVPassport’s specific commercial model.
The team’s most significant engineering milestone: consolidating web, iOS, and Android into a single React Native codebase. One surface to improve. One team fully aligned. Development cycles accelerated. Maintenance burden dropped.
Closing the security gaps
Security work ran in parallel. EVPassport built a phased roadmap that addressed critical exposures first: WAF deployment, mobile security hardening including Secure Sockets Layer (SSL) pinning and jailbreak detection, and a structured path toward SOC 2 Type 1 certification. Thirty-four SOC 2 policies are now in place or actively in progress.
For enterprise buyers evaluating EV charging vendors, a documented security posture and a credible SOC 2 timeline determine whether a procurement conversation starts — or never does.
The Results
A Platform That Scales with Business Growth
The improvements across the platform are now measurable. Amazon Web Services (AWS) Monthly Infrastructure Spend: 54%+ cost reduction.
Monthly infrastructure spend dropped by more than 54% against the prior five months. The gains came from a targeted optimization program: Network Address Translation (NAT) Gateway consolidation, Elastic Kubernetes Service (EKS) right-sizing and node group consolidation, Relational Database Service (RDS) adjustments for non-production environments, CloudWatch log retention tuning, Amazon Managed Streaming for Apache Kafka (MSK) enhanced monitoring optimization, and orphaned Virtual Private Cloud (VPC) cleanup. For a scaling company, that’s engineering capital returned to growth.
Beyond the numbers, EVPassport now has what it was missing: architectural headroom. A formal product roadmap. Owned backlogs. Structured QA. A platform built to absorb growth. And a security posture that opens enterprise conversations rather than closing them.
We knew we needed a robust platform that would grow as we grow. SoftServe helped us see our platform with new clarity and gave us the tools and architecture to scale with confidence.VP of Product and Engineering
Looking Ahead
Built for What Comes Next
EVPassport’s target of 20,000 chargers, with 100,000 on the horizon, is no longer a vision constrained by its own platform. The architectural debt is resolved. Security compliance is on a documented path. The engineering team is delivering against a real roadmap. Enterprise conversations once stalled by compliance questions now have a clear path forward.
EV charging infrastructure is one of the defining buildouts of this decade. EVPassport has built a platform to lead the industry.
Find out how SoftServe can help your organization build platforms that scale.
