Puter

A full desktop environment running in a browser tab, self-hostable and free. Here’s what it actually delivers — and where it falls short.

TL;DR

• What it is: An open-source “internet OS” — a full desktop environment running in the browser, combining personal cloud storage, built-in productivity apps (OnlyOffice), an app store, and a developer SDK for building browser-based apps [README][3].
• Who it’s for: Privacy-conscious individuals escaping Google Drive/OneDrive; developers wanting a platform to build and publish browser apps; anyone who wants files and a working environment accessible from any device without installing software [README][3].
• Cost savings: Google Workspace starts at $6/user/month and climbs from there. Puter self-hosted runs free on a VPS with 2GB RAM [README].
• Key strength: Nothing else in the self-hosted category delivers an actual desktop experience — taskbar, file manager, OnlyOffice, app store — all in a browser tab. The XDA Developers reviewer confirmed it held up for real document work [3].
• Key weakness: AGPL-3.0 (not MIT), a browser-in-browser ceiling that breaks complex web apps, and limited production track record compared to alternatives like Nextcloud [3][README].

---

What is Puter

The GitHub description calls it “The Internet Computer! Free, Open-Source, and Self-Hostable” [README]. That’s a bolder claim than most self-hosted projects make, and it’s worth unpacking precisely what it delivers.

Puter is a full desktop operating system experience that runs entirely inside a web browser. Not a stripped-down file picker, not a thin client for a remote machine — an actual desktop with a repositionable taskbar, file manager, app store, and bundled productivity software, all running in your browser tab [3][README].

The README describes four distinct use cases [README]:

1. Personal cloud storage — a Dropbox/Google Drive/OneDrive replacement with a fresh interface
2. App platform — build and publish websites, web apps, and games using the Puter SDK
3. Remote desktop environment — a browser-accessible workstation for servers
4. Educational project — open-source community for learning web dev, cloud computing, and distributed systems

That last point partly explains 39,921 GitHub stars [merged profile] — there’s genuine technical interest in how you build something like this, not just in using it as a product.

The license is AGPL-3.0 [README]. This matters more than it might seem: AGPL is more restrictive than MIT. If you embed Puter in your own SaaS or build a commercial product on top of it, AGPL requires you to open-source your code too. For personal self-hosting, this is irrelevant. For commercial use, it’s a real constraint worth checking with a lawyer before committing.

---

Why people choose it

Third-party review coverage of Puter is thin compared to more established self-hosted tools. One substantive hands-on review exists: João Carrasqueira’s April 2026 XDA Developers piece [3], which attempted to use Puter for actual work — including writing the article itself inside Puter.

The conclusion from that test is useful precisely because it’s honest about where the concept succeeds and where it hits walls.

What worked. The reviewer found Puter “impressively close to being fully usable” as a working environment [3]. The bundled OnlyOffice suite handled document work without issues. File persistence across sessions held up — files created months earlier were still present on return [3]. Uploading local files was specifically praised: the file picker inside apps running within Puter shows an upload button prominently, so you upload-and-use in one step rather than opening a separate file manager window, uploading, then switching back [3]. That small integration detail is the kind of thing that separates a thoughtful UX from bolted-together parts.

The App Center includes image manipulation tools, IDEs, and other utilities [3]. The taskbar — movable between left, bottom, or top — the app launcher, and the overall desktop feel are coherent rather than cobbled [3].

What didn’t. The reviewer couldn’t get their CMS editing page to load inside Puter’s browser environment [3]. They could log in and browse articles, but creating or editing them wasn’t possible. This is the fundamental ceiling in the concept: Puter runs inside a browser, and complex web apps inside it are effectively running browser-in-browser. Not every page renders correctly. For document work and general coding, it holds up. For web apps with complex JavaScript event handling, browser-specific APIs, or heavy DOM manipulation — it may not.

The privacy angle drives a meaningful portion of adoption. The self-hosted version means your files sit on your server, not in Google’s or Microsoft’s infrastructure. That’s the same appeal that drives Nextcloud, but Puter adds the bundled-desktop layer that Nextcloud doesn’t attempt [README][3].

---

Features

Based on the README and the XDA Developers hands-on review:

Desktop environment:

• Repositionable taskbar (left, bottom, or top) with app launcher [3]
• File manager with folder structure, right-click context menus, drag-and-drop [3]
• Camera app, notepad, and coding environment included by default [3]
• Full desktop UI — not a web frontend bolted onto a file server [3][README]

Built-in productivity apps:

• OnlyOffice Word Processor (.docx compatible) [3]
• OnlyOffice Spreadsheet [3]
• OnlyOffice Presentation [3]
• Reviewer confirmed these work for real document editing [3]

App store and developer platform:

• App Center with third-party apps: image tools, IDEs, and more [3]
• Dev Center for adding and publishing your own apps [3]
• Developer SDK (puter.js) for building browser-based apps [README]
• Puter CLI for command-line interactions [README]

