How it works

From paper plans to precise digital fences.

The whole cycle — plotting a stand, recording it immutably, and managing the people connected to it — happens in one secure workspace.

  1. 1

    Plot on the map

    Trace the stand's boundary using the built-in map. It's saved as GeoJSON geometry, not a hand-drawn line.

  2. 2

    Validated against the boundary

    PostGIS checks every polygon sits inside the authority's legal demarcation before it is accepted.

  3. 3

    Numbered & tracked

    Each stand receives a unique record number, and every change is recorded in its history.

  4. 4

    Approved & pinned

    Finalised records are pinned to IPFS — content-addressed, immutable storage.

  5. 5

    Managed & audited

    Families, disputes, fines and documents are all managed here — with a full audit trail behind them.

People

Families & members, handled with care.

Register households and their members, with ID numbers and contact details encrypted at rest. Family records link cleanly to the stands they are connected to.

  • • Encrypted personal information by default
  • • Head of household and member relationships
  • • Allocations and disputes traceable to the family

Family · Mabunda

NM

Naledi Mabunda

Head of household

TM

Thabo Mabunda

Child · born 2010

ID numbers & contacts encrypted at rest

MUKH1 Within boundary ✓

Land

Stands mapped with precision.

The authority draws stands on a live map and the system validates them against the registered boundary — no overlaps, no ambiguity.

  • • PostGIS boundary validation on every polygon
  • • Optional what3words address for every stand
  • • A complete, permanent history for every stand

Identity

A record number that means something.

Every stand carries a unique record number built from the authority's 4-letter code — for example MUKH for Mukhomi — followed by its sequence. Numbers are generated safely even under heavy use.

  • • The authority's code is globally unique and immutable
  • • Each stand's full history is preserved
  • • Finalised records carry their number into the immutable store

Record numbers

MUKH1First in the register
MUKH2Second in the register

Sequences are per-authority and concurrency-safe

Records

Approved records are pinned, not just saved.

When a document is approved or a record is finalised, its metadata — and for stands, its boundary — is packaged and pinned to IPFS. The content-address returned is stored on the record as proof.

Content-addressed

The IPFS content-address is derived from the content itself — change a byte and the address changes. Records can't silently be altered.

Decentralised

Files live on a distributed network rather than a single vendor's vault, reinforcing the authority's data sovereignty.

Toggleable by design

IPFS, maps and what3words are optional. Self-hosters control exactly which external services are used.

Deployment

Cloud, or completely self-hosted.

The platform ships as a standard Docker stack — app, database, Redis, queue worker and scheduler. Run it on any host you trust, backed up on your own schedule.

No hard-coded dependencies

IPFS, map providers and what3words are toggleable and configured by the superadmin.

Health-checked stack

A built-in health endpoint and dashboard widgets confirm the database, queue and storage are alive.

Backups & recovery

Scheduled backups to S3-compatible storage keep the register safe even beyond IPFS.

Ready to digitise your land register?

Register your authority