You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’ve noticed that while AFFiNE markets itself as a fully open-source Notion alternative, the backend architecture relies on a custom source-available/enterprise license rather than a standard OSI-approved license.
In past articles and discussions, AFFiNE has critiqued other workspace tools like AppFlowy for using Open Core models. However, AFFiNE appears to follow a very similar dual-licensing structure (open-source frontend editor, source-available backend server).
How do you justify claiming the "Open Source" title over "Source-Available" or "Open Core"? Isn't that just false advertising to claim to be an open-source notion alternative?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I’ve noticed that while AFFiNE markets itself as a fully open-source Notion alternative, the backend architecture relies on a custom source-available/enterprise license rather than a standard OSI-approved license.
In past articles and discussions, AFFiNE has critiqued other workspace tools like AppFlowy for using Open Core models. However, AFFiNE appears to follow a very similar dual-licensing structure (open-source frontend editor, source-available backend server).
How do you justify claiming the "Open Source" title over "Source-Available" or "Open Core"? Isn't that just false advertising to claim to be an open-source notion alternative?
All reactions