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 →
SprintRetro
5.9Jira-native retros with real sprint data
SprintRetro is an Atlassian Forge app from Agile Pulse that runs sprint retrospectives inside Jira Cloud. It pulls live sprint metrics (velocity and predictability, scope change, carryover, cycle time, second-by-second burndown) into the retro board itself. A major June 2026 release widened it into a continuous-improvement workspace: an infinite whiteboard with visual templates, anonymous team-health pulse checks with cross-sprint trends, an on-demand AI facilitator, and an action dashboard that quality-scores every action. Both Marketplace listings are Cloud Fortified. The free app still covers unlimited users, but a paid Pro app now carries custom templates, unlimited grouping and AI sprint summaries.
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.
SprintRetro scores 5.9 overall and is best for scrum teams already living in Jira Cloud who want retros, a whiteboard and real sprint metrics on one board — and are happy for everything to stay inside Jira's walls. It offers a free tier.
Metro Retro leads on open platform. SprintRetro leads on ease of use, retro toolkit, value, fun factor, AI & insights, integrations and enterprise-grade.
Across our eight scoring dimensions, SprintRetro edges ahead with an overall score of 5.9. That said, the right pick depends on your team — see the dimension-by-dimension breakdown below.
Scores compared
| Detail | Metro Retro | SprintRetro |
|---|---|---|
| Category | Whiteboard | Retrospectives |
| Team size | Small | Small |
| Free tier | No | Yes |
| Free limit | Unlimited users on a Jira site, but capped: 3 basic templates, no custom template creation, limited polls and card grouping, no AI sprint summary. Vendor has published planned caps of ~3–5 sessions/month and under 8 participants per session. | |
| Starting price | Free | $8.40/user/yr (SprintRetro Pro, annual only; free on Jira sites of 10 or fewer users) |
| Est. 3 teams × 8 people | N/A — brand retired; see the Spreo listing | $17.50/mo (Pro, $210/yr at the 25-user Jira tier) — the free app also still covers 24 users |
| Enterprise | No | No |
| Founded | — | — |
| HQ | United Kingdom | Waterlooville, United Kingdom |
| Data residency | — | — |
| Languages | English only | English only |
| Export formats | PDF · CSV · HTML · Markdown · JSON · Jira | Image · PDF · Jira |
| Features | 7 | 35 |
| Integrations | 0 | 1 |
Feature & integration comparison
Side-by-side checklist across features, integrations and security. Hover a note for details.
| Capability | Metro Retro | SprintRetro |
|---|---|---|
| Features | ||
| Custom templates | — | ✓note |
| Anonymous input | — | ✓ |
| Health Checks | — | ✓note |
| Action tracking | — | ✓ |
| Async mode | — | — |
| Whiteboard | ✓ | ✓ |
| Independent voting | ✓ | ✓ |
| Polling | — | ✓ |
| Icebreaker games | — | — |
| Agile Estimations | — | — |
| Team Kudos | — | ✓ |
| AI grouping/clustering | — | ✓ |
| AI action items | — | ✓ |
| AI Summaries | — | ✓note |
| 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 | — | ✓ |
| SSO / SAML | — | ✓note |
| 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)
SprintRetro — pros
- + <strong>Real Jira sprint data inside the retro</strong> — velocity and predictability over five sprints, scope change, carryover tagged with how many sprints an issue has slipped, cycle time per status, and a burndown that records every individual point change
- + The action loop is the best part: actions link back to the idea that triggered them, carry forward with duplicate protection, get an AI SMART quality score with a one-tap rewrite, and can be pushed into Jira as issues
- + June 2026 added a genuine infinite whiteboard — stickies, shapes, frames, tables, connectors, live cursors, follow-a-teammate, Tenor GIFs, private mode, a synced board timer, PNG/print-PDF export, and <em>board import from Miro or Mural</em>
- + Anonymous Team Health pulses across seven dimensions, with cross-sprint trends overlaid against committed-vs-delivered and carryover — the health-vs-delivery view is rare at this price
- + <strong>Cloud Fortified</strong> and Bugcrowd bug-bounty on both listings, and the free app still covers unlimited users on a Jira site
SprintRetro — cons
- − Jira Cloud only — every participant needs a Jira licence, and there is no Slack, Teams, Confluence or standalone web app, nor any public API, webhooks or MCP server
- − <em>The free tier is narrowing.</em> Today: 3 basic templates, no custom template creation, limited polls and grouping, no AI sprint summary. Published as planned: ~3–5 sessions/month and under 8 participants per session
- − No SOC 2 or ISO 27001 of its own — the trust centre's own entries attribute both to AWS, Atlassian Cloud and Render, not to an Agile Pulse audit. No SCIM, audit logs or data residency, and the app is not "Runs on Atlassian" certified
- − No async mode, no recurring or scheduled retros, and no cross-team or org-level health rollup — the Pro usage report covers adoption, not outcomes
- − Export is whiteboard-only (PNG or print-to-PDF); column-mode retros still have no board export beyond pushing an action into Jira
Keep comparing
Other Metro Retro comparisons
Other SprintRetro comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.