Nicheloom visits: 62,403 all-time · 8,415 in the last 7 days

The opportunity tracker for new startups.

Today: 2,085 launches · Niche of the day: browser-based utility tools · See what launched today →

Waputer

The WebAssembly Computer

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

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.

HN · launched Apr 17, 2026 · 7 upvotes (top 61%) · 0 views

Niche: browser code execution environments · 40 launches, 4 in the last 7 days · Explore this niche →

Category and tags

  • Horizontal
  • Model & infra
  • Developer
  • Not AI
  • Hobby / open-source project

Visit website ↗ Source listing ↗

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 : 73 launches clear the similarity bar, closest 8 shown.

Attention rank: #37 of 74 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 136 days after the earliest competitor.

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.