File management and storage:

• Data persists reliably across sessions [3]
• Integrated file picker in apps with prominent local upload [3]
• Functions as a full cloud storage layer accessible from any browser [README]

Deployment:

• Docker single-command install [README]
• Docker Compose (Linux, macOS, Windows) [README]
• npm start for local development [README]
• Self-hosting documentation with configuration guides [README]

Language support:

• UI translated into Arabic, French, German, Japanese, Chinese, Hindi, Hebrew, Bengali, and many more [README] — broader than most self-hosted tools at this stage.

---

Pricing: SaaS vs self-hosted math

Puter.com hosted service: Puter runs a hosted version at puter.com. Specific pricing tiers for the cloud offering were not available in the data captured for this review. The hosted service is described as a “privacy-first personal cloud” with free access available.

Self-hosted (open-source):

• Software: $0 (AGPL-3.0) [README]
• Minimum VPS: 2GB RAM, 1GB disk [README] — a $4–6/month Hetzner or Contabo instance covers this
• 4GB RAM recommended for comfortable use [README]

Google Workspace for comparison (the named SaaS competitor [merged profile]):

• Google One personal storage: $1.99/month (100GB), $9.99/month (2TB)
• Google Workspace Business Starter: ~$6/user/month
• Business Standard: ~$12/user/month
• Business Plus: ~$18/user/month

The comparison is asymmetric because Puter isn’t just cloud storage — it’s a full desktop environment. A closer framing: a solo user paying $9.99/month for Google One 2TB storage plus Google Docs access spends roughly $120/year. A 4GB RAM Hetzner VPS runs around $6–8/month, or $72–96/year, with unlimited storage bounded only by your disk, no per-user pricing, no Google observing your documents, and the full Puter desktop on top. The math favors self-hosting if you’re already comfortable with Docker. For teams comparing Google Workspace per-seat pricing ($12–18/user/month), the savings scale further.

---

Deployment reality check

The README deployment path is clean for anyone comfortable with Docker [README]:

mkdir puter && cd puter && mkdir -p puter/config puter/data
sudo chown -R 1000:1000 puter
docker run --rm -p 4100:4100 \
  -v `pwd`/puter/config:/etc/puter \
  -v `pwd`/puter/data:/var/puter \
  ghcr.io/heyputer/puter

That launches Puter at http://puter.localhost:4100. Docker Compose is also documented for Linux, macOS, and Windows [README].

System requirements [README]:

• Linux, macOS, or Windows
• 2GB RAM minimum (4GB recommended)
• 1GB free disk space (more depending on stored files)
• Node.js v24+ (if running without Docker)
• npm latest stable

What can go sideways:

• Node.js v24 is more recent than many VPS defaults. If you’re on an older Ubuntu LTS image, you’ll need to add the NodeSource repository before installing.
• puter.localhost works locally via browser localhost handling. For a public-facing deployment, you need a domain, a reverse proxy (nginx or Caddy), and HTTPS configured separately — none of which is included or scripted.
• Browser-in-browser compatibility will trip you up if you rely on specific web apps that use non-standard browser APIs or complex JavaScript event handling [3]. Test your actual workflow before committing.
• AGPL scope is worth checking if you’re deploying for an organization with legal compliance requirements. Some companies blanket-prohibit AGPL software in production regardless of how it’s used.
• Self-hosting documentation exists but the project is young enough that edge cases may require GitHub issue archaeology.

Realistic time estimate: 30–60 minutes to a working local instance via Docker. A public-facing deployment with domain and HTTPS: 1–2 hours for someone who has configured a reverse proxy before. First-timer: budget a full afternoon.

---

Pros and cons

Pros

• Genuinely unique positioning. No other self-hosted project delivers a full desktop OS experience — taskbar, apps, file manager, OnlyOffice — all in a browser tab. This isn’t Nextcloud with a different skin [3][README].
• OnlyOffice built in. Word processor, spreadsheet, and presentation tools included out of the box, confirmed functional for actual writing [3]. Most file-sync tools treat the editor as an add-on or paid integration.
• File persistence that actually works. The reviewer returned months later and found earlier files intact [3]. Basic but important: the storage layer is reliable.
• Developer platform. The App Center, Dev Center, SDK, and CLI mean Puter is also a publishing platform for browser-based apps — not just a personal desktop [README][3].
• Docker deployment is clean. Single-command install with documented variants for all major operating systems [README].
• 39,921 GitHub stars [merged profile]. Active, well-watched project — not an abandoned experiment.
• Multilingual UI. Arabic, French, German, Japanese, Chinese, Hindi, Hebrew, Finnish, Italian, and more [README]. Unusually broad for a project this young.
• Free, open-source, auditable. AGPL-3.0 means the source is readable and you can verify what the software actually does with your data [README].

Cons

