A national addressing system is more than a code. This white paper examines the implementation framework supplied by Onyx Space / Addressa for postal operators, policymakers, logistics providers, eCommerce businesses and technology partners. Onyx Space describes it as its vision of a full digital addressing implementation at country level — a concept fully open for discussion. It is a condensed editorial treatment of a supplier proposal, not evidence of national adoption, government approval or measured results.
A location reference becomes operationally useful when institutions can register it, maintain it, exchange it appropriately and use it within real service workflows.
1. Executive summary: an addressing system is more than a code
- Public portal / approved institutions
Register, update and request permitted information
- National platform
Addressa engine · registry · verification · GIS · controlled APIs
- Authorised service workflows
Postal, government and approved commercial systems
Foundation: nationally controlled hosting and recovery · governance · privacy · security · support
Conceptual information flow, condensed from the supplied proposal; not a deployed system or a detailed technical design. Public lookup must not disclose personal registration information.
The framework proposes a national digital addressing ecosystem rather than a standalone coding application. According to the source, Addressa supplies a unique 10-character geographic code and corresponding quick response (QR) code: a machine-readable symbol representing a location reference.
National implementation would add a public registration platform, a nationally managed address registry, verification and correction processes, domestic hosting and recovery, controlled institutional application programming interfaces (APIs), administrative and geographic information tools, governance, support and public adoption. APIs are interfaces through which authorised systems exchange information. None of these proposed components should be treated as an already completed national platform.
Onyx Space describes the framework as its vision of a full digital addressing implementation at country level, and states that the concept is fully open for discussion. Its approach is to pilot a project, implement it in phases and enhance or modify it along the way; it is seeking partners for pilot projects to be launched.
2. From a geographic cell to a usable service address
Three records need separate treatment. Geographic location is the underlying map cell and its reference. Service address is a registered delivery or service destination, including the relevant entrance, building, floor or unit. Associated person or organisation is an authorised relationship between that address record and an individual, household or business.
Geographic codes exist independently of registration. Registration associates an authorised record with a location; it does not create the underlying geographic cell. Several households or businesses may legitimately share an entrance or cell. A code alone cannot distinguish every apartment, establish identity, prove occupancy or demonstrate ownership.
The introductory guide explains how postal addresses, satellite positioning and location codes complement one another. A 3 × 3 metre cell is not a guarantee of positioning accuracy, nor is Addressa presented here as an international addressing standard.
3. The seven building blocks
The following structure is condensed from components A–G of the supplied framework. It describes proposed requirements, not a verified catalogue of finished or commercially available functionality.
| Component | Purpose | Key decision |
|---|---|---|
| A — Addressing technology | Code generation, QR representation and location resolution. | What technical documentation and interoperability evidence are available? |
| B — Public registration | Nationally branded, multilingual, mobile-friendly portal for registration, updates and downloadable records. | Can users activate records directly, or is institutional approval required? |
| C — National registry | Links locations to permitted attributes, postal addresses and administrative areas; maintains lifecycle history. | Who owns the authoritative registry and resolves conflicts? |
| D — Domestic infrastructure | Hosting, storage, monitoring, encrypted backups and a separate recovery location. | Which sovereignty requirements cover data, keys, administrators, subcontractors and recovery? |
| E — Institutional APIs | Controlled lookup, validation, registration and integration interfaces. | Who can retrieve which information, for what purpose? |
| F — Administration and GIS | National and regional oversight, geographic information system (GIS) tools, field verification and conflict resolution. | How are responsibilities and access restricted by role and jurisdiction? |
| G — Governance and operations | Privacy, cybersecurity, testing, training, support, maintenance, continuity and service levels. | Who funds, operates and maintains the service over time? |
4. Trust, sovereignty and appropriate transparency
The source calls for national registry control, defined registration and verification rules, correction and deactivation workflows, appeals and dispute processes. Role-based access limits actions to authorised responsibilities; audit trails record administrative changes. Data minimisation, retention and controlled disclosure belong alongside backup, restoration testing and continuity planning.
Domestic hosting is one part of the proposed sovereignty model. Physical location alone does not establish security, national control or legal compliance: control of keys, administrators, subcontractors and recovery arrangements also matters.
A valid code, a registered address, a verified registration and a location suitable for a particular service are different statuses. A downloadable ‘address certificate’ is not proof of title, identity, residency or official status beyond the issuing authority’s defined purpose.
- Public access: non-sensitive geographic lookup.
- Approved operational access: government and postal institutions.
- Controlled commercial access: authorised information for agreed purposes.
5. What this could mean for eCommerce
Potential applications include more precise checkout instructions, consistent destination references across fulfilment and carriers, better identification of entrances and collection points, reuse of agreed locations for returns, and coordination where conventional addressing is incomplete. Benefits are hypotheses to test through integrations and real workflows, not proven outcomes.
A registry records address information and changes. Parcel accountability additionally requires consignment identifiers, time-stamped operational events, responsible parties and appropriate delivery evidence. Neither a location code nor an address registry alone proves receipt. Routing optimisation, proof of delivery, fraud prevention and end-to-end tracking are not automatic consequences of the proposed platform.
6. Three phases of implementation
The source proposes staged implementation without dates, budgets or durations. This reflects Onyx Space’s stated approach: pilot a project, implement it in phases, and enhance or modify it along the way. Governance, privacy, cybersecurity and operational support begin in Phase 1, rather than being deferred until expansion.
- 01
Phase 1 — Establish the core
Addressing engine, registration portal, central registry, domestic hosting and backups, basic administration/GIS, core APIs and initial support.
- 02
Phase 2 — Connect institutions
Postal, government and commercial integrations; regional administration; field verification; legacy-data migration; training and adoption; enhanced monitoring and recovery.
- 03
Phase 3 — Extend services
Additional integrations, analytics, workflow automation, data-quality improvements and optional commercial API plans, according to demand.
7. Who would be responsible?
This is the source’s indicative allocation, subject to procurement, capability assessment and contractual agreement. One Alliance is not proposed as the registry operator or implementation supplier.
| Party | Indicative responsibility |
|---|---|
| Onyx Space | Core technology, licensing and updates; proposed GIS/API contributions; potential implementation or integration role. |
| National authority / postal operator | Registry ownership, policy, authorised access, registration and verification governance, national administration. |
| Implementation partner / local systems integrator | Portal and registry implementation as agreed; integration with agencies and operational systems. |
| Client / domestic ICT provider | Hosting, infrastructure and designated operational responsibilities. ICT means information and communications technology. |
| Shared responsibilities | Training, maintenance, helpdesk, security operations and continuity, explicitly allocated by agreement. |
8. Pilot a community before scaling
The community pilot is a proposed method, not a completed case study. Onyx Space is seeking partners for pilot projects to be launched; organisations interested in participating can contact Onyx Space directly. A useful trial would test registration and physical access together, including difficult premises and people with limited digital access.
- 1. Select a representative area and define eligible people and premises.
- 2. Map buildings, roads and intended entrances; confirm locations in the field where needed.
- 3. Register participating households, businesses and institutions using agreed verification procedures.
- 4. Associate records with existing codes and install approved entrance plaques.
- 5. Test lookup, QR scanning, APIs and postal or courier workflows.
- 6. Evaluate results, document issues and decide whether and how to expand.
9. Measure service value, not just registrations
Source-proposed measures cover household and establishment registrations, associated codes and installed plaques, location accuracy, registration and verification performance, portal/API functionality, user and institutional feedback, and technical or operational issues.
Additional One Alliance editorial recommendations for an eCommerce pilot appear below. These are suggested evaluation criteria, not reported Addressa results.
- Address-related delivery exceptions; driver search time and clarification calls.
- First-attempt delivery and returns collection success.
- Correction turnaround, unresolved disputes and cost per maintained, verified address.
- Availability and successful recovery tests.
10. Questions to resolve before national commitment
These are One Alliance editorial assessment questions, not confirmed deficiencies in Addressa.
- Is there a legally designated registry owner and operating authority?
- How will the system complement postal and municipal records?
- How will shared entrances and multi-unit buildings be handled?
- What evidence supports performance, interoperability and scale?
- What are the licensing, portability, supplier-exit and long-term support arrangements?
- How will updates, disputes and erroneous registrations be resolved?
- What capacity, recovery and service levels are actually required?
- How will participation and operational benefits be measured?
Contributor
Source attribution and evidence limits
The primary source is Onyx Space / Addressa’s ‘National Digital Addressing System — Proposed Implementation Framework Based on Addressa Technology’, supplied as Addressa -Full Implementation.pdf. Its seven components, three phases, indicative responsibilities and community pilot inform this paper.
The source proposes an implementation model; it does not establish completed national deployments or validated operational outcomes. Onyx Space presents the framework as a vision that is fully open for discussion: its stated approach is to pilot a project, implement it in phases, and enhance or modify it along the way. Onyx Space is seeking partners for pilot projects to be launched. No source publication date or version has been assigned. One Alliance’s assessment questions and additional pilot measures are identified separately; Onyx approval of this edited wording is not asserted.
Primary source: Onyx Space / Addressa · supplied implementation framework
https://www.addressa.io/
Sources and further reading
Based on the implementation framework supplied by Onyx Space / Addressa. Condensed and contextualised for the One Alliance Academy. Source: Addressa -Full Implementation.pdf, 19 pages. No publication date or version is established. Source wording has been reviewed against the supplied document; this does not constitute independent technical validation or supplier approval of the edited wording.
Related Insights
Which address-record, access or service-quality questions would your organisation need a pilot to resolve?
Share your experienceThis paper summarises a proposed framework supplied by Onyx Space / Addressa. It is informational and does not constitute One Alliance endorsement, procurement advice or independent validation of the technology.

