GoRetro
5.2Make every sprint impactful, efficient, and fun
GoRetro is a sprint-centric retro and estimation suite combining retrospectives, planning poker, capacity planning and a Jira-fed sprint monitor, with a limited free plan and flat per-team paid pricing.
Full review →
QRetro
6.3Manage team health, not sticky notes
QRetro is a completely free retrospective tool with no seat or team caps, built by solo developer Roman Ermilov and shipping since January 2023. It runs a fixed seven-stage session — optional health check, optional icebreaker game, cards, grouping, voting, discussion, results — and closes with an OpenAI-generated summary, a ROTI score, suggested next steps and an analysis layer that clusters the cards by topic, sentiment and urgency. An official, open-source MCP server exposes 29 read/write tools so Claude, Cursor or VS Code can query boards, health trends and actions directly.
Full review →Summary
GoRetro scores 5.2 overall and is best for scrum teams that live in Jira and want a polished retro plus planning-poker bundle priced per team, and can live without an active roadmap. It offers a free tier.
QRetro scores 6.3 overall and is best for small agile teams and independent squads that want a genuinely well-equipped retro — 52 templates, health checks, ROTI, timer, in-board surveys, icebreaker games and MCP access — at zero cost, and can accept a solo-maintainer vendor with no SSO, no PDF or spreadsheet export and no certifications. It offers a free tier.
GoRetro leads on enterprise-grade. QRetro leads on retro toolkit, value, AI & insights, integrations and open platform.
Across our eight scoring dimensions, QRetro edges ahead with an overall score of 6.3. That said, the right pick depends on your team — see the dimension-by-dimension breakdown below.
Scores compared
| Detail | GoRetro | QRetro |
|---|---|---|
| Category | Retrospectives | Retrospectives |
| Team size | Any | Small |
| Free tier | Yes | Yes |
| Free limit | Free plan: 1 team, 5 public boards, 2 team boards per 31-day cycle, 3 columns per board, unlimited users and guests, 20+ templates. Excludes exports, retro analytics, Jira sync, happiness index, polls, icebreakers and action-item management. No longer listed on the pricing page — you land on it when the 30-day trial ends. | Everything is free with no seat or team caps — 52 templates, unlimited public and team boards, planning poker, team games, health checks, ROTI, summaries and MCP access |
| Starting price | $29/team/mo | Free |
| Est. 3 teams × 8 people | $87/mo (Premium, 3 teams, billed annually; $105/mo billed monthly) | Free (no paid tier) |
| Enterprise | Yes | No |
| Founded | 2020 | 2023 |
| HQ | Israel | — |
| Data residency | United States | — |
| Languages | English only | English only |
| Export formats | PDF · CSV · Image | Markdown · Email · JSON |
| Features | 35 | 38 |
| Integrations | 2 | 3 |
Feature & integration comparison
Side-by-side checklist across features, integrations and security. Hover a note for details.
| Capability | GoRetro | QRetro |
|---|---|---|
| Features | ||
| Custom templates | ✓ | ✓note |
| Anonymous input | ✓ | ✓note |
| Health Checks | ✓note | ✓note |
| Action tracking | ✓ | ✓ |
| Async mode | ✓note | — |
| Whiteboard | — | — |
| Independent voting | ✓ | ✓ |
| Polling | ✓note | ✓note |
| Icebreaker games | — | ✓note |
| Agile Estimations | ✓note | ✓note |
| Team Kudos | ✓note | ✓note |
| AI grouping/clustering | — | ✓note |
| AI action items | — | ✓note |
| AI Summaries | — | ✓ |
| Team Insights | — | ✓note |
| In-meeting AI assistant | — | — |
| Action dashboard | ✓note | ✓note |
| Integrations | ||
| Asana | — | — |
| Azure DevOps | — | — |
| Basecamp | — | — |
| ClickUp | — | — |
| Confluence | — | — |
| GitHub | — | — |
| GitLab | — | — |
| Jira | ✓note | ✓note |
| Linear | — | ✓note |
| Microsoft Teams | — | — |
| Monday.com | — | — |
| Notion | — | — |
| Shortcut | — | — |
| Slack | ✓note | ✓note |
| Trello | — | — |
| Security & Privacy | ||
| SOC 2 | ✓note | — |
| GDPR | ✓ | ✓note |
| SSO / SAML | ✓note | — |
| SCIM provisioning | — | — |
| ISO 27001 | ✓note | — |
| On-premises | — | — |
| Public API | — | — |
| Webhooks | — | — |
| MCP server | — | ✓ |
GoRetro — pros
- + Flat per-team pricing ($29/team/mo annual) with unlimited members per team, plus a genuinely free plan for one team
- + Polished, real-time facilitation UX with per-board anonymity toggles (hide author, hide cards, hide votes) and drag-to-merge grouping
- + Bundles planning poker, capacity calculator and a Jira sprint monitor with retros
- + Real engagement extras — Giphy picker on cards, an optional kudos column, icebreakers, polls and a happiness index
- + Tight Jira Cloud integration; action items push through to Slack
GoRetro — cons
- − <strong>Effectively in maintenance mode</strong> — the production app was last built 9 Feb 2025, the changelog stopped 23 May 2023 and the blog 28 Jul 2023, and two features are still badged "coming soon" from that era
- − <em>No AI anywhere in the shipped app</em> — no clustering, summarisation or sentiment analysis; the .ai is a domain, not a capability
- − Integration breadth is narrow — Jira and Slack only, with no native MS Teams, Azure DevOps, GitHub, Linear, Confluence or Trello
- − No public API or webhooks; exports capped at PDF/CSV/PNG; US-only hosting with no EU residency option
- − The security page contradicts its own hero: SOC 2 Type II and ISO 27001 are billed as certified up top and "pending audit" in the detail row
QRetro — pros
- + Genuinely free with no seat caps, team caps or paywalled features — a 24-person org across three teams pays nothing, and there is no paid tier to be upsold to
- + Retro toolkit is deep for a free product: 52 templates, editable columns, private-mode submission, a timer, drag-and-drop grouping with auto-named groups, presentation mode, up to five in-board surveys, action items with owners and due dates, ROTI and a radar-charted health check stage
- + The analysis layer is the surprise — every card gets a system-assigned sentiment, category and urgency score, and the <strong>Perception Mirror</strong> compares the system's own topic clusters against the groups the team made and names the ones that quietly hold three different problems
- + Unusually strong engagement layer for a product that charges nothing — four built-in games (Draw & Guess, Sprint in one GIF, Hangman, Decoded) usable as a switchable icebreaker stage, plus GIF cards, emoji reactions and live cursors. TeleRetro and the whiteboard tools still go further, mainly on music and ambient audio
- + Official MCP server at a single address (mcp.qretro.com) with 29 read, write and delete tools, two analysis prompts and OAuth sign-in — verified live at v1.3.0, and the server source is public on GitHub
- + Guest access with no account or password, and guest contributions persist permanently rather than expiring after a day
- + Visibly active for a solo project: 14 dated changelog entries in 2026 (MCP, OAuth, poker over MCP, two new games), legal pages rewritten in late July 2026 and a site rebuild on 15 August 2026
QRetro — cons
- − Built and maintained by a single developer (Roman Ermilov) with no support team, SLA or published company entity — the enterprise-grade cap for founder-only vendors applies regardless of how good the product is
- − No enterprise controls: no SSO or SAML, no SCIM, no audit logs, no SOC 2 or ISO 27001, and no published hosting location or data-residency option
- − Export is thin — a Markdown copy of the summary, an email to the team, a Slack or Telegram recap, and a JSON dump of your own account data. There is no PDF, CSV or Excel, so there is nothing to hand a stakeholder and nothing to drop into a spreadsheet
- − Integration set is narrow: Jira, Linear, Slack and Telegram only — nothing for Teams, Confluence, GitHub, GitLab, Azure DevOps or any other tracker
- − No async or distributed-team support — the seven-stage flow assumes a live session, and there are no recurring or scheduled retros
- − Vote allowance is computed automatically (cards + 3, capped at 10) rather than set by the facilitator, the timer maxes out at 30 minutes, and the stage order itself cannot be customised
- − No working-agreements artifact that survives between retros — what the vendor calls an 'agreement' is an action item on a board
- − No cross-team or org-level reporting: the Analytics section of the dashboard is still labelled <em>Coming soon</em>, so health and action data stays inside a single team's boards
Keep comparing
Other GoRetro comparisons
Other QRetro comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.