Teable
Teable ships Scheduled Routines, a four-tier AI model system, and multi-model image generation — three sparks in five days
Comparison · Collab
Shiori vs Wiki.js
A side-by-side editorial comparison of Shiori and Wiki.js — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:self-hosted
Shiori vs Wiki.js: at a glance
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.
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.
Shiori vs Wiki.js: editorial side-by-side
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.
Wiki.js
6.3COLLAB
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 Shiori 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 Shiori or Wiki.js.
GitHub
GitHub Copilot tightens enterprise governance while AI security scanning drops its CodeQL prerequisite
Mattermost
Mattermost v11.11 adds data spillage exposure tracking as v12.0 breaking changes loom
SiYuan
SiYuan v3.8.4 beta cycle adds agent-controlled database fields, MiniMax image gen, and skill file management
Nextcloud
Nextcloud runs three LTS branches in parallel, shipping bug fixes and quiet performance wins.
Happeo
Happeo doubles down on SEO content to own intranet search terms for mid-market buyers.
See all Shiori alternatives → · See all Wiki.js alternatives →
Recent activity from Shiori and Wiki.js
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4d agoWiki.js3.0.0-beta.561
- 8d agoWiki.js3.0.0-beta.554 ⚡
- 9d agoWiki.js3.0.0-beta.550
- 10d agoWiki.js3.0.0-beta.543
- 14d agoWiki.js3.0.0-beta.537
- 17d agoWiki.js3.0.0-alpha.530
- 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 Shiori and Wiki.js?
Both compete on the same themes — self-hosted — within Collab. Wiki.js is currently shipping more aggressively (velocity 6.3 vs 0.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 Shiori 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 0.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 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.
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.