LetRetro
6.0The 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 →
Metro Retro
3.9Rebranded twice — Metro Retro became Ludi, now Spreo; the playful retro whiteboard lives on
Metro Retro was a fun, freeform online whiteboard built for sprint retrospectives, known for its playful templates, timer and engagement features. The product has since been renamed twice by its maker, Deqo Software Limited: to Ludi on 4 August 2025, then to Spreo on 1 July 2026 after a trademark cease-and-desist. The metroretro.io domain now 301-redirects straight to spreo.io. If you are searching for Metro Retro, the product you want is Spreo; the original Metro Retro brand and domain are no longer maintained.
Full review →Summary
LetRetro scores 6.0 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, card grouping, recurring retros or a procurement-grade security story. It offers a free tier.
Metro Retro scores 3.9 overall and is best for searchers who remember Metro Retro and need to know where it went — the product now ships as <strong>Spreo</strong>. Go there, or to a dedicated retro platform, instead. It is no longer available.
LetRetro leads on ease of use, value, AI & insights, integrations and open platform. Metro Retro leads on retro toolkit, fun factor and enterprise-grade.
Across our eight scoring dimensions, LetRetro 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 | LetRetro | Metro Retro |
|---|---|---|
| Category | Retrospectives | Whiteboard |
| Team size | Small | Small |
| Free tier | Yes | No |
| 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 | — |
| Starting price | $15/mo (Pro, flat) | N/A — brand retired; see the Spreo listing |
| Est. 3 teams × 8 people | $15/mo (Pro — flat plan covers unlimited teams within its 200 pooled-seat cap; 24 users fits) | N/A — brand retired; see the Spreo listing |
| Enterprise | Yes | Yes |
| Founded | 2025 | 2019 |
| HQ | Bengaluru, India | United Kingdom |
| Data residency | — | European Union |
| Languages | English only | English only |
| Export formats | CSV · PDF · Word · Notion · Jira | PDF · CSV · HTML · Markdown · JSON · Jira |
| Features | 31 | 40 |
| Integrations | 5 | 1 |
Feature & integration comparison
Side-by-side checklist across features, integrations and security. Hover a note for details.
| Capability | LetRetro | Metro Retro |
|---|---|---|
| Features | ||
| Custom templates | ✓note | ✓ |
| Anonymous input | — | ✓note |
| Health Checks | — | — |
| Action tracking | ✓note | ✓ |
| Async mode | — | — |
| Whiteboard | ✓note | ✓ |
| Independent voting | ✓ | ✓ |
| Polling | ✓note | ✓note |
| Icebreaker games | — | ✓note |
| Agile Estimations | — | ✓note |
| Team Kudos | — | ✓note |
| AI grouping/clustering | ✓note | — |
| AI action items | ✓note | — |
| AI Summaries | ✓ | — |
| Team Insights | ✓note | — |
| In-meeting AI assistant | — | — |
| Action dashboard | — | ✓note |
| Integrations | ||
| Asana | — | — |
| Azure DevOps | — | — |
| Basecamp | — | — |
| ClickUp | — | — |
| Confluence | — | — |
| GitHub | ✓ | — |
| GitLab | ✓ | — |
| Jira | ✓ | ✓note |
| Linear | — | — |
| Microsoft Teams | — | — |
| Monday.com | — | — |
| Notion | ✓ | — |
| Shortcut | — | — |
| Slack | ✓ | — |
| Trello | — | — |
| Security & Privacy | ||
| SOC 2 | — | — |
| GDPR | ✓note | ✓ |
| SSO / SAML | ✓note | ✓note |
| SCIM provisioning | — | — |
| ISO 27001 | — | — |
| On-premises | ✓note | ✓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 remote MCP server</strong> with browser sign-in and per-workspace approval, read-only by default, so Claude, Codex, Cursor or VS Code can search boards and, once writes are approved, add cards, polls and reports 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, use-case and help-centre pages advertise anonymous input, but every card shows its author once revealed and no setting hides it. There's also no card grouping, no recurring retros, no async mode and no team agreements
- − No public REST API and no webhooks; MCP is the only programmatic route, and like every integration it needs a Pro owner. 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
Metro Retro — pros
- + The product you remember still exists — it now ships as Spreo (Metro Retro → Ludi, 4 Aug 2025 → Spreo, 1 Jul 2026)
- + The vendor says accounts, boards, data and workflows carried through both renames, and old links redirect
- + At retirement it had private writing, Hide Identities anonymity, voting rounds, and actions with owners, due dates and overdue emails
- + Freeform whiteboard canvas that's friendly for engagement-first retros
Metro Retro — cons
- − The Metro Retro brand and metroretro.io domain are retired — the domain 301-redirects straight to spreo.io
- − Two name changes in under a year (Metro Retro → Ludi → Spreo) leave stranded searchers chasing a moving target; bookmarks, runbooks and SSO configs all need updating
- − No free tier at retirement — a 30-day trial, then paid — and Jira, SSO and PDF export needed the Business plan
- − No health checks, no async mode and no Slack or Teams integration
Keep comparing
Other LetRetro comparisons
Other Metro Retro comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.