Leantime vs Aha!
Side-by-side trajectory, velocity, and editorial themes.
Leantime swaps its rich-text engine, ships experimental PostgreSQL, and spends a month fixing the fallout.
Leantime just landed 3.7, which replaced TinyMCE with a Tiptap-based editor across every rich-text surface, redesigned the wiki, and added experimental PostgreSQL support beside MySQL/MariaDB. The three follow-up patches in three weeks are real bug-fix work — PostgreSQL ROUND/GROUP BY errors, ticket PATCH 500s, session lifetime regressions — not cosmetic tidying. The team also pushed accessibility to WCAG 2.1 AA in the prior 3.6 line.
Leantime is mid-modernization: editor stack, database portability, and design-system tokens are all moving at once. The volume of PostgreSQL-specific bug fixes since 3.7.0 suggests Postgres is being driven by real users hitting real edges, not just a checklist item. Editor-related fixes show Tiptap migration is still settling in.
Expect 3.7.4 within a couple of weeks closing the remaining migration-era bugs, then a clearer 3.8 push around design-token rollout or PostgreSQL going non-experimental.
Aha! Builder is reshaping the product — prototypes, databases, and an MCP server land in the same week.
Aha! is shipping at a daily cadence and pushing in two directions simultaneously. First, the Builder surface is being fleshed out into a full prototype-and-validate environment: built-in databases with preview/production split, in-app feedback widgets, prototypes saved as records linked to product work, AI-assisted feature mockups. Second, AI is being layered across the existing PM workflow — an MCP server that exposes Aha! data to Claude, ChatGPT, and Copilot; AI-built customer-insights reports; AI-assisted roadmap presentations. A new HubSpot integration on the Ideas side rounds out the recent moves.
Aha! is positioning to defend its roadmap-software seat against AI-native challengers (the Productboard comparison post is a tell) by becoming the layer where product managers prototype, validate with users, and connect the result back to the roadmap. The Builder line is the strategic bet — taking PMs out of Figma/Retool tooling and keeping them in Aha!. The MCP server matters in parallel: it positions Aha! as a data source for any agent runtime, not just as a destination workflow tool.
Expect Aha! Builder to be packaged as a standalone SKU (or upgraded tier) within the next quarter, given how complete the prototype-database-feedback loop now is. The MCP server is likely the first of several agent-integration surfaces; a second wave will probably target Linear/Jira-style sync agents that bridge Aha! into engineering execution tools.
See more alternatives to Leantime →
See more alternatives to Aha! →