Teable
Secrets get encrypted at rest while the computed-field engine keeps getting shored up
Comparison · Collab
HumHub vs Shiori
A side-by-side editorial comparison of HumHub and Shiori — release velocity, themes, recent moves, and the top alternatives to consider.
HumHub vs Shiori: at a glance
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.
What is Shiori?
A Go bookmark manager rebuilding itself around an API — and only ever shipping release candidates.
Shiori is a self-hosted read-later and bookmark tool whose recent history is entirely release candidates: v1.7.0-rc.2, rc.3, v1.7.2-rc.1, v1.8.0-rc.1. The visible work has moved off the web UI and into an API v1 surface — tag endpoints, bookmark-tag association, filtering and counts — plus infrastructure like proxy-header authentication and SQLite performance. The last tagged release in this window is from July 2025.
HumHub vs Shiori: editorial side-by-side
HumHub
5.0COLLAB
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.
Shiori
0.0COLLAB
A Go bookmark manager rebuilding itself around an API — and only ever shipping release candidates.
◆ Current state
Shiori is a self-hosted read-later and bookmark tool whose recent history is entirely release candidates: v1.7.0-rc.2, rc.3, v1.7.2-rc.1, v1.8.0-rc.1. The visible work has moved off the web UI and into an API v1 surface — tag endpoints, bookmark-tag association, filtering and counts — plus infrastructure like proxy-header authentication and SQLite performance. The last tagged release in this window is from July 2025.
◆ Where it's heading
The project is converting from a web app with an API bolted on into an API-first service with a client, and the login component, PWA and theme work are being rewritten around that split. Proxy forward-header authentication in particular is a deployment-shape decision: it assumes Shiori sits behind an authenticating reverse proxy rather than owning identity itself. The RC-only tagging pattern makes it hard to tell what the maintainers consider stable.
◆ Prediction
The next step is presumably a final v1.8.0 consolidating the API v1 tag work, though nothing in these entries indicates the RC-to-stable promotion is scheduled. If the pattern holds, the following RC continues on API endpoints rather than the UI.
Alternatives to HumHub and Shiori
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 Shiori.
GitHub
Security and governance controls catch up to the Copilot build-out
Elgg
A social-networking engine in careful maintenance across two supported branches.
NetNewsWire
7.1.3 ships on the Mac, closing a release spent almost entirely on rebuilding Feedly sync.
Hive
Hive keeps tightening the same three seams: planned time, admin control, and AI review scope
AFFiNE
A dated canary most days, with the beta line carrying the same commits later.
See all HumHub alternatives → · See all Shiori alternatives →
Recent activity from HumHub and Shiori
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 15h agoHumHubPrivate-space activity leak, installer 503 handling and the stranded theme skeleton
- 29d agoHumHub1.19 upgrade migration and orphaned content fixes
- 7mo agoHumHubLogin screen, theming and validator fixes
- 9mo agoHumHubGroup manager options and assorted UI fixes
- 1y agoShioriAPI v1 gains tag endpoints, filtering and counts; proxy header auth
- 1y agoShioriSwagger UI disabled by default; session auth and Postgres fixes
- 2y agoShioriLight, dark and system theme selection in the web UI
- 2y agoShioriHome button clears the active search query
Frequently asked questions
What is the difference between HumHub and Shiori?
They serve adjacent needs but don't currently overlap on shipped themes. HumHub is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Shiori?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HumHub is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Shiori?
Top Shiori alternatives in Collab are ranked by recent ship velocity. Browse the "Shiori alternatives" section above for the current picks, or visit /alternatives/shiori for the full list with editorial commentary on each.