I get it, and I'm sorry that I cake across as insensitive to that. Reading my comment again, I can see that I sounded just like an "Arch Master Race" Looney. On the other hand, none of us knew how to self-host, but each of the ones that do it now, learned. It's about privacy and how much you want to move away from our dependence on big tech (privacy). You could start with something as simple as SyncThing on your computer, and slowly scale from there as you learn. I would even argue that you could use something like sync.com, only to start at least segregating who could potentially have your data, my understanding is that they run a zero-knowledge model, even for the free tier. More importantly, suggesting to others to use Apple, Google, Microsoft or any of the other huge offenders out there, you could be looked down upon as a troll by in these privacy instances. I hope you can get away from Apple's grasp as much as possible at some point, and feel free to come and ask, many of us have already walked the rockiest roads to that freedom, and we're more than willing to share and help. Good luck.

I question whether a lot of people even need sync.

Passwords in general don't change for long periods of time. Really the only rationale for doing so is confirmed or suspected compromise (two-factor processes make this rarer still). It doesn't strike me that an almost permanently static input merits regular synchronization.

The alternative is doing a one-off manual sync (copy and paste) between two local DBs, then locally moving one of them to the target device. Zero online connectivity has to dramatically reduce attack surface. Is five minutes' maintenance per year an unacceptable convenience penalty to pay?