LetRetro
5.9The retro tool that thinks with your team
LetRetro is a fast-shipping, AI-forward retrospective platform aimed at engineering teams rather than Scrum Masters. AI writes the board summary (key themes, action items by owner, a sentiment snapshot) and Pro trend analyses track blockers and burnout signals across retros; cards open as Jira, GitHub or GitLab issues; Voice Mode lets anyone speak a card straight into the right column; and an official MCP server lets Claude, Cursor and VS Code read and drive boards. Excalidraw-style Canvas boards sit alongside, all on flat pooled-seat pricing — $15/mo for up to 200 seats — rather than per user.
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 hosted MCP server exposes 29 read/write tools so Claude, Cursor or VS Code can query boards, health trends and actions directly.
Full review →Summary
LetRetro scores 5.9 overall and is best for developer-leaning agile teams and startups that want AI-assisted retros wired into Jira, GitHub and GitLab, an official MCP server their AI clients can drive, and flat pricing that doesn't grow with headcount — and that don't need anonymous input, a shared timer, recurring retros or a procurement-grade security story. 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.
LetRetro leads on integrations and enterprise-grade. QRetro leads on ease of use, retro toolkit, fun factor 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 | LetRetro | QRetro |
|---|---|---|
| Category | Retrospectives | Retrospectives |
| Team size | Small | Small |
| Free tier | Yes | Yes |
| Free limit | 3 boards, 1 team, 20 pooled seats, 1 canvas, 2 AI docs/mo, 5 exports/mo, 10 voice cards/mo; no integrations and no MCP requests; community support | 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 | $15/mo (Pro, flat) | Free |
| Est. 3 teams × 8 people | $15/mo (Pro — flat plan covers unlimited teams within its 200 pooled-seat cap; 24 users fits) | Free (no paid tier) |
| Enterprise | Yes | No |
| Founded | 2025 | 2023 |
| HQ | Bengaluru, India | — |
| Data residency | — | — |
| Languages | English only | English only |
| Export formats | CSV · PDF · Word · Notion · Jira | Markdown · Email · JSON |
| Features | 28 | 39 |
| Integrations | 5 | 3 |
Feature & integration comparison
Side-by-side checklist across features, integrations and security. Hover a note for details.
| Capability | LetRetro | QRetro |
|---|---|---|
| Features | ||
| Custom templates | ✓note | ✓note |
| Anonymous input | — | ✓note |
| Health Checks | — | ✓note |
| Action tracking | ✓note | ✓ |
| Async mode | — | — |
| Whiteboard | ✓note | — |
| Independent voting | ✓note | ✓ |
| Polling | ✓note | ✓note |
| Icebreaker games | — | ✓note |
| Agile Estimations | — | ✓note |
| Team Kudos | — | ✓note |
| AI grouping/clustering | ✓note | ✓note |
| AI action items | ✓note | ✓note |
| AI Summaries | ✓ | ✓ |
| Team Insights | ✓note | ✓note |
| In-meeting AI assistant | — | — |
| Action dashboard | — | ✓note |
| 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 | — | — |
| GDPR | ✓note | ✓note |
| SSO / SAML | ✓note | — |
| SCIM provisioning | — | — |
| ISO 27001 | — | — |
| On-premises | ✓note | — |
| Public API | — | — |
| Webhooks | — | — |
| MCP server | ✓note | ✓ |
LetRetro — pros
- + Flat pricing — $15/mo Pro covers unlimited boards and teams within a 200 pooled-seat cap, so 24 users costs exactly what 4 do
- + AI is the product, not a bolt-on: board summaries with key themes, owner-sorted actions and a sentiment snapshot, 50 cross-retro trend analyses a month on Pro, and <strong>Voice Mode</strong> — hold Shift+Space, say a sentence, and it lands as a card in the right column
- + An <strong>official, MIT-licensed MCP server</strong> — one-command install, 17 tools, 11 clients, and its own component on the public status page — so Claude, Cursor or VS Code can read boards and file cards without a bespoke script
- + Dev-stack card linking is real and deep: Jira, GitHub and GitLab with inline issue editing, comments, MR/PR status, and one card linked across all three at once
- + Ships genuinely fast — AI summaries, MCP, GitLab, Canvas boards, 2FA, Voice Mode and CSV/Google Sheets board export all landed between June and September 2026, each documented in a changelog that matches the shipped product
LetRetro — cons
- − The integrations and comparison pages sell Linear, Asana, Confluence and Snowflake. The shipped app has setup pages for six connectors only — Jira, GitHub, GitLab, Slack, Notion and Google Docs. Verify anything you're depending on
- − Thin enterprise story: SAML is a line on the quote-only Enterprise tier, not something the shipped sign-in flow offers; no SCIM, no customer-facing audit log despite the homepage's <em>immutable audit trails</em> claim, and no LetRetro-held SOC 2 or ISO 27001
- − A bootstrapped team of four on the about page (the founder, one more engineer and two marketers) with negligible independent coverage and no support function behind an SLA. A durability risk for procurement whatever the shipping cadence
- − Retro basics the marketing promises aren't in the app: the templates and use-case pages advertise anonymous input, but every card shows its author and no setting hides it. There's also no card grouping, no shared countdown timer, no recurring retros, no async mode and no team agreements
- − No public REST API and no webhooks; the dashboard's API keys only authenticate the MCP server, which — like every integration — is Pro-only. Boards export to CSV (Google Sheets on Pro) and documents to PDF, Word, Google Docs or Notion; exports are capped at 5/mo on the free tier
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, cards hidden from everyone else until grouping, a timer, drag-and-drop grouping, presentation mode, up to five in-board surveys, action items with owners and priorities, ROTI and a radar-charted health check that trends across retros
- + 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 hosted MCP server with 29 read, write and delete tools, two analysis prompts and OAuth sign-in, listed in the official MCP Registry as com.qretro/retro, though as of October 2026 its documented address (mcp.qretro.com) returns an error
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
- − The data stays inside the product: export is a Markdown copy of the summary, an email, a Slack or Telegram recap and a JSON dump of your own account, with no PDF, CSV or Excel. There is no cross-team reporting either; the dashboard's Analytics section is still labelled <em>Coming soon</em>
- − Integration set is narrow: Jira, Linear, Slack and Telegram only — nothing for Teams, Confluence, GitHub, GitLab, Azure DevOps or any other tracker
- − Built for a live session: no async mode, no recurring or scheduled retros, a fixed stage order, a 30-minute timer cap and an automatic vote allowance (cards + 3, capped at 10). Once cards are grouped, only the group can be voted on
Keep comparing
Other LetRetro comparisons
Other QRetro comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.