/

/

Enrolment, attestation quotes, signed updates.

Node agent, inside Software: gitOps, secure update frameworks, device management, firmware resiliency and recovery and more. Every item is traced to its specification, from OpenGitOps principles to The Update Framework (TUF) specification, and runs on the open Observatory Protocol.

Technologies

9

At the frontier

0

Protocol functions

3 of 8

Industries served

3

Reference design, drawn to scale · drag to turn · hover a part

01What it is

OTA updates, GitOps and software supply chain.

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. How observations move from the edge into stores, catalogues and APIs with their provenance, licence and residency attached, and how they interoperate through open standards and the open Observatory Protocol. Each technology below carries what it is, what we do with it, and the standard it is drawn against.

02Architecture

Where it sits, and what it speaks.

Node agent draws on 2 domains and 16 layers of the spectrum; the highlighted layers carry this area. It speaks 3 of the protocol’s 8 core functions.

Edge tiers and multi-access edge computing

9

Modular edge data centres and the AI tower in a box

8

Servers and accelerators

8

Storage and edge data management

6

Cooling and ruggedisation

10

Kubernetes and fleet orchestration

8

OTA updates, GitOps and software supply chain

8

Confidential computing and hardware trust

8

Ingest and streaming

8

Storage and data lakes

6

Metadata, provenance and catalogues

8

Open standards and interoperability

7

APIs and SDKs

7

Licensing, residency and governance

8

Digital twins and observability

7

Open protocol interfaces and federation

8

01JoinIdentity, attestation quote, signed policy.

02AdmitAdmitted for a stated scope, nothing wider.

03DescribeWhat, where, how and by whom, with calibration.

04TimeOne clock across the grid, with its error bound.

05ObserveEvery value with quality and provenance.

06QualifyTested against the specification, state on record.

07FederateSigned exchange across grids and trust domains.

08OrchestrateSoftware and configuration by signed plan.

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. A site built here enrols into the same grid.

04In the field

Where this runs, sector by sector.

1 deployment scenarios from the sector research that rely on node agent.

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

• Node agent and SDKs (licence pending)
• App methods with worked examples

Enterprise, on this site

• Fleet operations
• Supported runtime
• Team workspaces
• Integration engineering

06The rest of the line

Software, area by area.

Bring us the site.

Survey, design, deployment and operation for node agent. The form names who receives your details.