• AGPL-3.0, not MIT. Commercial use or embedding in a proprietary product requires open-sourcing your code. This matters for founders who want to build on top of Puter [README].
• Browser-in-browser ceiling. Complex web apps may not render or function correctly inside Puter’s environment [3]. The XDA reviewer couldn’t load their CMS editor [3]. Your workflow’s mileage will vary.
• Limited third-party review record. Only one substantive hands-on review was available at time of writing [3]. Unlike Nextcloud or Seafile, there’s limited production case-study data to draw from.
• Node.js v24 requirement. Newer than most server defaults — adds an upgrade step before deploying on standard VPS images [README].
• No hosted pricing transparency. The puter.com cloud tiers aren’t publicly documented in captured data, making cloud-versus-self-host math harder to verify for the hosted service.
• “Internet OS” is a big claim. The reality is a very good browser-based desktop environment. It cannot run native applications, access local system resources, or escape the sandbox constraints of any browser context. Don’t arrive expecting macOS.
• No enterprise governance features visible. SSO, audit logs, RBAC, admin controls — none appear in the current README or documentation for either the self-hosted or cloud version.

---

Who should use this / who shouldn’t

Use Puter if:

• You’re a solo user paying for Google Drive storage who wants to own that infrastructure, keep your documents private, and get a usable document editing environment (OnlyOffice) in the same package.
• You’re a developer curious about building browser-based apps and want a platform — not just a runtime — to publish them.
• You want a lightweight “cloud computer” accessible from any browser: write documents, edit code, manage files, without installing anything on the client device.
• You’re comfortable with Docker or willing to spend an afternoon getting there.

Skip it (use Nextcloud instead) if:

• You need proven, production-tested self-hosted cloud storage with years of security audits and a mature plugin ecosystem.
• Your team needs real-time collaborative editing, shared calendars, contacts, and granular admin controls.
• AGPL introduces legal complications for your organization.

Skip it (stay on Google Workspace) if:

• Your team is distributed and deeply dependent on Google Docs real-time collaboration, Comments, and version history.
• You have fewer than 5 users and the Google free tier covers your storage needs.
• Nobody on your team has ever touched a Linux terminal and there’s no budget to deploy it once.

Skip it (use Seafile instead) if:

• You need pure file sync with the best performance-to-complexity ratio and don’t need a full desktop environment.

---

Alternatives worth considering

From the merged profile and natural comparisons in the personal cloud category:

• Nextcloud — the most mature self-hosted personal cloud. File sync, OnlyOffice/Collabora integration, calendar, contacts, video calls. AGPL with a larger plugin ecosystem. More enterprise-ready. The obvious choice if you want battle-tested and team-focused rather than “internet OS.”
• Seafile — faster file sync performance than Nextcloud, cleaner interface, less scope creep. No built-in office suite in the community edition. Best for pure file storage and sync without extras.
• ownCloud — Nextcloud’s ancestor. More enterprise-focused, shared codebase history. Less community momentum since the Nextcloud fork.
• Google Drive / Google Workspace — the incumbent. Best third-party integration, excellent real-time collaboration, proven at scale. Closed source, per-user pricing, all your data on Google’s infrastructure.
• Dropbox — simpler file sync, strong native clients. No self-host option. Pricing scales uncomfortably for teams.

The distinctive thing about Puter is that nothing in this list matches its “desktop OS in a browser” concept. Nextcloud and Seafile are file sync tools with document editors bolted on. Puter builds the desktop environment first and treats storage as one layer of it. If that distinction aligns with your actual use case, there’s nothing else like it in the self-hosted space.

---

Bottom line

Puter is the most ambitious concept in the personal cloud category: a full desktop OS — taskbar, apps, file manager, OnlyOffice, app store — running in a browser tab, self-hostable for free. For individuals who want to escape Google Drive’s data collection and pricing while retaining a usable working environment accessible from anywhere, the proposition is real. The XDA Developers reviewer confirmed it holds up for actual document work [3], and 39,921 GitHub stars [merged profile] confirm the technical community has taken notice. The trade-offs are honest: AGPL-3.0 limits commercial use, complex web apps inside the environment may not render correctly [3], and it lacks the production history of Nextcloud. For a privacy-focused individual or small team comfortable with Docker — who wants to own their cloud computer, not rent it — Puter offers something no other self-hosted tool does.

---

Sources

1. João Carrasqueira, XDA Developers — “I tried running a full desktop OS inside a browser tab, and it actually works for real work” (Apr 15, 2026). https://www.xda-developers.com/tried-running-full-desktop-os-inside-browser-actually-works-real-tasks/

Primary sources:

• GitHub repository and README: https://github.com/heyputer/puter (39,921 stars, AGPL-3.0 license)
• Official website: https://puter.com
• App Store: https://apps.puter.com
• Developer documentation: https://developer.puter.com
• CLI: https://github.com/heyputer/puter-cli