GCRI · Foundry
Developers and integrations
Foundry is designed to be integrated through versioned, documented interfaces rather than through private arrangements. This page, published by The Global Centre for Risk and Innovation (GCRI), explains how interfaces, software releases and documentation are managed, and what developers can expect as each is released. Interfaces open to external developers only with authorised projects. Information and enquiries are open today.
Developers and integrations in four parts.
Contracts first, then code.
Published contracts
Interfaces are described as machine-readable contracts, such as OpenAPI, with a version and a change log.
Change without surprise
Breaking changes take a new version. Earlier versions are deprecated with notice, not withdrawn silently.
Same gate for code
Every call is authorised by the policy gates of NXS-NSF (trust, authorisation and assurance), with OpenID Connect and OAuth for identity and delegation.
Standards the systems are designed to support.
| Area | Standards | Systems |
|---|---|---|
| Geospatial | OGC API Features, OGC API Records, STAC, Cloud Optimized GeoTIFF, GeoJSON, GeoPackage | NXS-EOP (earth observation and digital twins), NXS-NST (civilian common operating picture) |
| Warning | Common Alerting Protocol 1.2 | NXS-EWS (multi-hazard monitoring and warning) |
| Provenance and catalogues | W3C PROV, DCAT 3, JSON-LD, SKOS | NXS-GRX (canonical data, provenance and risk), NXS-POR (public, client and partner delivery), NXS-HUB (knowledge, records and learning) |
| Software supply chain | SPDX, CycloneDX, SLSA provenance, in-toto, OCI images | NXS-FAC (blueprints, builds and signing) |
| Observability | OpenTelemetry | NXS-FAC |
How software is built and released.
- 01
Build
The Factory system turns blueprints into tested applications with a software bill of materials and provenance.
- 02
Sign
Releases are signed and attestable. A release is not a deployment authorisation.
- 03
Install
The Apps system checks entitlement and compatibility and installs into a declared tenant environment, with rollback.
- 04
Correct
Defects and security fixes are released as new versions with notes.
Documentation is published as it is released.
Public technical documentation, examples and change logs are published on Foundry as each is reviewed for public release. Restricted documentation stays inside authorised projects. Each document states the version of the interface or release it describes, its date and its owner, and corrections are published as new versions rather than silent edits. Security issues go to the security report form, the security disclosure route.
Questions and answers.
Is there a public API today?
Can I build an application on Foundry?
How do I report a vulnerability?
Are the interfaces open source?
Will old interface versions keep working?
Bring a method, a dataset or a question.
Information and enquiries are open today. 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.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.