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↗$11.99/mo
$144/yr
Read off the official pricing page.
$50one-off24 h to build
$8/mo4 h/mo upkeep
On cash alone, building overtakes the subscription at 2 seats.
The code exists. It is not what you are paying for.
This project is real, published, and does the core job — and this page still says keep paying. What the subscription buys is conflict-free synchronization, data durability and secure sharing, and none of that ships in a repository. Fork it anyway if you want to. Go in knowing what it does not carry. What stays hard ↓ · All Dropbox alternatives, with the arithmetic →
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
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 2 seats.
Money you would actually spend
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
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.
