IoT sensor aggregation is already a major edge-compute use-case, it's not just for reducing latency for end-users. In this analogy you're just co-locating the e

IoT sensor aggregation is already a major edge-compute use-case, it's not just for reducing latency for end-users. In this analogy you're just co-locating the edge compute on the same LAN as the sensor. All of the orchestration, runtime, and framework concerns from existing edge compute systems still apply. Edge compute isn't solved; it's an area under active and aggressive development. The Cloudflare Workers wasm runtime for example. And if you're selling satelite edge compute, what's your control plane? You need a config store etc. Put differently; if I'm a satelite operator writing first-party software to run on my satelites, sure, there's no framework code to write, and I can just tailor the software to my satelite platform's hardware. However, if I'm selling colocated compute with ultra-low latency to third parties, then I need to build something that (IMO) looks very close, if not identical, to a current-generation edge-compute platform.