Democratising information in humanitarian settings.
Our mission is to put the person in need at the centre of the humanitarian data system — with every piece of information that is useful to them, and control over their own data and how their needs are shared.
Our goal is a world where humanitarian and development responses are tailored to individual needs, locally contextualised, and delivered by the organisations best placed to provide them.
Granite, built from the person in need inward
A person enters through the Mobile App, an organisation through Granite SaaS, a government partner through the Control Room. The Registry underlies all of them without being visible to any of them.
The person's own record — identity, consent and services in their hands
The Mobile App is Granite's interface for the people the entire system exists to serve. Through it a person creates and manages their own digital identity, controls who can access their data, navigates available services, and tracks what they have received and what they are entitled to. Organisations cannot push arbitrary content into it, cannot control its interface, and cannot see data the person has not agreed to share.
- Person-controlled consentSee which organisations can access which parts of your profile; modify or revoke at any time. Changes reach the Registry in real time when connectivity allows.
- Visibility and accountabilityThe full audit log of your data — every organisation that accessed it, every programme, every assessment and referral — is yours to read.
- Active participationInitiate referrals, update your own needs, report on the condition of services, and send feedback that reaches programme staff.
- Offline architectureRegistration, the identity QR code and your locally cached record all work without connectivity, and sync when it returns.
- Designed for deployment realitiesLow-literacy interfaces, multilingual support (Arabic, French, English, Swahili and more), and low-end Android devices as first-principles constraints.
The layer nobody sees that makes every other part trustworthy
Users never interact with the Registry directly. It holds verified identities, enforces data-access rules, and ensures that consent given by any person is technically honoured — not merely promised. It is the neutral identity and consent layer that makes interoperability possible in the first place.
- Consent as a technical gateAn access request outside the scope of active consent is rejected automatically. No manual review, no exception pathway that depends on goodwill.
- Data minimisation by designThe model holds only what is needed to establish identity, verify uniqueness and enforce consent. A request returns only the fields in scope, never the full record.
- Permanent, portable identityEvery person receives a Personal ID that belongs to them and travels with them across organisations, responses and borders.
- Neutral governanceOperated by Connectance as a neutral infrastructure provider. No single organisation controls it, no government holds the master database, no data buyer can reach it.
- Auditability as a rightEvery access is logged immutably — who, what, when, under which consent — and surfaced to the person in their app.
One record per person, across every organisation that serves them
Granite SaaS is the operational portal for humanitarian organisations: manage programmes, access beneficiary data within the consent scope each person has granted, execute referrals, and produce outcome evidence. The data model is anchored to the person, not the organisation — so deduplication is automatic, referral is native, and outcome data is longitudinal from the moment a response begins.
- Consent-scoped accessThe SaaS keeps no copy of beneficiary data. Every profile is fetched from the Registry in real time, scoped to what that person agreed your organisation can see.
- Person-anchored, not organisation-anchoredA person enrolled in three programmes has one record. Deduplication is a structural consequence of the architecture.
- Native cross-organisational referralNo bilateral agreements. One organisation refers, the person consents, the receiving organisation gets only what is relevant to the referral.
- Population targetingAggregate figures by admin level, disaggregated by age, sex, displacement status and key needs — so programmes reach the profiles they are designed for.
- Continuous outcome evidenceIndicators accumulate as activities are logged, computable across organisations and exportable in donor-compatible formats without extra data entry.
Bring the systems you already run — without rebuilding any of them
The Gateway is the controlled entry point between Granite and every external data system — UNHCR PRIMES, WFP SCOPE, national databases, donor platforms, third-party NGO tools. It handles translation, consent verification and routing so that data exchange is possible without each organisation building a custom integration to every Granite component. Crucially, it extends the Registry's consent and audit guarantees to data that did not originate in Granite.
- Single integration surfaceExternal systems connect once. When Granite's internals change, partner integrations do not — the Gateway absorbs the complexity.
- Consent verification on inbound dataData that maps to a known Personal ID is checked against the Registry before processing. Data without a valid consent grant is quarantined for review, never silently dropped.
- Transformation and harmonisationDifferent field names, vocabularies and classification schemes are mapped to Granite's canonical model once, at the Gateway.
- Governed integration agreementsEvery integration has a documented agreement — direction, frequency, consent conditions, retention, audit — and the Gateway enforces it technically.
See the response as it is today — populations, needs, coverage, gaps
The Control Room translates the aggregate operational data flowing through Granite into a live, visual picture of where populations are, what they need, which services are reaching them, and where the gaps are. It never displays an individual record: its unit of analysis is the programme, the area and the population. Privacy is protected by what it is architecturally able to show.
- Aggregated, never individualEvery visualisation is derived from aggregate computation. The value is the population picture.
- Near-real-time currencyProgramme activity, registrations and referrals as they stand today — not as they were at the last reporting cycle.
- Two-layer viewsEach organisation sees its own programmes; coordinators see the cross-response picture without any one organisation's data exposed to another.
- Government intelligence interfaceA curated aggregate feed for government partners under negotiated agreements — population distribution, needs indicators, recovery signals. No individual or organisational detail.
- Coordination briefings as an output3W-equivalent reports, gap analyses and population-movement briefings generated from live data instead of compiled by hand weeks later.
Ask the response a question, in plain language
Connectance+ synthesises Granite's deduplicated, anonymised population data with live external sources — conflict events, displacement indicators, needs assessments, sector feeds — into situation reports, trend analyses, gap assessments and a natural-language interface. It ships inside Granite SaaS as an analyst for programme staff, and inside the Mobile App as a guide for people in need.
- Grounded in Granite's own data assetNeeds profiles, service uptake and outcome trajectories across organisations, alongside external context. Not replicable from any single source.
- Privacy-preserving by architectureNever processes or exposes individual records. Outputs derive from aggregated, anonymised representations with differential-privacy safeguards.
- Natural-language interfaceRetrieval-augmented generation over the intelligence layer's structured data — ask about context, trends and coverage gaps directly.
- Continuous, not episodicUpdated as data flows, computed on rolling windows. An early-warning capability, not a retrospective summary.
What early partners are saying
“The first shared registry that treats consent as a gate, not a checkbox.”
“Every access is visible to the person it belongs to. That is the standard we have wanted for years.”
“Outcome data that is comparable across grantees, without another reporting template.”
“It runs offline on the phones our members actually carry. That is what makes it usable here.”
“Referrals used to take weeks of email. Now it is a consent-gated handoff inside one system.”
“Our first real picture of population-level need in near real time.”
“We stopped re-registering the same families across four programmes.”
“The Gateway meant we kept our own case system and still joined the shared layer.”
Feedback gathered during pilot consultations in Uganda and Kenya. Names and organisations are illustrative pending publication agreements.
Ready to build on shared ground?
Whether you are an organisation, a donor, or someone who believes humanitarian data should serve people first — we want to hear from you.
Get in touch