> For the complete documentation index, see [llms.txt](https://docs.therisk.global/organization/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.therisk.global/organization/use-by/technology-and-service-providers.md). # Technology and service providers How technology teams, infrastructure contributors and service providers can work with the Nexus programme: testbeds and mission calls, qualified contributions of computing and networks, and open stand **Where this fits.** Audience: SMEs, startups and technology teams; computing centres, research and education networks, telecoms and equipment contributors; standards bodies and professional societies; service providers. Pillars: Labs and Foundry (testbeds and builds), Universe (missions and the annual Nexus Network), Standards (interoperability profiles). Offerings: O04, O09, with O03, O08 and O10. Kind: audience guide. ## In brief The programme needs technology that solves real problems under real conditions, and capacity that can be brought together for a year's missions and released after. Providers can respond to testbed and mission calls, offer qualified computing, network or technical capacity, and work on interoperability profiles in the open standards process. Every external party works with the Nexus Consortium at arm's length under a written agreement, and this documentation describes providers by role only. Evaluation never depends on a high contribution, testing is not certification, and offered capacity is never counted as reserved, consumed or funded. ## What the programme looks for | Need of the programme | Framework it follows | What a provider brings | | ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | | Technology that works under representative conditions | Testbed protocols with comparator, metrics, limitations and a reproducible build | A candidate technology and a team for a defined test envelope | | Interoperable, safeguarded digital infrastructure | Universal DPI Safeguards Framework ([UN Tech Envoy and UNDP, 2024](https://www.dpi-safeguards.org/)); GovStack building blocks ([GovStack, 2020–](https://www.govstack.global/)) | Components that exchange data through open interfaces and respect rights and exit | | Temporary technical intensity for the year's missions | The annual [NXS-NET](/organization/systems/nxs-net.md) Network: qualified computing, networks and technical teams brought together each year | Qualified capacity, offered for a mission and released after | | Open, citable records | Open standards, licensed CC BY 4.0 (text) and Apache-2.0 (code) | Implementations and change proposals | ## What the programme offers | Route | What happens | Where in the programme | | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | | Testbed | Use case, comparator, data, metrics, limitations, reproducible build and test envelope defined; interoperability, failure behaviour, rights, security, resource cost and human use tested; a measured evaluation with failure cases | O04 | | Mission call | A documented selection decision, evaluation plan and controlled results | O09 | | Capacity contribution | A resource-offer disposition, a qualification record and separately approved allocations; seven states of contributed capacity, from offered to qualified, reserved, allocated, accessible, measured and accepted | O03, O09 | | Interoperability profile | A scoped profile, an interoperability protocol and reusable artefacts where licensed | O04, O10; [Nexus Standards](/organization/institutions/nexus-standards.md) | | Teaching a method | Courses hosted on [Risk Academy](/organization/programme/academy.md) | O08 | The [Nexus systems](/organization/systems.md), the twenty systems known by their NXS codes, are proprietary infrastructure, not open and not free. No standard depends on them. An external provider at arm's length supports them under written agreements and holds no vote in the governance of the standards. ## Routes that apply The Nexus Consortium model sets a route for each kind of participant: the action that opens it, the first outcome, the offerings that apply, and a boundary, quoted here as published ([How Nexus Consortium works](https://therisk.global/consortium/)). | Participant | Action | First outcome | Offerings | Boundary | | -------------------------------------------------------------------- | ------------------------------------------------- | --------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | | SMEs, startups and technology teams | Respond to a testbed or mission call | A documented selection decision, evaluation plan and controlled results. | O04 Responsible Innovation and Interoperability Testbeds; O09 Annual Universe Missions and Contributed Infrastructure | "Evaluation never depends on a high contribution, and testing is not certification." | | HPC centres, NRENs, telecoms, cloud and equipment contributors | Offer qualified resources or technical capacity | A resource-offer disposition, qualification record and separately approved allocations. | O03 Data, Compute and AI Capability; O09 Annual Universe Missions and Contributed Infrastructure | "Offered capacity is never counted as reserved, consumed or funded." | | Standards bodies, metrology organisations and professional societies | Propose methods or interoperability collaboration | A scoped profile, interoperability protocol and reusable artifacts where licensed. | O04 Responsible Innovation and Interoperability Testbeds; O08 Leadership, Academy and Workforce Formation; O10 Research, Publications and Evidence Services | "Test completion is never presented as accredited certification." | | Enterprises, manufacturers and industry associations | Explore a sector programme | A work scope, permitted data exchange, evaluation terms and an operational output. | O02 Sector and Critical-Infrastructure Resilience; O04 Responsible Innovation and Interoperability Testbeds; O06 Cross-Border and Shared-System Missions | "Precompetitive work never shares competitors' confidential information." | ## Entry route * [Systems](/organization/systems.md) in this documentation, and [Network and Core](https://therisk.global/ecosystem/network-and-core/) on the GCRI site * [Develop a standard](https://nexustandards.com/develop-a-standard/) and [Adopt and implement](https://nexustandards.com/adopt-and-implement/) on the standards site * [Nexus Universe at GRF](https://globalriskforum.com/nexus-universe/) for mission calls ## What the programme does not do Evaluation never depends on a high contribution, and testing is not certification. Testbed participation is not a regulatory sandbox, a certification or a procurement status. Neither membership nor sponsorship guarantees a computing allocation, and offered capacity is never counted as reserved, consumed or funded. Sponsorship never influences a result. Providers hold no institutional control, no vote, chair or Secretariat role in the standards, and no decision over personal data or national programmes beyond written instructions. Test completion is never presented as accredited certification. ## Status today The programme is in formation, at service level R0: information and enquiries. Calls, applications and allocations open only when their service team, terms and review capacity are in place ([Programme status](https://therisk.global/consortium/programme-status/)). ## Sources * GovStack Initiative (2020–). *GovStack building-block specifications*. [govstack.global](https://www.govstack.global/). * UN Office of the Secretary-General's Envoy on Technology and UNDP (2024). *Universal DPI Safeguards Framework*. New York: United Nations. * Nexus Standards (2026). *Adopt and implement*; *Standards IP and participation policy*. nexustandards.com, read 2026-10-21. * GCRI (2026). *How Nexus Consortium works*: the Nexus Consortium model, stakeholder routes and programme offerings. [therisk.global/consortium/](https://therisk.global/consortium/), read 2026-10-21. * The [Sources library](/organization/reference/sources.md) holds the full entries. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.therisk.global/organization/use-by/technology-and-service-providers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.