Skip to content
All Use Cases
Developer Tools

WebAssembly Deployment

Run WebAssembly workloads on Open Source Cloud. WASM is one of six runtimes My Apps accepts, and your module runs on other runtimes implementing the same WASI version.

What You Get

WASM is a first-class My Apps runtime
Deploy from a repository or a .wasm URL
Deploy through your AI agent over MCP
Runs sandboxed, with no ambient access to the host
Portable to other runtimes on the same WASI version
Every component open source, no lock-in

How It Works

WASM ModuleYour workload
+
AI AgentVia MCP
↓
RunningOn your workspace

Why WASM?

Two ways to run WebAssembly

Deploy a repository as a My App with the runtime type set to wasm, the same path used for Node.js, Python, Go, .NET and PHP. Or point the WASM Runner service at a .wasm file you have already built and let it execute that directly.

A module, not a machine image

A .wasm artifact is a single compiled module. There is no operating system image wrapped around it, and the sandbox it runs in has no ambient access to the filesystem, the network or the host unless the runtime grants it.

WASI 0.3 is out

WASI 0.3.0 was released in June 2026. It moves async into the Component Model itself, with native async functions, streams and futures, which is what makes WebAssembly a reasonable target for ordinary server workloads rather than only for short-lived functions.

AI-native deployment

Your AI coding agent can deploy a WASM workload through MCP exactly as it deploys any other runtime. Describe what you want running, and let the agent create it.

Start from a .wasm file

If you already have a compiled module, the WASM Runner service takes a URL to your .wasm file, or a Git repository to clone it from, and runs the first .wasm file it finds. To deploy from a repository instead, create a My App and set its runtime type to wasm.

Deploy WASM Runner

WASM Deployment Features

Deploy WebAssembly workloads through the same paths you already use for every other runtime.

My Apps WASM runtime

Deploy a repository as a WebAssembly app by setting the runtime type to wasm

WASM Runner service

Run an existing .wasm file from a URL or a GitHub repository, no build step of ours in between

Deploy over MCP

Your AI agent creates the app through the OSC MCP server, same as any other runtime

WASI 0.3

Released June 2026, with async, streams and futures native to the Component Model

Open Standards, No Lock-in

WebAssembly is an open W3C standard, and WASI is developed in the open by the WASI Subgroup of the W3C WebAssembly Community Group. A module you run here runs on other runtimes implementing the same WASI version, without being rebuilt for them. Deploy on OSC today, move to your own infrastructure whenever you want to.

Ready to run WebAssembly?

Start with a free account and deploy your first WASM workload through AI.

Get Started Free