Chargers Without Brains
Most EV chargers on the market are, architecturally speaking, glorified outlets. A contactor, a pilot signal, a plastic shell — and a permanent tether to a cloud server that decides whether your car gets to charge. Lose your internet connection, and you lose functionality. The server goes down, and a parking garage full of vehicles sits idle.
MRS Electronic and Technology Spirits took a different approach with the MCharger line. They put the entire charging management platform — user authentication, load balancing, scheduling, analytics, billing — on the charger itself. No cloud dependency. No subscription. Open the browser on any device connected to the same network, and you are looking at a full-featured charge point management system running on embedded hardware inside a 266×411mm polycarbonate enclosure rated to IP55.
Three Tiers. One Platform.
Plug-and-charge at 11 or 22 kilowatts. No authentication, no network features. For a single-car household that just wants to plug in and walk away. KfW 440 eligible.
RFID authentication, OCPP v1.6j, dynamic load balancing, 128 user accounts, OTA updates, solar integration, scheduling, analytics with PDF export. Full embedded CPMS accessible via browser. KfW 441 eligible.
Everything from Connected plus a MID-certified energy meter for legally accurate billing. The feature that unlocks public and commercial deployments where kilowatt-hour accounting has to hold up in court.
All three share the same physical platform: PC+ABS housing at 137mm deep, operating from -25°C to +60°C, Type 2 connectors, a 2.4-inch color display, DC fault detection at 6mA, three-direction cable entry, and a three-year warranty. CE, IEC 61851, RoHS, WEEE — the full European compliance stack.
The Brain Inside the Box
The hardware story is straightforward. MRS Electronic designs and manufactures the wallbox in Rottweil: power electronics, enclosure, connectors, display, RFID reader, DC fault detection circuitry. Clean, competent German manufacturing. The more unusual story is what happens when you connect to the device over your local network.
Technology Spirits built the entire software stack. The embedded CPMS. The OCPP v1.6j implementation. The load balancing algorithm. The user management layer. The scheduling engine. The analytics pipeline. The OTA update mechanism. The solar integration logic. The billing system. The web configuration application. The firmware running on the embedded processor inside the charger.
The OCPP v1.6j implementation deserves attention. Most chargers implement OCPP as a client — they call home to a cloud-hosted CPMS, which makes decisions and pushes them back down. The MCharger Connected runs the CPMS locally. It can still connect upstream to a third-party OCPP network when needed — for public charging scenarios where the wallbox needs to register with a roaming platform — but the core intelligence lives on the device.
Dynamic Load Balancing
In a multi-charger installation, total available power is finite. The algorithm distributes current across connected units dynamically, with prioritization logic that accounts for which vehicles need charge most urgently, which users have higher priority, and what the grid connection can handle. When paired with a two-way meter, the system factors in real-time solar generation, steering surplus photovoltaic power to connected vehicles before drawing from the grid. This runs continuously, on embedded hardware, inside a box that costs under five hundred euros.
On-Device vs. Cloud
The decision to run everything on-device rather than in the cloud was deliberate. Latency drops to near zero — there is no round trip to a remote server when a user taps an RFID card. Reliability improves categorically — the charger functions fully with no internet connection. Privacy is structural rather than promissory — charge data lives on the local network unless the operator explicitly connects to an external system.
There is no recurring SaaS fee, no API rate limits, no vendor lock-in to a platform that might pivot its pricing model or shut down. The management platform comes integrated, free of charge.
"The charger should work like a router — plug it in, connect to it, configure it from a browser. No app store, no account creation, no cloud dependency."
— Engineering philosophy, Technology Spirits
Zero Latency
RFID auth, scheduling decisions, and load balancing all happen locally. No server round trip.
No Internet Required
Core charging operations run without connectivity. Cloud is optional, not required.
No SaaS Fees
Management platform is embedded. No subscriptions, no API limits, no vendor lock-in.
Structural Privacy
Charge data stays on local network. External connections are opt-in, not default.
Private. Public. Fleet.
Private installations are the volume play. A homeowner mounts a Connected unit in the garage. Family members get RFID cards. The scheduling engine shifts charging to off-peak tariff windows automatically. If the household has rooftop solar, the two-way meter integration maximizes self-consumption. For company car drivers who charge at home and bill their employer, the analytics suite generates per-session reports with kilowatt-hour precision.
Public and semi-public deployments — hotel parking, retail, office buildings — use RFID access control to gate who charges and OCPP to register with existing roaming networks. The Energy variant, with its MID-certified meter, provides the legally defensible billing data that commercial operators require. A boutique hotel can install four units, connect them to the building's network, and offer EV charging to guests without subscribing to a managed service or installing additional backend infrastructure.
Fleet operations represent the highest-complexity use case. Per-vehicle tracking, cost allocation across departments, multi-location rollouts with site-specific load balancing. The 128-user capacity per unit, combined with role-based access control, means a single charger can serve a mid-sized fleet with granular permission structures — administrators, drivers, guests — without external user management systems.
Made in Germany. Coded in Dubai.
MRS Electronic, based in Rottweil, brings over 25 years of expertise in vehicle and industrial electronics. Technology Spirits, headquartered in Dubai with an extended development team in Islamabad, is the engineering partner. The hardware — enclosure, power electronics, connectors, display, RFID reader, fault detection — is designed and manufactured in Germany. The software — every line of firmware, every protocol implementation, every algorithm, every pixel of the web interface — is engineered by TS.
This is not outsourcing. It is a vertically integrated product development partnership split across geographies, with hardware expertise in Germany and software expertise in Dubai and Islamabad. The MCharger is a single product with a single brand, but its bill of materials spans two continents and two very different engineering disciplines.
The EV charging market is projected to grow at over 25 percent annually through the end of the decade. The products competing for residential, small commercial, and fleet segments increasingly look alike — same form factors, same connectors, same power levels. The differentiation is moving to software. Specifically, to how much intelligence lives in the device versus how much depends on external infrastructure.
Their chassis. Our cortex.
German hardware. Dubai software. No cloud required.