Hyveminds/Products/HyveMaps PRIVATE BETA
Product 06 · Beta · v0.7 · invite-only

Maps that show
their working.

A geospatial layer for community researchers, with provenance, uncertainty and consent baked into every pin.

HyveMaps is a thematic mapping tool for organisations who can’t use Google Maps because their data is sensitive, contested, or community-owned. Every layer carries its source, its consent terms, and its uncertainty. In private beta with eight Aboriginal land councils, two health districts and one housing-justice researcher.

02 · A look

Provenance is a first-class property.

A health-district researcher is mapping food-access deserts in outer-Melbourne. Each pin carries who collected it, when, with whose consent, and how confident they are.

hyvemaps.percapita.org.au/atlas/food-access-vic
FOOD-ACCESS DESERT · Sunshine N. · 14 min walk to grocer
WEEKLY MARKET · Sat 8am–1pm · est. 2003
+
SELECTEDFOOD-ACCESS DESERT
Sunshine North, VIC
Confidence
0.78 · medium
Collected
2026-04-14 · field walk
By
L. Ortega · West Health
Consent
Anonymised LGA-level
Method
StreetComplete + manual audit
Active layers · 4
Choropleth · grocer access
ABS 2021
Pins · field-collected
L. Ortega · 2026
Disputed boundaries
3 contested · note attached
OSM base map
2026 weekly

Demonstration data, pins, layer titles and field notes shown above are illustrative for the screenshot only. Real beta atlases are not public and never will be without explicit consent from the originating community.

03 · Why this exists

Most maps are opinions.

Three constraints that shaped HyveMaps. Each is a hard rule, not a setting.

Rule 01

Provenance & consent.

Every layer, pin and polygon carries its source, the date it was collected, the consent terms attached, and a confidence score. If the consent doesn’t cover a use case, the data refuses to render in that view.

Rule 02

Boundaries can disagree.

Cadastral, administrative, and traditional boundaries can disagree, overlap, or simply not exist in the official record. HyveMaps lets multiple boundary layers coexist without forcing one to be the “right” one.

Rule 03

Data sovereignty.

Self-host or community-host. Aboriginal land councils in the beta run their own instances on their own infrastructure. Per Capita never sees, copies or backs up their data.

04 · Where we are

Roadmap to v1.0.

Public, honest. We ship what works in beta. We say so when it doesn’t.

Q4 ’25 · done

Atlas authoring tool.

Layer editor, pin tool, boundary import (.geojson, .shp, .csv-with-postcodes). Stable since November.

Q1 ’26 · done

Provenance & consent fields.

Required metadata on every layer. Consent enforcement at render time. Tested with three beta partners.

Q3 ’26 · in flight

Field-collection app.

iOS & Android companion for offline pin capture in the field. In closed beta with West Health and Top End Land Council.

Q4 ’26 · next

Public-share atlases.

Read-only embeddable atlases for community-facing publication. Consent rules carry through to the public view.

Q1 ’27 · v1.0

General availability.

Self-host stable; managed hosting in Australian region. Free for community organisations.