AFFiNE
AFFiNE ships stable iOS Share Extension imports while patching editor correctness and selfhost deployment
A side-by-side editorial comparison of Flarum and Wiki.js — release velocity, themes, recent moves, and the top alternatives to consider.
Flarum's 2.0 candidates are accelerating, but the feed publishes only a link per tag.
Flarum is eight release candidates into 2.0, with rc.6, rc.7, and rc.8 landing within five days after a gap of roughly seven weeks following rc.5. The feed carries no notes: each entry is a single line pointing at the CHANGELOG.md for that tag, so the content of these candidates is not visible here. The last entry with substantive text was rc.1 in April, which addressed discussion-list and notification query costs.
Wiki.js 3.0 beta closes enterprise auth and SEO gaps at sprint pace
Wiki.js is running a dual-track strategy: v2.5.x is in maintenance, collecting only security and bug fixes, while v3.0.0 moves through beta weekly with substantial new features. The v3 beta has concentrated recent drops on two converging pillars — enterprise authentication (Entra ID, LDAP, SAML, Discord with group-to-role mapping) and operations infrastructure (Audit Log, admin metrics, sitemap serving, prerendering for anonymous requests). All active development runs through a single committer, shipping multiple named features per weekly beta build.
Flarum is eight release candidates into 2.0, with rc.6, rc.7, and rc.8 landing within five days after a gap of roughly seven weeks following rc.5. The feed carries no notes: each entry is a single line pointing at the CHANGELOG.md for that tag, so the content of these candidates is not visible here. The last entry with substantive text was rc.1 in April, which addressed discussion-list and notification query costs.
Tempo is the only signal this feed supports, and it has clearly changed: three candidates in five days after seven quiet weeks reads as convergence on a final rather than continued development. What is actually changing between candidates cannot be determined from this source without following the linked changelog.
A 2.0.0 final looks near given the candidate cadence, but this feed will not say what it contains.
Wiki.js is running a dual-track strategy: v2.5.x is in maintenance, collecting only security and bug fixes, while v3.0.0 moves through beta weekly with substantial new features. The v3 beta has concentrated recent drops on two converging pillars — enterprise authentication (Entra ID, LDAP, SAML, Discord with group-to-role mapping) and operations infrastructure (Audit Log, admin metrics, sitemap serving, prerendering for anonymous requests). All active development runs through a single committer, shipping multiple named features per weekly beta build.
The v3 beta is systematically filling the gaps that have kept Wiki.js out of enterprise environments: SSO across major identity providers, compliance tooling, SEO readiness, and theme customization for whitelabeled deployments. Each week's build adds a category that a production deployment actually requires. The remaining areas not yet visible in the beta changelog are storage/sync providers and full editor-module parity with v2 — those gaps are the logical preconditions for an RC.
The next beta cycle will likely address storage backends and remaining editor modules. A release candidate becomes the natural next step once those surface areas are covered.
Other Collab products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Flarum or Wiki.js.
AFFiNE ships stable iOS Share Extension imports while patching editor correctness and selfhost deployment
SiYuan 3.8.4 makes AI agents first-class participants in personal knowledge management
Readwise ships library-wide Ghostreader with tool-calling: tag, annotate, save across your full archive
Joplin 3.7 ships AI chat, semantic search, and MCP integration — all off by default, all controllable by the user.
GitHub Copilot splits into cost tiers and deepens agentic automation across the dev stack
Nuclino ships its MCP server in January 2026, making the team knowledge base queryable by AI agents—a directional move toward AI-native knowledge management.
See all Flarum alternatives → · See all Wiki.js alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Wiki.js is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Wiki.js is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Collab products to evaluate alongside.
Top Flarum alternatives in Collab are ranked by recent ship velocity. Browse the "Flarum alternatives" section above for the current picks, or visit /alternatives/flarum for the full list with editorial commentary on each.
Top Wiki.js alternatives in Collab are ranked by recent ship velocity. Browse the "Wiki.js alternatives" section above for the current picks, or visit /alternatives/wiki-js for the full list with editorial commentary on each.