There isn’t much of an issue with trust because the notes are end-to-end encrypted. That is, the notes are stored on server encrypted and you have the key.
As long as Obsidian is not open source and has reproducible builds that is not really helping as it comes down to a matter of trust in the devs doing their jobs correctly with no possibility to verify the encryption, no?
We use the following solution at work because we are not allowed to use random third party syncs (no offense) either:
- Vault on Sharepoint
- Every user keeps a local copy of the vault folder on Sharepoint as “always available” via OneDrive
- Manual conflict resolution for notes
- Conflicts that arise for vault-settings are ignored
So this boils down to trusting M$ with the data - which is already the case with other data, so no additional open flank - and using bog-standard tools like OneDrive and Sharepoint. It’s a rather ugly solution, especially because there are lots of conflicting copies for settings and data in the .obsidian folder but it still works fine. For the very unusual case where two users edit the same file at the same time, we do manual resolution of the conflicting versions.
With few users (<10) this works, but it can not scale and you can not do collaborative note-taking as in OneNote. But for the moment this is fine. 