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 →
Neatro
5.5Structured retros built around psychological safety
Neatro runs retrospectives through a guided four-step framework with optional per-comment anonymity, AI grouping suggestions, an automatic ROTI survey, and Team Radar health checks aimed at distributed agile teams.
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.
Neatro scores 5.5 overall and is best for scrum Masters who want a guided, safety-first facilitation flow with built-in team health tracking. It offers a free tier.
LetRetro leads on value, AI & insights, integrations and open platform. Neatro leads on ease of use, 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 | Neatro |
|---|---|---|
| Category | Retrospectives | Retrospectives |
| Team size | Small | Mid-market |
| Free tier | Yes | Yes |
| 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 | Free forever for 1 team of up to 10 members: unlimited retrospectives and Team Radars, all 70 ready-to-use templates, 1 custom template, 40 Neatroverse community templates, basic facilitation tools, 30-day data history — no exports and no integrations |
| Starting price | $15/mo (Pro, flat) | $23.20/team/mo billed annually ($29/team/mo billed monthly), USD |
| Est. 3 teams × 8 people | $15/mo (Pro — flat plan covers unlimited teams within its 200 pooled-seat cap; 24 users fits) | $69.60/mo billed annually (3 teams x Premium at $23.20; members per team are unlimited) — $87/mo if billed monthly |
| Enterprise | Yes | Yes |
| Founded | 2025 | 2020 |
| HQ | Bengaluru, India | Quebec, Canada |
| Data residency | — | Canada |
| Languages | English only | 2 (English, French) |
| Export formats | PDF · Markdown | PDF · CSV · Jira |
| Features | 27 | 30 |
| Integrations | 5 | 5 |
Feature & integration comparison
Side-by-side checklist across features, integrations and security. Hover a note for details.
| Capability | LetRetro | Neatro |
|---|---|---|
| Features | ||
| Custom templates | ✓note | ✓ |
| Anonymous input | ✓ | ✓ |
| Health Checks | ✓note | ✓ |
| Action tracking | ✓ | ✓ |
| Async mode | — | ✓note |
| Whiteboard | ✓note | — |
| Independent voting | ✓ | ✓ |
| Polling | ✓note | — |
| Icebreaker games | — | — |
| Agile Estimations | — | — |
| Team Kudos | — | — |
| AI grouping/clustering | ✓ | ✓note |
| AI action items | ✓note | — |
| AI Summaries | ✓ | — |
| Team Insights | ✓note | — |
| In-meeting AI assistant | — | — |
| Action dashboard | ✓note | ✓ |
| Integrations | ||
| Asana | — | ✓note |
| Azure DevOps | — | ✓note |
| Basecamp | — | — |
| ClickUp | — | — |
| Confluence | — | — |
| GitHub | ✓ | ✓note |
| GitLab | ✓ | — |
| Jira | ✓ | ✓note |
| Linear | — | — |
| Microsoft Teams | — | — |
| Monday.com | — | ✓note |
| Notion | ✓ | — |
| Shortcut | — | — |
| Slack | ✓ | — |
| Trello | — | — |
| Security & Privacy | ||
| SOC 2 | — | — |
| GDPR | ✓note | — |
| SSO / SAML | ✓note | ✓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
Neatro — pros
- + Guided four-step framework with optional anonymous commenting and a timer on every step
- + Team Radar is a proper recurring health check with up to 10 custom dimensions, not a repurposed template
- + AI grouping suggestions at Step 2 that the facilitator accepts or rejects one at a time — assistive, not automatic
- + Action Kanban board, an automatic ROTI survey and a prompt about last retro's open actions keep follow-through visible
- + Cheap per head — <strong>$23.20/team/mo covers unlimited members</strong>, and the free tier runs 10 members forever
Neatro — cons
- − No native Slack or Microsoft Teams integration — reminders and summaries land wherever you paste the link
- − AI stops at grouping suggestions; no summaries, sentiment analysis, or AI-extracted action items
- − Free tier has <em>no exports and no integrations</em> — both start at Premium
- − Per-team pricing gets awkward past a handful of squads — volume discounts only start at 20+ teams
- − No SOC 2 or ISO 27001 of its own (the security FAQ points at Azure's), no GDPR statement, and hosting is Quebec-only
- − No cross-team rollups, org health dashboard, SCIM, audit logs, public API or webhooks
Keep comparing
Other LetRetro comparisons
Other Neatro comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.