← Back to home
Comparison · Collab

HumHub vs Wiki.js

A side-by-side editorial comparison of HumHub and Wiki.js — release velocity, themes, recent moves, and the top alternatives to consider.

HumHub vs Wiki.js: at a glance

FeatureHumHubWiki.js
SectorCollabCollab
Velocity score5.06.3
Sparks · 30d01
Top themessocial intranet, beta releases, upgrade migrations, permissionswiki, self-hosted, enterprise-auth, sso
Last editorial update27d ago4d ago
WebsiteVisit →Visit →

What is HumHub?

HumHub's public feed carries only betas, and 1.19's is still about surviving the upgrade.

The four releases visible here are all pre-release: 1.19.0-beta.2 and beta.1, and 1.18.0-beta.6 and beta.5 before them. The 1.19 line is dominated by upgrade-path and data-integrity repair — a foreign key violation aborting the comment content_id migration on databases with orphaned rows, fatal errors when purging content whose underlying record was gone, and in beta.2 a fatal SCSS build loop left behind when the 1.19 move of static/themes into protected/humhub stranded an empty theme skeleton. Beta.2 also fixes a real leak: activities from private spaces appearing in the summary mail and dashboard of users holding only a pending invite or join request.

Read the full HumHub trajectory →

What is Wiki.js?

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.

Read the full Wiki.js trajectory →

HumHub vs Wiki.js: editorial side-by-side

H
HumHub
COLLAB
5.0

HumHub's public feed carries only betas, and 1.19's is still about surviving the upgrade.

◆ Current state

The four releases visible here are all pre-release: 1.19.0-beta.2 and beta.1, and 1.18.0-beta.6 and beta.5 before them. The 1.19 line is dominated by upgrade-path and data-integrity repair — a foreign key violation aborting the comment content_id migration on databases with orphaned rows, fatal errors when purging content whose underlying record was gone, and in beta.2 a fatal SCSS build loop left behind when the 1.19 move of static/themes into protected/humhub stranded an empty theme skeleton. Beta.2 also fixes a real leak: activities from private spaces appearing in the summary mail and dashboard of users holding only a pending invite or join request.

◆ Where it's heading

The 1.19 cycle is being spent making the migration survivable on real installations rather than adding capability, which is the usual shape when a schema and directory-layout change meets databases and webroots that have accumulated years of drift. Beta.2 extends that into the installer itself, where an unreachable database was offering to re-set-up a live instance during a transient outage. The permission and visibility fixes point the same way: tightening authorisation and content boundaries is cleanup of an existing model, not an extension of it.

◆ Prediction

Only beta tags appear in this feed, so a 1.19.0 stable is the obvious next milestone, but nothing here dates it. The beta.1-to-beta.2 gap of about a month is a faster rhythm than the roughly six months between the 1.18 and 1.19 betas.

W
Wiki.js
COLLAB
6.3

Wiki.js 3.0 beta closes enterprise auth and SEO gaps at sprint pace

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to HumHub and Wiki.js

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 HumHub or Wiki.js.

See all HumHub alternatives → · See all Wiki.js alternatives →

Recent activity from HumHub and Wiki.js

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4d agoWiki.js3.0.0-beta.561
  2. 8d agoWiki.js3.0.0-beta.554
  3. 9d agoWiki.js3.0.0-beta.550
  4. 10d agoWiki.js3.0.0-beta.543
  5. 14d agoWiki.js3.0.0-beta.537
  6. 17d agoWiki.js3.0.0-alpha.530
  7. 28d agoHumHubPrivate-space activity leak, installer 503 handling and the stranded theme skeleton
  8. 1mo agoHumHub1.19 upgrade migration and orphaned content fixes
  9. 8mo agoHumHubLogin screen, theming and validator fixes
  10. 10mo agoHumHubGroup manager options and assorted UI fixes

Frequently asked questions

What is the difference between HumHub and Wiki.js?

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.

Is HumHub better than Wiki.js?

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.

What are the best alternatives to HumHub?

Top HumHub alternatives in Collab are ranked by recent ship velocity. Browse the "HumHub alternatives" section above for the current picks, or visit /alternatives/humhub for the full list with editorial commentary on each.

What are the best alternatives to Wiki.js?

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.