Technology thesis · Computing Infrastructure
medium conviction growthWebAssembly
WebAssembly won the edge-function and plug-in niche, not the container war — the 2026 settlement is containers for services, Wasm for functions where cold start and sandboxing decide.
Position maintained continuously · last reviewed Jun 24, 2026
The thesis
Core thesis
Wasm started as a browser technology for near-native performance, then expanded to server-side (WASI), edge computing and plug-in systems. Advantages: sandboxed execution, language-agnostic, sub-millisecond cold starts versus the milliseconds containers need. Docker's Solomon Hykes said in 2019 that if Wasm and WASI had existed in 2008 there would have been no need to create Docker. By 2026 the server-side story has matured – WASI 0.3.0 shipped native async in June 2026 – and the market has settled on containers for long-lived services and Wasm for functions and plug-ins where cold start and dense multi-tenancy decide.
State of the art (2026)
The server-side story matured in 2026. WASI 0.3.0 (Preview 3) shipped on 11 June 2026, bringing native async — async funcs, streams and futures — into the Component Model and folding the old wasi:io package into the canonical ABI; Wasmtime 43 and jco support it, and Fermyon Spin reached it via release-candidate builds. The market consolidated around a clear division of labour: containers for long-lived services, Wasm for functions and plug-ins where sub-millisecond cold starts and dense multi-tenancy matter. Akamai’s acquisition of Fermyon put Spin functions across thousands of edge locations, while Wasmer 6.0 closed to roughly 95% of native speed. The browser remains the proven base — Figma, Adobe, Google Earth — but the contested ground is now edge and plug-in extensibility.
Everything below is live inside CanaryIQ
The full analysis behind the verdict — the structure is real; the content unlocks when you log in.
Signal stack
Evidence stacked leading → lagging
Technology-native KPIs
Metrics that predict trajectory, tracked over time
Landscape map
Who builds what — and who depends on whom
Catalyst calendar
Dated events that will move the position
Technology roadmap
Milestones on the path to maturity
Watchlists
Companies, people and papers — each with a remove-by condition
Decision frameworks
The same call, framed for your desk
Thesis changelog
When our view changed, and why
Change our mind
4 disconfirming conditions
The rest is inside
You've read the verdict. The file is much deeper.
The full signal stack, technology-native KPIs tracked over time, the landscape of who depends on whom, the dated catalyst calendar, decision frameworks for every desk, live watchlists and the changelog of every time our call on WebAssembly has changed — all live inside CanaryIQ.