Nexus Observatory Sign inCreate account

Observatory Protocol

Open

Planetary observation, on one open protocol.

Satellites, radars, towers, buoys, seismometers and fibre already measure the Earth, each on its own clock, format and terms. The Observatory Protocol gives every instrument one way to join, attest, keep time and publish what it sees. Open, and stewarded by the Nexus Consortium. Designed, deployed and run by Nexus Observatory.

Build on the protocolRead the specificationThe record
Instruments on the grid
153,402
Observatories in the atlas
69
Technologies mapped
997
Data as of
2026-10-27

Heritage69observatories, each with sources

Milestones345dated in the record

Spectrum997technologies in 16 domains

Protocol12functions, specified in public

IHeritage

From naked eye to planetary grid.

69 observatories, 6 eras, 108 people named in the record. Each generation solved what the last could not: a better instrument, a shared clock, a wire, an orbit, a network. The open problem now is coordination. That is the one we work on.

1945

Jodrell Bank Observatory

Cheshire, England, United Kingdom

Radar tracking of Sputnik’s booster rocket in 1957.

Bernard Lovell

1956

Green Bank Observatory

Green Bank, West Virginia, United States

The first SETI search with a radio telescope.

Frank Drake

1956

Halley Research Station

Brunt Ice Shelf, Antarctica

Discovery of the Antarctic ozone hole.

Joe Farman · Brian Gardiner

1956

Amundsen–Scott South Pole Station

Geographic South Pole, Antarctic Plateau

Continuous occupation of the geographic South Pole since 1956–57.

Paul Siple

1956

Mauna Loa Observatory

North flank of Mauna Loa, Island of Hawaiʻi, United States

The Keeling Curve, the foundational record of rising atmospheric carbon dioxide.

Charles David Keeling

1960

TIROS-1

Low Earth orbit (launched from Cape Canaveral)

First successful weather satellite.

Morris Tepper · Edgar Cortright

IIFrontier

16 domains, moving at once.

125 frontier technologies, each traced to the release, study or framework it comes from: 3GPP non-terrestrial networks, O-RAN, IMT-2030, analysis-ready data, geospatial foundation models. They arrive on the same site at the same time. The site has to absorb all of them.

● Satellite and space systems

HAPS and HIBS stratospheric platforms

Platforms at 20–50 km acting as relays or IMT base stations, filling the gap between towers and satellites.

ITU RR No. 1.66A (HAPS definition) · ITU Resolution 221 (Rev. WRC-23) HIBS

● Ground segment

Optical ground stations

Telescope terminals with adaptive optics for laser downlinks, sited for clear-sky statistics and diversity.

CCSDS 141.0-B (optical physical layer) · IEC 60825-1 (laser safety)

● 5G and 6G radio access networks

Distributed and cell-free MIMO

Many coordinated access points serving users jointly instead of separate cells.

Rec. ITU-R M.2160 (IMT-2030 framework)

● AI-RAN and Open RAN

Real-time control at the DU (dApps)

Research into sub-10 ms control loops running next to the DU on live radio data.

O-RAN next Generation Research Group (nGRG) reports

● Core and transport networks

6G core architecture studies

Release 20 work on the next system architecture, including AI, sensing and NTN as native features.

3GPP TR 22.870 (6G use cases) · Rec. ITU-R M.2160

● Spectrum, timing and PNT

Distributed low-cost SDR sensor networks

Many inexpensive receivers at sites forming a continuous spectrum picture.

Rec. ITU-R SM.1880 · ITU Handbook on Spectrum Monitoring

● Compute and edge

Edge-cloud continuum

Placing each workload at the device, edge or cloud tier by latency, cost, energy and data rules, and moving it when conditions change.

3GPP TS 23.548 (5GC enhancements for edge computing) · ETSI GS MEC 003

● AI systems

Split and collaborative inference

Dividing a model between device, edge and cloud to balance latency, bandwidth and privacy.

3GPP TR 22.874 (AI/ML model transfer in 5GS) · 3GPP TR 23.700-80

● Remote sensing and Earth observation

High-altitude platform stations (HAPS)

Stratospheric aircraft and balloons that loiter over an area for persistent imaging, sensing or relay.

ITU Radio Regulations No. 1.66A (HAPS definition) · ITU-R HAPS spectrum identifications (WRC-19, WRC-23)

IIIProtocol

One protocol for instruments that have never met.

Twelve functions take a node from unboxed to trusted: join, admit, describe, time, observe, qualify, federate, orchestrate, correct, exchange, prove, exit and decommission. Every value carries its metadata, clock, quality and provenance. No vendor, cloud or central service becomes the owner of local truth.Open the specification

01JoinA node proves what it is, receives an identity and a policy, then a signed plan.

02AdmitProviders enter by manifest, rights, security and technical review, for a stated scope.

03DescribeEvery instrument and observation carries what, where, how and by whom.

04TimeOne time base across the grid, with time quality as explicit state.

05ObserveStreams and files move over whatever link the site has, with store and forward.

06QualifyQuality flags, calibration and provenance travel with each value.

07FederateNodes form cells, cells form clusters, and clusters federate across trust domains.

