Architecting Interoperable BaaS Platforms to Scale African Micromobility
A platform shift is quietly happening in electric two‑wheelers – and it changes where value and complexity sit
We often assume vehicle OEMs must solve every last piece of the user experience: the vehicle, the battery, the energy network. Recent developments in East Africa show a different pattern: local pioneers have deconstructed that stack, building interoperable battery and energy services that turn charging into a horizontal platform other manufacturers can plug into. That’s not just a product evolution – it’s an architectural one.
What the market signal is
I recently came across reporting on how Kenyan startups moved from stripped-down pilot bikes to purpose‑designed EVs, then deliberately pivoted parts of their business toward battery-as-a-service (BaaS) and energy-as-a-service (EaaS). The result: a distributed swap/charge network and standardized battery packs that allow multiple vehicle brands to operate on a shared energy layer. Early pilots validated rider needs, later funding scaled swap hubs, and now interoperability partnerships are emerging.
Why this matters for enterprise architects and CTOs
This is a textbook example of platformization – taking a capital‑intensive, functionally narrow capability (energy provisioning) and exposing it as a reusable service. The implications for system design are profound:
-
Modularization is strategic. Splitting vehicle hardware/software from energy provisioning forces clear interface contracts: mechanical form factors, electrical connectors, communications (telemetry, SOC), and commercial APIs (billing, entitlement, roaming). Enterprises should design for explicit contracts, versioning, and graceful fallbacks when a partner’s implementation lags.
-
Data as the operational glue. Swap networks depend on low‑latency telemetry (battery health, location, cycle counts), robust identity for riders and assets, and reliable reconciliation across operators. Architects must design pipelines for streaming ingestion, edge filtering (on-vehicle BMS), and a secure canonical ledger for swapping/payments. Planning for telemetry volume and data lifecycle (including battery EoL records) reduces later technical debt.
-
Open vs optimized trade-off. Interoperability enables faster market growth and lowers customer friction, but it constrains per‑OEM optimization (pack chemistry, thermal systems). Firms must choose: prioritize scale through standards or squeeze more range/performance through bespoke integration. The right choice depends on go‑to‑market speed and capital availability.
-
Operational technology meets cloud at scale. Swap networks are cyber‑physical systems: inventory management, predictive maintenance, routing of charged packs, and energy forecasting must tie into cloud orchestration and local edge controllers. Design patterns from logistics platforms (fleet telemetry, dynamic routing, surge capacity) are directly applicable.
-
New financial and regulatory vectors. BaaS shifts battery from capex on the rider to opex via subscription. That requires robust billing integrations, fraud detection, and consumer protections. Regulators will need asset tracing, recycling proof, and safety compliance – architects must capture the metadata needed for certification and audit.
A pragmatic angle for India (and similar markets)
India’s two‑wheeler dominance and dense urban corridors make the BaaS/EaaS model particularly relevant. If policymakers and industry align on connector standards and digital interoperability, local players can replicate the Kenya pattern: iterative field pilots, build-out of swap points, and then platform monetization. Digital public infrastructure – secure digital identity, ubiquitous payments rails, and localized energy metering – can accelerate interoperability while protecting consumers.
Actionable takeaways
- Start with interfaces, not features: define mechanical, electrical, and API contracts before scaling hardware variants.
- Architect for data ownership and portability: battery passports, lifecycle logs, and interoperable telemetry reduce future compliance and recycling frictions.
- Balance openness and differentiation: choose which layers are standardized and which remain competitive edges.
- Treat the energy layer as a logistics problem: invest in predictive maintenance, routing, and inventory forecasting early.
- Engage regulators early: safe swapping, recycling, and commercial models need policy clarity to unlock capital at scale.
Closing thought
When infrastructure becomes a platform, electric mobility stops being a vehicle problem and becomes a systems engineering challenge – and the winners will be those who design the contracts, controls, and data flows that let many products use one shared energy backbone.
About the Author: Sanjeev Sarma is the Founder Director and Chief Software Architect at Webx Technologies. With a core focus on Generative AI integration, Cloud-Native Scalability, and Enterprise Software Architecture, he has spent over two decades driving digital transformation across Northeast India and beyond. Beyond his corporate leadership, Sanjeev is deeply invested in shaping the future of the IT industry. He serves as an Industry Expert on the Board of Studies for Assam Don Bosco University’s School of Technology, advises state technology committees, and actively mentors emerging tech startups at STPI. He brings a unique, dual perspective of high-level enterprise execution and future-ready academic curriculum development.
