/

/

Open projects, open methods and open templates this community builds on, with the licence of every source carried through.

Reference design, drawn to scale · drag to turn

1. Transport · Open

   Corridors that report their own conditions

   Road-weather and corridor sensing, avalanche and slope detection above the line, port and maritime observation, timing and positioning integrity, and connectivity along routes where coverage ends. Needs: road surface and visibility, slope, snow and avalanche, port and vessel conditions, positioning integrity and coverage along routes.

2. Open · Sensors & instruments

   Open with Sensors & instruments

   Metadata and quality rules and Open networks on the grid: free to use and build on. The enterprise layer adds sensing as a Service, Calibration programmes and Qualification, delivered under contract by Nexus Observatory Inc. Open methods let anyone check how a product was made.

3. Open · Connectivity

   Open with Connectivity

   Band tables and sources, Country guides and Coverage methods: free to use and build on. The enterprise layer adds private Wireless as a Service, AI-RAN deployment and Spectrum route support, delivered under contract by Nexus Observatory Inc. Open methods let anyone check how a product was made.

4. Open · Edge compute & AI

   Open with Edge compute & AI

   Class assumptions and Power and thermal methods: free to use and build on. The enterprise layer adds MEC deployment and Edge AI sites, delivered under contract by Nexus Observatory Inc. Open methods let anyone check how a product was made.

5. Open · Data & licensing

   Open with Data & licensing

   Open tier and Dataset cards: free to use and build on. The enterprise layer adds paid tiers and Residency by contract, delivered under contract by Nexus Observatory Inc. Open methods let anyone check how a product was made. Service levels are written as numbers you can measure.

6. Open · Space and satellite systems

   Open with Space and satellite systems

   Orbit and pass methods, Payload class catalogue and Ground-station interfaces on the protocol: free to use and build on. The enterprise layer adds mission and payload integration, Tasking and downlink services and Non-terrestrial backhaul for remote sites, delivered under contract by Nexus Observatory Inc.

7. Trust

   Every node proves what it is

   A node joins only after its hardware root of trust answers an attestation challenge. Keys stay in secure hardware, software arrives signed, and every reading carries a signature, so its origin can be checked by anyone downstream without asking us.

8. Time and place

   Every reading carries when and where

   Readings are stamped against a disciplined clock, from satellite time or a PTP grandmaster, together with the station position and its siting record. When time or position is degraded, the record says so instead of hiding it, and every analyst downstream sees the same warning.

9. How it scales

   One base unit, repeated

   A programme starts with one base node and the instruments it reads. A station adds power and radio, a site adds a relay, a fleet repeats the proven site across many places, and a network federates fleets through edge and core. Capacity grows by adding units, never by replacing what works.

10. Updates

    Updates in rings, with rollback

    Software and configuration reach the fleet in rings: a canary site first, then a few, then all, each ring gated on health and data completeness. A failed gate stops the wave and returns each node to its last good release, without a site visit.

11. Operations

    Every node watched, every incident closed

    The operations console shows every node with its state, its plan and its evidence. Alerts arrive with their data and a runbook; acknowledging one opens a work order, and an incident closes only when the cause is recorded and the fix verified.

12. What you get

    Transport and logistics corridor sensing

    Road weather, rail condition, port and cold-chain sensing along corridors, with connectivity where coverage ends. Delivered as managed service and data licence, for transport agencies, rail and port operators, logistics firms. Scale: Corridor to network. Service levels are written as numbers you can measure on your own dashboard.

    Talk to sales

13. Next step

    Plan a transport deployment

    Tell us the sites, the measurements and the people who will use them. We reply with a design and a scope for transport. An engineer replies with a survey proposal and a scope, and the plan grows from one site to the network you need, at your pace.

    Plan a deploymentOpen the StudioRead the stories

01Open projects

What this community builds on.

Open hardware, software and data projects, named as references. Each keeps its own licence and its own governance.

• Open Weather Station
• AISHub
• WeeWX

02Open methods and templates

Every calculation, with a worked example.

Observatory templates for this industry, each a starting design you can read, run and adapt on the open protocol.

03Open data

Networks on the grid, with their licences.

The open observing networks on the grid, each shown with its source and licence, and the protocol that lets new ones join.

01

Open networks

Instruments from open networks, on real relief.Earth and maps →

02

Sources and licences

Every dataset with its source and the terms it is used under.Data credits →

03

The protocol

The open specification any instrument or network can implement.Read the protocol →

Bring us the site.

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