Every app I build starts the same way. I went looking for it, and it wasn't there. Sada writes a small file into iCloud Drive on one Mac and waits for the other to notice it and reply. It times each direction separately, so instead of "sync is unhappy" you find out which direction is the broken one. If the file goes missing, it reads the sync queue to tell a stuck upload from a stuck download. Sada is Arabic for echo, which is the whole idea. It checks both machines too: same Apple Account, iCloud Drive on, sync services alive, iCloud storage and free disk, Apple's servers reachable, clocks in agreement. Fix Automatically restarts the sync services, prompts stalled downloads, clears old test files, and asks the copy of Sada on the other Mac to repair its own side, then re-runs the whole test to prove the repair worked. Anything needing System Settings or a password stays step-by-step guidance, with a button that opens the exact pane. It needs two Macs on the same Apple Account, because it works by timing an echo between them. One Mac alone cannot be tested. I have a MacBook Air and a Mac mini on one account, and I wanted to know why sync between them was misbehaving. macOS gives you a vague status, and the common advice is to sign out and back in and hope. Neither tells you where it broke. That gap is the whole product: I'm not building a better version of something crowded, I'm building the thing I already tried and failed to buy. Free, no account, no telemetry. macOS 14+, universal, notarized, with built-in updates. It is a direct download rather than a Mac App Store app, since the sandbox blocks restarting the sync services and reading iCloud storage, which is most of what it does, so direct download fits. Tell me what it found on your Macs, or where it got it wrong: support@appsbymo.app reaches me and I answer it myself.

Sada

The iCloud sync doctor for your two Macs.

The iCloud sync doctor for your two Macs.