Open Infrastructure and Developers
Standards are used through registries, resolvers, APIs, deployments and monitors. This programme covers that infrastructure, the public monitoring tools and test environment, and the developer guidance through which the standards are implemented in code. Each artefact of these areas carries a UNI (Unique Nexus Identifier).
- Registries and the resolver: couples with
identification-standards,sovereign-stack,indexing-and-discovery. - Deployment services: couples with
software-and-supply-chain-standards,identification-standards,monitoring-services. - Monitoring services: couples with
verification-and-monitoring-standards,commons-and-command-rooms,real-time-fabric. - Developers and APIs: couples with
conformance-test-suites,registries-and-resolver,sandbox-and-simulated-data. - Commons and command rooms: couples with
policies-and-clauses-standards,decision-records-and-accountability,monitoring-services. - Indexing and discovery: couples with
registries-and-resolver,documentation-and-publication-standards,translation-and-localisation. - Real-time fabric: couples with
real-time-and-streaming,alerting-and-messaging,monitoring-services. - Sandbox and simulated data: couples with
conformance-test-suites,compatibility-profiles,privacy-and-data-protection. - Sovereign stack: couples with
sovereign-deployment-and-data-residency,deployment-services,sovereign-deployment-pathway. - Sovereign deployment and data residency: couples with
sovereign-stack,registries-and-resolver,privacy-and-data-protection. - For developers: couples with
developer-and-api,sandbox-and-simulated-data,software-and-supply-chain-standards,conformance-program.
The process.
NXS · Process
Record lifecycle
Standard lifecycle · NS-13 track · Contribution channels · IETF track · W3C track · OGC track · OASIS track · ISO and IEC stages · Conformance · Record lifecycle · Routing · Monitoring.
The catalogue allocates a UNI, the writer creates and versions the record, corrections make new versions, and the ledger archives every version.
01 Writer
- 02RecordRecord · the writer, under a scopeA record carries uni, title, scope, category, status and rights.
- 04CorrectionStep · any person, through a change proposalA correction names what was wrong and cites its evidence; the fix is a new version.
- 05VersionStep · the writerA new version leaves the previous one unchanged; both resolve.
02 Registry and ledger
- 01UNI allocatedStart · the catalogue or the record serviceThe reference command-line tool allocates the identifier; the serial has six digits.
- 03ResolvesGate · the resolverThe resolver returns a landing page or a machine-readable record; for a restricted record it returns the reason for restriction.
- 06Later record or withdrawalDecision · a later record or a withdrawal decisionThe later record refers back; the earlier record shows its status and refers forward.
- 07ArchivedOutcome · the ledgerThe ledger retains every version and every status change.
NS-1: the UNI and the artefact catalogue · NS-3: records · NS-7: resolver landing pagesAn outline of how the work is designed to run; it does not report the status of any decision or record.
The operations, as a table
| Step | Phase | Operation | Who | Decision rule | Record |
|---|---|---|---|---|---|
| 01 | Registry and ledger | UNI allocated (start). The reference command-line tool allocates the identifier; the serial has six digits. | the catalogue or the record service | serials are allocated by the tool and are not reused (NS1-R2, NS1-R3) | an allocated serial |
| 02 | Writer | Record (record). A record carries uni, title, scope, category, status and rights. | the writer, under a scope | required fields, rights and status are set at creation | the record with its required fields |
| 03 | Writer | Version (step). A new version leaves the previous one unchanged; both resolve. | the writer | semantic versioning for schemas and the registry; dated editions for documents | a new version, the previous kept |
| 04 | Registry and ledger | Resolves (gate). The resolver returns a landing page or a machine-readable record; for a restricted record it returns the reason for restriction. | the resolver | published, non-restricted records resolve (NS-7) | HTML or JSON for the UNI |
| 05 | Writer | Correction (step). A correction names what was wrong and cites its evidence; the fix is a new version. | any person, through a change proposal | corrections are submitted as change proposals (NS-13) and produce a new version with its history | a change proposal, then a new version |
| 06 | Registry and ledger | Later record or withdrawal (decision). The later record refers back; the earlier record shows its status and refers forward. | a later record or a withdrawal decision | the status displayed is the status recorded | supersededBy set; status updated |
| 07 | Registry and ledger | Archived (end). The ledger retains every version and every status change. | the ledger | retained permanently; history is append-only | the record, kept |
Table.A record from allocation to archive, with its status at each step; identifiers are never deleted or reused. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: NS-1: the UNI and the artefact catalogue · NS-3: records · NS-7: resolver landing pages.
Summary
- Programme
nexustandards.com/open-infrastructure/ - StatusIn preparation.
- Areas11 · 5 catalogued
- Nexus StandardsNS-1, NS-7, NS-3, NS-6, NS-9, NS-12, NS-11, NS-10, NS-8, NS-3b, NS-2, NS-14, NS-0
- Open standards41
- Data sources27
- Couplings32 with 6 programmes
Area profiles are proposed.
- Areas
- 11
- 5 catalogued, 6 proposed
- Nexus Standards
- 13
- applied across the areas
- Open standards
- 41
- named and linked, never reproduced
- Data sources
- 27
- listed for reference
- UNI
- requested · allocation in progress
- Status
- Proposedin preparation
- Last reviewed
- area profile
Nexus Standards (2026). Open Infrastructure and Developers: a programme of the Nexus Standards. Proposed. https://nexustandards.com/open-infrastructure/. Last reviewed 17 October 2026.
Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.
The programme at work
Its development and participation, the areas it holds, the standards that apply and the channels to related areas.
Monitoring console
Version and source status for each standard; the sandbox presents the console with worked examples.
NXS · Process
Monitoring loop
A licence-reviewed source is retrieved with digests, each item becomes a change record checked for drift, and editors record a disposition through a change proposal.
01 Data source register
- 01Source listedDecision · the Secretariat, after licence reviewData sources are listed for reference; live data is displayed once licence review is complete.
02 Data service
- 02Change recordRecord · the data serviceEach feed item becomes a change record appended to the transparency log with an inclusion proof.
- 03Drift checkGate · the data serviceDrift is a comparison of two version strings; the register entry is corrected through a change proposal.
- 07Feed retrievedStep · the governed data serviceThe data service reads the feed named in the register entry and stores each response with its digest and retrieval time.
03 Pages
- 04NoticeStep · the page buildThe package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such.
04 Nexus Standards editors
- 05DispositionDecision · Nexus Standards editorsThe editors determine what the change means for the register entry and the crosswalk; the page shows the disposition.
- 06Next retrievalOutcome · the data service, on scheduleThe loop continues on the schedule recorded in the register entry.
Feed update register (admitted feeds only) · Licensing rules · Registries and resolverAn outline of how the work is designed to run; it does not report the status of any decision or record.
The operations, as a table
| Step | Phase | Operation | Who | Decision rule | Record |
|---|---|---|---|---|---|
| 01 | Data source register | Source listed (decision). Data sources are listed for reference; live data is displayed once licence review is complete. | the Secretariat, after licence review | the entry records the licence terms and the permitted delivery | an entry in the data source register |
| 02 | Data service | Feed retrieved (step). The data service reads the feed named in the register entry and stores each response with its digest and retrieval time. | the governed data service | retrieved on the source’s schedule; each response is stored unchanged | the response with digest and retrieval date |
| 03 | Data service | Change record (record). Each feed item becomes a change record appended to the transparency log with an inclusion proof. | the data service | kind: release, errata, comment period, deprecation or supersession; version, date, URL, digest | a change record with a UNI |
| 04 | Data service | Drift check (gate). Drift is a comparison of two version strings; the register entry is corrected through a change proposal. | the data service | registered version compared with the latest release; deprecation and supersession flagged | a drift flag against the registered version |
| 05 | Pages | Notice (step). The package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such. | the page build | the age of the information is stated | a notice with date and source |
| 06 | Nexus Standards editors | Disposition (decision). The editors determine what the change means for the register entry and the crosswalk; the page shows the disposition. | Nexus Standards editors | each disposition is a change proposal under NS-13, with written reasons | a change proposal with the disposition |
| 07 | Nexus Standards editors | Next retrieval (end). The loop continues on the schedule recorded in the register entry. | the data service, on schedule | the source’s schedule, subject to the body’s terms | the next response |
Table.From a data source to a change record, a version check, a notice and a disposition. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: Feed update register (admitted feeds only) · Licensing rules · Registries and resolver.
- Live0
- Listed for reference38
- Stale snapshot0
- Version drift0
- Closing in 30 days0
Data sources are listed for reference; live data is displayed once licence review is complete.
| Standard | Body | Registry version | Latest from the body | Feed state | Last change | Age |
|---|---|---|---|---|---|---|
| OASIS Common Alerting Protocol Version 1.2 | OASIS Emergency Management TC | 1.2 (OASIS Standard 1 July 2010;… | not yet available | listed for reference | none recorded | no live data |
| OASIS STIX Version 2.1 (Structured Threat Information… | OASIS Cyber Threat Intelligence TC | 2.1 (OASIS Standard, 10 June 2021) | not yet available | listed for reference | none recorded | no live data |
| OASIS TAXII Version 2.1 (Trusted Automated Exchange of… | OASIS Cyber Threat Intelligence TC | 2.1 (OASIS Standard, 10 June 2021) | not yet available | listed for reference | none recorded | no live data |
| OASIS Common Security Advisory Framework (CSAF) Version 2.0 | OASIS CSAF TC | 2.0 (OASIS Standard, November 2022) | not yet available | listed for reference | none recorded | no live data |
| OASIS Emergency Data Exchange Language (EDXL) Distribution… | OASIS Emergency Management TC | 2.0 (Committee Specification 02, 19… | not yet available | listed for reference | none recorded | no live data |
| OASIS EDXL Situation Reporting (EDXL-SitRep) Version 1.0 | OASIS Emergency Management TC | 1.0 (Committee Specification 01, 11… | not yet available | listed for reference | none recorded | no live data |
| SpatioTemporal Asset Catalog (STAC) specification | STAC community; OGC Community… | 1.1.0 (OGC Community Standard); core… | not yet available | listed for reference | none recorded | no live data |
| OGC API – Features – Part 1: Core | Open Geospatial Consortium | 1.0.1 (17-069r4 corrigendum); Parts 2… | not yet available | listed for reference | none recorded | no live data |
| OGC API – Records – Part 1: Core | Open Geospatial Consortium | 1.0 (20-004r1, International Standard) | not yet available | listed for reference | none recorded | no live data |
| OGC GeoPackage Encoding Standard | Open Geospatial Consortium | 1.4.0 (12-128r19, 6 February 2024) | not yet available | listed for reference | none recorded | no live data |
| OGC SensorThings API Part 1: Sensing | Open Geospatial Consortium | 1.1 (18-088); Part 2 Tasking Core 1.0;… | not yet available | listed for reference | none recorded | no live data |
| OGC Technical Committee Policies and Procedures | Open Geospatial Consortium | 05-020r29 | not yet available | listed for reference | none recorded | no live data |
| W3C PROV-O: The PROV Ontology | W3C Provenance Working Group | W3C Recommendation 30 April 2013 | not yet available | listed for reference | none recorded | no live data |
| W3C Verifiable Credentials Data Model v2.0 | W3C Verifiable Credentials Working… | W3C Recommendation 15 May 2025 | not yet available | listed for reference | none recorded | no live data |
| W3C Decentralized Identifiers (DIDs) v1.0 | W3C DID Working Group | W3C Recommendation 19 July 2022 | not yet available | listed for reference | none recorded | no live data |
| W3C Data Catalog Vocabulary (DCAT) – Version 3 | W3C Dataset Exchange Working Group | W3C Recommendation 22 August 2024 | not yet available | listed for reference | none recorded | no live data |
| Schema.org vocabulary | Schema.org Community Group (W3C) | 29.4 (8 December 2025); 30.0 of 25… | not yet available | listed for reference | none recorded | no live data |
| W3C Process Document (2025) | World Wide Web Consortium | effective 18 August 2025; Proposed… | not yet available | listed for reference | none recorded | no live data |
| RFC 7946 The GeoJSON Format | IETF | Proposed Standard (August 2016) | not yet available | listed for reference | none recorded | no live data |
| OAuth 2.0 (RFC 6749) and OpenID Connect Core 1.0 | IETF and OpenID Foundation | RFC 6749 (2012); OpenID Connect Core 1.0 | not yet available | listed for reference | none recorded | no live data |
| RFC 2026 The Internet Standards Process – Revision 3 (BCP 9) | IETF | RFC 2026 (1996) with BCP 9 amendments;… | not yet available | listed for reference | none recorded | no live data |
| RFC 5378 Rights Contributors Provide to the IETF Trust… | IETF Trust | BCP 78; Revised BSD License for code… | not yet available | listed for reference | none recorded | no live data |
| RFC 6852 Affirmation of the Modern Paradigm for Standards… | IAB, IEEE-SA, IETF, Internet… | Informational RFC (January 2013);… | not yet available | listed for reference | none recorded | no live data |
| DataCite Metadata Schema 4.5 | DataCite Metadata Working Group | 4.5 (22 January 2024) | not yet available | listed for reference | none recorded | no live data |
| Digital Object Identifier system – ISO 26324 | ISO/TC 46/SC 9; International DOI… | ISO 26324:2022 withdrawn March 2025… | not yet available | listed for reference | none recorded | no live data |
| Research Organization Registry (ROR) | ROR (California Digital Library,… | schema v2 (v1 retired December 2025… | not yet available | listed for reference | none recorded | no live data |
| SPDX (System Package Data Exchange) specification; ISO/IEC… | SPDX project (Linux Foundation);… | 3.0.1 (December 2024); ISO/IEC… | not yet available | listed for reference | none recorded | no live data |
| SPDX License List | SPDX Legal Team (Linux Foundation) | 3.27.0 (1 July 2025) per packaging… | not yet available | listed for reference | none recorded | no live data |
| CycloneDX Bill of Materials specification (ECMA-424) | OWASP CycloneDX; Ecma… | 1.6 (9 April 2024; ECMA-424 ratified… | not yet available | listed for reference | none recorded | no live data |
| Supply-chain Levels for Software Artifacts (SLSA) | OpenSSF (Linux Foundation) | 1.1 (April 2025, Approved… | not yet available | listed for reference | none recorded | no live data |
| in-toto Attestation Framework | in-toto project (CNCF) | 1.0 (stable per in-toto.io) | not yet available | listed for reference | none recorded | no live data |
| OpenSSF Scorecard | OpenSSF | automated checks scored 0–10 | not yet available | listed for reference | none recorded | no live data |
| OpenSSF Best Practices Badge | OpenSSF | passing, silver, gold tiers | not yet available | listed for reference | none recorded | no live data |
| CodeMeta software metadata vocabulary | CodeMeta project | 3.0 (2023); context lists 3.1 and the… | not yet available | listed for reference | none recorded | no live data |
| Citation File Format (CITATION.cff) | Citation File Format project | 1.2.0 | not yet available | listed for reference | none recorded | no live data |
| JSON Schema 2020-12 | JSON Schema organisation | 2020-12 (current per json-schema.org) | not yet available | listed for reference | none recorded | no live data |
| OpenAPI Specification | OpenAPI Initiative (Linux… | 3.1.1 (24 October 2024); 3.1.2 and… | not yet available | listed for reference | none recorded | no live data |
| WMO Register of Alerting Authorities and CAP alert… | WMO | operational register; alert hub… | not yet available | listed for reference | none recorded | no live data |
A worked example shows how the console reads once live data is available. Monitoring console: worked example.
Registries and the resolver
The record lifecycle and the monitoring process.
SandboxMonitoring console sandbox
Worked examples of how the console presents version changes and comment periods.
AreaFor developers
The UNI grammar, the record schema, the command-line tool, exports and the WordPress integration.
Transmission channels to related areas and programmes
The systemic couplings recorded for this context, grouped by transmission mechanism. The bar summarises each mechanism (select one to filter); each entry names the connected area or programme and describes the mechanism.
The interactive view requires JavaScript; the sections below present the same records.
How a shock travels through this system
A system model of this programme built from the registry: 25 systems, 10 sectors, 19 controls, 26 feeds, 19 indicators. Select the components to include, choose an initiating hazard and run the scenario. Stress propagates through the hazard relations of the Nexus Hazard Standard (NHS-1), the exposure of each system, the recorded couplings and the sectors that carry the loss; adopted standards dampen transmission and live data sources support detection. All parameters are stated assumptions that the reader can adjust; results are illustrative scenario outputs for exercises and training, not forecasts or risk assessments.
Systems and couplings
- Registries and the resolver
- Deployment services
- Monitoring services
- Developers and APIs
- Commons and command rooms
- Indexing and discovery
- Real-time fabric
- Sandbox and simulated data
- Sovereign stack
- Sovereign deployment and data residency
- For developers
- Identification (the UNI) Coupling
- Software and supply chain Coupling
- Verification and monitoring Coupling
- Conformance test suites Coupling
- Policies and clauses Coupling
- Decision records and accountability Coupling
- Documentation and publication Coupling
- Translation and localisation Coupling
- Real-time and streaming data Coupling
- Alerting and messaging Coupling
- Compatibility profiles for closed standards Coupling
- Privacy and data protection Coupling
- Sovereign deployment pathway Coupling
- Conformance programme Coupling
Controls
NS-1The UNI and the artefact catalogue (grammar v0.2: domain, sector, region and environment segments)NS-7Resolver landing pages, page meta tags, sitemapNS-3Risk record UNIs (grammar, legacy crosswalk, allocation authority)NS-6Surface wiring (API header, panel provenance, passports, OpenAPI)NS-9Contextual UNIs (deployments, instances, programme instances)NS-12Software, model and AI/ML artefacts (supply chain, model cards, dataset sheets)NS-11Verification and monitoring (evidence, attestations, zero-trust conformance observation)NS-10Policies and clauses (machine-readable obligations: definition, binding, evaluation and enforcement)NS-8Zenodo publishing workflow with legal gate, DOI write-back, Software Heritage archivalNS-3bDataset and product metadata profile (STAC, DCAT, PROV-O)NS-2Citation and attribution format for UNIsNS-14Conformance and crosswalk to external standardsNS-0Constitution and principlesNRS-H94Hazard family: Systemic cyber events (NHS-1 cyber.systemic-cyber)NRS-H62Hazard family: Compound and multi-hazard events (NHS-1 sys.compound)NRS-A1Standards as code: machine-readable standards, requirements and testsNRS-A6One-click deployment and adoption kitsNRS-H120Hazard family: Structural fragility of interconnected systems (NHS-1 sys.fragility)NRS-H61Hazard family: Cascading failure (NHS-1 sys.cascade)
Observation
- DataCite REST API (DOIs) (listed for reference)
- ROR REST API v2 (listed for reference)
- Software Heritage archive API (listed for reference)
- endoflife.date API (listed for reference)
- OSV.dev vulnerability API (listed for reference)
- deps.dev API (listed for reference)
- CISA Known Exploited Vulnerabilities catalogue (listed for reference)
- NVD CVE API 2.0 (listed for reference)
- APIs.guru OpenAPI directory (listed for reference)
- GitHub REST API (releases) (listed for reference)
- WMO Register of Alerting Authorities CAP feeds (listed for reference)
- INFORM Risk index data (listed for reference)
- OpenAlex API (listed for reference)
- OpenAIRE Graph API (listed for reference)
- Crossref REST API (works) (listed for reference)
- Wikidata Query Service (listed for reference)
- WIS2 Global Discovery Catalogue (OGC API – Records) (listed for reference)
- USGS earthquake GeoJSON summary feeds (listed for reference)
- NOAA NWS alerts API (listed for reference)
- Natural Earth vector data (listed for reference)
- UN M49 standard country or area codes (listed for reference)
- geoBoundaries gbOpen (listed for reference)
- Artifact Hub API (listed for reference)
- UNCTAD Data Protection and Privacy Legislation Worldwide (listed for reference)
- ITU DataHub (listed for reference)
- World Development Indicators (listed for reference)
- Metadata can be accessed manually through a resolvable identifier
- Metadata is guaranteed to remain available after data is no longer available
- Hardened build platform with non-forgeable provenance
- Project pins dependencies by hash (learning signal)
- Continuous monitoring category of the Detect function
- Countries that have multi-hazard early warning systems (monitoring and forecasting component)
- Project is actively maintained (learning signal)
- Metadata is accessed through standardised protocol
- Countries that have accessible, understandable, usable and relevant disaster risk information and assessment
- Proportion of population satisfied with their last experience of public services
- Metadata is offered in such a way that it can be harvested and indexed
- Metadata includes the identifier for the data
- People per 100,000 covered by early warning information through local governments or national dissemination mechanisms
- Proportion of population covered by a mobile network, by technology
- Plurality of accurate and relevant attributes are provided to allow reuse
- Statistical capacity indicators (training context)
- Fixed Internet broadband subscriptions per 100 inhabitants
- Hosted build platform with signed provenance
- Proportion of individuals using the Internet
Couplings, indicators and sources
The couplings with other programmes, the indicators, the references and the data sources the programme draws on.
Couplings with other programmes
32 couplings link the areas of this programme with 6 other programmes, counted in both directions from the area profiles.
| Coupled programme | Couplings | Example mechanism |
|---|---|---|
| Data and Evidence | 11 | Every UNI minted under NS-1 and NS-3 must resolve at /uni/{uni} with content negotiation; an identifier that does not resolve is treated as unallocated by the resolver.Identification (the UNI) to Registries and the resolver |
| Trust, Verification and Assurance | 11 | Deployment declines an image or package whose signature, SBOM or provenance predicate fails verification, so that supply-chain evidence is enforced at the point of deployment.Software and supply chain to Deployment services |
| Communities, Learning and Contribution | 4 | Full-text search uses per-language configurations so translated editions are discoverable in their language.Indexing and discovery to Translation and localisation |
| Readiness and Adoption | 3 | The sovereign deployment pathway in the Readiness and Adoption programme uses this package as its reference deployment.Sovereign stack to Sovereign deployment pathway |
| Early Warning and Anticipatory Action | 2 | WIS 2.0 topic hierarchy and MQTT publish-subscribe are the model followed by the real-time messaging infrastructure of the Open Infrastructure and Developers programme.WMO and hydrometeorological services to Real-time fabric |
| Foundations and Governance | 1 | Protected profiles for closed standards are exercised only on simulated data in the sandbox.Sandbox and simulated data to Compatibility profiles for closed standards |
Working groups, participation and learning
How to take part, the proposed working groups, the readiness pathways, learning at Risk Academy, the institutions of the network and common questions.
Participation and governance
- 01
Charter a working group
Select an area above, adopt its proposed charter and submit it as a public change record under NS-13; the editors decide with written reasons. Develop a standard.
- 02
Amend an area brief
Propose an amendment to an area profile, citing a peer-reviewed or official source.
- 03
Propose a data source
Propose a source with its provider, licence and delivery path for licence review.
- 04
National participation
Each participating country takes part through its National Nexus Consortium (NNC). The National Standards Council (NSC) decides adoption, adaptation or reference in its jurisdiction, and National Working Groups (NWGs) draft national inputs and run field exercises. Competent national authorities are engaged through official channels.
- 05
Contribute at the issuing body
Contributions to an external standard are made through the issuing body’s own channels; outcomes are reflected here as register changes. Movement and contribution.
Questions and answers
What is the status of Open Infrastructure and Developers?
What is the basis of the area briefs?
How are data sources presented?
Contribute evidence from this page.
Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- EmailGateway GW-STDSend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsNexus StandardsSee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Every figure on this page is indexed: hazards, climate, conflict, the world.
The Index is the Consortium’s indexing system for risk data. Every indicator, hazard, series and country profile carries its Nexus Standards identifier, its source and its licence, so what this page shows can be traced, corrected and reused.
- 01 · Sources205 registered sourcesEvery value keeps its source and licence; withheld values are counted.Data and licences
- 02 · Nexus StandardsNIS-1 and NHS-1451 indicators, 905 hazards; every record carries a UNI.Nexus Standards
- 03 · The Index54 series, 195 country profilesComputed on the standards; no value is published until an edition is released.The Global Risks Index
- 04 · This pageOpen Infrastructure and DevelopersMaps, figures and feeds read the Index in the context of hazards, climate, conflict.Public API
global, sector, strategic, technology, thematicSeries in this context hazards, climate, conflict
- GLBGlobal SystemsThe state of interdependent global risk: the twenty domain indices aggregated to the world, the five core systems (water, energy, food, health, biodiversity) and their couplings, the global tail register and the gap…NXS-GRX-AR-000002Hazards · Climate · Conflict
- THDisaster Risk Intelligence (DRI)Signals, observations, event streams, geospatial layers and scenario packs turned into structured risk intelligence for preparedness and planning.NXS-GRX-AR-000111Hazards · Climate · Conflict
- GSGlobal CitiesUrban exposure, heat, flooding, informal settlement, service dependency and the economic weight of cities at risk.NXS-GRX-AR-000068Hazards · Infrastructure · Climate
- GSGlobal ClimateChronic and acute physical climate hazard, transition exposure, adaptation gaps and scenario pathways to 2030, 2050 and 2100.NXS-GRX-AR-000065Climate · Hazards · Finance
Country profiles the world
Every country profile carries the source and licence of each value. Correct a value or reply.
Hazard domains NHS-1
- Atmosphere and weatherNXS-GRX-AR-000135
- Solid EarthNXS-GRX-AR-000138
- Systemic and compound eventsNXS-GRX-AR-000148
Geodata and API open
Open layers on an equal-area hexagon grid, shown as densities per km² or as symbols: People · GHSL 2025People · WorldPop 2025Built-up areaPortsAirportsRoadsRailwaysRivers and lake centrelines.
/api/v1/public/grix · https://nexustandards.com/uni/{uni}
Developers · Data · Made with Natural Earth, Public domain; GHSL and WorldPop, CC BY 4.0.
Snapshot of the Index registries pinned 2026-10-23 · 22c6eed. Research and risk-analytics information: not a rating, an official classification, a warning, a benchmark or advice.
Contribute to Open Infrastructure and Developers
Institutions and experts are invited to charter a working group, amend an area brief or propose a data source. National participation is organised through each country’s National Nexus Consortium (NNC) and its National Working Groups (NWGs); competent national authorities are engaged through official channels.
Status and use. The Nexus Standards are proposed standards developed through an open process under NS-13 and published for voluntary use; they do not constitute certification, accreditation or regulatory approval, and adoption remains a decision of the Global Standards Council and, in each country, of its National Standards Council. A UNI (Unique Nexus Identifier) identifies an artefact; it does not certify it. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.
Licences: CC BY 4.0 for standards text, registries, schemas and data; Apache-2.0 for reference code. External standards are cited by name, number and link under their own licences. Third-party data, libraries and fonts keep their own licences: see Third-party notices.