Sign inCreate account
Open by defaultOpen

Open means you can check it.

An observing grid is as trustworthy as what anyone can inspect. The specification, the reference designs, the atlas, the methods and every dataset we may redistribute are public: read them, test them, build on them. Open science, open source, open data. Contributors keep their rights.

01Principle

No licence, not open.

Nothing is labelled open until its licence is recorded. Undecided licences show in red. Data whose terms bar commercial reuse or impose share-alike stays off the shared grid, and is listed here instead.

01

Licence first

Every item names its licence. A missing licence shows as a placeholder that blocks publication.

02

Sources always

Every record in the atlas and every network on the grid carries its source and its terms.

03

Reproducible

Every calculation publishes its formula, its inputs and a worked example you can check by hand.

04

Your rights stay yours

Contributions come in under an inbound licence. No copyright assignment; your commercial rights remain.

02What is open

The stack, item by item, with its terms.

From the specification to reference hardware: where each item is published and under which licence. Red tokens are decisions still with legal. They are shown, not hidden.

Programme items (docs/18 §7.1). Status as of 2026-10-27.
ItemWhat it isVenueLicence
03Open data

Public networks, on their own terms.

The home-page grid is built from openly published station lists. A network appears on it only when its terms permit commercial reuse with no non-commercial or share-alike condition. Everything else is listed here, with the reason it was left out.

NetworkDomainTermsCommercial reusePositions
04Open science

Every number here checks by hand.

Methods publish their formula, units, assumptions and a hand-derived golden case. Data is described to FAIR and governed to CARE. Qualification states carry their evidence, and can go down as well as up.

REPRODUCIBILITY

Methods with worked examples

Line of sight, coverage, link budget, power autonomy, siting cost: each method states its formula, units and assumptions, and carries a hand-derived golden case that the code is tested against.

Studio methods · [PLACEHOLDER] licence
EVIDENCE

Evidence bundles

A device, site or software release reaches a qualification state only with its evidence attached: the manifest, the test plan, the results and who reviewed them. States can go down as well as up.

Manifests · test plans · results
TRANSPARENCY

Corrections in public

When a record is wrong, the correction is published with what changed, why and when. Superseded values stay readable so anyone can follow the history.

Change log · [PLACEHOLDER] transparency report

FAIR

How the data is described
  • FFindable: every dataset has a stable identifier and a metadata card.
  • AAccessible: retrievable over open protocols, with terms stated before access.
  • IInteroperable: open formats such as COG, Zarr, GeoJSON and PMTiles, described with STAC where it applies.
  • RReusable: licence, provenance and method attached to every release.

CARE

Who the data is for
  • CCollective benefit: observing serves the communities on the ground it measures.
  • AAuthority to control: communities and Indigenous Peoples decide how data about their lands is governed.
  • RResponsibility: we say how data is used and who it reaches.
  • EEthics: the rights and wellbeing of people come before reuse.
05Contribute

Change the protocol in public.

Anyone can propose a change. Proposals are drafted, reviewed and accepted in the open, and land only when their conformance tests pass. The Nexus Consortium stewards the process.

How stewardship works
ProposalA written change with motivation, specification text, compatibility notes and a test plan. English and French summaries.
Inbound licenceContributions come in under a developer certificate of origin or a licence-grant agreement, never a copyright assignment. [PLACEHOLDER] legal decides
RecognitionCredit in the change log and release notes. Opt-in spotlights and hackathons.

Enrol an instrument in a few lines.

The node agent and SDKs carry the protocol for you: enrolment, TPM attestation, WIGOS description, PTP time and the data stream.

enrol.tsTypeScript
// enrol a weather station on the grid
const node = await grid.enrol({
  role: "weather-environment",
  evidence: await tpm.quote(),
  describe: { standard: "WIGOS", sensors },
  time: { source: "ptp", profile: "G.8275.1" },
});
// UNENROLLED → DISCOVERED → ATTESTING → …
node.on("state", (s) => log(s));
await node.observe(stream);
06Open and enterprise

Open here. Enterprise depth on the lines.

Everything on the main site is open. When a programme needs a system designed, qualified, deployed and run at scale, each enterprise line has its own site, on the same protocol and the same open records.

Main site · open layer

For everyone

Hosts, builders, students, researchers, communities, cities and manufacturers reading the specification.

  • Protocol specification, states and flows
  • Atlas of observatories and the observing grid
  • Spectrum of technologies and reference designs
  • Methods, data cards and an account to start building
Line sites · enterprise

For programmes

Networks, agencies and operators who need a system designed, built and kept running.

  • Private and federated grids
  • Hardware, sensors, connectivity and edge AI
  • Earth observation, field services and data products
  • In Canada the seller is Nexus Observatory Inc.; elsewhere, Nexus Ecosystem Inc.
—Begin

Read it, test it, build on it.

Start with the specification, or create an account and run the open tools.

Read the protocolCreate accountStewardship