Skip to content
Nexus Observatory

/

Frontier labs

/

Architecture
How frontier labs is built.

One reference architecture under every deployment: the layers of a site, the protocol functions this platform relies on, and the evidence that travels with every observation.

Plan with usIndustries

Areas · 6 Technologies · 253 Industries · 3

01Reference architecture

From one instrument to the grid.

Every deployment is drawn on the same six layers. A typed contract sits at every boundary, so parts from different makers fit together.

  1. 01InstrumentThe sensor or radio that makes the measurement, with its calibration.
  2. 02NodeThe device that hosts instruments: identity, time, power and storage.
  3. 03SiteNodes in one place, on one mast or in one shelter, with their links.
  4. 04CellSites that share a backhaul, a power plan and an operator.
  5. 05ClusterCells run as one service, with one fleet plan and one evidence trail.
  6. 06GridClusters that federate across owners through the open protocol.
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.

The protocol functions this platform relies on most.

02Trust and evidence

Every observation carries its proof.

What a buyer, a regulator or a partner grid can check, on every site we build.

Evidence

Identity and attestation

Hardware-rooted identity, with a quote checked at every join.

Evidence

Segmentation

Least privilege between nodes, tenants and sites.

Evidence

Time integrity

Every clock monitored, every holdover logged.

Evidence

Evidence bundles

What was done, by whom, with what result.

Evidence

Qualification state

Each device and release, with the tests behind it.

Evidence

Signed plans

Software and configuration change only by a signed plan.

03Read further

The open specification behind it.

Observatory Protocol

Specification

Functions, state machines, objects and flows.Read →Observatory Protocol

Reference designs

Nodes and sites drawn to the protocol.Read →Observatory Protocol

Conformance

Run the suite against an implementation.Read →

04On this site

Where to go next.

Frontier labs

Areas

Every area, with its systems and standards.Open →Frontier labs

Technologies

The layered map of what we build with.Open →Frontier labs

Industries

The industry sites built on this platform.Open →Frontier labs

Resources

Explainer, stories, specification and forms.Open →

Bring us the site.

We bring the survey, the design and the crew. The form names who receives your details.

Plan a deploymentContact
Skip to content

How frontier labs is built.

Bring us the site.

We bring the survey, the design and the crew. The form names who receives your details.