Cloud storage decision

Dropbox

A file uploader is easy; trustworthy multi-device sync is not. Conflict resolution, offline behavior, recovery, sharing security, and data durability justify the subscription.

Visit website
Subscription$11.99/month ✓ verified
Initial build24 hours
Monthly upkeep4 hours + $8
EvidenceAn open-source build exists

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.

What a replacement has to do

  • Browser upload and download
  • Folders
  • Share links
  • Simple version history

What it still won’t have

  • Native background sync
  • Conflict resolution
  • Offline files
  • Recovery guarantees
  • Mature security controls

What remains hard

  • Conflict-free synchronization
  • Data durability
  • Secure sharing
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 2 seats.

Paid seatsseats

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

Time you would spend

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a small private browser-based file vault, not a Dropbox sync client.

Use Astro server rendering, TypeScript, PostgreSQL, and S3-compatible object storage.
Require email magic-link authentication for one owner.
Support folder creation, upload, download, rename, move, delete, and restore.
Generate expiring signed links and never expose bucket credentials.
Keep the last five versions of a file and a 30-day trash.
Hash uploads, reject dangerous file names, and enforce configurable size limits.
Add an append-only audit log and a storage-usage screen.
Do not build desktop sync, offline support, collaboration, or public permanent links.
Add tests for authorization and signed-link expiry.
Document backups and the limits of this replacement.
How we checkedno sources · evidence score 34