← Back to home
Comparison · Collab

AFFiNE vs LibrePhotos

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

AFFiNE vs LibrePhotos: at a glance

FeatureAFFiNELibrePhotos
SectorCollabCollab
Velocity score6.30.0
Sparks · 30d00
Top themesself-hosting, canary builds, byok, mcpself-hosted, photo-management, monorepo, semver
Last editorial update4d ago12d ago
WebsiteVisit →Visit →

What is AFFiNE?

The nightly canary keeps shipping, and self-hosting just got a one-click path.

AFFiNE publishes a dated canary build most days alongside a slower beta line, and the two carry the same commits at different points on the maturity curve. The recent stream is maintenance-shaped: dependency security bumps in Mermaid and Electron, a journal lookup fix for trashed docs, retry handling for failed transcription jobs. The last directional move was workspace BYOK profiles with model catalogs and key rotation in early August, which sits on top of the MCP credential work from July.

Read the full AFFiNE trajectory →

What is LibrePhotos?

LibrePhotos folded five repositories into one and started versioning like a real product.

The project spent April through June on structural work rather than features. Backend, frontend, mobile app, docs, and Docker deployment were merged into a single repository with each project's git history preserved, and the versioning scheme moved to semver, producing the first 1.0.x releases. The releases since are consolidation: authorization hardening on the user API, a fix for the validation popups that hardening caused for non-admin users, and repeated pinning fights to keep the GPU image building.

Read the full LibrePhotos trajectory →

AFFiNE vs LibrePhotos: editorial side-by-side

A
AFFiNE
COLLAB
6.3

The nightly canary keeps shipping, and self-hosting just got a one-click path.

◆ Current state

AFFiNE publishes a dated canary build most days alongside a slower beta line, and the two carry the same commits at different points on the maturity curve. The recent stream is maintenance-shaped: dependency security bumps in Mermaid and Electron, a journal lookup fix for trashed docs, retry handling for failed transcription jobs. The last directional move was workspace BYOK profiles with model catalogs and key rotation in early August, which sits on top of the MCP credential work from July.

◆ Where it's heading

Two threads run in parallel. The AI thread is about who supplies and controls the model - BYOK profiles, MCP credentials, access modes - rather than adding model features. The other thread is self-host ergonomics, and the Render blueprint is the clearest recent instance: AFFiNE keeps lowering the cost of running your own instance while keeping the AI layer pluggable. Between those, the canary absorbs a steady flow of upstream security patches with little product change attached.

◆ Prediction

Expect the self-host track to keep collecting deploy targets and the BYOK work to extend to more provider surfaces; on current cadence the next 0.27 beta will consolidate the canary work rather than introduce anything new.

L0.0

LibrePhotos folded five repositories into one and started versioning like a real product.

◆ Current state

The project spent April through June on structural work rather than features. Backend, frontend, mobile app, docs, and Docker deployment were merged into a single repository with each project's git history preserved, and the versioning scheme moved to semver, producing the first 1.0.x releases. The releases since are consolidation: authorization hardening on the user API, a fix for the validation popups that hardening caused for non-admin users, and repeated pinning fights to keep the GPU image building.

◆ Where it's heading

This is a self-hosted project doing the unglamorous work that makes contribution and release possible at scale — one repo, unified CI and Dockerfiles, predictable version numbers. The backend changes running underneath it are about resilience rather than capability: retrying transient face-service drops, hardening metadata extraction against exif-service failures, preserving scan baselines during job cleanup. The recurring Renovate-versus-GPU-pin conflicts suggest the dependency story for the CUDA image is still fragile.

◆ Prediction

With the monorepo and semver in place, the next releases are likely to return to user-facing features on a 1.x line rather than more restructuring. The GPU image pins look like they will need a more durable fix than repeated Renovate overrides.

Alternatives to AFFiNE and LibrePhotos

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 AFFiNE or LibrePhotos.

See all AFFiNE alternatives → · See all LibrePhotos alternatives →

Recent activity from AFFiNE and LibrePhotos

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

  1. 5d agoAFFiNEOne-click self-host deploy via Render blueprint
  2. 6d agoAFFiNEFailed transcription jobs can be retried without being recreated
  3. 8d agoAFFiNETrashed journals no longer surface in date lookups
  4. 9d agoAFFiNEMermaid 11.16.1 patches an XY-chart denial-of-service flaw
  5. 10d agoAFFiNEElectron 39.8.10 fixes a spoofable code-sign check
  6. 13d agoAFFiNEAtlaskit drag-and-drop auto-scroll upgraded to v3
  7. 1mo agoLibrePhotos1.0.3 - Fix user list popup for non-admin users
  8. 1mo agoLibrePhotosGPU image: restore the onnxruntime and timezonefinder pins
  9. 1mo agoLibrePhotosGPU image: stop Renovate collapsing the scikit-learn pin
  10. 1mo agoLibrePhotosSwitching to semantic versioning
  11. 1mo agoLibrePhotosLibrePhotos moves backend, frontend, mobile and docs into one monorepo
  12. 7y agoLibrePhotos2019 release candidate: timezone environment variable

Frequently asked questions

What is the difference between AFFiNE and LibrePhotos?

They serve adjacent needs but don't currently overlap on shipped themes. AFFiNE is currently shipping more aggressively (velocity 6.3 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 AFFiNE better than LibrePhotos?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. AFFiNE is currently shipping more aggressively (velocity 6.3 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 AFFiNE?

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

What are the best alternatives to LibrePhotos?

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