Fermyon Built the WebAssembly Cloud. The Cloud Hosts Functions, Not Self-Executing Objects.

by Nick Clark | Published March 28, 2026 | PDF

Fermyon built Fermyon Cloud as a managed platform for WebAssembly serverless applications, providing instant scaling, global deployment, and developer-friendly tooling. The cloud platform is well-engineered. But Fermyon Cloud hosts trigger-based functions that execute in response to events and terminate upon completion. It does not host objects that carry their own execution cycle, maintain governed memory, or self-evaluate between invocations. The gap is between managed serverless hosting and a platform for memory-resident self-executing objects.


Fermyon Cloud's WebAssembly-native platform and instant scaling provide genuine infrastructure innovation. The gap described here is about the execution model it hosts.

Serverless scaling without execution continuity

Fermyon Cloud scales WebAssembly functions based on incoming requests. Each function invocation is independent. The platform manages the scaling. But the objects being scaled have no execution continuity between invocations. Each invocation starts fresh, evaluates a trigger, and terminates. There is no persistent execution state that the platform maintains between invocations.

Global deployment without governed state migration

Fermyon Cloud deploys functions globally. But there is no mechanism for governed state to migrate with execution, for trust slope to persist across deployment regions, or for memory lineage to remain intact as functions execute across different locations.

What memory-resident execution provides

Memory-resident execution objects maintain governed state that persists across execution cycles and can migrate between substrates with full lineage. The execution cycle is intrinsic to the object, not triggered by external events. Fermyon Cloud's efficient WebAssembly hosting could serve as one substrate for memory-resident objects. The governed memory and self-execution cycle would be provided by the memory-resident execution layer above the hosting platform.

Nick Clark Invented by Nick Clark Founding Investors: Devin Wilkie