Cloud storage decision
iCloud Plus
A competent developer can build a useful, smaller iCloud-like file sync and sharing service, but reproducing Apple’s OS integration, global scale, and ecosystem features is impractical for a DIY replacement.
Visit website↗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 and sync user files between devices and a central cloud store, with web access and basic sharing links.
What it still won’t have
- Deep OS-level integration (automatic device/system backups and seamless Finder/iOS Files integration)
- Apple-managed global scale, redundancy, and CDN optimizations
- Family sharing, bundled Apple ecosystem features, and device-specific privacy features
- Official Apple support and guaranteed regional availability
What remains hard
- Product polish and ongoing maintenance
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 minimal cloud-storage + file-sync service using Node.js (Express), Postgres for metadata, and an S3-compatible backend for file blobs; provide a React web UI. In scope: user signup/login, authenticated file upload/download, per-file metadata in Postgres, a change-tracking endpoint for clients to poll for updates, generation of expiring public share links, background worker to delete expired links, and basic conflict-resolution policy (last-writer-wins). Out of scope: native macOS/iOS filesystem integrations, device-level encrypted backups, family-sharing billing, and global CDN optimization. Include error handling, input validation, end-to-end tests for upload/download and share links, and deployment instructions for Docker + a cloud VM and S3 bucket.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 cited sources+3
- Evidence score60
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 · 3
Every page the run actually retrieved.
- official productApple
- open sourcecloudreve/cloudreve
- open sourcehaiwen/seafile
Integrity checks
What held up, and what did not.
