← Back to home
Comparison · Collab

Shiori vs Document360

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

Shiori vs Document360: at a glance

FeatureShioriDocument360
SectorCollabCollab
Velocity score0.06.3
Sparks · 30d01
Top themesbookmarks, self-hosted, api-first, golangagent-native-docs, mcp, api-documentation, eddy-ai
Last editorial update2h ago1d ago
WebsiteVisit →

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.

Read the full Shiori trajectory →

What is Document360?

Document360 is rebuilding its knowledge base to be read by agents as much as by people.

Document360 ships monthly, and the last five releases trace one line: making documentation machine-consumable. The MCP server went from read and write access to full lifecycle control including publishing and workflow, llms.txt generation became automatic, and readers can now copy articles as Markdown or open them straight in ChatGPT or Claude. The August release turns the API reference itself into an interactive console — a rebuilt Try It!, live schema validation, in-console authorization, Eddy AI answering inline — alongside a new Widget 2.0 embedding architecture beginning rollout.

Read the full Document360 trajectory →

Shiori vs Document360: editorial side-by-side

S
Shiori
COLLAB
0.0

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.

D6.3

Document360 is rebuilding its knowledge base to be read by agents as much as by people.

◆ Current state

Document360 ships monthly, and the last five releases trace one line: making documentation machine-consumable. The MCP server went from read and write access to full lifecycle control including publishing and workflow, llms.txt generation became automatic, and readers can now copy articles as Markdown or open them straight in ChatGPT or Claude. The August release turns the API reference itself into an interactive console — a rebuilt Try It!, live schema validation, in-console authorization, Eddy AI answering inline — alongside a new Widget 2.0 embedding architecture beginning rollout.

◆ Where it's heading

Two audiences are being served out of one content store. The human-facing work — Mermaid diagrams, PDF export controls, multilingual guides, SCIM and JWT provisioning — continues as steady enterprise hygiene, while the agent-facing surface expands faster and with more architectural intent. The API-reference rebuild is the first time that convergence shows up in what a reader sees rather than in an integration.

◆ Prediction

Expect Widget 2.0 to finish its rollout and the Eddy AI inline-answer pattern to spread from the API reference into the wider knowledge base site. Further MCP expansion looks likely given the lifecycle tools already shipped, though these entries don't indicate what is left uncovered.

Alternatives to Shiori and Document360

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 Document360.

See all Shiori alternatives → · See all Document360 alternatives →

Recent activity from Shiori and Document360

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

  1. 1d agoDocument360Interactive API reference with Try It! console and Widget 2.0
  2. 22d agoDocument360Readers can open articles in ChatGPT or Claude; smarter find/replace
  3. 1mo agoDocument360Native Mermaid diagrams and automatic llms.txt generation
  4. 1mo agoDocument360MCP server gains publishing and workflow management
  5. 2mo agoDocument360Multiple JWT configs and an MCP analytics dashboard
  6. 3mo agoDocument360Multilingual step-by-step guides and portal CSP controls
  7. 1y agoShioriAPI v1 gains tag endpoints, filtering and counts; proxy header auth
  8. 1y agoShioriSwagger UI disabled by default; session auth and Postgres fixes
  9. 2y agoShioriLight, dark and system theme selection in the web UI
  10. 2y agoShioriHome button clears the active search query

Frequently asked questions

What is the difference between Shiori and Document360?

They serve adjacent needs but don't currently overlap on shipped themes. Document360 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 Document360?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Document360 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 Document360?

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