---
title: "About | Nexus Observatory"
description: "Nexus Observatory Inc. is the system designer and integrator for the open Observatory Protocol, from survey to operation."
url: https://observatory.global/about/
publisher: Nexus Observatory Inc.
updated: 2026-10-28
---

About · Nexus Observatory Inc.

# We build the grid that observes the planet.

Nexus Observatory Inc. is the system designer and integrator for the open Observatory Protocol. Instruments, power, links, timing, compute, AI and data: we design them as one system, commission them on the protocol and keep them current for the working life of the site.

Talk to us

How we work

[Read the protocol](https://observatory.global/protocol/)

**Office**: Toronto, ON
**Protocol**: Open

**Reference design** · drawn to scale

Drag to turn · hover a part

**I** Who we are

## The hard problems live between the parts.

An observatory is never one instrument. It is ground, a mast, a power budget, a set of sensors, a backhaul link, a clock with an error bound, a computer and the crew who keep it all inside specification. Each part ships with its own datasheet. None of them ships with the interfaces between them.

That is our work. **We design the whole system, integrate every part on the open Observatory Protocol and stay accountable for it through its working life.** The protocol is stewarded by the Nexus Consortium, so what we build interoperates with what anyone else builds on it.

**Company**: Nexus Observatory Inc.
**Office**: Toronto, ON M4R 1V2 Canada
**Role**: System designer and integrator Supports the open Observatory Protocol

**II** Lifecycle

## From first survey to the fifth upgrade.

Eleven stages, one record. Each stage hands the next a site that is described, evidenced and ready to change, so nothing is relearned at handover. Choose a stage to see what we deliver.

**01** · Stage

### Learn

Know what an observatory can do for you before anything is bought.Lines · [Academy](https://observatory.global/#lifecycle)[Field services](https://observatory.global/field-services/)

What we deliver

- *01* Briefings on the protocol and the observing domains
- *02* Academy paths for teams and partners
- *03* The atlas and methods, open to everyone

**III** Orchestration

## Orbit to application, one spine.

Every layer speaks the same protocol: it enrols each node, attests what it is, disciplines its clock, describes what it measures, moves its data and carries the evidence. Swap a radio, a sensor or a model, and the rest of the site keeps working.

The spine

### Observatory Protocol

1. Enrolment
2. Identity
3. Time
4. Description
5. Data
6. Orchestration
7. Evidence
8. Federation

Open, and stewarded by the Nexus Consortium.

**Space and air** 

01

**Orbit** 

EO and communication satellites, ground stations

02

**Air** 

Drones, balloons and aircraft payloads

**Ground** 

03

**Ground site** 

Masts, enclosures, foundations, access

04

**Power** 

Grid, solar, storage, microgrids

05

**Sensors** 

Weather, seismic, RF, ocean, imaging

06

**Connectivity** 

Fibre, private 5G, AI-RAN, satellite links

07

**Timing** 

GNSS, PTP profiles, holdover

**Compute and data** 

08

**Edge compute** 

Ruggedised servers and edge racks

09

**AI** 

Inference and models beside the instruments

10

**Data** 

Streams, archives, catalogues, licences

11

**Applications** 

the Nexus Observatory app, dashboards, alerts, public portals

**IV** How we work

## Five rules we engineer by.

They decide every design review, every commissioning report and every sentence on this site.

01

### Exact

We name the instrument, the standard, the unit and the tolerance. A requirement that cannot be measured is not yet a requirement.

02

### Evidence first

Every claim about a site sits beside its evidence: a test, a calibration record, a state. What is not yet proven is never presented as done.

03

### Open first

We build on the open protocol and publish what we can license. Your instruments, your data and your rights stay yours.

04

### Safe and civil

Science, safety, infrastructure and public service, nothing else. Every site is designed first for the crew who climb it.

05

### People and places

An observatory serves a place. We work with the communities, landholders and agencies around each site, in their language and on their terms.

**V** The group

## Open protocol. Named companies.

The protocol is open and governed in the open. The company that builds and runs it is named here, and it is the one you contract with.

**Company** 

### Nexus Observatory Inc.

Designs, builds and runs observatories on the open protocol: instruments, sensors and calibration, Earth observation and digital twins.

**Office**: Toronto, ON M4R 1V2

### Stewarded by the Nexus Consortium

The Observatory Protocol is open, so anyone can build on it. The Nexus Consortium stewards it and its change process. Nexus Observatory Inc. supports the open work and builds enterprise systems on it.

Open protocol

**VI** Lines

## Nine lines, one architecture.

Each enterprise line has its own site and team, built on the same protocol, grid and design.

[/grid-services Protocol & GridYour grid, on the open protocol.Open the line →](https://observatory.global/grid-services/)

[/software SoftwareOne runtime. Every node. Every state.Open the line →](https://observatory.global/software/)

[/hardware Hardware & powerBuilt for the site, not the lab.Open the line →](https://observatory.global/hardware/)

[/sensors Sensors & instrumentsMeasurements that carry their own proof.Open the line →](https://observatory.global/sensors/)

[/connectivity ConnectivityPrivate 5G, AI-RAN and orbit, on site.Open the line →](https://observatory.global/connectivity/)

[/edge-ai Edge compute & AIInference beside the instrument.Open the line →](https://observatory.global/edge-ai/)

[/earth-observation Earth observation & GeoAIThe ground, measured and modelled.Open the line →](https://observatory.global/earth-observation/)

[/field-services Field servicesSurvey to decommission, one accountable crew.Open the line →](https://observatory.global/field-services/)

[/data-products Data & licensingGrid data, licensed for your use.Open the line →](https://observatory.global/data-products/)

**VII** Contact and careers

## Bring us the site.

Where it is, what it must measure and who depends on it. We will tell you what it takes, and what it will not do.

### Plan a site

One station, a regional network or a federated grid. Bring the question; we bring the method and the crew.

[contact@observatory.global](mailto:contact@observatory.global?subject=Deployment)

### Build on the protocol

Instrument makers, software teams and researchers putting their work on the open protocol.

[contact@observatory.global](mailto:contact@observatory.global?subject=Protocol)

### Careers

Engineers, scientists, field crews and designers who want their work standing outside, in weather, for decades.

[contact@observatory.global](mailto:contact@observatory.global?subject=Careers)

**—** Begin

## The next observatory starts with one site.

Start on the open protocol today, or talk to us about designing, commissioning and running yours.

Create account

Talk to us

[Read the protocol](https://observatory.global/protocol/)

© 2026 Nexus Observatory Inc.

**Open** [Protocol](https://observatory.global/protocol/) · [Atlas](https://observatory.global/observatories/) · [Open science](https://observatory.global/open/) · [Learn](https://observatory.global/learn/) **Company** [About](https://observatory.global/about/) · [Stewardship](https://observatory.global/consortium/)

**Legal** [Privacy](https://observatory.global/legal/privacy/) · [Cookies](https://observatory.global/legal/cookies/) · [Terms](https://observatory.global/legal/terms/) · [Data credits](https://observatory.global/credits/)