← Back to home
Comparison · Collab

Paperless-ngx vs Read the Docs

A side-by-side editorial comparison of Paperless-ngx and Read the Docs — release velocity, themes, recent moves, and the top alternatives to consider.

Paperless-ngx vs Read the Docs: at a glance

FeaturePaperless-ngxRead the Docs
SectorCollabCollab
Velocity score6.35.0
Sparks · 30d10
Top themesdocument-management, self-hosted, paperless-ai, breaking-changesbuild-infrastructure, uv-migration, isolated-builders, schema-cleanup
Last editorial update17d ago2h ago
WebsiteVisit →Visit →

What is Paperless-ngx?

Paperless-ngx shipped its 3.0 rewrite, then spent a week putting out the fires.

3.0.0 landed on July 22 after a long beta, carrying both the largest feature set in the project's history and nine breaking changes. The five releases since are pure repair: a broken migration in 3.0.1 that forced an immediate 3.0.2, then three patch rounds covering OCR skipping, permission-filtered dedup, Gotenberg conversion, email date parsing, AI suggestion caching and search index edge cases. The pace tells you 3.0 shipped into real deployments fast.

Read the full Paperless-ngx trajectory →

What is Read the Docs?

Read the Docs is rebuilding its build farm around uv and isolated builders, one week at a time.

Weekly date-tagged releases, almost entirely build infrastructure. The visible work is a migration to uv-managed environments and isolated, ephemeral builders, shipped in small increments between routine dependency bumps. The two most recent releases are the quietest of the run: plumbing for uv and build status in one, and a video extension bump, a nullable-field step toward dropping has_valid_clone, and Python 3.14 for the pip-tools workflow in the other.

Read the full Read the Docs trajectory →

Paperless-ngx vs Read the Docs: editorial side-by-side

P6.3

Paperless-ngx shipped its 3.0 rewrite, then spent a week putting out the fires.

◆ Current state

3.0.0 landed on July 22 after a long beta, carrying both the largest feature set in the project's history and nine breaking changes. The five releases since are pure repair: a broken migration in 3.0.1 that forced an immediate 3.0.2, then three patch rounds covering OCR skipping, permission-filtered dedup, Gotenberg conversion, email date parsing, AI suggestion caching and search index edge cases. The pace tells you 3.0 shipped into real deployments fast.

◆ Where it's heading

The project has moved from a document scanner-and-tagger to a document platform with AI in the core: Paperless AI, remote OCR via Azure, a document parser plugin framework, tantivy replacing Whoosh for search, file versions and sharelink bundles. The breaking changes are the other half of that story — dropping API v1, Python 3.10, document encryption and the old consumer clears the decks for that platform. Recent patches keep touching LLM plumbing, including passing output language into chat and adding docstrings so the classifier reads better as an LLM tool.

◆ Prediction

The 3.0.x patch cadence looks set to run at least another round or two — 3.0.5 is still landing search-compatibility and AI-suggestion fixes rather than tapering. Feature work resuming before that queue empties would be the surprise.

R5.0

Read the Docs is rebuilding its build farm around uv and isolated builders, one week at a time.

◆ Current state

Weekly date-tagged releases, almost entirely build infrastructure. The visible work is a migration to uv-managed environments and isolated, ephemeral builders, shipped in small increments between routine dependency bumps. The two most recent releases are the quietest of the run: plumbing for uv and build status in one, and a video extension bump, a nullable-field step toward dropping has_valid_clone, and Python 3.14 for the pip-tools workflow in the other.

◆ Where it's heading

The isolated builder is the arc worth tracking — private repository support, an ephemeral builder script, and removal of the old scale-in protection path all point at builds that run in disposable environments. Alongside it runs a quieter cleanup pattern: fields are made nullable before removal, feature flags are deleted once the code behind them lands, and Python versions are pushed forward in the tooling before the runtime. User-facing change is rare and arrives as a side effect, as when July's release moved images to Ubuntu 26.04 and Python 3.14.

◆ Prediction

Expect the isolated builder to become the default path and further uv environment fixes; the has_valid_clone column being made nullable signals its removal in a following release. Feature work should stay secondary until that migration finishes.

Alternatives to Paperless-ngx and Read the Docs

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 Paperless-ngx or Read the Docs.

See all Paperless-ngx alternatives → · See all Read the Docs alternatives →

Recent activity from Paperless-ngx and Read the Docs

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

  1. 22h agoRead the Docshas_valid_clone made nullable before removal; tooling bumps
  2. 7d agoRead the DocsBuild status skipped for commit-less builds; uv venv path fix
  3. 14d agoRead the DocsIsolated builders gain private-repo support and uv installs
  4. 17d agoPaperless-ngxFifth 3.0 patch round: AI cache keying and search date units
  5. 21d agoRead the DocsDependency-only maintenance release
  6. 22d agoPaperless-ngxPaperless-ngx v3.0.4
  7. 24d agoPaperless-ngxPaperless-ngx v3.0.3
  8. 26d agoPaperless-ngxPaperless-ngx v3.0.1
  9. 26d agoPaperless-ngxPaperless-ngx v3.0.2
  10. 27d agoPaperless-ngxPaperless-ngx v3.0.0
  11. 28d agoRead the DocsEphemeral builders land; subproject aliases accept slashes
  12. 1mo agoRead the DocsUbuntu 26.04 and Python 3.14 build images; automation fixes

Frequently asked questions

What is the difference between Paperless-ngx and Read the Docs?

They serve adjacent needs but don't currently overlap on shipped themes. Paperless-ngx 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 Paperless-ngx better than Read the Docs?

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

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

What are the best alternatives to Read the Docs?

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