Skip to content

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 modelling, with a null where there is no coverage rather than a guess.

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 and the coverage collapses.

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 across 909 real UK sites, filterable by connector and power, built by AI agents in under a day.

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: a null where there is no coverage, never a guess dressed up as a number. The same profile sits behind the showcase app's range ring.

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 a stop costs the journey. On Preston to Kendal, 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 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. Route to a charger and draw 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

Give us your site list and a coverage target.

The 909-site charging app in our showcase runs on the same SDK and gateway, built in under a day. Our AI agents will build your site-planning model the same way.

The offer

What you are actually being offered.

On the page, not in the small print: the scope, the deliverable, the timetable and how the money works, before you spend an hour on a call finding out.

Who it is for
A charge point operator or site developer deciding where the next chargers go.
What is in scope
You give us your site list and a coverage target. We build the site-planning model on it: drive-time coverage, the gaps, and the residents each candidate site reaches.
What you get
A working gap model on your own sites, and the driver-facing map if you want one, built on the same SDK and gateway as the 909-site app in our showcase.
How long
Days rather than months. The showcase charging app was built in under a day.
What it costs
Scoped on the call. Hosted API pricing is published; a self-host licence is quoted per deployment.
Next step
Send the site list and the coverage target, and we will show you where the gaps actually are.
Send us your site list