/

/

Learning paths, the standards cited across this site and the explainers that show the systems in 3D.

1. Humanitarian · Resources

   Observation where the need is greatest and the grid is thinnest

   Deployable connectivity and sensing for displacement sites and crisis response, observing-network gap filling where stations are fewest, satellite backhaul where nothing else reaches, and evidence funders can audit. Needs: weather and water where stations are missing, connectivity at camps and field offices, off-grid power, hazard exposure and audit-ready evidence for funders.

2. Story

   Federation

   A worked story shows how a humanitarian deployment runs end to end, from the instruments and the radio to the edge, the console and the people who act on the result. Each story names its sources and the standards it relies on.

   Read the stories

3. Story

   Resilient ops

   A worked story shows how a humanitarian deployment runs end to end, from the instruments and the radio to the edge, the console and the people who act on the result. Each story names its sources and the standards it relies on.

   Read the stories

4. What must be measured

   Humanitarian: what must be measured

   Weather and water where stations are missing, connectivity at camps and field offices, off-grid power, hazard exposure and audit-ready evidence for funders. Each is measured by instruments sited to recognised practice, read by a base node that stamps, checks and signs every value.

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

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

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

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

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

10. Field service

    One crew, from survey to repair

    The same crew surveys, installs, commissions, calibrates and repairs, working from the site’s own record. Each visit updates it, so the next crew knows exactly what is there, when it was last checked and why it was changed. Spares and references are planned from that history.

11. Failure and recovery

    When a node fails, the fleet knows first

    When a node goes silent or a sensor drifts, the node buffers its data, fails over to a second link where one exists, and the alert carries the evidence a responder needs. Nothing is lost and nothing is counted twice.

12. What you get

    Deployable connectivity and sensing kits

    A cell on wheels with satellite backhaul, mesh telemetry and environment nodes for incident bases and events. Delivered as rental and managed service, for emergency agencies, humanitarian logistics, event operators. Scale: Pre-positioned fleets. Service levels are written as numbers you can measure on your own dashboard.

    Talk to sales

13. Next step

    Plan a humanitarian deployment

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

01Learning paths

From first principles to a commissioned site.

01

Academy

The principles of observation, the protocol and the lifecycle of a site.Start learning →

02

Training and enablement

Operator, crew and engineer training on the systems you own.The training platform →

03

Explainers

The systems in 3D, chapter by chapter, drawn to scale.Open the explainer →

02Standards

The standards cited on this site.

• WMO-No. 8 (CIMO Guide)
• WMO-No. 1160 (Manual on WIGOS, GBON)
• WMO WIS 2.0
• WMO-No. 306 (BUFR)
• Open school-mapping and daily-check tools of the programme
• GLOBE protocols (optional)
• UNHCR data-protection policy
• Sphere and Core Humanitarian Standard

03Explainer and stories

See it at work.

The industry in 3D, and field stories with the systems in each and the sources behind them.

04Terms

What people search for in this industry.

Bring us the site.

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