Skip to content
Skip to content

Nexus Observatory

Into the product: a prototype that passed its pilot becoming a production unit. The loop, step by step: 1. A prototype on the bench beside a finished unit. 2. The prototype is measured against the unit. 3. Each reading is stamped with time and place. 4. Results reach the review board. 5. Relays carry the packets without reading them. 6. The edge verifies every signature first. 7. The board checks cost, risk and benefit. 8. Only a confirmed result leaves the edge. 9. The design is frozen and tooled. 10. Sensors check that the response worked. 11. The first production units are crated. 12. The alert arrives with its evidence attached. 13. Record, proof and action are archived together. 14. Everything settles back to idle.

01 / 14

A prototype on the bench beside a finished unit

Nexus Observatory

/

Frontier labs

/

Into the product
From a result to a qualified release.

Into the product, inside Frontier labs: continuous training and deployment to edge fleets, drift and performance monitoring, model provenance and signing, build provenance and more. Every item is traced to its specification, from 3GPP TS 28.105 (AI/ML management) to OpenGitOps principles, and runs on the open Observatory Protocol.

Plan with usArchitectureThe protocol
Technologies
5
At the frontier
0
Protocol functions
3 of 12
Industries served
3

01What it is

MLOps.

AI from model to accountable operation: edge inference and model optimisation, foundation models for Earth observation and geospatial work, time-series and sensor AI, multimodal fusion and supervised agentic operations, federated and privacy-preserving learning, physical AI and robotics within stated red lines, MLOps, evaluation and model risk, and the governance frameworks that apply to each. Compute placed where data is produced and decisions are needed: the device, far, near and regional edge tiers, multi-access edge computing, modular edge data centres including the AI tower in a box, servers and accelerators, storage, power and cooling, ruggedisation, fleet orchestration, OTA and GitOps, and the hardware trust that makes remote sites safe to run. Each technology below carries what it is, what we do with it, and the standard it is drawn against.

AI systems

Continuous training and deployment to edge fleets

Pipelines that retrain, test and roll models out to sites in stages.

We design, integrate and operate.

3GPP TS 28.105 (AI/ML management) · OpenGitOps principles

AI systems

Drift and performance monitoring

Watching input and output distributions and field accuracy, with triggers for review or rollback.

We operate and maintain.

ISO/IEC 5338 · 3GPP TS 28.105

AI systems

Model provenance and signing

Signed, traceable model artefacts and labelled AI-generated content.

We design and operate.

SLSA (OpenSSF) · C2PA Technical Specification

Compute and edge

Build provenance

Verifiable records of how and from what each artefact was built.

We design and operate.

SLSA (OpenSSF) · in-toto

Compute and edge

Staged rollout and rollback

Canary, ring and site-group rollouts with automatic rollback on health signals.

We design and operate.

OpenGitOps principles

02Architecture

Where it sits, and what it speaks.

Into the product draws on the spectrum below; the highlighted layers carry this area, and the protocol functions it speaks are marked.

Edge inference, model serving and optimisation

10

Foundation models for Earth observation and geospatial

9

Time-series and sensor AI

8

Multimodal fusion and agentic operations

7

Federated and privacy-preserving learning

7

Physical AI and robotics (within red lines)

7

MLOps

7

Evaluation, model risk and AI governance

10

O-RAN architecture and open interfaces

7

Fronthaul (7.2x split) and transport

8

RAN intelligent controllers, xApps and rApps

8

SMO, O-Cloud and accelerated L1

8

AI-RAN: shared accelerated infrastructure

7

AI/ML in the air interface and network management

8

Energy saving and efficiency

6

Testing, integration and security

8

01Join Identity, attestation quote, signed policy.

02Admit Admitted for a stated scope, nothing wider.

03Describe What, where, how and by whom, with calibration.

04Time One clock across the grid, with its error bound.

05Observe Every value with quality and provenance.

06Qualify Tested against the specification, state on record.

07Federate Signed exchange across grids and trust domains.

08Orchestrate Software and configuration by signed plan.

09Correct A correction marks what depends on it and publishes a new version.

10Exchange Products reach people and applications through versioned interfaces.

11Prove Signed proof receipts that an independent verifier can check.

12Exit and decommission An open exit path, and a record that closes.

03On the grid

Every site joins one observing grid.

The open networks on the grid today, over real relief and the geodesic cells we count them into, filtered to the space domain this area serves. A site built here enrols into the same grid.

The observing grid

  1. Open space instruments on the observing grid.

04In the field

Where this runs, sector by sector.

Deployment scenarios from the sector research that rely on into the product.

Transport

Non-federal automated weather observing for small airports

Aviation-grade stations under the civil-aviation authority's advisory circular; pricing not researched.
Defence-adjacent (civil dual-use)

Research and development route through the defence science programme

A science-and-technology programme on all-domain situational awareness.
Government and public safety

National GBON surface and upper-air network

WMO-grade stations reporting through WIS 2.0, funded through the systematic-observations financing pathway.
Government and public safety

Alerting integration with the Common Alerting Protocol and cell broadcast

Software-heavy: sensor triggers feed an alert origination tool; the alert authority keeps every decision.
Government and public safety

Deployable communications and sensing for incident command

A cell on wheels with satellite backhaul, mesh telemetry and environment nodes at the incident base.
Industrial

Utility private LTE for the grid edge

Distribution automation, distributed-energy control and wildfire-risk weather on a dedicated band.

05Open and enterprise

Open by default. Enterprise by contract.

The open counterpart lives on the main site for anyone to read and run. The enterprise service is designed, deployed and operated with you, under contract.

Open, on the main site

  • Benchmark methods
  • Pilot reports, published either way

Enterprise, on this site

  • Research pilots
  • Prototype engineering

06The rest of the line

Frontier labs, area by area.

Frontier labs

Pilots

New technology, a real site, a written plan.
Frontier labs

Benchmarks

Open data, one method, comparable results.
Frontier labs

AI-RAN and 6G

Sensing and communication on shared compute.
Frontier labs

Space and NTN

Direct-to-device and new payloads, tested.
Frontier labs

Physical AI

Drones and robots, inside published red lines.

Bring us the site.

Survey, design, deployment and operation for into the product. The form names who receives your details.

Talk to usAsk for a quote

More presentations

See it from every side.

Each opens as a full-screen presentation: deeper pages on the same subject, explainers, stories, guided tours of the places, network scenes and the observatories that came before.

All presentations for this page

In depth

Product or service · Frontier labs Into the productFrom a result to a qualified releaseUse case Bioacoustic biodiversity observatoryUse case Citizen seismology nodeUse case Hybrid air-quality observatoryUse case Research-infrastructure gap node

Explainers

Explainer · Environment and climate Environment and climate — SectorsMethane fencelines, acoustic biodiversity grids, flux towers, river sondes and smoke networks: an interactive explainer with the method behind every number.

From a result to a qualified release.

Into the product, inside Frontier labs: continuous training and deployment to edge fleets, drift and performance monitoring, model provenance and signing, build provenance and more. Every item is traced to its specification, from 3GPP TS 28.105 (AI/ML management) to OpenGitOps principles, and runs on the open Observatory Protocol.

01What it is

02Architecture

Where it sits, and what it speaks.

03On the grid

04In the field

Where this runs, sector by sector.

05Open and enterprise

Open by default. Enterprise by contract.

The open counterpart lives on the main site for anyone to read and run. The enterprise service is designed, deployed and operated with you, under contract.

Open, on the main site
    Enterprise, on this site
      06The rest of the line

      Bring us the site.