50,000 free calls a month, card-free. Get an API key →

Solutions / EV Charging Networks

Find the gaps. Plan the sites. Route the range honestly.

Drive-time coverage against real residents shows exactly where the network is thin. Elevation profiles feed range and fuel modelling, with a null where there is no coverage rather than a guess.

Why MapMap for charging networks

From site planning to the driver's range ring.

The gap analysis and the driver-facing app below are both live: one plans the network, the other proves the developer experience.

Live demo

Where the network doesn't reach

Drive-time coverage from every public charge point in East Lindsey, Herefordshire and Stoke-on-Trent, measured against Census 2021 population centroids. Toggle to rapid-only, as this capture of the live tool does, and watch the coverage collapse.

Open the gap finder
The 909-site EV charging app filtered to ultra-rapid 150 kW chargers, clustered on a dark UK map
Built with MapMap

909 real sites, a working app

A full EV-charging companion, clustered and status-coloured across 909 real UK sites, filterable to the connector and power you need, built by autonomous AI agents in under a day on the MapMap SDK. The fastest proof of the developer experience we can offer.

See the showcase
A real elevation profile for the Preston to Kendal drive, 29 to 67 metres and gently rolling, drawn as a blue area chart
Range-honest

Elevation profiles for range modelling

Elevation along the route feeds range and fuel modelling directly: a null where there is no coverage, never a guess dressed up as a number. It is the same profile behind the range ring and arrival-battery estimate in the showcase app.

A real MapMap route from Preston to Kendal with a charging station marked near Lancaster and a card showing its genuine detour cost of three minutes
Along the route

Chargers with an honest detour cost

Search along a route returns charging stops with their real engine-computed detour, so an app can say what the stop actually costs the journey instead of drawing a radius and hoping. This is a real result on the Preston to Kendal drive: the Lune Aqueduct station adds three minutes.

the whole stack, on your own network
$ docker compose up -d --build
→ tiles · geocoder · router · guidance · territories
→ 0 external map dependencies
Self-hosted

No per-call metering on your own box

Docker distribution and signed territory packages: a self-hosted deployment has no metering to a third party sitting between your app and your drivers.

Illustration of an API request and response for a routing query
Agent-first

An API key in one call

A hosted MCP server, one-step installs for Claude, Cursor and VS Code, and a card-free API key with no sales call in between. Your team can be routing to a charger and drawing a range ring this afternoon.

Known limit: coverage percentages come from open charge-point registries and Census centroids, not live network telemetry. Registries carry stale and dead entries, so treat site counts as indicative, and a driver being inside a drive-time ring says nothing about whether that charger is working, free or affordable right now.

Agent-first

We will build your site-planning proof of concept, fast.

The 909-site charging app and the low-bridge app in our showcase were both built by autonomous AI agents in under a day, on the same MapMap SDK and gateway. Give us your real site list and your coverage target, and we will build a working proof of concept on your own network, fast enough that you will see it before the next planning meeting.