Cloud storage decision

Dropbox Plus

A competent developer can build a useful single-user cloud-storage replacement (upload, share links, previews, basic versioning) in about a week, but cannot cheaply reproduce Dropbox’s desktop sync client, global scale, enterprise security, AI integrations, or brand/support advantages.

Visit website
Subscription$9.99/month ✓ verified
Initial build30 hours
Monthly upkeep8 hours + $25
Evidence3/3 runs agree

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

  • Upload files to cloud storage, generate shareable links, preview common file types in-browser, and restore recent versions

What it still won’t have

  • Native desktop background sync client with selective sync and advanced offline handling
  • Massive global scale, high-volume API capacity and optimizations
  • Enterprise-grade security & compliance features (advanced key management, SSO, EKM)
  • Integrated advanced productivity and AI features (Dash integrations, built-in AI summaries)
  • Brand trust, ecosystem integrations, and large-user support network

What remains hard

  • Brand trustJoin the over 700 million registered users who trust Dropbox
  • Infrastructure at scale1 billion API calls/month for data transport partners
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 3 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 minimal Dropbox-like web service using React frontend, Node/Express backend, Postgres for metadata, and AWS S3 for object storage. Implement: user signup/login (Auth0 or JWT), file upload with server-side multipart to S3, metadata and version records in Postgres, expiring signed URLs for downloads and previews, shareable link generation with permission control, and a 30-day restore endpoint. Out of scope: native desktop sync client, enterprise SSO/EKM, large-scale multi-region replication. Include error handling, input validation, automated unit/integration tests, and deployment scripts for a single VM plus S3.
How we checked5 sources · 3/3 runs agreed · evidence score 64

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 5 cited sources+3
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • Hard moats found in the evidence-3
  • Evidence score64

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.

How scoring works →

Cited sources · 5

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 2 moats quoted from the page