Teamhood
Teamhood's recent feed is all comparison SEO, leaning hard into construction PM
A side-by-side editorial comparison of Vikunja and Everhour — release velocity, themes, recent moves, and the top alternatives to consider.
Vikunja crossed the v1.0 finish line and pivoted hard into security hardening.
Vikunja shipped two v1.0 release candidates through late 2025 and early 2026, then jumped to a v2 series whose first widely-tagged point release, v2.2.1, is dominated by security work. The latest release patches multiple SSRF and IDOR vulnerabilities, enforces disabled/locked-account semantics across every auth surface (OIDC, API tokens, CalDAV, LDAP), and adds a shared SSRF-safe HTTP client that webhooks and migrations now route through. User-facing feature work has slowed; the visible energy is in plumbing and audit cleanup.
Everhour's tracked feed is its workplace-topics blog, not a changelog — no product signal to read.
The recent entries are educational blog posts about workplace and scheduling topics — unpaid time off, float in project management, bereavement leave, working-hours math. None describe a change to Everhour's time-tracking product. There is no observable product state to assess from this feed.
Vikunja shipped two v1.0 release candidates through late 2025 and early 2026, then jumped to a v2 series whose first widely-tagged point release, v2.2.1, is dominated by security work. The latest release patches multiple SSRF and IDOR vulnerabilities, enforces disabled/locked-account semantics across every auth surface (OIDC, API tokens, CalDAV, LDAP), and adds a shared SSRF-safe HTTP client that webhooks and migrations now route through. User-facing feature work has slowed; the visible energy is in plumbing and audit cleanup.
The arc moves from feature-completion (S3 storage, drag-and-drop project moves, hover previews in late 2025) toward platform credibility — closing security gaps a self-hosted task tool needs to clear before serious team adoption. The rapid version-number jump from v1.0.0-rc4 to v2.2.1 in two months suggests v1.0 shipped and the team tagged a v2 line aimed at addressing accumulated authz debt. Expect the next several releases to keep the security-first posture rather than return to a feature push.
The next release will likely continue closing remaining authz edges (more IDOR audits, additional credential-stripping in API responses) and bundle a translations and dependency sweep. A user-facing feature push probably waits until the security work plateaus.
The recent entries are educational blog posts about workplace and scheduling topics — unpaid time off, float in project management, bereavement leave, working-hours math. None describe a change to Everhour's time-tracking product. There is no observable product state to assess from this feed.
This is SEO-oriented content marketing around HR and project-management terms, consistent over weeks. It reflects an audience-acquisition strategy, not the product roadmap. Inferring product direction from these posts would not be grounded in the entries.
More keyword-driven workplace explainers are likely, but no product move can be predicted from this feed. The crawl source appears to target the blog rather than a release/changelog page.
Other PM 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 Vikunja or Everhour.
Teamhood's recent feed is all comparison SEO, leaning hard into construction PM
Celoxis's feed is SEO comparison articles, not product releases
HoneyBook's feed is blog and competitor-comparison content, not a product release log
Atlassian threads Rovo AI through the developer loop while its blog leans on case studies
Unito's tracked feed is its content-marketing blog, not a product changelog — no shipped moves to read.
Planview's feed is strategic-portfolio thought leadership, not release notes — product signal is absent.
See all Vikunja alternatives → · See all Everhour alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Everhour 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. Everhour 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 PM products to evaluate alongside.
Top Vikunja alternatives in PM are ranked by recent ship velocity. Browse the "Vikunja alternatives" section above for the current picks, or visit /alternatives/vikunja for the full list with editorial commentary on each.
Top Everhour alternatives in PM are ranked by recent ship velocity. Browse the "Everhour alternatives" section above for the current picks, or visit /alternatives/everhour for the full list with editorial commentary on each.