QRetro
5.8Manage 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 continuously 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 auto-generated summary, ROTI score and action items. An official MCP server exposes 29 read/write tools so Claude, Cursor or VS Code can query boards, health trends and actions directly.
Full review →
SprintRetro
5.0Free sprint retros, embedded in Jira
SprintRetro is a free Atlassian Forge app from Agile Pulse that runs sprint retrospectives directly inside Jira Cloud. It pulls live sprint metrics (velocity, scope change, carryover, cycle time, committed vs delivered) into a collaborative retro board, and the free listing also carries an infinite whiteboard, anonymous team-health pulse checks, timers, and an AI facilitator, alongside templates, anonymous voting, cross-sprint action tracking that can create Jira issues, GIFs, kudos, polls, and icebreakers. Both Marketplace listings are Cloud Fortified. A separate paid Pro app sits alongside the free one.
Full review →Summary
QRetro scores 5.8 overall and is best for small agile teams and independent squads that want a genuinely well-equipped retro — 52 templates, health checks, ROTI, timer, icebreaker games and MCP access — at zero cost, and can accept a solo-maintainer vendor with no SSO, no export files and no certifications. It offers a free tier.
SprintRetro scores 5.0 overall and is best for scrum teams already living in Jira Cloud who want a no-cost, no-friction sprint retro tool with sprint metrics baked in. It offers a free tier.
QRetro leads on ease of use, retro toolkit, fun factor, AI & insights, integrations and open platform. SprintRetro leads on enterprise-grade.
Across our eight scoring dimensions, QRetro edges ahead with an overall score of 5.8. That said, the right pick depends on your team — see the dimension-by-dimension breakdown below.
Scores compared
| Detail | QRetro | SprintRetro |
|---|---|---|
| Category | Retrospectives | Retrospectives |
| Team size | Small | Small |
| Free tier | Yes | Yes |
| Free limit | 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 | Free for unlimited users on a Jira instance (free app listing) |
| Starting price | Free | $8.40/user/yr (Pro app; free on Jira sites of 10 or fewer users) |
| Est. 3 teams × 8 people | Free (no paid tier) | Free (within free tier) |
| Enterprise | No | No |
| Founded | 2023 | — |
| HQ | — | Waterlooville, United Kingdom |
| Data residency | — | — |
| Languages | English only | English only |
| Export formats | — | Jira |
| Features | 32 | 27 |
| Integrations | 3 | 1 |
Feature & integration comparison
Side-by-side checklist across features, integrations and security. Hover a note for details.
| Capability | QRetro | SprintRetro |
|---|---|---|
| Features | ||
| AI Summaries | ✓ | ✓ |
| AI grouping/clustering | — | ✓ |
| AI action items | ✓note | ✓ |
| Action tracking | ✓ | ✓ |
| Team Insights | ✓note | ✓note |
| Polling | — | ✓ |
| Action dashboard | ✓note | ✓note |
| Custom templates | — | ✓ |
| Anonymous input | ✓note | ✓ |
| Independent voting | ✓ | ✓ |
| Async mode | — | — |
| Agile Estimations | ✓note | — |
| Health Checks | ✓note | ✓note |
| Team Kudos | ✓note | ✓ |
| Whiteboard | — | ✓ |
| Integrations | ||
| Asana | — | — |
| Azure DevOps | — | — |
| Basecamp | — | — |
| ClickUp | — | — |
| Confluence | — | — |
| GitHub | — | — |
| GitLab | — | — |
| Jira | ✓note | ✓ |
| Linear | ✓note | — |
| Microsoft Teams | — | — |
| Monday.com | — | — |
| Notion | — | — |
| Shortcut | — | — |
| Slack | ✓note | — |
| Trello | — | — |
| Security & Privacy | ||
| SOC 2 | — | ✓note |
| GDPR | ✓note | ✓ |
| SSO / SAML | — | ✓note |
| SCIM provisioning | — | — |
| ISO 27001 | — | ✓note |
| On-premises | — | — |
| Public API | — | — |
| Webhooks | — | — |
| MCP server | ✓ | — |
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, private-mode submission, timer, drag-and-drop grouping with auto-named groups, action items, team agreements, ROTI and a radar-charted health check stage
- + 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 and OAuth sign-in, so Claude, Cursor or VS Code can pull board summaries, health trends and action items with nothing to paste
- + Guest access with no account or password, and guest contributions now persist permanently rather than expiring after a day
- + Visibly active despite being a solo project — 15+ dated changelog entries across 2026, including the v4 relaunch, MCP OAuth, poker over MCP and two new games in July–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 at all: no SSO or SAML, no SCIM, no audit logs, no SOC 2 or ISO 27001; a DPA and sub-processor list are published but there is no explicit GDPR compliance claim
- − No file export — results share to Slack or Telegram as a recap message, but there is no documented PDF, CSV, Excel, Markdown or email export, so the retro record cannot be filed anywhere outside those two channels
- − 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, and the stage order itself cannot be customised
- − AI is deliberately limited — summaries, recommended next steps and health trends, but no clustering, sentiment analysis or coaching; the vendor pitches this as avoiding 'intrusive chatbots'
- − No cross-team or org-level reporting, so health and action data stays inside a single team's boards
SprintRetro — pros
- + Genuinely free for unlimited users on your Jira instance — the paid Pro app is optional, not the entry point
- + Pulls <strong>real sprint metrics</strong> (velocity, scope change, carryover, cycle time, committed vs delivered) into the retro itself
- + Strong action loop: unfinished actions carry into the next retro, get quality-scored, and can be pushed into Jira as issues
- + <strong>Cloud Fortified</strong> on the Atlassian Marketplace — bug bounty, reliability SLOs, and a one-business-day response commitment on critical tickets
- + Built on Forge: no separate login, and the vendor states no third-party API calls or external data sharing
SprintRetro — cons
- − Jira Cloud only — every participant needs a Jira licence, and there's no Slack, Teams, Confluence, GitHub, or standalone web app
- − <em>No board export at all</em> — no PDF, CSV, or image download; the only data that leaves is a Jira issue
- − No async mode, presentation mode, drag-and-drop grouping, or scheduled/recurring retros
- − No SOC 2 or ISO 27001 of its own — the trust centre shows framework logos with no status label and no attestation report behind them; no SCIM, audit logs, or cross-team reporting either
- − Free-versus-Pro split is undocumented: both Marketplace listings advertise the same feature set, and Pro is never mentioned on sprintretro.co
Keep comparing
Other QRetro comparisons
Other SprintRetro comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.