--- title: "Edge runtime: Software | Nexus Observatory" description: "Edge runtime, inside Software: device edge, far edge, near edge, regional edge and more. An edge runtime and node agent that enrol…" url: https://observatory.global/software/edge-runtime/ publisher: Nexus Observatory Inc. updated: 2026-10-27 --- [Nexus Observatory](https://observatory.global/) / [Software](https://observatory.global/software/) / **Edge runtime** # One runtime from gateway to rack to tower. Edge runtime, inside Software: device edge, far edge, near edge, regional edge and more. Every item is traced to its specification, from ISO/IEC 30141 (IoT reference architecture) to ETSI GS MEC 003 (framework and reference architecture), and runs on the open Observatory Protocol. [Plan with us](https://observatory.global/contact/) Architecture [The protocol](https://observatory.global/protocol/specification/) **Technologies**: 9 **At the frontier**: 1 **Protocol functions**: 3 of 8 **Industries served**: 3 Reference design, drawn to scale · drag to turn · hover a part **01** What it is ## Edge tiers and multi-access edge computing. Compute placed where data is produced and decisions are needed: the device, far, near and regional edge tiers, multi-access edge computing, modular edge data centres including the AI tower in a box, servers and accelerators, storage, power and cooling, ruggedisation, fleet orchestration, OTA and GitOps, and the hardware trust that makes remote sites safe to run. Each technology below carries what it is, what we do with it, and the standard it is drawn against. Compute and edge ### Device edge Compute inside sensors, gateways, vehicles and robots that acts on data with no network round trip. We design, integrate and deploy. ISO/IEC 30141 (IoT reference architecture) Compute and edge ### Far edge Servers at cell sites, towers and customer premises that host DUs, local breakout and latency-critical apps. We design, integrate, deploy, operate and maintain. ETSI GS MEC 003 (framework and reference architecture) · O-RAN WG6 Cloud Architecture and Deployment Scenarios Compute and edge ### Near edge Aggregation sites and central offices serving a town or district with shared compute and CU/core functions. We design, integrate, deploy and operate. ETSI GS MEC 003 · GSMA OPG.02 (Operator Platform telco edge requirements) Compute and edge ### Regional edge Metro and regional data centres that host heavier AI, storage and core functions for a province or region. We design, integrate and operate. EN 50600 (data centre facilities and infrastructures) · ANSI/TIA-942 Compute and edge ### MEC application enablement Platform services that let applications register, discover services and receive traffic rules at the edge. We design, integrate and operate. ETSI GS MEC 011 (edge platform application enablement) · 3GPP TS 23.558 (EDGEAPP) Compute and edge ### MEC service APIs Radio network information, location and other APIs that let edge apps adapt to network conditions. We design and integrate. ETSI GS MEC 012 (radio network information API) · ETSI GS MEC 013 (location API) Compute and edge ### Application mobility and edge federation Moving app state between edge sites as users move, and sharing edge capacity across operators. We design and integrate. ETSI GS MEC 021 (application mobility service API) · GSMA OPG.02 **Frontier** · Compute and edge ### Edge-cloud continuum Placing each workload at the device, edge or cloud tier by latency, cost, energy and data rules, and moving it when conditions change. We design, integrate and operate. 3GPP TS 23.548 (5GC enhancements for edge computing) · ETSI GS MEC 003 Compute and edge ### Data residency and jurisdiction controls Policy controls that keep data processed and stored in the locations a contract or law requires. We design and operate. ISO/IEC 27701 (privacy information management) · PIPEDA (Canada) **02** Architecture ## Where it sits, and what it speaks. Edge runtime draws on 2 domains and 16 layers of the spectrum; the highlighted layers carry this area. It speaks 3 of the protocol's 8 core functions. Edge tiers and multi-access edge computing 9 Modular edge data centres and the AI tower in a box 8 Servers and accelerators 8 Storage and edge data management 6 Cooling and ruggedisation 10 Kubernetes and fleet orchestration 8 OTA updates, GitOps and software supply chain 8 Confidential computing and hardware trust 8 Ingest and streaming 8 Storage and data lakes 6 Metadata, provenance and catalogues 8 Open standards and interoperability 7 APIs and SDKs 7 Licensing, residency and governance 8 Digital twins and observability 7 Open protocol interfaces and federation 8 01**Join** Identity, attestation quote, signed policy. 02**Admit** Admitted for a stated scope, nothing wider. 03**Describe** What, where, how and by whom, with calibration. 04**Time** One clock across the grid, with its error bound. 05**Observe** Every value with quality and provenance. 06**Qualify** Tested against the specification, state on record. 07**Federate** Signed exchange across grids and trust domains. 08**Orchestrate** Software and configuration by signed plan. **03** On the grid ## Every site joins one observing grid. The open networks on the grid today, over real relief and the geodesic cells we count them into. A site built here enrols into the same grid. **04** In the field ## Where this runs, sector by sector. 4 deployment scenarios from the sector research that rely on edge runtime. [Government and public safety Wildfire camera network and fire-weather stationsCamera towers with edge inference and co-located fire-weather stations, utility- or agency-funded.](https://observatory.global/sectors/public-safety/) [Industrial Utility private LTE for the grid edgeDistribution automation, distributed-energy control and wildfire-risk weather on a dedicated band.](https://observatory.global/sectors/industrial/) [Energy Utility grid-edge private LTESee industrial.](https://observatory.global/sectors/energy/) [Government and public safety Alerting integration with the Common Alerting Protocol and cell broadcastSoftware-heavy: sensor triggers feed an alert origination tool; the alert authority keeps every decision.](https://observatory.global/sectors/public-safety/) **05** Open and enterprise ## Open by default. Enterprise by contract. The open counterpart lives on the main site for anyone to read and run. The enterprise service is designed, deployed and operated with you, under contract. Open, on the main site - Node agent and SDKs (licence pending) - App methods with worked examples Enterprise, on this site - Fleet operations - Supported runtime - Team workspaces - Integration engineering **06** The rest of the line ## Software, area by area. [Software Node agentEnrolment, attestation quotes, signed updates.](https://observatory.global/software/node-agent/) [Software FleetEvery node: its state, its plan, its evidence.](https://observatory.global/software/fleet/) [Software Field appsSurvey, commissioning and maintenance, offline first.](https://observatory.global/software/field-apps/) [Software app workspaceCoverage, power and timing, modelled as a team.](https://observatory.global/software/app-workspace/) [Software IntegrationsSCADA, GIS and data platforms, by typed contract.](https://observatory.global/software/integrations/) ## Bring us the site. Survey, design, deployment and operation for edge runtime. The form names who receives your details. [Talk to us](https://observatory.global/contact/) [contact@observatory.global](mailto:contact@observatory.global?subject=Software%3A%20Edge%20runtime) [Nexus Observatory](https://observatory.global/)**Software** . One runtime. Every node. Every state.[Talk to us](https://observatory.global/contact/) Software - [Edge runtime](https://observatory.global/software/edge-runtime/) - [Node agent](https://observatory.global/software/node-agent/) - [Fleet](https://observatory.global/software/fleet/) - [Field apps](https://observatory.global/software/field-apps/) - [app workspace](https://observatory.global/software/studio-workspace/) - [Integrations](https://observatory.global/software/integrations/) Technologies - [Edge tiers and multi-access edge computing](https://observatory.global/technologies/edge/edge-tiers-and-multi-access-edge-computing/) - [Modular edge data centres and the AI tower in a box](https://observatory.global/technologies/edge/modular-edge-data-centres-and-the-ai-tower-in-a-box/) - [Ingest and streaming](https://observatory.global/technologies/data/ingest-and-streaming/) - [Storage and data lakes](https://observatory.global/technologies/data/storage-and-data-lakes/) Industries - [Government](https://observatory.global/industries/) - [Civil resilience](https://observatory.global/industries/) - [Industry](https://observatory.global/industries/) Service platforms - [Observatory Protocol](https://observatory.global/protocol/) - [Protocol & Grid](https://observatory.global/grid-services/) - [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/) © 2026 Nexus Observatory Inc. [Privacy](https://observatory.global/legal/privacy/) [Terms](https://observatory.global/legal/terms/) [Accessibility](https://observatory.global/legal/accessibility/) [Cookie settings](https://observatory.global/privacy-choices/) [Data credits](https://observatory.global/credits/)