---
title: "Upstream oil and gas monitoring | Nexus Observatory"
description: "Wellpads, tank batteries and gathering facilities are many, small and mostly unstaffed, and methane rules now expect leaks to be found…"
url: https://observatory.global/industries/energy/upstream-oil-gas/
publisher: Nexus Observatory Inc.
updated: 2026-11-02
---

[Nexus Observatory](https://observatory.global/)

/

[Energy](https://observatory.global/industries/energy/)

/

[Specialized fields](https://observatory.global/industries/energy/fields/)

/

**Upstream oil and gas** 

# Upstream oil and gas, measured to the last leak.

Wellpads, tank batteries and gathering facilities are many, small and mostly unstaffed, and methane rules now expect leaks to be found, quantified and fixed with evidence. An observation network on every pad reads gas, flow, pressure and flare, watches with thermal cameras and weather stations, and reports over satellite or private radio to one record that operators and regulators can check.

[Plan a deployment](https://observatory.global/contact/deployment/)

How it works

[Station Builder](https://observatory.global/studio/builder/)

**Industry**: Energy
**Measurements**: 6
**Sources cited**: 5

1. Energy · Upstream oil and gas Many small sites, one emissions record Upstream oil and gas runs on many small, mostly unstaffed sites spread across a basin. Methane escapes from equipment, tanks and flares, and the rules now expect leaks to be found, fixed and reported with evidence. The only practical way to know every pad is an observation network that never sleeps.
2. What is measured Gas, wind, flare and flow Gas sensors sit around wellheads, separators, tanks and compressors; a weather station gives wind for attributing a rise to its source; a thermal camera watches the flare and the tanks. Pressure, flow and tank level come from the pad controller, so emissions are read with their production context. InstrumentsMethane sensors · Thermal camera · Weather station · Pad controller data
3. The base node A node that attributes and confirms The pad's base node reads every sensor, signs and stores each value and runs the attribution logic: from wind direction and sensor positions it estimates where a rise came from, and asks the camera for a clip. The event leaves the pad with its evidence, not as a bare alarm.
4. Radio and links Satellite where nothing else reaches Most pads have no network, so a LEO terminal carries readings and clips to the operations centre. Dense basins can share one private LTE network, battery sensors on tanks report over LoRaWAN, and public cellular serves the pads it reaches. The station stays the same whatever the link. RadioSatellite · Private LTE · LoRaWAN · Public cellular
5. How it works From a sensor to a work order A methane rise is read over Modbus through the industrial gateway, joined to wind and camera data on the node, signed and sent by satellite to the record. There it opens an event with its likely source, a work order for the crew and an entry in the emissions inventory.
6. From order to operation · Order Scope the basin and the rules The scope starts from the operator's sites, equipment counts by type and the methane rules that apply to each. Nexus Observatory Inc. returns a monitoring design per site class, the radio approach, the repair workflow and the reports each regulator and reporting framework expects, with a price per pad and per facility. [Plan a deployment](https://observatory.global/contact/deployment/)
7. From order to operation · Survey Survey a sample of every site class Crews visit representative pads, tank batteries and compressor stations with the operator's field staff. They map emission sources, prevailing wind, sight lines for cameras, sky view for satellite terminals and the controllers already on site, and record each position so the design repeats across the class.
8. From order to operation · Permits Access, hot work and data agreements Installation follows the operator's permit-to-work and hazardous-area rules, with equipment certified for the zones it enters. Agreements set which data goes to partners and regulators, and how sensor alerts are recorded in the leak detection and repair programme. Every installation is recorded against the site's equipment register.
9. From order to operation · Build Build one design per site class Stations for each site class are assembled with their sensors, cameras, weather stations, nodes, solar power and satellite terminals, configured and tested on the bench. Each is enrolled with its identity and labelled for its position, so a crew installs a known design rather than improvising on the pad. [Open the Station Builder](https://observatory.global/studio/builder/)
10. From order to operation · Install Install on the crews' routes Installation is planned along the crews' existing routes. Masts and solar go up first, then gas sensors around the sources, the thermal camera on the flare and tanks, the weather station clear of obstructions and the gateway to the pad controller. Each pad is photographed and its positions recorded.
11. From order to operation · Commission Commission with a controlled release Each node proves its identity, then sensors are checked against calibration gas and, where agreed, a controlled release confirms the pad's detection and attribution. Alert thresholds and the repair workflow are tested end to end, from the pad to the crew's tablet.
12. From order to operation · Operate From alert to repair, with evidence The console shows every pad, its emissions trend, flare status and production context. An event arrives with its likely source, its wind and a camera clip; a crew is dispatched, the repair is recorded against it and the emissions record is updated, ready for the reports the rules require.
13. From order to operation · Maintain Calibrate and follow the field Sensors are bump-tested and calibrated on schedule, stations are moved as pads are added or abandoned and software reaches the fleet in rings. Every visit updates the record, and the year's data feeds the measurement-based reporting the operator commits to. [Book field services](https://observatory.global/contact/field-service/)
14. Data products From the pad to the regulator Field crews receive events with the equipment to check; maintenance closes each with its repair; environmental teams build the emissions inventory from measurement; production engineers see flare performance; regulators receive the reports the rules require. Each product is built from the same signed readings. [See the data products](https://observatory.global/data-products/)
15. Evidence Evidence the rules ask for Calibrations, controlled-release tests, every event, every repair and every report are signed and kept. Monitoring follows the methane rules that apply to each site and the reporting framework the operator has joined, so an inspector or a partner can trace any reported number to its readings. Drawn against40 CFR Part 60 · Regulation (EU) 2024/1787 · OGMP 2.0
16. What you get Environmental and permit monitoring Emissions, water quality, noise and dust monitoring for permit conditions, with traceable calibration and evidence bundles. Delivered as managed service and data licence, for industrial operators, municipalities, regulators. Scale: Site to portfolio. Service levels are written as numbers you can measure on your own dashboard. [Talk to sales](https://observatory.global/contact/sales-enquiry/)
17. Next step Plan upstream oil and gas with us Tell us the site, the measurements and the rules it answers to. We reply with a survey proposal, a design and a scope for upstream oil and gas. 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 deployment](https://observatory.global/contact/deployment/) [Open the Station Builder](https://observatory.global/studio/builder/) [Open the Studio](https://observatory.global/studio/)

**01** The place and its hazards

## Where it runs, and what can go wrong.

Operating contextUpstream operations drill and produce wells, then separate, store and compress what comes out on wellpads and in gathering facilities. Sites are spread over large areas and visited by crews on routes rather than staffed. Methane, the main component of natural gas, escapes from equipment leaks, venting, tanks and incomplete flaring, and regulations in several jurisdictions now set leak detection and repair duties and reporting.

Hazards

- Methane and volatile organic compound leaks from valves, connectors, tanks and compressors
- Unlit or inefficient flares and unplanned venting
- Hydrogen sulphide where sour gas is produced
- Fire and explosion around wellheads and tank batteries
- Spills of produced water and oil

**02** What must be measured

## What, where, how often, and under which rules.

Each measurement names where it is taken, how often, and the public standard or regulation behind it. Numbers in the sources column open the cited source below.

| Measurement | Where | Cadence | Sources |
| --- | --- | --- | --- |
| Methane concentration and emission events | Fixed sensors around wellheads, separators, tanks and compressors, with wind for source attribution | Continuous | 12 |
| Leak survey results and repairs | Every component in scope of the leak detection and repair programme | On the survey schedule the rules set, and after every alert | 12 |
| Flare status and combustion | Flare stacks, by thermal camera and pilot monitoring | Continuous | 1 |
| Wellhead and line pressure, flow and tank level | Wellheads, separators, meters and tanks | Continuous | 3 |
| Wind speed and direction | On each pad, sited clear of obstructions | Continuous | 4 |
| Hydrogen sulphide | Sour gas sites, at wellheads and the fence | Continuous, with local alarms | 5 |

**03** The observation stack

## From one base unit to a network.

The same blocks at every scale: instruments and a base node, a site with its radio, a fleet run as one, and a network federated on the open protocol.

1. **01** Base unit A pad station: gas sensors, a thermal camera and a weather station read by a base node that signs every reading and keeps it through a lost link. [Build a station →](https://observatory.global/studio/builder/)
2. **02** Site A wellpad or facility: sensors around every emission source, the existing controller reached through an industrial gateway, and a satellite or private radio link. [Plan a site →](https://observatory.global/contact/deployment/)
3. **03** Fleet Every pad of a basin run as one fleet, with one alert policy, one repair workflow and one emissions record. [Managed offers →](https://observatory.global/industries/energy/solutions/)
4. **04** Network Operators, joint-venture partners and regulators read one federated record, each with the access their role gives them. [The open protocol →](https://observatory.global/protocol/)

- **01** Gas detector (industrial)
- **02** Flow meter
- **03** Thermal camera
- **04** Compact weather station
- **05** OT gateway (OPC UA, Modbus)
- **06** Edge node (Wedge)
- **07** LEO flat-panel terminal
- **08** Solar array
- **09** Battery case
- **10** Pole

Radio and links

### Satellite

Many pads lie beyond any network; LEO terminals carry sensor data and short video clips from each pad to the operations centre.

Radio and links

### Private LTE

In dense basins, one private network over the field carries pad data, cameras and crew tablets at a lower cost per site.

Radio and links

### LoRaWAN

Battery sensors on tanks and remote valves report short readings without cabling across the pad.

Radio and links

### Public cellular

Where public coverage reaches a pad, a cellular modem is the simplest backhaul.

Edge computeThe pad's node attributes a methane rise to a likely source from wind and sensor positions, confirms it with the thermal camera and sends an event with its evidence, so a crew is dispatched to the right equipment.

PowerPad stations run on solar and batteries sized for the darkest season, independent of the pad's own power, so monitoring continues when the site is shut in.

**04** How it works

## From the instrument to the product.

One observation's path, tier by tier, with the interface on every link and a bill of materials below; then how the one node grows to a site, a fleet and federated networks.

Upstream oil and gas: data path

– of 07

01 Instruments Measurement with sensor identity andcalibration 02 Gateway 03 Node – Wrap in an observation envelope with timequality– Measure quality and uncertainty, attachquality flags– Buffer locally (store-and-forward when thelink drops) 04 Backhaul Commit with transactional outbox andpublish, delivered at least once 05 Site Consumer inbox deduplicates and applieseach record once into governed data 06 Data store Governed product through API, map orexport, correction-aware 07 Products OPC UA (IEC 62541)MQTT 5OGC SensorThings API 08 Power and structure Supplies 12 V DC, 24 V DC, 48 V DC to thefield equipment 01 Gas detector (industrial) Analogue I/O · RS-485 · Ethernet 02 Flow meter SDI-12 · RS-485 · Ethernet 03 Thermal camera Ethernet 04 Compact weather station SDI-12 · RS-485 · Ethernet 05 OT gateway (OPC UA, Modbus) Ethernet · RS-485 · CAN · AnalogueI/O 06 Edge node (Wedge) Ethernet · Fibre · USB · RS-485 ·BMC 07 LEO flat-panel terminal Ethernet Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Methane events with likelysource and evidence Emissions inventory frommeasurement Flare performance records Repair records tied to eachevent Pad status and productioncontext 08 Solar array RS-485 09 Battery case USB 10 Pole RS-485 · Modbus RS-485 · Modbus Ethernet · RTSP/ONVIF RS-485 Ethernet · opc-ua Ethernet Satellite IP

From the instrument to the published product: each band is a tier, each connector names its interface, and the numbers match the bill of materials. Hover or focus a block to trace its path; scroll or step to follow one observation.

| Item | Equipment | Data ports | Protocols | Power in |
| --- | --- | --- | --- | --- |
| 01 | **Gas detector (industrial)** Fixed detector for flammable or toxic gas in industrial areas, with alarm outputs. | Analogue I/ORS-485Ethernet | Modbus, OPC UA, MQTT 5 | 24 V DC |
| 02 | **Flow meter** Open-channel or pipe flow meter (Doppler, ultrasonic, electromagnetic). | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC |
| 03 | **Thermal camera** Long-wave infrared camera for fire detection, equipment hot spots and night monitoring. | Ethernet | RTSP with ONVIF profiles, MQTT 5 | PoE |
| 04 | **Compact weather station** All-in-one or compact station for temperature, humidity, pressure, wind and rain at a site. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC |
| 05 | **OT gateway (OPC UA, Modbus)** Read-only bridge from industrial fieldbuses and controllers (Modbus, OPC UA, DNP3, IEC 61850, CAN) to the site network, behind a security boundary. | EthernetRS-485CANAnalogue I/O | OPC UA, Modbus, DNP3 (IEEE 1815), IEC 61850 (MMS, GOOSE), MQTT 5 | 24 V DC |
| 06 | **Edge node (Wedge)** Rugged edge node that boots from signed media, attests itself and establishes a site cell from little or no infrastructure. | EthernetFibreUSBRS-485BMC | MQTT 5, DMTF Redfish, IEEE 1588 PTP, NTP with NTS, OPC UA | 12 V DC, 24 V DC, 48 V DC, AC mains |
| 07 | **LEO flat-panel terminal** Electronically steered flat-panel user terminal for low-Earth-orbit broadband constellations. | Ethernet | — | PoE, 48 V DC, AC mains |
| 08 | **Solar array** PV modules with charge controller sized to the site's load and climate. | RS-485 | Modbus | — |
| 09 | **Battery case** Portable battery pack with DC outputs for field kits. | USB | Modbus | AC mains, HV DC, USB PD |
| 10 | **Pole** Utility, street or dedicated pole with clamp positions. | — | — | — |

How it scales

01 Instruments Arbitrary qualified sensors and instruments whosemeasurements are ingested with calibration, units,geometry, time, custody and uncertainty. ×n 02 Node The minimum useful deployable unit: server, ruggedappliance, radio node, sensor gateway, satelliteterminal, AI, scientific, vehicle or virtual node. Node Node agent 03 Site The minimum independently operable localgovernance and failure domain: one or more nodesplus local network, identity, policy, evidence,storage, products and operator surfaces.

SITE

Node Node Node ×n 04 Cluster An optional scale or specialisation domain forscheduling, shared storage, accelerators or datalocality.

CLUSTER

×n 05 Fleet Coordinates plans, acknowledgements,convergence evidence, update campaigns andcorrection propagation across nodes and sites.

FLEET

Fleet controller ×n 06 Federation An exchange of products, capabilities, events orwork across approved, independently administeredtrust domains, using explicit trust, policy,data-locality, version and correction contracts.

TRUST DOMAIN

TRUST DOMAIN

TRUST DOMAIN

×n Verifier Applications Data in the field Telemetry Control Data upstream Control Data upstream Control Exchange Evidence Events Exchange

The smallest deployable unit is one node; the same unit is replicated to meet the demand. Nodes form a site, sites may form a cluster, sites and clusters are coordinated as a fleet, and fleets exchange across independently administered trust domains. Each plane is a separate channel with its own open binding.

**Data in the field**: MQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses.
**Telemetry**: OpenTelemetry OTLP.
**Control**: TLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2.
**Data upstream**: At-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links.
**Evidence**: DSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts.
**Events**: Event envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3.
**Exchange**: OpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0.

**05** From order to operation

## Every step, from the first call to a running site.

The same crew and the same record carry the work from scope to maintenance.

1. 01 Order Scope the basin and the rules The scope starts from the operator's sites, equipment counts by type and the methane rules that apply to each. Nexus Observatory Inc. returns a monitoring design per site class, the radio approach, the repair workflow and the reports each regulator and reporting framework expects, with a price per pad and per facility. 12
2. 02 Survey Survey a sample of every site class Crews visit representative pads, tank batteries and compressor stations with the operator's field staff. They map emission sources, prevailing wind, sight lines for cameras, sky view for satellite terminals and the controllers already on site, and record each position so the design repeats across the class.
3. 03 Permits Access, hot work and data agreements Installation follows the operator's permit-to-work and hazardous-area rules, with equipment certified for the zones it enters. Agreements set which data goes to partners and regulators, and how sensor alerts are recorded in the leak detection and repair programme. Every installation is recorded against the site's equipment register. 2
4. 04 Build Build one design per site class Stations for each site class are assembled with their sensors, cameras, weather stations, nodes, solar power and satellite terminals, configured and tested on the bench. Each is enrolled with its identity and labelled for its position, so a crew installs a known design rather than improvising on the pad.
5. 05 Install Install on the crews' routes Installation is planned along the crews' existing routes. Masts and solar go up first, then gas sensors around the sources, the thermal camera on the flare and tanks, the weather station clear of obstructions and the gateway to the pad controller. Each pad is photographed and its positions recorded.
6. 06 Commission Commission with a controlled release Each node proves its identity, then sensors are checked against calibration gas and, where agreed, a controlled release confirms the pad's detection and attribution. Alert thresholds and the repair workflow are tested end to end, from the pad to the crew's tablet.
7. 07 Operate From alert to repair, with evidence The console shows every pad, its emissions trend, flare status and production context. An event arrives with its likely source, its wind and a camera clip; a crew is dispatched, the repair is recorded against it and the emissions record is updated, ready for the reports the rules require.
8. 08 Maintain Calibrate and follow the field Sensors are bump-tested and calibrated on schedule, stations are moved as pads are added or abandoned and software reaches the fleet in rings. Every visit updates the record, and the year's data feeds the measurement-based reporting the operator commits to.

**06** Data products and integration

## What it delivers, to whom, and into which systems.

Data products

- **Methane events with likely source and evidence** Field operations and leak detection and repair teams
- **Emissions inventory from measurement** Environmental and reporting teams, regulators
- **Flare performance records** Production engineers and regulators
- **Repair records tied to each event** Maintenance teams and auditors
- **Pad status and production context** Production and operations centres

Integration

- **Field SCADA and historian** Pad controller data arrives through an industrial gateway over Modbus or OPC UA and is stored with its quality flags.
- **Maintenance management** Each event opens a work order and closes only when the repair is recorded.
- **Emissions reporting** Measured emissions are exported for the inventories and frameworks the operator reports to.

Exchanged through OPC UA (IEC 62541), MQTT 5, OGC SensorThings API.

**07** Questions buyers ask

## Before you scope it.

Does continuous monitoring replace leak surveys?

That depends on the rules that apply. Where regulations allow continuous monitoring as an alternative or a complement, the design follows them; otherwise it supports the required surveys with evidence between them.

Can you quantify emissions, not only detect them?

Sensor readings, wind and source positions allow estimates of emission rates with stated uncertainty. Methods and their uncertainty are documented so reports can show how numbers were made.

What about sites with no power or network?

Stations run on solar and batteries and report over satellite, so they work on pads with neither.

Can we use the cameras we already have?

Usually yes. Cameras with standard video interfaces are read by the same node, and their clips join the same event record.

**08** Resources

## The sources behind this page.

Public standards, regulations and guidance, cited where they apply. Each applies only where its jurisdiction or scope does.

1. **1** [40 CFR Part 60: Standards of performance for new stationary sources, including the oil and natural gas methane subparts](https://www.ecfr.gov/current/title-40/part-60) US Environmental Protection Agency (eCFR)
2. **2** [Regulation (EU) 2024/1787 on the reduction of methane emissions in the energy sector](https://eur-lex.europa.eu/eli/reg/2024/1787/oj) European Union · 2024
3. **3** [Oil and Gas Methane Partnership 2.0 (OGMP 2.0) reporting framework](https://www.unep.org/) United Nations Environment Programme
4. **4** [Guide to Instruments and Methods of Observation (WMO-No. 8)](https://library.wmo.int/) World Meteorological Organization
5. **5** [ISA/IEC 62443 series: security for industrial automation and control systems](https://www.isa.org/standards-and-publications/isa-standards/isa-iec-62443-series-of-standards) ISA and IEC

**09** Related

## Use cases and solutions.

[Use case Methane fenceline observatoryPoint sensors on the fenceline with optical gas imaging and quantification, feeding leak-detection reports.The full use case →](https://observatory.global/use-cases/methane-fenceline/)

[Solution Environmental and permit monitoringEmissions, water quality, noise and dust monitoring for permit conditions, with traceable calibration and evidence bundles.Solutions for energy →](https://observatory.global/industries/energy/solutions/#environmental-compliance)

[Solution Mine, plant and port site monitoringSlope radar, tailings monitoring, dust and water, and site connectivity for operations and closure.Solutions for energy →](https://observatory.global/industries/energy/solutions/#industrial-site-monitoring)

[Solution Satellite and non-terrestrial backhaulLEO and GEO backhaul, 3GPP non-terrestrial integration and direct-to-device fallbacks for remote sites.Solutions for energy →](https://observatory.global/industries/energy/solutions/#ntn-backhaul)

**10** Energy: specialized fields

## Other fields of this industry.

[Specialized field Pipelines and midstreamLeak detection, cathodic protection, pressure and flow along the line, geohazards at crossings and compressor and pump stations, on LoRaWAN, satellite and private links over hundreds of kilometres.The full field →](https://observatory.global/industries/energy/pipelines/)

[Specialized field Thermal power plantsContinuous emissions, machine condition, cooling water and plant weather for gas, coal and biomass plants, with an industrial network that keeps the control system separate and secure.The full field →](https://observatory.global/industries/energy/thermal-generation/)

[Specialized field Hydropower and damsDam safety instruments, reservoir and river levels, inflow forecasting and downstream warning, with links that keep working in the flood the dam is there to hold.The full field →](https://observatory.global/industries/energy/hydropower/)

[Specialized field Wind farmsWind resource and power performance, turbine condition, icing, lightning and wildlife monitoring, from the first met mast to an operating farm on one record.The full field →](https://observatory.global/industries/energy/wind/)

[Specialized field Solar power plantsIrradiance, module temperature, soiling, inverter output and plant weather to international monitoring classes, for bankable performance ratios and fewer surprises in operation.The full field →](https://observatory.global/industries/energy/solar/)

[Specialized field Transmission networksLine ratings from measured weather and conductor state, wildfire and vegetation watch, substation automation and synchrophasor timing, on private LTE, microwave and fibre along the corridor.The full field →](https://observatory.global/industries/energy/transmission/)

[Specialized field Distribution networks and the grid edgeFeeder and transformer monitoring, distributed energy resources, fault location and outage evidence, on a utility private network that reaches every pole and substation.The full field →](https://observatory.global/industries/energy/distribution/)

### Bring us the site.

Plan a deployment, configure a station, model it in the Studio or talk to sales. The form names who receives your details.

[Plan a deployment](https://observatory.global/contact/deployment/)

[Station Builder](https://observatory.global/studio/builder/)

[Open the Studio](https://observatory.global/studio/)

[Talk to sales](https://observatory.global/contact/sales-enquiry/)

[Request a quote](https://observatory.global/contact/hardware-quote/)

[Nexus Observatory](https://observatory.global/)**Energy** . The grid edge, observed.[Talk to us](https://observatory.global/contact/)

Energy

- [Overview](https://observatory.global/industries/energy/)
- [Explainer](https://observatory.global/industries/energy/explainer/)
- [Specialized fields](https://observatory.global/industries/energy/fields/)
- [Use cases](https://observatory.global/industries/energy/use-cases/)
- [Solutions](https://observatory.global/industries/energy/solutions/)
- [Platforms](https://observatory.global/industries/energy/platforms/)
- [Resources](https://observatory.global/industries/energy/resources/)
- [Contact](https://observatory.global/industries/energy/contact/)

Platforms

- [Observatory Protocol](https://observatory.global/protocol/)
- [Protocol & Grid](https://observatory.global/grid-services/)
- [Software](https://observatory.global/software/)
- [Hardware & power](https://observatory.global/hardware/)
- [Sensors & instruments](https://observatory.global/sensors/)
- [Connectivity](https://observatory.global/connectivity/)
- [Edge compute & AI](https://observatory.global/edge-ai/)
- [Earth observation & GeoAI](https://observatory.global/earth-observation/)
- [Space and satellite systems](https://observatory.global/space/)
- [Digital twins and simulation](https://observatory.global/digital-twins/)
- [Data & licensing](https://observatory.global/data-products/)
- [Field services](https://observatory.global/field-services/)
- [Frontier labs](https://observatory.global/labs/)

Solutions

- [Early warning](https://observatory.global/use-cases/street-flood/)
- [Wildfire and fire weather](https://observatory.global/use-cases/wildfire-camera/)
- [Environmental compliance](https://observatory.global/use-cases/methane-fenceline/)
- [Asset monitoring](https://observatory.global/industries/infrastructure/)
- [Private networks](https://observatory.global/connectivity/private-5g/)
- [Remote power and sites](https://observatory.global/use-cases/remote-microgrid/)
- [Climate and resilience](https://observatory.global/industries/climate/)
- [Site twins](https://observatory.global/digital-twins/)
- [Data licensing](https://observatory.global/data-products/)

Industries

- [Public safety](https://observatory.global/industries/public-safety/)
- [Government](https://observatory.global/industries/government/)
- [Cities](https://observatory.global/industries/cities/)
- [Civil resilience](https://observatory.global/industries/resilience/)
- [Communities](https://observatory.global/industries/communities/)
- [Humanitarian](https://observatory.global/industries/humanitarian/)
- [Climate](https://observatory.global/industries/climate/)
- [Water](https://observatory.global/industries/water/)
- [Nature](https://observatory.global/industries/nature/)
- [Oceans](https://observatory.global/industries/oceans/)
- [Agriculture](https://observatory.global/industries/agriculture/)
- [Energy](https://observatory.global/industries/energy/)
- [Telecom](https://observatory.global/industries/telecom/)
- [Transport](https://observatory.global/industries/transport/)
- [Infrastructure](https://observatory.global/industries/infrastructure/)
- [Mining](https://observatory.global/industries/mining/)
- [Industry](https://observatory.global/industries/industry/)
- [Research](https://observatory.global/industries/research/)
- [Education](https://observatory.global/industries/education/)
- [Health](https://observatory.global/industries/health/)
- [Insurance and finance](https://observatory.global/industries/insurance/)
- [Events](https://observatory.global/industries/events/)

Products

- [Field Deployment Studio](https://observatory.global/studio/)
- [Station Builder](https://observatory.global/studio/builder/)
- [Field services](https://observatory.global/field-services/)
- [Data products](https://observatory.global/data-products/)
- [APIs and SDKs](https://observatory.global/protocol/developers/)
- [Edge runtime and fleet](https://observatory.global/software/)
- [Hardware catalogue](https://observatory.global/hardware/)
- [Reference designs](https://observatory.global/protocol/reference-designs/)

Resources

- [Learn](https://observatory.global/learn/)
- [Stories](https://observatory.global/stories/)
- [Environments](https://observatory.global/environments/)
- [Network scenes](https://observatory.global/environments/networks/)
- [Observatories atlas](https://observatory.global/observatories/)
- [Earth and maps](https://observatory.global/earth/)
- [Technologies](https://observatory.global/technologies/)
- [Countries](https://observatory.global/countries/)
- [Spectrum](https://observatory.global/spectrum/)
- [Specification](https://observatory.global/protocol/specification/)
- [Conformance](https://observatory.global/protocol/conformance/)
- [Open source](https://observatory.global/open/)
- [Data credits](https://observatory.global/credits/)

Company

- [About](https://observatory.global/about/)
- [Consortium](https://observatory.global/consortium/)
- [Security and trust](https://observatory.global/security/)
- [Contact sales](https://observatory.global/contact/)
- [Privacy requests](https://observatory.global/privacy-request/)

© 2026 Nexus Observatory Inc.

[Security and trust](https://observatory.global/security/)

[Privacy choices](https://observatory.global/privacy-choices/)

[Accessibility](https://observatory.global/legal/accessibility/)

[Privacy](https://observatory.global/legal/privacy/)

[Terms](https://observatory.global/legal/terms/)
