Skip to main content

Running Māori GIS locally and using hybrid architecture

Local infrastructure can provide direct custody and offline operation, but it transfers operational responsibility to the organisation. Hybrid architecture can be a strong fit where different information classes need different levels of access, resilience and exposure.

Local can mean several things

  • one encrypted laptop
  • QGIS and a GeoPackage
  • a shared NAS
  • an office file server
  • PostgreSQL/PostGIS on a local server
  • ArcGIS Enterprise on premises
  • a co-located server
  • a disconnected archive
  • a private network with no internet route

These have very different operating burdens.

Benefits of local custody

Local or disconnected systems can provide:

  • direct physical custody
  • operation without internet
  • architectural autonomy
  • separation from external SaaS accounts
  • controlled environments for highly restricted information
  • predictable local access to large datasets

For some highly sensitive kōrero, those benefits may justify the extra work.

Local risks are operational

A local system is only as resilient as its administration.

Common failure modes include:

  • no off-site backup
  • ageing disks or server hardware
  • unpatched operating systems
  • ransomware
  • shared administrator passwords
  • one knowledgeable person
  • fire, flood or theft
  • missing encryption keys
  • no monitoring
  • unsupported software
  • no tested recovery procedure

A server under a desk is physically local. That does not make it a good preservation strategy.

NAS is storage, not governance

A network-attached storage device can be useful for shared files and backups. It does not automatically provide:

  • fine-grained GIS permissions
  • robust audit trails
  • database transactions
  • data lineage
  • publication separation
  • off-site disaster recovery

Use it for the role it can sustain rather than treating it as a complete GIS platform.

Hybrid separates data by purpose

An established Māori organisation may deliberately use different environments:

Conceptual flow

The important control is the approved movement between tiers.

Complexity is the hybrid risk

Hybrid can become expensive if every tier uses different identity, backup and support arrangements. Document:

  • system owner
  • administrators
  • authoritative source for each dataset
  • approved flows
  • backup responsibility
  • monitoring
  • annual cost
  • exit path

Do not create three platforms when one simple environment and a publication copy would meet the need.

Disconnected archives

A disconnected store can be appropriate for information where online availability is not required and unauthorised disclosure would be serious.

But isolation introduces risks:

  • forgotten passwords
  • stale software
  • failed storage media
  • no remote backup
  • no routine use to expose problems

Maintain more than one protected copy, document recovery and periodically verify readability.

Last verified: 16 August 2026