File
SMF·ICLOUD-PLUS
Received on
31.07.2026
Reviewed on
28.09.2026
Exhibits annexed
3
Questions
4

SMF·ICLOUD-PLUS

Can a prompt replace iCloud Plus?

Cloud storage & backup — device-integrated storage

Not yet Verdict recorded on 28.09.2026 · Verified on 31.07.2026
Price
$9.99/moSource: www.apple.com · Checked on July 31, 2026
Per year
$119.88
Build time
One sitting
Votes
0 votes
YesAlmostNot yet (checked)

Exhibit tracking slip

Exhibit A The prompt
Exhibit B What you lose
Exhibit C Why people still pay: operating-system integration
Exhibit Q Questions

Verdict

iCloud+ is not really a storage product, it is an operating-system feature with a bill: device backups, the photo library, keychain sync and Private Relay, all wired into places no third party can reach. That integration is not something code replaces. What a personal build can do is meet the phone where it is, through the open protocols Apple's own apps already speak, and get contacts, calendars and files onto the device without an app.

Exhibit B — What you lose

Exhibit A — The prompt

Received on31.07.2026
Build a personal server that the phone already knows how to talk to. No app, no installation — just open protocols.

Stack: your choice, Postgres, Docker Compose, and a real domain with valid TLS, because Apple's clients refuse anything else. Use existing CalDAV, CardDAV and WebDAV server libraries rather than implementing the protocols by hand.

Three endpoints:
1. **CardDAV** — contacts, read-write, with vCard round-tripping that preserves photos and custom fields. Editing a contact on the phone must write back correctly.
2. **CalDAV** — calendars, read-write, with recurrence, exceptions, alarms and timezones. Recurrence is where these implementations break; test a weekly series with two modified instances and one deletion.
3. **WebDAV** — files, mountable from macOS Finder and reachable from the iOS Files app.

Discovery matters more than it looks: implement `.well-known/caldav` and `.well-known/carddav` redirects and the principal-URL discovery flow, so a user types a server address and an application password rather than five URLs. Half the perceived difficulty of self-hosting this is discovery not working.

Authentication: per-device application passwords, listed, named and individually revocable, never the account password. A lost phone should be one click to cut off.

A plain web interface for the same data, so contacts and calendars are editable from a desktop browser too.

Be explicit in the README about what is deliberately absent: device backup, the photo library, and keychain sync are not open protocols and are not attempted.

Write tests for the vCard round trip including a photo and a custom field, for CalDAV recurrence with modified and deleted instances, and for a revoked application password immediately failing.

Do not attempt device backup, photo library sync, or password sync.

Opening prefills the prompt — press enter to run it.

Exhibit B — What you lose

  • B.1 whole-device backup and restore to a new phone
  • B.2 the Photos library with its sync, sharing and on-device search
  • B.3 keychain and password sync across devices
  • B.4 Private Relay and Hide My Email
  • B.5 the invisibility — it works without anyone configuring anything

Prior art

Exhibit C — Why people still pay: operating-system integration

Because it is already switched on and it restores a lost phone in one step. Ten dollars for the family's photos and the ability to walk out of a shop with a working replacement device is not a hard sale.

Questions

Do Apple's built-in apps really sync against a third-party server?

Yes — Contacts and Calendar speak CardDAV and CalDAV natively, and Files speaks WebDAV. Add the account in settings and it behaves like any other. That is the entire reason this build is worth doing.

What breaks most often?

Discovery and recurrence. Discovery because clients expect specific well-known redirects, and recurrence because a repeating event with edited and deleted instances has a fiddly representation that many servers get subtly wrong.

Why per-device application passwords?

Because a phone stores the credential permanently, and losing the phone should not mean rotating the password on every other device. Named, individually revocable credentials make that a single click.

How do I get my data out of iCloud?

Apple's privacy portal exports contacts, calendars, photos and Drive files. Device backups are the exception — they are not exportable in any usable form, which is precisely why that half of the product is not rebuildable.

Receipt

Already built this yourself?