Can I vibe code Dropbox?
Your files, synced everywhere, shared with anyone.
Sync is the graveyard of confident weekend projects. The demo — upload file, list files, download file — is an afternoon; the product is conflict resolution when two devices edit offline, delta sync of gigabyte files, a decade of client daemons that never corrupt anything, and restore-from-anywhere reliability your family photos deserve. Open source already fought this war: Syncthing for device sync and managed object storage for cloud copies get you sovereignty without betting your data on your own bug tracker.
Build my file sovereignty setup without writing sync code. Part 1 (assembly): document Syncthing across my laptop/desktop/phone with a folder plan and conflict-handling notes. Part 2 (build): a personal file web app over S3-compatible object storage — browse folders, upload/download, image/PDF previews, and unguessable share links with optional expiry and password, plus a nightly script syncing my Syncthing folder to the bucket (rclone) for offsite copies. Admin-only auth, Next.js, deployable to Vercel. README states plainly: Syncthing does sync, the bucket does backup, my app does browsing and sharing — no custom sync logic anywhere.
Honest path: Syncthing across your devices plus a vibe-coded web UI over object storage for share-links and browsing — sovereignty without homemade sync.
- Battle-tested conflict resolution and file versioning
- Client daemons trusted on every OS for a decade
- Selective sync, smart sync, and bandwidth micro-optimizations
- The share-link ubiquity normal humans recognize
It's the reliability, stupid: people pay Dropbox to never think about the scenario where sync eats the family photos.
A prompt is the first move, not the whole game. Course 01 teaches you to take a prompt like this one to a shipped, working app — reviewing, correcting, and steering the agent the whole way.
Start Course 01 →