Discofork
Repository brief

HeyPuter/puter

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:58:18.267Z
1mo ago

HeyPuter/puter

HeyPuter/puter is an actively maintained, large open-source "Internet OS" / browser desktop project that is free, self-hostable, and positioned as a personal cloud and web app platform. It has strong adoption signals from its 40k+ stars and 3.5k+ forks, and recent commits show ongoing feature and UX work. Forks are most interesting if you care about self-hostable cloud-desktop systems, browser-based app platforms, or a Node/TypeScript codebase with room for substantial product and infrastructure changes.

GitHub
Loading tags...
Stars40,093
Forks3,581
Default branchmain
Last pushed2026-03-30T14:26:35Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if you want its added AI/chat features and are willing to own a materially divergent codebase. Choose upstream if you want the safest path, broader feature coverage, and easier long-term maintenance.

Choose this fork only if you want a custom Puter variant and accept substantial upkeep. If you want the latest upstream fixes and a lower-risk self-hosted base, the main project is the better choice.

Choose this fork only if you want its older customizations and are prepared to maintain a large divergence. If you want an actively maintained Puter install with the newest fixes and features, upstream is the better default.

Choose this fork only if its custom app/runtime and domain workflow changes are specifically useful to you. For most adopters, upstream is the safer default because it is much more current and likely has fewer compatibility and maintenance risks.

Prefer this fork only if its added WebDAV/app-launch/documentation changes are specifically valuable to you. If you want the newest Puter features, lower maintenance, or easier upstream compatibility, upstream is the better choice.

Choose this fork only if its worker/auth/runtime changes are the point. For most adopters, upstream is safer and more current; this fork is for people willing to trade freshness and compatibility for deeper customization.

Choose this fork only if the iframe/security changes and custom UI direction matter more than staying current with upstream. If you want an actively maintained Internet OS platform, upstream is the safer default.

Choose this fork if you want a strongly opinionated, platform-oriented Puter branch and are prepared to own upstream drift. Choose upstream instead if you want the more actively maintained, broadly adopted, lower-risk base.

Choose this fork if you want a more experimental, PC2-specific Puter base with custom integrations and hardware/transport work. Choose upstream if you want the broadest feature parity, lower maintenance cost, and the newest Puter fixes with less merge friction.

Choose this fork only if you want an upstream-faithful starting point and are comfortable carrying the 56-commit lag yourself. If you want current features or an actively evolving distribution, upstream is the better default.