WebAssembly
WebAssembly components can now do more than run short, isolated functions. The WebAssembly System Interface (WASI) 0.3 added native asynchronous composition in June. Adoption still depends on runtime support, tooling and results on real workloads. It is not yet clear that containers will keep services while WebAssembly takes functions.
Research snapshot · updated Nov 12, 2026
State of the art (2026)
WASI 0.3 was released in June 2026. It adds native asynchronous functions, streams and futures to the Component Model, so components can do more than run short isolated functions. Wasmtime 45 ran the last release candidate, and the Bytecode Alliance said Wasmtime 46 would ship WASI 0.3.0 with asynchronous support switched on by default. WebAssembly is well proven in the browser, in products such as Figma and Google Earth. On servers it is used most for functions and plug-ins, where fast start-up and running many tenants on one machine matter. Wider use depends on runtime support, tooling and results on real workloads.
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.
Explore the deeper analysis in CanaryIQ
Explore what is covered below. These previews show the structure; log in to read the full analysis.
Signal stack
Evidence stacked leading → lagging
7 signals
Signal stack
Evidence stacked leading → lagging
Technology-native KPIs
Metrics that predict trajectory, tracked over time
3 tracked
Technology-native KPIs
Metrics that predict trajectory, tracked over time
Landscape map
Who builds what, and who depends on whom
178 players · 6 layers
Landscape map
Who builds what, and who depends on whom
Catalyst calendar
Dated events that will move the position
3 ahead
Catalyst calendar
Dated events that will move the position
Technology roadmap
Milestones on the path to maturity
7 milestones
Technology roadmap
Milestones on the path to maturity
Watchlists
Companies, people and papers, each with a condition for removing it
20 · 20
Watchlists
Companies, people and papers, each with a condition for removing it
Decision frameworks
What our view means for your job
Locked
Decision frameworks
What our view means for your job
Thesis changelog
When our view changed, and why
8 updates
Thesis changelog
When our view changed, and why
Change our mind
4 disconfirming conditions
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 a record of every time our view on WebAssembly has changed. All of it is in CanaryIQ.