/

/

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. Public safety · Open

   Warning time, gained at the sensor

   Observing networks, communications and data for emergency management: hydromet and fire-weather stations, camera towers with inference at the edge, deployable cells for incident command, and the integration that hands a trigger to the alerting authority, which keeps every decision. Needs: rainfall, river level and soil moisture, fire weather, smoke and ignition, ground movement and seismic activity, communications at the incident base and reporting uptime and data latency.

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 · Field services

   Open with Field services

   Guides, Templates and Lifecycle: free to use and build on. The enterprise layer adds eight services and Government buyers, delivered under contract by Nexus Observatory Inc. Open methods let anyone check how a product was made. Every reading and every change leaves a record that can be checked later.

4. 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.

5. 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.

6. Open · Hardware & power

   Open with Hardware & power

   Device classes with 3D models and Reference designs (licence pending): free to use and build on. The enterprise layer adds kit supply, Bills of materials and deployment plans and OEM co-engineering, delivered under contract by Nexus Observatory Inc. Open methods let anyone check how a product was made.

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

    Hydrometeorological and flood observing networks

    Stream gauges, rain gauges, weather radar and automatic weather stations built to WMO practice, reporting through WIS 2.0 where the agency requires it. Delivered as hardware + software, managed service and build-operate-transfer, for national meteorological and hydrological services, river-basin agencies, utilities.

    Talk to sales

13. Next step

    Plan a public safety deployment

    Tell us the sites, the measurements and the people who will use them. We reply with a design and a scope for public safety. 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.

• FloodNet NYC open hardware
• UCAR 3D-PAWS
• Open CAP editors
• WIS2 reference nodes (wis2box)
• Sensor.Community

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 public safety. The form names who receives your details.