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 →
Parabol
7.4Open-source agile meetings for retros, poker, standups and check-ins
Parabol is an open-source agile meeting platform spanning retrospectives, sprint poker, async standups, team check-ins and recurring team health checks, with deep backlog sync to Jira, GitHub, GitLab, Azure DevOps and Linear, recurring meeting series, Zoom and Google Meet transcript capture, a scoped GraphQL API, and a built-in knowledge base (Pages) that auto-publishes every meeting summary and runs AI queries across past retros.
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.
Parabol scores 7.4 overall and is best for distributed agile teams that want one open-source tool for retros, poker, standups and team health checks. It offers a free tier.
LetRetro leads on value. Parabol leads on ease of use, retro toolkit, fun factor, AI & insights, integrations, open platform and enterprise-grade.
Across our eight scoring dimensions, Parabol edges ahead with an overall score of 7.4. That said, the right pick depends on your team — see the dimension-by-dimension breakdown below.
Scores compared
| Detail | LetRetro | Parabol |
|---|---|---|
| Category | Retrospectives | All-in-One Agile |
| Team size | Small | Any |
| 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 | Unlimited users, 2 teams, 10 meetings/month, 30-day history, 2 custom templates, 3 AI retro summaries/month |
| Starting price | $15/mo (Pro, flat) | $8/active user/mo |
| Est. 3 teams × 8 people | $15/mo (Pro — flat plan covers unlimited teams within its 200 pooled-seat cap; 24 users fits) | $192/mo |
| Enterprise | Yes | Yes |
| Founded | 2025 | 2015 |
| HQ | Bengaluru, India | Remote (San Diego, CA) |
| Data residency | — | United States · European Union · Self-hosted |
| Languages | English only | English only |
| Export formats | PDF · Markdown | CSV · Email |
| Features | 27 | 49 |
| Integrations | 5 | 8 |
Feature & integration comparison
Side-by-side checklist across features, integrations and security. Hover a note for details.
| Capability | LetRetro | Parabol |
|---|---|---|
| Features | ||
| Custom templates | ✓note | ✓note |
| Anonymous input | ✓ | ✓ |
| Health Checks | ✓note | ✓note |
| Action tracking | ✓ | ✓ |
| Async mode | — | ✓ |
| Whiteboard | ✓note | — |
| Independent voting | ✓ | ✓ |
| Polling | ✓note | ✓note |
| Icebreaker games | — | — |
| Agile Estimations | — | ✓ |
| Team Kudos | — | — |
| AI grouping/clustering | ✓ | ✓note |
| AI action items | ✓note | — |
| AI Summaries | ✓ | ✓note |
| Team Insights | ✓note | ✓note |
| In-meeting AI assistant | — | — |
| Action dashboard | ✓note | ✓ |
| Integrations | ||
| Asana | — | — |
| Azure DevOps | — | ✓ |
| Basecamp | — | — |
| ClickUp | — | — |
| Confluence | — | ✓note |
| GitHub | ✓ | ✓ |
| GitLab | ✓ | ✓ |
| Jira | ✓ | ✓ |
| Linear | — | ✓ |
| Microsoft Teams | — | ✓ |
| Monday.com | — | — |
| Notion | ✓ | — |
| Shortcut | — | — |
| Slack | ✓ | ✓ |
| Trello | — | — |
| Security & Privacy | ||
| SOC 2 | — | ✓ |
| GDPR | ✓note | ✓ |
| SSO / SAML | ✓note | ✓note |
| SCIM provisioning | — | ✓note |
| ISO 27001 | — | — |
| On-premises | ✓note | ✓note |
| Public API | — | ✓ |
| Webhooks | — | ✓note |
| 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
Parabol — pros
- + Open source (AGPL-3.0) with Docker/Kubernetes self-host, on-prem and air-gapped deployment
- + 40+ meeting templates plus poker, standups, check-ins and team health in one tool
- + Strong backlog write-back to Jira, GitHub, GitLab, Azure DevOps and Linear
- + CSV export of reflections, groups, votes and discussion threads on <em>every</em> tier
- + Public GraphQL API with published schema, a GraphiQL explorer and scoped personal access tokens
- + Recurring retro series with a real recurrence rule, Google Calendar sync and automatic facilitator rotation
- + DoD Iron Bank hardened container — IL4 via Platform One, IL5 via Arcus
Parabol — cons
- − Free tier capped at 2 teams, 10 meetings/month, 30-day history and 3 AI summaries
- − No native whiteboard, presentation mode or screen-share mode
- − Team Health, as of Sep 2026: 5 Likert questions per cycle across 5 fixed categories, a streak counter rather than a trend view, no cross-team rollup and no export
- − AI grouping and team health need the paid Team tier; Pages Insights and Confluence export need org-level enablement
- − Webhooks stop at Mattermost/MS Teams notification URLs — no general event subscriptions and no MCP server
- − English-only UI; no Trello, Asana, ClickUp or Notion integration
Keep comparing
Other LetRetro comparisons
Other Parabol comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.