Waputer
The WebAssembly Computer
Details
- External ID
- 47808554
- Source
- HN
- Company
- —
- Product
- Waputer
- Website domain
- waputer.app
- Launched
- April 17, 2026
- Cohort
- —
- Upvotes
- 7
- Upvotes percentile
- 0.38817480719794345
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
Waputer is an operating system that runs entirely in the browser. When you visit the website at https://waputer.app, a kernel written in JavaScript sets up a filesystem and launches a WebAssembly program, which in turn talks to the kernel to handle the display and input. A purely terminal-based version is at https://waputer.dev.My original intention was to create programs that run in the browser that have a lot more in common with the desktop. The traditional "hello world" program is not really suited for the web. Waputer changes that. The GitHub repo at https://github.com/waputer/docs gives a very brief overview of compiling a C program and running it on Waputer. There is a blog available from the main site that has a long-form explanation of Waputer and my motivations if you want some additional reading.
Enrichment
- Theme
- audio and music production tools
- Vertical
- Horizontal
- Function
- Hardware & robotics
- Audience
- Developer
- AI stance
- Not AI
- Project type
- Hobby / open-source project
- Normalized one-liner
- webassembly virtual machine
- Manually corrected
- False
Could you build this?
No Building an in-browser operating system kernel in JavaScript/WASM with custom virtual filesystems and display/input subsystems requires deep low-level systems programming expertise.
What it would actually take: The system involves a custom JS kernel implementing POSIX-like system calls, an in-memory virtual filesystem, and a WASM runtime executor communicating via shared memory buffers and an event loop. The hard parts are memory management, trap handling, virtualized I/O devices, and compiling standard C/Rust runtimes to interact with the custom JS syscall interface. This demands advanced systems architecture knowledge, compilers, and WebAssembly internals.
Discussion
2 comments analyzed.
Concerns raised: Architecture unclear - relationship between Waputer, School, Terminal, and Editor components, Workflow documentation incomplete - where exactly do WASM files run, Package system and publishing APIs not yet documented
Feature requests: Documentation for package creation and publishing APIs, Clarify typical workflow and architecture in guides, Integration of package publishing directly into Nako
Competitors
Other products that read as similar to this one — 42 launches clear the similarity bar, closest 8 shown.
Attention rank: #23 of 43 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 136 days after the earliest competitor.
- Firefox in WebAssembly · hn · 2026-07-15 · 273 upvotes · similarity 0.48
- Codex CLI compiled to WASM running in the browser · hn · 2026-08-19 · 5 upvotes · similarity 0.46
- Building a Rust-ish programming language with 100% coding agents: Wado · hn · 2026-07-17 · 5 upvotes · similarity 0.43
- FFmpeg WebCLI · hn · 2026-06-04 · 86 upvotes · similarity 0.41
- Ferroterm · hn · 2026-07-05 · 6 upvotes · similarity 0.40
- Robotics runtime in the browser (flight controller, WebAssembly) · hn · 2026-03-09 · 7 upvotes · similarity 0.40
- ZenCompiler · ph · 2026-09-15 · 1 upvotes · similarity 0.39
- BrowserCode · hn · 2026-05-07 · 6 upvotes · similarity 0.39
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a hardware & robotics tool for Fintech yet.