08OrchestrateSoftware, configuration and upgrades roll out by signed plan, with evidence for every change.

09CorrectAn upstream correction marks dependants stale, triggers recompute and publishes a new version.

10ExchangeGoverned products reach people and applications through versioned APIs, events, maps and exports.

11ProvePeers answer unpredictable challenges and emit signed proof receipts for an independent verifier.

12Exit and decommissionEvery material provider has an open export and replacement path, and decommissioning closes the record.

UNENROLLED

DISCOVERED

ATTESTING

IDENTITY_ISSUED

POLICY_BOUND

PLAN_STAGED

LOCAL_READY

DEGRADED

QUARANTINED

REVOKED

Stewarded by the Nexus Consortium

Open specification, open change process, open to any implementer. Nexus Observatory Inc. supports the protocol and builds enterprise systems on it.

Open protocol

IVSpectrum

997 technologies, orbit to edge rack.

16 domains and 127 layers, from spacecraft buses to RedCap modems, PTP grandmasters and GPU edge nodes. Each entry names the standard it is drawn against and what we design, integrate, deploy and operate around it.

  • Satellite and space systems 66 18 frontier
  • Ground segment 63 5 frontier
  • 5G and 6G radio access networks 62 14 frontier
  • AI-RAN and Open RAN 60 8 frontier
  • Core and transport networks 60 6 frontier
  • Spectrum, timing and PNT 59 6 frontier
  • Compute and edge 65 5 frontier
  • AI systems 65 11 frontier
  • Remote sensing and Earth observation 67 12 frontier
  • GIS, maps and GeoAI 65 5 frontier
  • In situ sensors and instruments 61 7 frontier
  • IoT, LPWAN and mesh 54 9 frontier
  • Power, energy and ruggedisation 64 5 frontier
  • Security, identity and trust 61 6 frontier
  • Data, software and interoperability 59 4 frontier
  • Field operations and lifecycle 66 4 frontier

Open the full spectrum

Satellite and

Ground segment

5G and

AI-RAN and

Core and

Spectrum

Compute and

AI systems

Remote sensing

GIS

In situ

IoT

Power

Security

Data

Field operations

997

VEngineering

Drawn to scale, down to the bolt.

Reference designs at true dimensions: lattice towers, edge modules, radars, domes, dishes, floats. Every part is named for what it does. Hover a part; drag to turn.

Drag to turn · hover a part

VIEarth, maps and GeoAI

See the ground the way the grid sees it.

Where a 30 m mast can see, where water will run, when the next pass images the valley. Interactive explainers on real elevation, from hillshade to a GeoAI detector.

Elevation

Terrain mesh and contours, computed from the elevation model.

Hillshade

Slope and aspect under a sun you move.

Line of sight

Drop a mast; compute its viewshed across the terrain.

Satellite pass

The swath an orbit lays down as it crosses.

GeoAI

A detector run on real slopes, labelled as simulated.

Hex grid

Open stations binned into geodesic cells.

Layer stack

Elevation to AI layer, exploded and recombined.

Open data

Every layer carries its source and licence state.

VIIDimensions

An instrument, a system and an institution at once.

An observatory fails if any one of these fails: wrong science, fragile engineering, lost trust. We design all seven together, not one after another.

S

Science

Every value traceable: metadata, calibration, quality flags and provenance travel with it.

69observatories studied

T

Technology

Radios, satellites, sensors, timing, edge compute and AI, each mapped to its standards.

997technologies mapped

E

Engineering

Every node and provider moves through defined states, with evidence at each transition.

11state machines

M

Mathematics

Every calculation ships with its method, formula, source and a worked example run as a test.

Methodswith worked examples

S

Society

Open data and an open protocol, stewarded by the Nexus Consortium. Anyone can build on it.

Openprotocol and atlas

P

Policy

Jurisdiction, spectrum, privacy and procurement rules, read before design, country by country.

Per countryguides and regimes

S

Standards

Composed from open standards, named on every page as design references.

48standards composed

VIIILifecycle

From survey to the fifth upgrade.

Sensors drift, firmware ages, spectrum rules change and the frontier keeps moving. A site is never finished. We carry it through every stage, and bring an upgrade from the frontier only once it is qualified for the field.

01LearnRead the record and the frontier for the site.

02BuildDesign to the terrain, the spectrum and the mission.

03DeployInstall, commission, accept against the plan.

04ClusterForm sites and clusters.

05MonitorEvery node, its state and its evidence.

06ExpandAdd sites, links and sensors without re-architecting.

07MaintainCalibrate, repair, predict the next failure.

08RefurbishRenew the hardware; keep the record.

09UpgradeBring the frontier to the field, qualified.

IXProducts

Nine lines, one architecture.

Grid, software, hardware, sensors, connectivity, edge AI, Earth observation, field services and data: each line has its own site and team, all nine run on one protocol and one grid.

5 areas

Protocol & Grid

Your grid, on the open protocol.Open the Protocol & Grid site
6 areas

Software

One runtime. Every node. Every state.Open the Software site
6 areas

Hardware & power

