Cloud storage decision

MEGA Pro I

A single developer can build a minimal zero-knowledge file store (uploads, client-side encryption, links) but reproducing MEGA's global scale, multi-platform apps, bundled VPN/password-manager products and production-grade infra is not realistic for a small DIY effort.

Visit website
Subscription$10.99/month
Initial build80 hours
Monthly upkeep8 hours + $10
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

  • Allow a user to upload a file from a browser, encrypt it client-side, store the encrypted blob in object storage, persist searchable metadata on a server, and let the user generate a shareable link that others can use to download and decrypt the file.

What it still won’t have

  • MEGA multi-platform desktop and mobile apps
  • Bundled VPN and password-manager products
  • Global scalable object storage and large-scale infrastructure
  • Polished sync clients, real-time collaboration and meeting features

What remains hard

  • Infrastructure at scaleObject storage Fully scalable S3 compatible storage
  • Brand trustMillions of people trust us
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 minimal zero-knowledge cloud storage web app using React for the frontend, Node.js (Express) for the backend, Postgres for metadata, and an S3-compatible object store for blobs. In scope: client-side encryption/decryption (WebCrypto), streaming uploads/downloads of encrypted blobs to S3, metadata CRUD in Postgres, user auth (email + password), shareable links with optional password and expiry, and a simple React UI to upload, list, generate links, and download. Out of scope: mobile/desktop native apps, VPN, password manager, advanced sync clients, multi-region replication, enterprise billing. Include unit and integration tests for crypto, upload/download, and link expiry paths; log and surface clear error messages for failed uploads, decryption errors, and expired links.
How we checked4 sources · 3/3 runs agreed · evidence score 61

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 4 cited sources+3
  • 3/3 assessment runs agreed+4
  • Hard moats found in the evidence-3
  • Evidence score61

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 · 4

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! Price not confirmed on the page — this pricing page renders its price in the browser✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 2 moats quoted from the page