Puter — Open-Source Cloud Desktop in Your Browser

What it is

Puter is an open-source cloud desktop operating system that runs in your web browser. It provides a full desktop environment with a file system, app ecosystem, and developer APIs. You can self-host it on your own server or use the public instance. Puter aims to be a privacy-first alternative to cloud services like Google Drive and Dropbox by keeping your data on infrastructure you control.

It targets developers who want a web-based OS for remote access, users who want a privacy-first cloud desktop, and teams building web apps that need filesystem and storage APIs.

How it saves time or tokens

Puter provides a complete cloud environment without stitching together multiple services. You get file storage, a desktop UI, and developer APIs from one Docker command. For AI workflows, you can use Puter as a sandboxed environment to test web apps, manage files remotely, or provide users with a browser-based workspace. The JavaScript SDK lets you integrate Puter's file system and auth into your own applications.

How to use

1. Start Puter with Docker:

docker run --rm -p 4100:4100 ghcr.io/heyputer/puter

1. Open http://localhost:4100 in your browser. Your cloud desktop is ready.

1. For development from source:

git clone https://github.com/HeyPuter/puter.git
cd puter && npm install && npm start

Example

// Using Puter.js SDK in a web app
// Include <script src='https://js.puter.com/v2/'></script>

// Write a file to the cloud
await puter.fs.write('notes/ai-log.txt', 'Model output saved at ' + new Date());

// Read it back
const content = await puter.fs.read('notes/ai-log.txt');
console.log(content.toString());

// Use key-value store
await puter.kv.set('last_model', 'claude-sonnet');
const model = await puter.kv.get('last_model');

Related on TokRepo

• Self-hosted tools -- More self-hostable infrastructure for developers
• AI tools for automation -- Automation and productivity tools

Common pitfalls

• Puter runs in the browser, so performance depends on the host server and network speed. Large file operations may be slower than native filesystem access.
• The app ecosystem is growing but smaller than established platforms. Check if the apps you need are available before migrating workflows.
• Self-hosting requires securing your instance with HTTPS and authentication if exposed to the internet. The default configuration is for local development.