Built for the site, not the lab.Open the Hardware & power site
5 areas

Sensors & instruments

Measurements that carry their own proof.Open the Sensors & instruments site
7 areas

Connectivity

Private 5G, AI-RAN and orbit, on site.Open the Connectivity site
5 areas

Edge compute & AI

Inference beside the instrument.Open the Edge compute & AI site
4 areas

Earth observation & GeoAI

The ground, measured and modelled.Open the Earth observation & GeoAI site
6 areas

Field services

Survey to decommission, one accountable crew.Open the Field services site
5 areas

Data & licensing

Grid data, licensed for your use.Open the Data & licensing site

XOpen by default

Open by default. Your rights stay yours.

The protocol, the atlas, the grid and the methods are public. Fork them, test them, contribute back. Contributors keep their rights. What is open, and on what terms

  • ProtocolFunctions, states, objects and flows, versioned in public.
  • SDKs and agentsPut an instrument or an application on the grid.
  • Reference designsSites, towers, racks and stations at true dimensions.
  • Atlas and gridEvery observatory and open network, each with sources.
  • MethodsEvery calculation with its formula and a worked example.

enrol.ts

TypeScript

// 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);

XITowards the future

From one site to a planetary grid.

What runs today, what comes next and the frontier the architecture is built to absorb. Everything beyond today is marked planned.

Now

The core runs end to end.

In a reference environment the protocol’s core runs complete: admission, enrolment, signed plans, fleet state, disconnect and replay, correction.

  • Provider admission and qualification runtime
  • Node bootstrap with software attestation
  • Plan-only deployment plan compiler
  • Disconnect, replay and correction

Next · planned

Into the field.

The reference moves onto real sites: hardware attestation, field qualification of providers, the opening sites.

  • Hardware roots of trust on nodes
  • Field qualification of providers
  • Sites and managed operations
  • Open SDKs and the node agent, once licensed

Frontier · planned

Federated, intelligent grids.

The frontier the architecture is designed to absorb, entry by entry, as each is qualified for the field.

  • HAPS and HIBS stratospheric platforms
  • Virtualised and cloud-native modems
  • Software-defined L1 on GPUs
  • Confidential AI on accelerators
  • Imaging spectroscopy constellations
  • Wi-Fi sensing

—Begin

The next observatory starts with one site.

Start on the open protocol and the atlas today. When you are ready to deploy, we design, build and run it with you.

Create accountTalk to usRead the protocol
Observatory ProtocolOpen

Planetary observation, on one open protocol.

Satellites, radars, towers, buoys, seismometers and fibre already measure the Earth, each on its own clock, format and terms. The Observatory Protocol gives every instrument one way to join, attest, keep time and publish what it sees. Open, and stewarded by the Nexus Consortium. Designed, deployed and run by Nexus Observatory.

IHeritage

From naked eye to planetary grid.

IIFrontier

Every domain is moving at once.

IIIProtocol

One protocol for instruments that have never met.

Open the specification

Stewarded by the Nexus Consortium

Open specification, open change process, open to any implementer. Nexus Observatory Inc. supports the protocol and builds enterprise systems on it.

Open protocol
IVSpectrum

Every technology, orbit to edge rack.

    Open the full spectrum
    VEngineering

    Drawn to scale, down to the bolt.

    Reference designs at true dimensions: lattice towers, edge modules, radars, domes, dishes, floats. Every part is named for what it does. Hover a part; drag to turn.

    Drag to turn · hover a part
    VIEarth, maps and GeoAI

    See the ground the way the grid sees it.

    Where a 30 m mast can see, where water will run, when the next pass images the valley. Interactive explainers on real elevation, from hillshade to a GeoAI detector.

    VIIDimensions

    An instrument, a system and an institution at once.

    An observatory fails if any one of these fails: wrong science, fragile engineering, lost trust. We design all seven together, not one after another.

    VIIILifecycle

    From survey to the fifth upgrade.

    Sensors drift, firmware ages, spectrum rules change and the frontier keeps moving. A site is never finished. We carry it through every stage, and bring an upgrade from the frontier only once it is qualified for the field.

    IXProducts

    Nine lines, one architecture.

    Grid, software, hardware, sensors, connectivity, edge AI, Earth observation, field services and data: each line has its own site and team, all nine run on one protocol and one grid.

    XOpen by default

    Open by default. Your rights stay yours.

    The protocol, the atlas, the grid and the methods are public. Fork them, test them, contribute back. Contributors keep their rights. What is open, and on what terms

    • ProtocolFunctions, states, objects and flows, versioned in public.
    • SDKs and agentsPut an instrument or an application on the grid.
    • Reference designsSites, towers, racks and stations at true dimensions.
    • Atlas and gridEvery observatory and open network, each with sources.
    • MethodsEvery calculation with its formula and a worked example.
    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);
    XITowards the future

    From one site to a planetary grid.

    What runs today, what comes next and the frontier the architecture is built to absorb. Everything beyond today is marked planned.

    —Begin

    The next observatory starts with one site.

    Start on the open protocol and the atlas today. When you are ready to deploy, we design, build and run it with you.