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 clusters the cards, writes the board summary and drafts action items that 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, sentiment trend analyses and a team health checker sit on flat pooled-seat pricing — $15/mo for up to 200 seats — rather than per user.
Full review →
Metro Retro
3.0Rebranded 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 a timer, recurring retros or a procurement-grade security story. It offers a free tier.
Metro Retro scores 3.0 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 offers custom pricing.
LetRetro leads on ease of use, retro toolkit, value, AI & insights, integrations, open platform and enterprise-grade. Metro Retro leads on fun factor.
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) | Free |
| 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 | No |
| Founded | 2025 | — |
| HQ | Bengaluru, India | United Kingdom |
| Data residency | — | — |
| Languages | English only | English only |
| Export formats | PDF · Markdown | PDF · CSV · HTML · Markdown · JSON · Jira |
| Features | 27 | 7 |
| Integrations | 5 | 0 |
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 | ✓ | — |
| Health Checks | ✓note | — |
| Action tracking | ✓ | — |
| Async mode | — | — |
| Whiteboard | ✓note | ✓ |
| Independent voting | ✓ | ✓ |
| Polling | ✓note | — |
| Icebreaker games | — | — |
| Agile Estimations | — | — |
| Team Kudos | — | — |
| AI grouping/clustering | ✓ | — |
| 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 | ✓ | — |
| Linear | — | — |
| Microsoft Teams | — | — |
| Monday.com | — | — |
| Notion | ✓ | — |
| Shortcut | — | — |
| Slack | ✓ | — |
| Trello | — | — |
| Security & Privacy | ||
| SOC 2 | — | — |
| GDPR | ✓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: card clustering, board summaries, action items organised by owner, a sentiment snapshot, 50 trend analyses a month, and <strong>Voice Mode</strong> — hold Shift+Space, say a sentence, and it lands as a card in the right column with a priority and due date
- + 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 and Voice Mode all landed between June and August 2026, each documented in a changelog that has matched the product every pass
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: Google and Microsoft sign-in but no SAML, SCIM still 'working on', no customer-facing audit log despite the homepage's <em>immutable audit trails</em> claim, and no LetRetro-held SOC 2 or ISO 27001; on-premise and SLA sit behind a quote-only Enterprise tier
- − Solo-founder micro-SaaS — the team page still lists one person (Dhanush Kandhan, Bengaluru) — and independent coverage is negligible. A durability risk for procurement whatever the shipping cadence
- − Facilitation staples are missing: no timer, no recurring or scheduled retros, no async-first mode, no parking lot and no team agreements. It's built around live sessions
- − No public REST API and no webhooks; MCP is the only programmatic route in, and it — like every integration — is Pro-only. Documented exports are PDF and Markdown, metered 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
- + Carried its playful templates, session timer and icebreakers into the rebrand
- + 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 standalone free tier under the new brand — a 30-day trial, then paid
- − Neither old domain is a clean redirect everywhere: metroretro.io/pricing and ludi.co/pricing both return HTTP 200 with a stale Spreo <em>Non-prod environment</em> stub instead of forwarding (checked 1 Sep 2026)
Keep comparing
Other LetRetro comparisons
Other Metro Retro comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.