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
{{ message }}
Repository navigation
Any updates on the May 2026 plan to move AFFiNE toward Apache 2.0?
#15764
In the "May 13 announcement", Vincent outlined plans to move AFFiNE away from its open-core model toward a fully open-source repository under Apache 2.0, including opening up backend and storage options and separating enterprise-specific functionality from the core product.
It's been about five months, and I haven't been able to find any follow-up announcements or public tracking issues for this transition.
The repository still uses its existing split licensing model, and the "October 26 article" continues to describe the backend as enterprise-licensed.
Could the team share an update on a few things?
Current progress: Is the Apache 2.0 transition actively underway? Have any milestones been completed?
Remaining work: What are the main technical, legal, or organizational challenges preventing the transition?
Timeline: Is there an approximate timeframe, even a tentative one?
Community involvement: Is there a public roadmap or tracking issue where contributors can follow progress or help with the transition?
I'm particularly interested in the implications for self-hosting and the long-term openness of the project.
The May announcement was encouraging, and I think greater visibility into the transition would help build confidence among users and potential contributors.
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.
Uh oh!
There was an error while loading. Please reload this page.
Hi AFFiNE team!
In the "May 13 announcement", Vincent outlined plans to move AFFiNE away from its open-core model toward a fully open-source repository under Apache 2.0, including opening up backend and storage options and separating enterprise-specific functionality from the core product.
It's been about five months, and I haven't been able to find any follow-up announcements or public tracking issues for this transition.
The repository still uses its existing split licensing model, and the "October 26 article" continues to describe the backend as enterprise-licensed.
Could the team share an update on a few things?
I'm particularly interested in the implications for self-hosting and the long-term openness of the project.
The May announcement was encouraging, and I think greater visibility into the transition would help build confidence among users and potential contributors.
Thanks!
All reactions