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 →
TeamRetro
8.7Retrospectives, health checks and agile estimations in one suite
TeamRetro pairs structured retrospectives with longitudinal team health checks and planning-poker estimations, aimed at agile organisations running multiple teams under a coach or programme. An in-meeting AI assistant (trAI) and a GA MCP server sit on top of all paid plans.
Full review →Summary
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.
TeamRetro scores 8.7 overall and is best for agile coaches and engineering managers running ongoing health-check programmes alongside sprint retros. It offers paid plans from $20.83/mo billed annually ($25/mo billed monthly) — Single Team, 1 team, 25 members.
TeamRetro leads on ease of use, retro toolkit, value, fun factor, AI & insights, integrations, open platform and enterprise-grade.
Across our eight scoring dimensions, TeamRetro edges ahead with an overall score of 8.7. That said, the right pick depends on your team — see the dimension-by-dimension breakdown below.
Scores compared
| Detail | Metro Retro | TeamRetro |
|---|---|---|
| Category | Whiteboard | Retrospectives |
| Team size | Small | Any |
| Free tier | No | No |
| Free limit | No free plan — 30-day trial, no credit card required | |
| Starting price | Free | $20.83/mo billed annually ($25/mo billed monthly) — Single Team, 1 team, 25 members |
| Est. 3 teams × 8 people | N/A — brand retired; see the Spreo listing | $50/mo billed annually ($60/mo billed monthly) — Small Organization plan, a 3-team bundle with unlimited members |
| Enterprise | No | Yes |
| Founded | — | 2017 |
| HQ | United Kingdom | Australia |
| Data residency | — | United States · European Union |
| Languages | English only | 29 (English, Arabic, Bengali, …) |
| Export formats | PDF · CSV · HTML · Markdown · JSON · Jira | Excel · CSV · PDF · Markdown · Email · Image |
| Features | 7 | 68 |
| Integrations | 0 | 15 |
Feature & integration comparison
Side-by-side checklist across features, integrations and security. Hover a note for details.
| Capability | Metro Retro | TeamRetro |
|---|---|---|
| Features | ||
| Custom templates | — | ✓ |
| Anonymous input | — | ✓ |
| Health Checks | — | ✓ |
| Action tracking | — | ✓ |
| Async mode | — | ✓ |
| Whiteboard | ✓ | ✓ |
| Independent voting | ✓ | ✓ |
| Polling | — | ✓ |
| Icebreaker games | — | ✓note |
| Agile Estimations | — | ✓ |
| Team Kudos | — | ✓ |
| AI grouping/clustering | — | ✓ |
| AI action items | — | ✓ |
| AI Summaries | — | ✓ |
| Team Insights | — | ✓ |
| In-meeting AI assistant | — | ✓note |
| Action dashboard | — | ✓ |
| Integrations | ||
| Asana | — | ✓ |
| Azure DevOps | — | ✓ |
| Basecamp | — | ✓ |
| ClickUp | — | ✓ |
| Confluence | — | ✓ |
| GitHub | — | ✓ |
| GitLab | — | ✓ |
| Jira | — | ✓ |
| Linear | — | ✓ |
| Microsoft Teams | — | ✓ |
| Monday.com | — | ✓ |
| Notion | — | ✓ |
| Shortcut | — | ✓ |
| Slack | — | ✓ |
| Trello | — | ✓ |
| Security & Privacy | ||
| SOC 2 | — | ✓note |
| GDPR | — | ✓ |
| SSO / SAML | — | ✓ |
| SCIM provisioning | — | ✓note |
| ISO 27001 | — | ✓note |
| On-premises | — | — |
| Public API | — | ✓note |
| Webhooks | — | ✓ |
| MCP server | — | ✓ |
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)
TeamRetro — pros
- + Health checks and maturity models as a first-class module — custom dimensions, radar charts, trends across sprints
- + Three modules on one subscription: retrospectives, health checks, planning-poker estimation
- + SAML SSO, RBAC and US-or-EU hosting on <em>every</em> plan, not just Enterprise
- + GA MCP server, team-level API keys and HMAC-signed webhooks on all plans; 15 native agile-stack integrations plus Zapier and n8n
- + <em>trAI</em> in-meeting assistant on trial and paid plans, plus 12 native in-meeting icebreaker games on every account
TeamRetro — cons
- − No free tier — 30-day trial, then a paid plan
- − The SOC 2 Type 2 report is Enterprise-only; lower tiers get the SOC 3 report instead
- − SCIM, IP allowlisting, domain capture and guest/observer roles are Enterprise-only, and audit logs are on request rather than self-serve
- − Cross-team insights, reports and programs (team-of-teams) require Enterprise
- − ISO 27001 is inherited from AWS, and hosting is US or EU only — no APAC region despite the Australian HQ
Keep comparing
Other Metro Retro comparisons
Other TeamRetro comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.