Company profile · 4 min read
Wavedash: Zero-install game distribution with a visible developer economics pitch
Wavedash brings games to the browser without downloads and offers hosting, distribution, game services and a company-stated 10% in-game purchase fee.
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
Published · Updated
Wavedash is a zero-install game distribution platform. It fits studios that want browser reach and a simpler path from game build to player, not another game-development tool.
What it does
Wavedash’s homepage lets players open games in a browser without downloads or installation. The current public catalogue includes games across action, adventure, simulation and other tags, with accounts for cloud saves, achievements and friends.
For developers, the platform page says Wavedash handles hosting, distribution, cloud saves, multiplayer, achievements and analytics. It supports engines including Unity, Godot, Unreal and Three.js, with one import and minimal code changes according to the company. The pitch is simple: remove the install step and take the game to any device with a browser.
Why I’d look closer
The economics are more visible than the average platform pitch. Wavedash says it charges 10% of in-game purchases, compared with the 30% fee it lists for the App Store, Google Play and Steam, and 12% for Epic. It also describes a Creator Fund based on eligible playtime and says the first build can go live without an upfront platform charge.
Those are company-stated terms, not a guarantee of player reach or revenue. The distribution question is still the important one: does browser access create enough additional discovery and conversion to offset porting work, support, performance and platform dependence?
The founder context is relevant. YC describes Kyler Blue as a former Tenor product leader; the launch record says he helped build Tenor’s GIF Keyboard and API before Google acquired it. The other founders bring engineering and game/production experience. That background fits a distribution problem: getting content into places people already are.
What could make it the wrong choice
Zero-install does not mean zero friction. Browser performance, controller support, mobile behavior, save compatibility and game-specific networking still matter. A studio should test its actual title, not infer quality from the platform promise.
The revenue split also deserves careful reading. The Creator Fund depends on eligible playtime, with manipulation and fraud excluded. The platform page does not establish how much a typical game earns or how much discovery Wavedash supplies.
My editorial take
I would shortlist Wavedash for a studio whose main problem is distribution friction: large downloads, device compatibility or a desire to reach players through a link. I would not treat the 10% fee as the whole business case. The real question is whether browser convenience creates enough qualified playtime to matter.
Quick facts
| Field | Sourced detail |
|---|---|
| Product | Browser game platform with no-download play |
| Buyers | Game studios and developers |
| Developer fee | Company says 10% of in-game purchases |
| Developer services | Hosting, distribution, saves, multiplayer, achievements and analytics, company-described |
| Main gate | Actual title performance, player discovery and playtime economics |
Sources checked
| Source | Checked |
|---|---|
| YC profile | 2026-09-19 |
| Wavedash homepage | 2026-09-19 |
| Developer page | 2026-09-19 |
| YC launch | 2026-09-19 |
Cohort context
Wavedash is listed in Spring 2025. In our 2026-09-18 directory snapshot, 7 of 143 listed companies in that cohort have YC’s primary industry label Consumer (4.9%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.
Public website snapshot
Observed 2026-09-19T16:15:58.042Z in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.
| Signal | Homepage observation |
|---|---|
| Product description metadata | Observed |
| Canonical link | Observed |
| H1 or H2 heading | Observed |
| Typed structured data | Observed |
| Docs/developer link | Observed |
| Pricing link | Not observed in this response |
| llms.txt link | Not observed in this response |
| Markdown alternate | Not observed in this response |
Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.
About the author
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.
First1000 ↗ · X ↗