Kyushu – A self-hostable WASM sandbox for JavaScript workers: VALIDATE, 62/100 | Ideas Lab

A self-hosted sandbox for running untrusted JavaScript code safely using WebAssembly, targeting developers who need worker isolation without cloud dependencies.

The pain

Developers running user-submitted or third-party JavaScript code face security risks. Existing solutions require cloud infrastructure (AWS Lambda, Cloudflare Workers) or lack fine-grained resource controls. Self-hosting options are fragmented or incomplete.

The gap

No clear market leader in self-hostable, WASM-based JavaScript sandboxing. The space sits between niche (academic projects) and enterprise (expensive platforms). Unclear who pays and how much they value isolation over convenience.

Build angle

Start by identifying a specific use case with acute pain: plugin systems for SaaS apps, user-generated content execution, or AI agent sandboxing. Build the minimal sandbox, get 10 paying customers, then expand. Don't build a general-purpose tool hoping someone finds it useful.

Strengths

Technical differentiation: WASM sandboxing is genuinely harder than alternatives and creates defensibility
Self-hosting appeal: Avoids vendor lock-in and data residency concerns that matter to enterprises
Growing demand: AI agents, plugin ecosystems, and edge computing increase sandbox use cases
Low marginal cost: Once built, distribution is cheap

Risks

Unclear customer segment: 'JavaScript workers' is too broad. Who specifically buys this and why?
Competing free options: Deno Deploy, Cloudflare Workers, and open-source projects (Wasmer, Wasmtime) offer similar functionality
Execution complexity: WASM sandboxing requires deep systems knowledge; bugs are security vulnerabilities
Chicken-and-egg: Needs ecosystem (libraries, tooling, docs) to be useful, but ecosystem only grows with users
Sales friction: Developer tools require either viral adoption or direct sales to engineering teams, both slow

Fly Labs Method

Is the pain real, is there a gap, is it the right time, can one person build it.

62

Value Equation

Dream outcome and how likely it feels, against the time and effort it costs.

45

One-Person Business

Curiosity pull, identity fit, and a path from free value to paid for a solo creator.

58

Viral Frameworks

Hook strength, shareability, and how cheaply it can be tested.

71

Builder Lens

Evidence the problem exists, timing, defensibility, and a model that fits on a napkin.

64

Five lenses, one composite. How scoring works

The angle

Start by identifying a specific use case with acute pain: plugin systems for SaaS apps, user-generated content execution, or AI agent sandboxing. Build the minimal sandbox, get 10 paying customers, then expand. Don't build a general-purpose tool hoping someone finds it useful.

No market research recorded for this idea yet.

SaaS founders lack a platform for finding partners and organizing joint advertising campaigns with bloggers to reduce costs by 5 times while maintaining the same reach

Other

BUILD

85FL score

Founders waste hours daily on repetitive tasks that AI could automate instantly

Founders spend excessive time on routine tasks that AI could complete in minutes, but no simple, purpose-built tool exists to handle them automatically without complex setup.

Other

BUILD

82FL score

Owners of modern Macs can't launch old games due to complex instructions involving emulators and file conversion

Other

BUILD

79FL score

All Other ideas