Wado

Wado

A Rust-flavored programming language built for WebAssembly and WASI

Open Source
4.4 (8 reviews)

Gallery

About Wado

Wado is a programming language built from the ground up for WebAssembly. It draws syntax and type system ideas from Rust but compiles exclusively to the WebAssembly Component Model and WASI 0.3+. The result is a language that feels familiar to anyone who has written Rust or TypeScript but produces small, portable Wasm modules without a bundled runtime.

The project tackles a specific frustration in the Wasm ecosystem. General purpose languages like Rust or C++ can target WebAssembly, but they drag along runtime machinery and produce binaries larger than they need to be. Wado takes the opposite approach by designing every feature around what WebAssembly actually supports. It uses Wasm GC for garbage collection so modules carry no runtime overhead, keeps the type system aligned with the Component Model, and makes WASI capabilities explicit in function signatures. What you write is close to what ships.

Under the hood, Wado is statically typed with generics, closures, pattern matching, and a trait system. Errors are values through Result and Option types rather than exceptions. There are no macros, no implicit conversions, and no hidden control flow. The language spec calls this predictable design, and it shows in how readable the compiled output tends to be. For debugging, that transparency matters.

One unusual piece of context is the development story. The compiler was written entirely by AI coding agents, a claim the maintainers highlight on the site and in the repository. That makes Wado an interesting test case for agent assisted tooling as much as a practical language. The legible syntax was chosen partly so that future agents could work in it easily, and the project documentation is explicit about that intent.

Tooling includes a browser based playground that compiles and runs code without installing anything, a VS Code extension with language server support, and pre built binaries for Linux, macOS, and Windows. The playground requires Chrome or Chromium 137+ because it relies on JavaScript Promise Integration, a relatively new browser capability. For local work, you can install via a curl command or build from source with Cargo.

Wado is open source under the MIT license. The repository is active, with documentation covering the language spec, a cheatsheet for common patterns, and performance dashboards. The audience is developers embedding small, type safe Wasm modules into browsers, edge runtimes, or plugin systems where binary size and predictability outweigh the ecosystem maturity of established languages. It is still experimental, and the maintainers are clear about that, but the core feature set works and the community is growing around it.

Key Features

  • Static typing with generics and pattern matching
  • Compiles to WebAssembly Component Model
  • Browser based playground and editor
  • VS Code extension with LSP support
  • No runtime overhead via Wasm GC
  • Explicit WASI capabilities in types

Pros & Cons

What we like

  • Produces small Wasm binaries without bundled runtime
  • Predictable design with no hidden control flow
  • Open source under MIT license
  • Works in browser with no install required

Room for improvement

  • Experimental status with limited ecosystem maturity
  • Targets only WebAssembly, not general purpose
  • Playground requires Chrome 137+ for JSPI
  • Smaller community than established Wasm languages

Frequently Asked Questions

What is Wado?
Wado is a statically typed programming language that compiles exclusively to WebAssembly and WASI. It borrows syntax ideas from Rust and TypeScript but targets only the WebAssembly Component Model, producing small binaries with no runtime overhead.
Is Wado free to use?
Yes. Wado is open source under the MIT license. The compiler, playground, VS Code extension, and all documentation are freely available.
Who is Wado for?
Developers embedding small, type safe WebAssembly modules into browsers, edge functions, or plugin systems. It suits anyone who wants predictable Wasm output without the overhead of general purpose language runtimes.
How stable is Wado?
The project is experimental but functional. Core language features work for real use cases, and the maintainers publish a language spec and performance dashboards. Full maturity depends on broader WebAssembly ecosystem developments.

Best For

Embedding type safe Wasm modules in browsersBuilding WASI plugins for edge runtimesPrototyping WebAssembly components quicklyLearning Wasm internals through a legible language

Featured in

Alternatives to Wado

View all

Reviews (8)

S
Sana Rossi Verified

Decent with some rough edges

Started using Wado casually, now it is pinned in my dock. What stands out is how it handles open source under mit license. Found it works best for building wasi plugins for edge runtimes. My only gripe is experimental status with limited ecosystem maturity. Easy yes for anyone weighing the same trade offs.

4/2/2026 14 found this helpful
J
Jordan Okafor

Finally something that fits

Started using Wado casually, now it is pinned in my dock. Their take on produces small wasm binaries without bundled runtime is genuinely good. The thing I keep coming back to is how reliable it is. Found it works best for embedding type safe wasm modules in browsers. Easy yes for anyone weighing the same trade offs.

7/11/2026 12 found this helpful
N
Nia Lund Verified

Two months in, no regrets

Wado has quietly become part of my daily flow. It does what it says, which is rarer than it should be. Mostly using it for building wasi plugins for edge runtimes. Hard to imagine going back to my old setup.

6/24/2026 9 found this helpful
M
Mia Lima

It just works

Tried Wado on a side project first, then rolled it out everywhere. Their take on browser based playground and editor is genuinely good. Glad I made the switch.

6/25/2026 6 found this helpful
T
Theo Gupta Verified

Quietly excellent

Three months of Wado later, here is what holds up. Got real value out of produces small wasm binaries without bundled runtime. Worth it for what I get out of it.

5/6/2026 6 found this helpful
M
Mia Lund

Two months in, no regrets

Came to Wado after getting frustrated with what I had before. Got real value out of no runtime overhead via wasm gc. Worth it for what I get out of it.

6/8/2026 5 found this helpful
R
Riley Martin Verified

Two months in, no regrets

Hadn't planned on switching, but Wado was hard to ignore. The thing I keep coming back to is how reliable it is. Found it works best for learning wasm internals through a legible language.

5/10/2026 3 found this helpful
N
Nia Zhou

Recommended without reservation

Three months of Wado later, here is what holds up. Support actually answered when I had a question, which surprised me. Setup was painless and I was productive the same day. Found it works best for prototyping webassembly components quickly.

3/24/2026 3 found this helpful