Building a Scalable EV Charging Backend — For Operators, Developers, and Innovators

As electric mobility expands, so does the need for smart, reliable, and auditable charging infrastructure. At Simplico, we’ve designed an EV charging backend that serves both business goals and engineering needs — one that supports real-time OCPP communication, robust user management, session tracking, and future growth.

This article walks through how our backend architecture is structured — and why it matters to both business stakeholders and developers.

🧩 What the Backend Tracks (And Why It Matters)

At the core of our platform are five interconnected models:

Entity	Description	Business Relevance
User	Drivers, admins, station owners	Role-based access, ownership
Vehicle	Registered EVs with license plates	Loyalty, usage history
Station (Charge Point)	Physical charger device (cp_id)	Site and asset management
Connector	Individual charging socket (connector_id)	Power delivery + session matching
Session	Every charging transaction	Billing, reporting, energy analytics

Each model is connected using carefully designed relationships. For example:

A User owns Vehicles and Stations
A Station has multiple Connectors
A Session is created when a Vehicle starts charging on a Connector
All actions are recorded with audit fields: created_by, updated_by, created_at, updated_at

🧠 Technical Design Highlights

We use a normalized, flexible schema that prioritizes reliability and growth.

🔑 Connector Uniqueness

Each connector is uniquely identified by the combination of:

("cp_id", "connector_id")  # e.g. "STATION001", 1

This ensures:

No duplicates across your fleet
Precise status updates and fault logging
Session tracking without ambiguity

🕵️‍♂️ Audit Fields

Every record includes:

created_at, updated_at: Timestamps for lifecycle visibility
created_by, updated_by: Tied to the authenticated User (stored as ObjectId in Mongo)

This gives your business:

Full change logs
Accountability across users and teams
Traceable history for compliance

🔄 Session Tracking

Each Session links to:

user_id: Who initiated it
vehicle_id: What EV was used
cp_id + connector_id: Where it happened
start_time, end_time, energy_kwh: What was consumed

🧱 How Models Connect

Here's a high-level view of model relationships:

graph TD
  User -->|owns| Vehicle
  User -->|manages| Station
  Station -->|has| Connector
  Session -->|uses| Connector
  Session -->|started_by| User
  Session -->|includes| Vehicle
  Session -->|generates| Payment

This design enables secure filtering:

A driver only sees their sessions
An operator sees only their stations and data
Admins see everything — with full context

💼 Business Benefits

Here’s how this architecture helps real-world operations:

✅ Clean Ownership

You always know who owns what — critical for multi-tenant platforms.

🧾 Accurate Billing & Auditing

Session data is precise, and always linked to verified users and vehicles.

📊 Reliable Insights

Track:

Utilization rates
Energy trends
Station availability
Fault reports

📦 Ready for Expansion

Add payments? Just relate to Session
Add loyalty programs? Just extend User or Vehicle
Add partners? Group stations under Company model

🛠️ Built on Proven Tech

FastAPI: modern, high-performance web framework
MongoDB: scalable NoSQL for flexible EV data
Motor (Async Mongo Driver): for speed and concurrency
FastAPI Pagination: built-in filtering and listing support
OCPP 1.6 support: full integration with open charging standards

🌱 Designed for Whom?

This backend is built to support:

⚙️ Charge Point Operators (CPOs)
→ Manage large networks of chargers, users, and usage data
🧠 SaaS Platforms
→ White-label and integrate this backend into your own services
🚗 EV App Startups
→ Quickly launch user apps with full charging + vehicle logic
🏢 Real Estate / Retail
→ Provide EV charging at locations you manage, with data insights