Vepler is the API-native Ordnance Survey partner. All nine NGD themes — half a billion features, twenty thousand refreshed daily — joined to planning, ownership and price history, live behind one key in 24 hours. Built for product teams and the public sector alike.
GET /v1/ngd/features?point=51.5055,-0.0754 → 9 themes, one key
500M+
Geographic features
9/9
NGD themes served
20,000+
Features updated daily
24h
From enquiry to API key
The partnership
Most partners resell the map as a project: their portal, their contract, their timeline. We built infrastructure instead — and the difference shows up everywhere you can measure it.
A typical OS partner Quote form, sales calls, procurement — weeks before you touch a feature.
Vepler Enquiry to live API key in 24 hours. Pay-as-you-go from £0, no minimum commitment.
A typical OS partner Bulk files you download, load, index and host yourself.
Vepler A hosted API answering point, polygon and UPRN queries in under 100 ms.
A typical OS partner A slice of the database, repackaged per product line.
Vepler Every theme and every collection: 500M+ features across Great Britain.
A typical OS partner Quarterly releases, collected from a portal and reconciled by hand.
Vepler 20,000+ features refreshed every day from the national database, live in the API.
A typical OS partner The map alone — joining it to anything else is your project.
Vepler Every feature already joined by UPRN to planning, ownership, energy, risk and price history — the whole platform behind one key.
A typical OS partner Account managers, ticket queues and first-line triage.
Vepler The engineers who run the platform, on a direct line, same working day.
The test is simple: ask a partner for a live API key today, then count the days. Ready to build? OS NGD API and pricing.
Who it's for
The same database and the same API, delivered on the terms each side of the market actually needs.
Private sector
For PropTech, insurers, utilities and consultancies building customer-facing products or internal analytics on authoritative geography.
Public sector
For councils, agencies and public bodies under the Public Sector Geospatial Agreement, or with deployment requirements a hosted API alone can't meet.
The join
Every NGD building carries a UPRN — the same identifier the rest of the national record keys on. We maintain those joins, so one call returns the map and its meaning together.
The UPRN on the building is the UPRN on its title, its planning file and its EPC. We keep those joins current so you never re-derive them.
Geometry and property context arrive together — no second supplier, no matching exercise, no reconciliation queue.
Every OS theme and every property dataset we hold sit behind the same API key and the same usage meter.
One UPRN → geometry, planning, EPC and title in one response
Beyond the API
Not every team wants an endpoint. The same joined record powers working software — built by the engineers who run the platform.
A workflow your team runs by hand, shipped as a hosted dashboard on the joined record — every figure sourced, yours to keep.
Agents that read the record for you — checking constraints, assembling reports and answering property questions with sources attached.
Automation that watches the national record for change — new applications, updated designations, fresh transactions — and acts the moment it lands.
Licensing
One agreement
Your OS use is scoped under our partner contract — internal analytics or customer-facing product — signed in hours, with no separate OS paperwork.
Bring your own licence
Already licensed with OS? Keep your commercial terms and connect them to our infrastructure — caching, query optimisation and the linked datasets included.
Metered, not reconciled
Usage is metered per attribute as you query. Royalty reporting to OS is handled on our side — nothing for you to tally at year end.
Provenance inline
Every response names its source, theme and snapshot, so attribution and audit are never guesswork.
Access routes
Licence, data, infrastructure and support are separable. Start with one, take the stack when it earns it.
The full NGD behind an OGC API — Features endpoint. Query by bounding box, UPRN or collection.
Every theme as managed extracts for warehouses and GIS estates that want the data local.
Bring an existing OS agreement and run it through our API layer and joins.
For PSGA bodies and regulated estates: the same stack, deployed where you need it.
