---
id: edge-computing
name: Edge Computing
family: technological
tier: active
url: https://explorer.talin.digital/e/edge-computing/
author: Benjamin Talin
citation: Talin, B. (2026). The Future Explorer. https://explorer.talin.digital (dataset v0.4.0, 2026-11-16)
license: CC-BY-NC-4.0
---

# Edge Computing

Doing computing close to where data is made, in a box at a factory, a phone mast or a local server, instead of sending everything to a distant data centre. That saves delay and data costs, which matters for machines that must react instantly. It is real in phone networks and factories but has not spread widely: only about 4% of computing work runs this way, and most firms still send data to the big building.

> Computing done close to where data is produced - a factory gateway, a phone mast, a content cache - instead of in a distant data centre.

## Maturity
3/5 — Genuine production use in specific places - telecom networks, factory gateways, content caching - and it has not generalised. Edge and micro data centres hosted 4% of IT workloads in 2025. The Commission's own count of EU edge nodes was small and mostly test and research.

Capability 4 · deployment 3 · absorption 3 · bound by capital · flat

Source: Eurostat, Cloud computing statistics on the use by enterprises (data extracted Jan 2026); European Commission, State of the Digital Decade 2024 (Jul 2024); Uptime Institute, Global Data Center Survey 2025 (Jul 2025, INDUSTRY-BELIEF). The 75 per cent claim in the print text is a 2018 Gartner prediction - INDUSTRY-BELIEF with no primary basis (2024–2026)

## What it is
Processing performed close to where data is generated rather than in a distant datacentre.

## What it does
It makes latency-sensitive and bandwidth-heavy applications possible, and it changes where data physically sits - which is a jurisdiction question as much as an engineering one.

## Common misconception
That it is a cost optimisation. Its more consequential property is that it lets processing happen inside a jurisdiction, which is one of the few practical routes to data residency that does not require owning a cloud.

## Steepens
- Digital Sovereignty (digital-sovereignty) — moderate
- Autonomous Systems and Mobility (autonomous-systems-and-mobility) — moderate
- Precision Everything (precision-everything) — moderate
- Hyper-automation of Industrial Production (hyper-automation-of-industrial-production) — moderate

## What would change its gradient
- Fleet management tooling that makes distributed operation tractable
- Data residency requirements, which are pulling deployment faster than latency is
- Hardware cost at the edge relative to centralised capacity
