Tigris
Tigris still ships features inside essays, and the newest one is a recycle bin.
A side-by-side editorial comparison of Frappe Framework and Pelican — release velocity, themes, recent moves, and the top alternatives to consider.
Two trains ship the same features minutes apart while v16 absorbs the CRM stack.
v15 and v16 now release in lockstep: v15.118.0 and v16.31.0 went out the same minute carrying the same two features, a between filter for numbers and dates and an activity timeline that records edits, milestones, and sharing events. What separates them is what only v16 receives — a Recorder timeline for document lifecycle, a grouped settings dialog, Cloud Settings in Desk. Both trains carry the same breaking export change, where CSV and Excel now show linked-record titles instead of internal names.
Pelican now ships roughly once a year, and 4.12 is theme housekeeping
Pelican is a mature Python static site generator in low-cadence maintenance: 4.12.0 in April 2026 followed 4.11.0 by fifteen months, which itself followed 4.10.0 by sixteen. Nearly all recent work lands in the bundled notmyidea and Simple themes, in summary generation, and in the file-watching and logging plumbing. The contributor pattern is telling — a handful of names carry most merged PRs, and the changelogs read as accumulated small fixes rather than planned feature arcs.
v15 and v16 now release in lockstep: v15.118.0 and v16.31.0 went out the same minute carrying the same two features, a between filter for numbers and dates and an activity timeline that records edits, milestones, and sharing events. What separates them is what only v16 receives — a Recorder timeline for document lifecycle, a grouped settings dialog, Cloud Settings in Desk. Both trains carry the same breaking export change, where CSV and Excel now show linked-record titles instead of internal names.
v15 is being held at parity on features that are cheap to backport while v16 takes everything structural. The clearest case is the shared CRM and Helpdesk layer — forms, phone number fields, notifications, activity history — being folded into the framework so those apps stop carrying their own copies. Running underneath both is steady permission work: access checks on linked-record lookups, Report scripts restricted to approved methods, server-side Google sign-in, one-time codes for linked accounts.
Expect v16 minors to keep pulling app-level features into the framework while v15 receives only the small portable ones; the divergence between the two Features sections is already the reliable tell.
Pelican is a mature Python static site generator in low-cadence maintenance: 4.12.0 in April 2026 followed 4.11.0 by fifteen months, which itself followed 4.10.0 by sixteen. Nearly all recent work lands in the bundled notmyidea and Simple themes, in summary generation, and in the file-watching and logging plumbing. The contributor pattern is telling — a handful of names carry most merged PRs, and the changelogs read as accumulated small fixes rather than planned feature arcs.
The project is stable rather than growing: the last genuinely structural changes were switching the build tool to PDM and moving file watching to watchfiles back in 4.9.0, and nothing since has altered how Pelican works. Recent releases invest in making the bundled themes usable as inheritance bases — more template blocks, CSS_FILE support, dark mode — which pushes customization toward theme authors instead of core. Expect continuity, not reinvention.
The entries show no roadmap signal beyond incremental theme and Python-version support, so the next release most likely follows the same pattern: another year-scale gap, more Simple-theme inheritance hooks, and test-matrix updates for a newer Python.
Other DevOps 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 Frappe Framework or Pelican.
Tigris still ships features inside essays, and the newest one is a recycle bin.
Workato just made itself the control plane for every MCP server in the building.
Four branches on a servicing drumbeat, with 10.0 taking the only real fixes.
Laravel runs two trains in lockstep, and 13.x is still where features land.
Weaviate is turning the vector database into an agent runtime with tunable search effort
Undertow 2.4.0 clears three CVEs and finally lands long-open HTTP/2 and timeout requests
See all Frappe Framework alternatives → · See all Pelican alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Frappe Framework 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Frappe Framework 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 DevOps products to evaluate alongside.
Top Frappe Framework alternatives in DevOps are ranked by recent ship velocity. Browse the "Frappe Framework alternatives" section above for the current picks, or visit /alternatives/frappe-framework for the full list with editorial commentary on each.
Top Pelican alternatives in DevOps are ranked by recent ship velocity. Browse the "Pelican alternatives" section above for the current picks, or visit /alternatives/pelican for the full list with editorial commentary on each.