--- title: "Edge data centres monitoring | Nexus Observatory" description: "Edge and regional data centres sit in containers, rooms and buildings close to users, often unattended. Power, cooling, air…" url: https://observatory.global/industries/telecom/edge-data-centres/ publisher: Nexus Observatory Inc. updated: 2026-11-02 --- [Nexus Observatory](https://observatory.global/) / [Telecom](https://observatory.global/industries/telecom/) / [Specialized fields](https://observatory.global/industries/telecom/fields/) / **Edge data centres** # Edge data centres, measured to the standard. Edge and regional data centres sit in containers, rooms and buildings close to users, often unattended. Power, cooling, air, leak and vibration sensors report to one record behind a security gateway, so operators keep equipment in its envelope, find faults early and report efficiency on the standard indicators. [Plan a deployment](https://observatory.global/contact/deployment/) How it works [Station Builder](https://observatory.global/studio/builder/) **Industry**: Telecom **Measurements**: 5 **Sources cited**: 4 1. Telecom · Edge data centres Nobody is in the room An edge data centre sits in a container or a small room close to the people it serves, and nobody works there. A cooling unit fails at night, a pipe leaks under a raised floor, a generator will not start. Knowing every rack's air and every unit's state lets operators act before customers notice. 2. What is measured Power, air, cooling, leaks and vibration Meters read incomers, UPS, distribution and IT loads. Sensors at rack inlets read temperature and humidity, flow and temperature sensors follow the coolant, leak cables lie under cooling units and pipework, and vibration sensors watch chillers and generators for developing faults. InstrumentsPower meters · Rack inlet sensors · Coolant flow · Leak cables · Vibration sensors 3. The base node Faults predicted, data guarded The site node predicts rack inlet temperatures from trends and keeps every rack inside its envelope, detects cooling and power faults early and raises leak alarms at once. It computes efficiency indicators, and everything leaves only through the security gateway. 4. Radio and links A secured path on the site's fibre Edge sites are on fibre for their own traffic, and monitoring rides a separate, secured path on it. An out-of-band cellular path reports when the fibre is down, and battery leak and temperature sensors are added over LoRaWAN without cabling in live rooms. LinksFibre · Public cellular · LoRaWAN 5. How it works From a failing fan to a planned repair A cooling unit's fan starts to vibrate and its supply air warms slightly. The node sees the trend, predicts rack inlets will leave their envelope within hours and alerts operations. A crew replaces the fan in a planned visit, before any rack overheats, and the record keeps it. 6. From order to operation · Order Scope the sites and the indicators The scope reads the site designs, power and cooling systems, existing building management, service commitments and the efficiency indicators to report. Nexus Observatory Inc. returns the point plan per site type, the security design, the integration with operations and a price per site and per year. [Plan a deployment](https://observatory.global/contact/deployment/) 7. From order to operation · Survey Survey a live site Crews survey a live site of each type with the operator: incomers, UPS and distribution, rack rows, cooling units and pipework, generators and network points. They record existing meters and controls and plan work that never touches live loads. Every finding is photographed. 8. From order to operation · Permits Change control and security Every change follows the operator's change control and access rules. The network design follows the operator's security policy, with the monitoring network separated from customers' traffic, and every approval is kept with the site record. Engineers are escorted and logged on every visit, as the site rules require. 9. From order to operation · Build Build and test off site Meters, sensors, gateways, nodes and the security gateway are built and tested together off site, configured with the site's systems and thermal envelopes and enrolled with their identities. Each part is labelled with its rack, unit or panel. Spares are kept for quick swaps. [Open the Station Builder](https://observatory.global/studio/builder/) 10. From order to operation · Install Install without touching the load Crews install in agreed windows: clamp-on meters, rack inlet sensors, flow sensors on coolant pipes, leak cables under cooling units and vibration sensors on chillers and generators. Nothing interrupts the load, and every point is photographed and located. Cables follow existing trays. 11. From order to operation · Commission Test a cooling failure Each device proves its identity behind the security gateway. Meters are checked against the electrical system, sensors against references, and a planned cooling unit stop tests the thermal alarms. Leak alarms are tested with water on the cable. Results are kept with the site record. 12. From order to operation · Operate Keep every rack in its envelope Operators see power, cooling and every rack's inlet against its envelope, with faults predicted before alarms. Leaks raise alarms at once, field crews are sent with the evidence, and efficiency indicators are reported monthly to customers and management. Every alarm is kept on the record. 13. From order to operation · Maintain Maintain with the plant Sensors are checked during planned plant maintenance, meters verified, and baselines updated when equipment changes. Software updates reach the monitoring fleet in rings with rollback, and every change goes through change control and is recorded with the site. Spares are kept on site. [Book field services](https://observatory.global/contact/field-service/) 14. Data products For operations, engineers and customers Operations teams receive rack thermal compliance; facilities engineers receive power and cooling fault predictions; operations and field crews receive leak alarms; management and customers receive efficiency indicators. Each product carries its calibration and the site's configuration. Reports are dated, versioned and kept with the site. [See the data products](https://observatory.global/data-products/) 15. Evidence Facilities to the standard Every reading, alarm and change is signed and kept. Facilities follow the European data centre infrastructure standard, thermal envelopes follow the recognised guidelines, efficiency follows the international indicator standard, and security supports the cybersecurity duties of essential digital services. Records are open to audit. Drawn againstEN 50600 · ISO/IEC 30134 · ASHRAE thermal guidelines · Directive (EU) 2022/2555 16. What you get Modular edge data centre (AI tower in a box) A containerised edge data centre at the foot of a tower: GPU nodes, power, cooling and attestation, run as a service. Delivered as hardware + software and managed service, for carriers, utilities, governments, industrial sites. Scale: Regional edge capacity. 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 edge data centres 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 edge data centres. 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 contextEdge data centres bring compute close to users and devices, in places with no staff on site. Facilities are designed and operated to data centre infrastructure standards, equipment has recommended thermal envelopes, efficiency is reported on standard indicators, and operators of essential digital services carry cybersecurity duties. Hazards - Cooling failure overheating equipment - Power failures and generator problems - Water leaks from cooling - Unattended sites with slow response - Monitoring itself opening a path for attackers **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 | | --- | --- | --- | --- | | Power and energy | Incomers, UPS, distribution and IT loads | Continuous | 12 | | Inlet temperature and humidity | Rack inlets and room or container air | Continuous | 31 | | Cooling performance | Coolant flows and temperatures, cooling units | Continuous | 1 | | Leaks and vibration | Under cooling units and pipework; chillers and generators | Continuous | 1 | | Efficiency indicators | Each site, computed from its meters | Continuous, reported monthly and yearly | 2 | **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 site point: meters and environmental sensors on an industrial gateway with an edge node. [Build a station →](https://observatory.global/studio/builder/) 2. **02** Site An edge data centre: every meter, rack and cooling unit behind a security gateway with fibre home. [Plan a site →](https://observatory.global/contact/deployment/) 3. **03** Fleet Every edge site of an operator run as one fleet, with one record. [Managed offers →](https://observatory.global/industries/telecom/solutions/) 4. **04** Network Operators and their customers exchange service and efficiency records through open standards. [The open protocol →](https://observatory.global/protocol/) - **01** Energy and power-quality meter - **02** Air quality monitor - **03** Flow meter - **04** Vibration and condition monitor - **05** OT gateway (OPC UA, Modbus) - **06** Edge node (Wedge) - **07** Zero-trust gateway - **08** Fibre terminal Radio and links ### Fibre Edge sites are on fibre for their own traffic; monitoring rides a separate, secured path on it. Radio and links ### Public cellular An out-of-band path reports when the site's fibre is down. Radio and links ### LoRaWAN Battery leak and temperature sensors are added without new cabling in live rooms. Edge computeThe site node keeps every rack inside its thermal envelope with predictions from inlet trends, detects cooling and power faults early, raises leak alarms at once and computes efficiency indicators, with all data leaving only through the security gateway. PowerMonitoring runs from the site's protected supply with its own battery, so it reports through a power failure. **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. Edge data centres: data path – of 08 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 Local network 05 Backhaul Commit with transactional outbox andpublish, delivered at least once 06 Site Consumer inbox deduplicates and applieseach record once into governed data 07 Data store Governed product through API, map orexport, correction-aware 08 Products EN 50600ISO/IEC 30134OPC UA 01 Energy and power-quality meter SDI-12 · RS-485 · Ethernet 02 Air quality monitor SDI-12 · RS-485 · Ethernet 03 Flow meter SDI-12 · RS-485 · Ethernet 04 Vibration and condition monitor Analogue I/O · 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 Zero-trust gateway Ethernet · Fibre 08 Fibre terminal Fibre · Ethernet Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Rack thermal compliance Power and cooling fault predictions Leak alarms Efficiency indicators RS-485 · Modbus RS-485 · Modbus RS-485 · Modbus RS-485 · Modbus Ethernet · opc-ua Ethernet Fibre Fibre 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 | **Energy and power-quality meter** Meter for voltage, current, power, energy and power quality at a site or on a feeder. | SDI-12RS-485Ethernet | Modbus, IEC 61850 (MMS, GOOSE), DNP3 (IEEE 1815), MQTT 5 | 12 V DC | | 02 | **Air quality monitor** Particulate and gas monitor (PM, NO2, O3, CO, SO2) for outdoor or indoor air. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC | | 03 | **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 | | 04 | **Vibration and condition monitor** Accelerometer-based vibration and temperature sensor for rotating machinery and structural condition monitoring. | Analogue I/ORS-485Ethernet | Modbus, OPC UA, MQTT 5 | 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 | **Zero-trust gateway** Gateway that terminates encrypted tunnels, enforces segmentation and gates every flow by identity and policy. | EthernetFibre | — | 12 V DC, AC mains | | 08 | **Fibre terminal** Optical network terminal or media converter that lands fibre backhaul at a site. | FibreEthernet | IEEE 1588 PTP | 12 V DC, 48 V DC, AC mains | 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 sites and the indicators The scope reads the site designs, power and cooling systems, existing building management, service commitments and the efficiency indicators to report. Nexus Observatory Inc. returns the point plan per site type, the security design, the integration with operations and a price per site and per year. 12 2. 02 Survey Survey a live site Crews survey a live site of each type with the operator: incomers, UPS and distribution, rack rows, cooling units and pipework, generators and network points. They record existing meters and controls and plan work that never touches live loads. Every finding is photographed. 3. 03 Permits Change control and security Every change follows the operator's change control and access rules. The network design follows the operator's security policy, with the monitoring network separated from customers' traffic, and every approval is kept with the site record. Engineers are escorted and logged on every visit, as the site rules require. 4 4. 04 Build Build and test off site Meters, sensors, gateways, nodes and the security gateway are built and tested together off site, configured with the site's systems and thermal envelopes and enrolled with their identities. Each part is labelled with its rack, unit or panel. Spares are kept for quick swaps. 5. 05 Install Install without touching the load Crews install in agreed windows: clamp-on meters, rack inlet sensors, flow sensors on coolant pipes, leak cables under cooling units and vibration sensors on chillers and generators. Nothing interrupts the load, and every point is photographed and located. Cables follow existing trays. 6. 06 Commission Test a cooling failure Each device proves its identity behind the security gateway. Meters are checked against the electrical system, sensors against references, and a planned cooling unit stop tests the thermal alarms. Leak alarms are tested with water on the cable. Results are kept with the site record. 7. 07 Operate Keep every rack in its envelope Operators see power, cooling and every rack's inlet against its envelope, with faults predicted before alarms. Leaks raise alarms at once, field crews are sent with the evidence, and efficiency indicators are reported monthly to customers and management. Every alarm is kept on the record. 32 8. 08 Maintain Maintain with the plant Sensors are checked during planned plant maintenance, meters verified, and baselines updated when equipment changes. Software updates reach the monitoring fleet in rings with rollback, and every change goes through change control and is recorded with the site. Spares are kept on site. **06** Data products and integration ## What it delivers, to whom, and into which systems. Data products - **Rack thermal compliance** Operations teams - **Power and cooling fault predictions** Facilities engineers - **Leak alarms** Operations and field crews - **Efficiency indicators** Management and customers Integration - **Building and power management** Readings are taken from existing systems over Modbus or OPC UA, read-only. - **Data centre infrastructure management** Data and alarms are delivered to the operator's management system. - **Customer reporting** Service and efficiency indicators are exported to customer reports. Exchanged through EN 50600, ISO/IEC 30134, OPC UA. **07** Questions buyers ask ## Before you scope it. Will it interrupt our load? No. Meters clamp on and work happens in agreed windows under change control. Is it secure? All data leaves through a security gateway on a network separated from customer traffic. Which efficiency indicators? Those of the international data centre indicator standard. Does it work unattended? Yes. It is built for sites with no one on them. **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** [EN 50600: Information technology, data centre facilities and infrastructures](https://www.cencenelec.eu/) European Committee for Electrotechnical Standardization 2. **2** [ISO/IEC 30134: Data centres, key performance indicators](https://www.iso.org/) International Organization for Standardization 3. **3** [Thermal Guidelines for Data Processing Environments](https://www.ashrae.org/) ASHRAE 4. **4** [Directive (EU) 2022/2555 on a high common level of cybersecurity across the Union (NIS2)](https://eur-lex.europa.eu/) European Union · 2022 **09** Related ## Use cases and solutions. [Solution Modular edge data centre (AI tower in a box)A containerised edge data centre at the foot of a tower: GPU nodes, power, cooling and attestation, run as a service.Solutions for telecom →](https://observatory.global/industries/telecom/solutions/#edge-data-centre) [Solution Operational-technology assurance for observing sitesIdentity, attestation, segmentation and monitoring for instruments and edge nodes, with evidence for audits.Solutions for telecom →](https://observatory.global/industries/telecom/solutions/#ot-site-assurance) [Solution Microgrids and off-grid site powerPV, storage and generator sizing for instruments and edge sites, with telemetry and remote control.Solutions for telecom →](https://observatory.global/industries/telecom/solutions/#site-power) **10** Telecom: specialized fields ## Other fields of this industry. [Specialized field Mobile network sitesPower and batteries, shelter climate, tower movement, intrusion and site weather at every mobile site, with an out-of-band path that reports when the site itself is down.The full field →](https://observatory.global/industries/telecom/mobile-sites/) [Specialized field Fibre networks and outside plantDistributed fibre sensing along routes, flooding and gas in chambers, and cabinet access and climate, on LoRaWAN and the fibre itself, so dig-ins and faults are found before the cable is cut.The full field →](https://observatory.global/industries/telecom/fibre-networks/) [Specialized field Satellite ground stationsRain, wind and lightning at the antennas, antenna drive condition, timing and site security at satellite ground stations, on the site's fibre, so passes are planned around the weather and faults are caught between passes.The full field →](https://observatory.global/industries/telecom/ground-stations/) [Specialized field Spectrum monitoring and interferenceFixed and mobile receivers that measure occupancy, find interference and locate its source by direction finding and time difference, with GNSS timing, so regulators and operators clear the bands they depend on.The full field →](https://observatory.global/industries/telecom/spectrum-monitoring/) ### 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/)**Telecom** . Towers that compute, sense and connect.[Talk to us](https://observatory.global/contact/) Telecom - [Overview](https://observatory.global/industries/telecom/) - [Explainer](https://observatory.global/industries/telecom/explainer/) - [Specialized fields](https://observatory.global/industries/telecom/fields/) - [Use cases](https://observatory.global/industries/telecom/use-cases/) - [Solutions](https://observatory.global/industries/telecom/solutions/) - [Platforms](https://observatory.global/industries/telecom/platforms/) - [Resources](https://observatory.global/industries/telecom/resources/) - [Contact](https://observatory.global/industries/telecom/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/) - [Open governance](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/)