Anytype is built on the open-source AnySync protocol: a local-first protocol based on CRDTs. Users of Anytype can create spaces - graph-based databases with modular UI. Each space has unique access rights. Today, Anytype's beta is in single-player mode. Multiplayer mode, which will support local-first collaboration between multiple users, will be launched in the first half of 2024.
Anytype fulfils the seven ideals of local first software from here - https://www.inkandswitch.com/local-first/ , our team felt these things are important to all of us:
• No spinners: your work at your fingertips. Anytype keeps the primary copy of each space on the local device. Data synchronization with other devices happens quietly in the background - allowing you to operate with your data at your fingertips.
• Your work is not trapped on one device. Users can easily work on different devices. Each device keeps data in local storage, synchronisation between devices happens in the background using CRDTs to resolve conflicts.
• The network is optional. Everything works offline. Data synchronization need not necessarily go via the Internet: AnySync allows users to sync data via local WiFi networks. Still, there is a role for the network - it works as additional backup, helps with peer discovery and especially solves the closed-laptop problem (you made changes on laptop, when your phone was offline, the changes can either sync when both devices are online or via backup node).
• Seamless collaboration with your colleagues. Achieving this goal is one of the biggest challenges in realizing local-first software, but we believe with CRDTs it's possible. AnySync supports it & we will release multiplayer version soon.
• The Long Now. Because you have a local-first application, you can use it on your computer even if the software author disappears. This is also strengthened by open data standards and open code.
• Security and privacy by default. AnySync uses end-to-end encryption so that backup nodes store encrypted data that they cannot read. Conflict resolution happens on-device. The keys are controlled by users.
• You retain ultimate ownership and control. Users control encryption keys; there is no central registry of users (we don’t ask even your email). We added an option to self-host your backup to support full autonomy of users from the network.
I don't know if I can get past the faux-open-source-community appearance, however. In particular, there's an invitation to contribute to the project, and I don't understand why I would sign a CLA to give unlimited license for unpaid contributions to an "association" which will only share that contribution back with the community in a restricted way, that they can also modify to their choosing at any time.
Presumably, most or all of the "contributors" on the contributors page are employees.