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 →
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, open-source MCP server exposes 29 read/write tools so Claude, Cursor or VS Code can query boards, health trends and actions directly.
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.
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.
QRetro leads on ease of use, retro toolkit, value, fun factor, AI & insights, integrations 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 | Metro Retro | QRetro |
|---|---|---|
| Category | Whiteboard | Retrospectives |
| Team size | Small | Small |
| Free tier | No | 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 | |
| Starting price | Free | Free |
| Est. 3 teams × 8 people | N/A — brand retired; see the Spreo listing | Free (no paid tier) |
| Enterprise | No | No |
| Founded | — | 2023 |
| HQ | United Kingdom | — |
| Data residency | — | — |
| Languages | English only | English only |
| Export formats | PDF · CSV · HTML · Markdown · JSON · Jira | Markdown · Email · JSON |
| Features | 7 | 38 |
| Integrations | 0 | 3 |
Feature & integration comparison
Side-by-side checklist across features, integrations and security. Hover a note for details.
| Capability | Metro Retro | QRetro |
|---|---|---|
| Features | ||
| Custom templates | — | ✓note |
| Anonymous input | — | ✓note |
| Health Checks | — | ✓note |
| Action tracking | — | ✓ |
| Async mode | — | — |
| Whiteboard | ✓ | — |
| Independent voting | ✓ | ✓ |
| Polling | — | ✓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 | — | ✓note |
| Microsoft Teams | — | — |
| Monday.com | — | — |
| Notion | — | — |
| Shortcut | — | — |
| Slack | — | ✓note |
| Trello | — | — |
| Security & Privacy | ||
| SOC 2 | — | — |
| GDPR | — | ✓note |
| SSO / SAML | — | — |
| SCIM provisioning | — | — |
| ISO 27001 | — | — |
| On-premises | — | — |
| Public API | — | — |
| 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)
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, private-mode submission, a timer, drag-and-drop grouping with auto-named groups, presentation mode, up to five in-board surveys, action items with owners and due dates, ROTI and a radar-charted health check stage
- + 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 MCP server at a single address (mcp.qretro.com) with 29 read, write and delete tools, two analysis prompts and OAuth sign-in — verified live at v1.3.0, and the server source is public on GitHub
- + Guest access with no account or password, and guest contributions persist permanently rather than expiring after a day
- + Visibly active for a solo project: 14 dated changelog entries in 2026 (MCP, OAuth, poker over MCP, two new games), legal pages rewritten in late July 2026 and a site rebuild on 15 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: no SSO or SAML, no SCIM, no audit logs, no SOC 2 or ISO 27001, and no published hosting location or data-residency option
- − Export is thin — a Markdown copy of the summary, an email to the team, a Slack or Telegram recap, and a JSON dump of your own account data. There is no PDF, CSV or Excel, so there is nothing to hand a stakeholder and nothing to drop into a spreadsheet
- − 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, the timer maxes out at 30 minutes, and the stage order itself cannot be customised
- − No working-agreements artifact that survives between retros — what the vendor calls an 'agreement' is an action item on a board
- − No cross-team or org-level reporting: the Analytics section of the dashboard is still labelled <em>Coming soon</em>, so health and action data stays inside a single team's boards
Keep comparing
Other Metro Retro comparisons
Other QRetro comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.