Launch release: 16.4M address points and derived postal code points, national coverage. See coverage

Map hosting

We build the map and run it on our servers. You get a link to share or embed, and nothing to maintain.

The problem this solves

You have the data. You may have downloaded it from this site. Getting it onto a map that other people can actually open is where it stalls.

Serving spatial data on the web means vector tiles, a tile server or a static tile store, a CDN, a styling layer, and someone who understands all four. For a district with three million address points and a planning department of four, that is not a reasonable ask. The usual outcome is a PDF map that goes stale the day it is exported, or a desktop GIS file that only one person can open.

Hosted maps skip that. Send us the data and what it needs to show. We build it, host it, and give you a URL.

What you get

A live map at a URL. Shareable with anyone, or restricted to people you name. Embeddable in your intranet, your board reports, your public site.

Your data, our base. Your enrolment figures, service areas, catchments or project sites, drawn over the Canadian address and parcel base we already maintain — so context is there without you having to source it.

Updates on your schedule. Send a new file, or point us at a feed. The map updates and the URL stays the same, which means the link in last quarter’s report still works and still shows current information.

No infrastructure. No tile server, no storage bill, no certificate renewals, no upgrade that breaks the map the week before a board meeting.

Who this is for

School districts publishing catchment maps, showing enrolment pressure by area, or running a boundary review where the public needs to see the options.

Municipalities and regional districts with service areas, asset inventories, development applications, or anything currently living in a PDF.

Consultancies delivering a map as part of a study, without becoming the client’s long-term hosting arrangement.

How it works

  1. Tell us what the map needs to show. Usually a short call. The question matters more than the file format.
  2. Send the data. Whatever you have — spreadsheets, Shapefiles, a database extract, a PDF someone drew in 2019.
  3. We build it. Styling, layers, legend, popups, filters. You review a draft and change what you want changed.
  4. It goes live. You get the URL and, if you want, an embed snippet.
  5. You send updates. As often as the data changes.

Done for you, for now

Every map is built by us at present. That is deliberate: the maps that matter to a planning department usually need judgement about what to show and what to leave out, and that judgement is most of the value.

Self-serve editing is coming. Clients on hosted maps now will get access to it as it lands.

Why not host it yourself

Sometimes you should. If you have a GIS team that already runs tile infrastructure and a spare person to maintain it, self-hosting is cheaper and gives you more control.

If you do not, the true cost of self-hosting is not the server. It is the person who has to understand it, and what happens when that person leaves.

What it costs

Priced per map, by how much data it carries and how often it changes. Get in touch with what you are trying to publish and we will quote it. See pricing for how the tiers work.

Start smaller

If you are not sure it is worth it, download the data first. It is free, and it will tell you whether the base is good enough for the map you have in mind.