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 →
Reetro
6.0Fun, easy and AI-powered online retrospectives
Reetro is a lightweight retrospective tool with a genuinely free tier, a scheduler that auto-creates recurring boards, and AI-powered paid tiers covering meeting summaries, sentiment analysis, AI card grouping, customizable health checks and an action tracker. SSO, 2FA and audit logs start on the $10/team Pro plan rather than an enterprise tier. ISO 27001 is claimed at the vendor level; SOC 2 is described as compliance on SOC 2-certified infrastructure rather than a published Reetro-level Type 2 audit.
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.
Reetro scores 6.0 overall and is best for small to mid-sized agile teams who want a low-cost, easy retro board with AI summaries, customizable health checks, SSO from the $10/team tier and Jira/Azure DevOps export — with a flat-rate org-wide tier if you outgrow per-team pricing. It offers a free tier.
QRetro leads on ease of use, fun factor and open platform. Reetro leads on AI & insights and enterprise-grade.
Across our eight scoring dimensions, Reetro edges ahead with an overall score of 6.0. That said, the right pick depends on your team — see the dimension-by-dimension breakdown below.
Scores compared
| Detail | QRetro | Reetro |
|---|---|---|
| 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 | 3 teams, 9 members per team, 10 active boards per team, 4 columns, 50 guests, 1 health check/month |
| Starting price | Free | $10/team/mo |
| Est. 3 teams × 8 people | Free (no paid tier) | Free (within free tier) |
| Enterprise | No | Yes |
| Founded | 2023 | 2019 |
| HQ | — | Copenhagen, Denmark |
| Data residency | — | — |
| Languages | English only | English only |
| Export formats | — | CSV · Word · Email · Jira · Confluence |
| Features | 32 | 41 |
| Integrations | 3 | 6 |
Feature & integration comparison
Side-by-side checklist across features, integrations and security. Hover a note for details.
| Capability | QRetro | Reetro |
|---|---|---|
| Features | ||
| AI Summaries | ✓ | ✓note |
| AI grouping/clustering | — | ✓note |
| AI action items | ✓note | — |
| Action tracking | ✓ | ✓ |
| Team Insights | ✓note | ✓ |
| Polling | — | ✓note |
| Action dashboard | ✓note | ✓ |
| Custom templates | — | ✓note |
| Anonymous input | ✓note | ✓note |
| Independent voting | ✓ | ✓note |
| Async mode | — | ✓ |
| Agile Estimations | ✓note | — |
| Health Checks | ✓note | ✓ |
| Team Kudos | ✓note | ✓note |
| Whiteboard | — | ✓note |
| Integrations | ||
| Asana | — | — |
| Azure DevOps | — | ✓note |
| Basecamp | — | — |
| ClickUp | — | — |
| Confluence | — | ✓note |
| GitHub | — | — |
| GitLab | — | — |
| Jira | ✓note | ✓note |
| Linear | ✓note | — |
| Microsoft Teams | — | ✓note |
| Monday.com | — | — |
| Notion | — | — |
| Shortcut | — | — |
| Slack | ✓note | ✓note |
| Trello | — | ✓note |
| Security & Privacy | ||
| SOC 2 | — | ✓note |
| GDPR | ✓note | ✓ |
| SSO / SAML | — | ✓note |
| SCIM provisioning | — | — |
| ISO 27001 | — | ✓ |
| On-premises | — | ✓note |
| 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
Reetro — pros
- + Genuinely free tier, no credit card — 3 teams, 9 members and 50 guests covers a 24-person org
- + <strong>SSO (Google, OneLogin, Azure AD, Okta), 2FA and audit logs start on the $10/team Pro plan</strong>, not an enterprise tier
- + Scheduler auto-creates the next retro board weekly or every 2–4 weeks with layout and settings pre-applied
- + AI meeting summaries, sentiment analysis and automatic card grouping on paid, alongside customizable health checks, polls and a happiness index
- + Trust center is actively maintained — policy pack, sub-processor list and an AI governance portal all published or refreshed in 2026
Reetro — cons
- − Free plan capped at 3 teams, 9 members, 10 active boards and 4 columns, with both anonymity and multi-voting paid-only
- − Pro Unlimited's own marketing is self-contradictory — the FAQ and plan table call it flat org-wide $49/mo while the plan card badge says PER TEAM with a 180-member cap
- − Team, comparative and monthly reporting are ticked on the paid columns yet tagged <em>coming soon</em> in the same table — verify the reporting story before you buy
- − On-premises is sold as a Pro Unlimited feature but the tooltip on that plan card says 'coming soon'
- − No published Reetro-level SOC 2 Type 2 audit (their trust center lists SOC 2 as 'compliant', not certified) and no SCIM
- − No public API, webhooks or MCP server; no GitHub/Linear; help-doc footers still read 2020–2021 and there's no public changelog
Keep comparing
Other QRetro comparisons
Other Reetro comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.