Bins, benches, lamp posts, signs and trees on a single map that doubles as a searchable database — one record, shared by the crews who repair an asset and the planners who budget for it.
The live demo is the real product, filled with an invented town's assets. No sign-up, nothing to install.
A traditional GIS is built for the one specialist who knows how to drive it. mapzaa is a GIS for everyone else who needs the same map — the crew out on a round, the planner with a budget, the person answering a resident on the phone.
Open it and you see your own town with your own things on it. Click a pin and you read what it is, where it stands and what state it is in. Nobody has to know what a shapefile is.
A bench is a bench, with an address, a status and the fields you chose — not a feature class with attribute columns. The same record is a pin on the map and a row in the table, so nobody keeps a spreadsheet on the side.
Precise coordinates on every asset, filters across any field, a CSV export at any time and an API for other systems. The specialist loses nothing; everyone else gains a map they can actually use.
Already have your assets in a spreadsheet or another GIS? See how we move them for you
Field crews, maintenance planners and finance all need the same asset record, approached from different directions.
Which lamp posts on the high street are in maintenance? Which benches were installed before 2015? Filter on any field you record, then send the link — the filters travel with it, so a colleague opens exactly the view you were looking at.
How views and filters workEvery asset gets a short code like BEN-BY66GW. It leaves out characters that are easy to misread, so it survives a sticker, a phone call and a handwritten work order — and pasted into the search box, it finds the asset even after it has moved category.
Finding assets againGroup the assets a round needs into a plan, give it a due date and assign the people doing it. Each of them gets the whole plan by email in their own language, with its own map, and sees only the plans that are theirs.
More on plansA REST API reads the register for your reports and works systems, and lets vehicles, sensors and surveys report where things are — those pins move live on the map. A key can read, or update locations, and nothing else.
Read the API documentationDrop a pin where the asset stands, or type an address and let mapzaa place it. Every pin is a full record, and every record is a point on the map.
Set up the asset types your municipality actually tracks, each with its own colour, then add the fields that matter per type: install date, material, serial number, last inspection.
Every asset holds both coordinates and a real street address, looked up automatically, so a work order means something to whoever picks it up.
Switch from the map to a sortable table when you need to plan a maintenance round, review a category or hand a list to a contractor.
Select rows in the table and set a category, status or field on all of them in one step, then export exactly what you're looking at as CSV, GeoJSON or KML.
The map, the register and the edit form all work on a phone, so a crew can correct a record while standing in front of the asset.
No procurement cycle, no installation, no training week.
Start from the asset types most municipalities track and adjust them to match how your departments are organised.
Click the map, search an address or paste coordinates. Record the status and the details you need; the address fills itself in.
Filter by category or status to plan maintenance rounds, and check any record from a phone while you are out in the field.
An asset register outlives the people who set it up. It should be dull, durable and private by default.
Email and password, plus a one-time code sent to that address each time, or a passkey that unlocks with a fingerprint, face or screen lock. Sign-in attempts are rate limited and every form is protected against bots.
Connect Microsoft Entra ID, Google Workspace or any other SAML identity provider, and require it for everyone except administrators, who keep a way back in.
Every sign-in and every change is recorded with who made it and when, kept for 180 days and searchable by your administrators.
There is no public sign-up. Administrators invite colleagues by email, decide who may edit, and every invitation expires after 72 hours.
Each organisation's assets, categories and fields are kept separate at the database level. Nothing is pooled between municipalities and nothing is sold on.
This site loads no analytics and no third-party scripts — the only code it runs is our own, and the typefaces come from our own domain too. The dashboard sets only the cookies your session needs.
mapzaa is made in Umeå in northern Sweden and hosted in Denmark, inside the EU. GDPR from the ground up, and your register never leaves the Nordics.
Evaluate mapzaa for free with your own assets. When you're ready to run your register on it, we agree a price that fits your municipality.
Free
We set your municipality up and invite your first administrator, who then invites the rest of the team.
Price on request
For running your municipality's register on mapzaa, across as many departments as need it.
Both include the whole product. Need an on-premise deployment? Tell us and we'll work out what fits. Moving from another system? See how we move your data.
Something else on your mind? Ask us.
An afternoon. We create your organisation, you set up the categories you track, and your first assets can be on the map the same day. There is nothing to install.
On servers in Denmark, inside the EU, run by a Swedish company. Each organisation's register is kept separate, never pooled with another's and never sold on.
Whenever you like. The assets table exports exactly what you are looking at as CSV, GeoJSON or KML, and the API reads the whole register.
No. Send us what you have and we move it across for you — see how migration works.
Rarely. If you can use a map on your phone, you can use mapzaa: click a pin to see what it is, and edit it if you are allowed to.
Every sign-in needs a password and a one-time code (or an authenticator app) or a passkey, single sign-on is available, every change is logged and each organisation’s data is kept apart. Security and data protection lists it all, including who processes what.
We are a Swedish company and host in Denmark. For accounts we are the controller; for what your organisation records in its register, you are and we are the processor. If you need an Article 28 agreement we put one in place — ask us. The privacy policy has the detail.
Four roles, each including the one before: viewers read and export, field workers update the condition of an asset and add photos, editors change the register itself, and administrators manage people and settings. The server checks it on every request.
Yes. A REST API reads the register for reports and works systems, and lets vehicles, sensors and surveys report positions. Sign-in can go through your own identity provider (SAML), and the whole register exports as CSV, GeoJSON or KML. API documentation.
Every asset gets a short code such as BEN-BY66GW. Print it as a QR label — on an A4 sheet or from a label printer — and scanning the label opens the asset. How labels work.
On a phone the map, the register and the edit form all work in the browser, and there is an Android app that also scans labels and takes photos. It needs a connection; there is no offline editing.
Each organisation has an agreed limit on assets and on people. An evaluation typically starts at 1,000 assets and five people, and we set the limits for your municipality together when you go beyond it.
The dashboard and this website are in English, Swedish, Norwegian and Danish. Each person can choose their own language, and emails arrive in it.
You can export the whole register whenever you like. After an organisation is closed we keep its data for 30 days so a mistake can be undone, then delete it permanently.
A free demo takes about twenty minutes: we set up a register for your municipality, put a few of your real assets on it, and you decide from there. Nothing to sign, nothing to pay, no sales sequence afterwards.
Or open the live demo and have a look around first — no sign-up.
Your message wasn't sent: your browser didn't say which page the form came from. Reload the page and try again, or write to [email protected].
Your message wasn't sent: too many messages have come from here in a short time. Try again in an hour, or write to [email protected].
Your message wasn't sent: that email address doesn't look right. Check it and send it again.
Your message wasn't sent. Fill in your name and email address — and, for a question, the message itself — then send it again.
Your message wasn't sent: it can hold at most two links. Remove some and send it again.
Your message couldn't be delivered just now. Try again in a minute, or write to [email protected].
Sending…