Skip to main content
Mapit GIS Cloud
Coming soon

Built, running, and opening to selected users shortly. General availability is planned for January 2027.

Mapit GIS Cloud

One project, your whole crew, everything back in one place.

Mapit GIS Cloud hands the same project to everybody who collects for you, takes back the rows each person changed, merges them without losing a value, and shows whoever runs the job what has arrived. Work offline and sync when it suits you.

Mapit Cloud is an organisation’s own subscription, separate from the app. Mapit GIS is a GIS in its own right and does not need the cloud to do its work.

Three surveyors collect offline in the field, their changes meet in the cloud, and the manager sees the result as of the last syncas of 14:20
One project, one structure
Everybody collects against the same layers and the same fields, so the work comes back reconcilable.
Rows, not files
A sync moves the rows that changed. A project stays a download you did once, not one you repeat.
Nothing is lost
Where two people disagree, both values are kept and put in front of a manager.
Encrypted, in the EU
Your projects are encrypted whenever they are not in use, and your data stays in the EU.

How the loop runs

One project, released once, collected by everybody, merged in one place. Every step below is running in production today.

Release, collect, sync, see01Release02Collect03Sync04See
  1. 01

    Author and release

    A manager builds the project once: the layers, the fields, the drop-downs, the styles. Releasing fixes that structure and gives it a version number, which is what makes work coming back from six phones reconcilable at all.

  2. 02

    The crew collects

    Everybody works from their own copy of the project, with a connection or without one, and nothing about the cloud sits in the way of a day's fieldwork.

  3. 03

    Sync exchanges rows, not files

    When a phone finds a network it sends the rows that changed and receives the rows other people changed. Two edits to different fields of one feature both land. Two edits to the same field are merged on the server and the discarded value is kept, never dropped.

  4. 04

    See it when it arrives

    The board shows each cloud project, what each person has synced into it and when they last synced. Every figure carries its own timestamp, because a crew in a valley is working, not missing.

A city skyline across a planted water garden in flower

A planned place is a maintained one: the drainage, the planting, the lighting, the structures, the trees. Somebody has to go and look at all of it, and somebody has to be able to trust what comes back.

What the cloud does

Built and running

Project sync

A whole GeoPackage project, released to a crew and collected into by all of them at once. The file on the server is the record; the transport is rows. A phone that already holds the project sends what it changed and receives what everybody else changed, so the second sync and the two hundredth are small.

  • Field-level merge. Two people editing different fields of one feature both land.
  • Nothing lost. A discarded value becomes a conflict record with both sides and who sent them.
  • Structure changes safely. A new field ships as a schema patch, not as a new download.
  • Yours to take away. Download the project as a GeoPackage and open it in QGIS.

How it works →

At launch

QGIS on the desktop. A Mapit plugin that opens a cloud project in QGIS as a copy to view, and brings in the crew’s latest work when you ask. Read only: the work itself is done on the phones. It is released with Mapit Cloud.

Your clients’ work, kept closed

A surveying firm’s projects are its clients’ property before they are our data, and they are treated that way.

  • Encrypted whenever it is not in use. Under a key that belongs to your organisation and to nobody else.
  • Your data stays in the EU. Where it is held and where it is served from.
  • Private until you share it. Nothing is visible to anybody, inside your organisation or outside it, until you decide it is.
  • Yours to take away. Export a project as a GeoPackage at any time and open it in QGIS.
A project file sealed on an encrypted disk, opened only in memory, with a key that belongs to one organisationEU

Running a crew? Set up an organisation

On your own, the cloud is a place to keep your forms and your work. An organisation is what turns it into a team tool: you invite the people who collect for you, decide what each of them may do, and get the activity board for the crew as a whole.

The organisation runs on its own cloud subscription, which you buy. On top of that each person holds their own app subscription: Pro+ for you and for anybody you make a manager, Pro for the people who collect. A viewer who only reads what you share needs neither the app nor a subscription.

  • Invite by email, one person at a time. Nothing is a shared code somebody can forward. You name who joins.
  • Five roles, from admin to viewer. A contributor collects. A manager runs the roster. Only the admin spends money.
  • Seats you buy and assign separately. A seat holds whoever you put in it, so changing somebody's role converts nothing.
  • One organisation, several clients. Groups keep one client's work out of another's, which org-wide visibility cannot.

Who needs what

What each role can do

There are two subscriptions and they pay for different things.

The organisation pays for the cloud

One subscription per organisation, bought by its admin. It carries the seats its people fill, the viewer places it shares with, and the storage its projects use.

Each person holds an app subscription

Mapit GIS Pro or Pro+, bought in the app, which is what the app itself runs on and what decides the role that person can hold. The free tier includes no cloud access at all.

Mapit Pro

For the people who collect

  • Create a Mapit Cloud account from the app
  • Accept an invitation as a contributor or a publisher
  • Collect for any organisation that gives them a seat
  • Collect into the projects shared with them
  • Design attribute sets, with or without an organisation

Not included

  • Hold the manager role
  • Start an organisation of their own

Mapit Pro+

For managers, and for whoever owns the organisation

  • Everything Pro does
  • Hold the manager role: run projects, releases and the roster
  • Create an organisation, and buy the cloud subscription it runs on

Invited viewer

For a client or a colleague who only reads

  • Get an account from the invitation itself
  • Read exactly what has been shared with them
  • Needs neither the app nor a subscription

Not included

  • Collect, sync, or open a project file

The attribute designer needs no organisation at all: any Pro or Pro+ subscriber can build their own sets and export them to the app. A seat is typeless: it holds a manager, a publisher or a contributor, so changing what somebody does converts nothing. Nobody needs two cloud subscriptions to work for two organisations, because the seat belongs to the organisation rather than to the person.

There is no sign-up form here, on purpose

Accounts come from exactly two places, and signing in cannot create one. Making the account costs nothing; what you can do with it afterwards follows your subscription.

From the Mapit GIS app

The normal route, and the one to use if you survey. Install Mapit GIS, open Mapit Cloud inside it, and create your account there. The app installs free and runs with no account at all; Pro and Pro+ are bought in the app, and the cloud itself is your organisation’s subscription.

From an invitation

Opening an emailed invitation to an organisation creates your account. This is the route for somebody who needs to read a team’s work without surveying themselves, and it is the one case that needs neither the app nor a subscription.

Sign in with an emailed code if one of those has already happened.

A roadside at night: lit street lamps, road markings, parking bays and a bridge beyond

Fourteen thousand street lights, three weeks, four surveyors

One job walked through from the first form to the finished file, including the Thursday somebody surveys a lamp post that was already done.

Read the story