Ruby Reaches ICP Through the WebAssembly Toolchain

Ruby has reached the Internet Computer—not as a new officially supported language, but as a working community-built experiment that shows how far the platform’s WebAssembly boundary can be pushed.

In a September 21–22 forum thread, developer graial reported that Ruby was bootable and runnable on ICP. The deployed demo includes a visitor counter, which the author says demonstrates persistence. The report also records practical friction: roughly 400 KB PNG images were visibly slow to load, and the author found the backend call similarly slow in the initial test.

The important engineering story is the build path. Ruby already supports a WASI target, which provided part of the route to WebAssembly. But that was not enough for deployment. The author says Ruby had to be rebuilt from scratch with additional shims, after encountering version-specific WASI SDK issues. In other words, the breakthrough is less “Ruby is now an ICP language” than “a Ruby runtime can be adapted to ICP’s canister boundary.”

That distinction matters. ICP documentation describes canisters as sandboxed WebAssembly module instances and says that languages compiling to Wasm can work in principle. The platform’s official language documentation, however, distinguishes officially supported Motoko and Rust from community-maintained language integrations. Ruby is not presented there as an official CDK or supported language.

The next bottleneck is repeatability. The forum discussion points toward an icp-cli recipe and template so other developers could create a Ruby project with a single command. The current icp-cli template repository documents the template workflow, but the cited material does not establish that a Ruby template or production-ready recipe has already landed there.

That makes this a useful milestone for ICP builders. It demonstrates that the canister model can host more than the standard language paths, while also showing that “compiles to Wasm” is only the starting condition. Runtime shims, WASI SDK compatibility, deployment recipes, interface bindings, and performance testing still determine whether an experiment becomes a practical developer platform.

Editorial caveat: this remains an early community demonstration, not an official Ruby support announcement or an independent benchmark. The live demo and implementation may change, and the cited sources do not yet provide a reproducible public build recipe. The strongest claim supported today is that Ruby has been made to run in one reported ICP canister deployment.