Cost of a Māori GIS
There is no single price called the cost of Māori Data Sovereignty. The real cost comes from running a system that can keep exercising agreed authority over time: software, infrastructure, people, governance, security, training, backup, preservation, migration and exit.
Storage is often not the largest cost
For many small GIS environments, specialist labour and continuity cost more than disk space.
A system may need continuing work for:
- GIS administration
- database administration
- identity and permissions
- backups and restore testing
- software updates
- metadata
- data cleaning
- training
- documentation
- security review
- vendor management
- governance meetings and approvals
- migration and archive
Open-source software can remove a proprietary licence but it does not remove those activities.
Cost categories
| Cost type | Typical GIS examples |
|---|---|
| Capital | workstation, server, NAS, UPS, scanner, networking |
| Recurring platform | SaaS licences, cloud compute, storage, database, domains |
| Labour | GIS, database, security and governance administration |
| Capability | training, mentoring, documentation and succession |
| Assurance | privacy, security review, penetration testing where justified |
| Preservation | archival exports, media replacement, migration |
| Switching | data extraction, transformation, rebuilding applications |
| Exit | supplier handover, cloud egress, deletion verification |
| Opportunity | volunteer, kaumātua and staff time that could support other mahi |
Free software is not a free system
QGIS and PostgreSQL can be used without proprietary software-licence fees. That is a real benefit. If a complex deployment needs 200 specialist hours each year, the labour cost can still dominate.
Likewise, cheap cloud storage can become expensive once identity, applications, support, backup, monitoring and migration are included.
Count governance work
A culturally and technically sound GIS may require time from:
- kaumātua and knowledge holders
- trustees or governance
- iwi/hapū staff
- environmental teams
- legal or policy advisers
- GIS specialists
Do not treat that time as zero merely because it is volunteered. It is a real resource and opportunity cost.
Count exit before purchase
Ask for the cost and process of:
- exporting every dataset
- exporting attachments and metadata
- recovering source code and configuration
- converting proprietary formats
- rebuilding identity and applications elsewhere
- retaining an archive
- deleting or expiring provider copies
A platform with a low entry cost and a high exit cost can be expensive over its full life.
Do not over-engineer sovereignty
An individual project may need:
- QGIS
- one well-managed GeoPackage
- encrypted storage
- two recoverable backups
- source notes
- a handover page
It may not need Kubernetes, a high-availability database cluster or a custom sovereignty portal.
Architecture should match the kaupapa and organisational capability.
Long-term cost matters more than launch cost
A grant can fund initial configuration while leaving the organisation responsible for years of:
- licences
- storage
- domain renewals
- staff
- upgrades
- support
- hardware replacement
For a realistic comparison, use Ten-year cost models.
Practitioner note
GIS projects can look cheap when the estimate counts only software and initial configuration. In practice, the expensive part is often keeping enough capability inside the organisation that the system remains useful after the original project team has moved on.
Training and handover are therefore part of the architecture, not optional change-management extras.
Related pages
Last verified: 16 August 2026