G09 · PAGE · nexcoreGCRI dossier · service level R0
GCRINexus FoundryEstablished
Nexus Foundry · NEXCORE

NEXCORE

NEXCORE is the compute fabric: where workloads are enrolled, placed and run across infrastructure, with data residency, cost and continuity requirements respected.

Publisher
The Global Centre for Risk and Innovation
Field
Data and compute, Methods and modelling
Canvas · the Nexus cycleDesign, not a record
The Nexus cycle on Nexus FoundryA question from a programme becomes evidence, a governed build, an organized community, a controlled test, a reviewed publication and a decision taken by the competent authority. Design of the cycle, not a record of a run.

Fig.The Nexus cycle, from question to renewal. Design, not a record of a run.

01In brief

The short answer.

NEXCORE Secure Compute and Edge Backbone is the Nexus Foundry system for a compute control plane across cloud, private infrastructure and edge locations. It serves 7 platforms, among them Energy Nexus as well as Climate and Hazards, and its stated limit is that it runs authorized workloads only, under each project's data terms. Access is through an authorized project with an accountable owner, data terms and a review plan.

02Geography

Digital demand and connectivity in Brazil.

Urban demand centres and the hubs that anchor digital and data infrastructure, shown for Brazil as an example geography for this subject.

Urban demand centres and the hubs that anchor digital and data infrastructure.Indicator derived from Natural Earth at map scale; a screening view, not an assessment.
GCRI · Nexus Foundry · fieldDESIGN FIGURE
04The problem it addresses

Analysis that depends on one provider inherits that provider's risk.

Large risk analyses need significant compute, and public institutions need to know where their data and workloads run, under which jurisdiction, and what happens if a provider becomes unavailable. Placement is therefore a policy decision as well as a technical one.

  • Workload placement against residency and sovereignty rules.
  • Continuity across providers and regions.
  • Energy efficiency of compute, reported with ISO/IEC 30134 metrics where available.
05Reference practice

The standards a design like this is read against.

ReferenceRelevance
ISO/IEC 30134 seriesData-centre efficiency indicators
NIST CSF 2.0Security of compute services
FAIR principlesData stewardship across environments
06Neighbouring systems

What it exchanges with the other systems.

  • Runs builds from Factory and agent capabilities from NEXQ.
  • Policy decisions on placement come from NSF.
07Access

Authorized projects only.

Access requires an authorized project with an accountable owner, data terms and a review plan. Enquiries go to contact@therisk.global.

08Key terms

Terms used on this page.

Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.

TermDefinition
Edge computingProcessing data close to where it is produced or used rather than in a central data centre.
Data residencyA requirement that data be stored and processed within a stated jurisdiction.
Zero trustA security model that grants access based on continuous verification, not network location.
09Sources

Where this page's references lead.

The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.

10Questions

Questions and answers.

Is the system available now?
Allocations open when their terms and review capacity exist; the current service level is R0, information and enquiries.
Nexus Foundry

Bring your expertise to this field.

The current service level is R0: information and enquiries. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.

Have questions?