Kollabe
5.6Agile meetings made easy — retros, standups and planning poker
Kollabe began life as a planning poker tool and has extended into retrospectives and standups — the estimation side remains the centre of gravity, with retros and standups added as adjacent rituals rather than the headline product. It bundles icebreakers, anonymous input, AI summaries and action-item sync-back to Jira, GitHub and Azure DevOps in a flat per-space workspace, and retro history exports in bulk to CSV or JSON. Recent additions include a Slack-based async standup flow, a public API and MCP server, and cross-ritual weekly reporting. Some retro mechanics the marketing asserts are not corroborated outside the vendor's own pages — verify the board before committing.
Full review →
LetRetro
5.6The retro tool that thinks with your team
LetRetro is a young, AI-forward retrospective platform built around retros wired into sprint data. Its headline differentiator is now shipped rather than promised: an official MCP server lets Claude, Cursor, VS Code and other AI clients read and drive boards directly. Real-time collaborative boards, AI-generated retro documentation, sentiment/trend analysis and a team health checker sit on flat (pooled-seat) pricing rather than per-user, with Jira, GitHub, GitLab and Linear card linking to close the loop.
Full review →Summary
Kollabe scores 5.6 overall and is best for small to mid-size agile teams that want retros, standups and planning poker in one clean tool — without per-seat pricing. It offers a free tier.
LetRetro scores 5.6 overall and is best for developer-leaning agile teams and startups that want AI-assisted retros wired into their sprint data and dev stack — Jira, GitHub, GitLab and Linear card linking, plus an official MCP server their AI clients can drive — with health and sentiment tracking and no enterprise overhead. It offers a free tier.
Kollabe leads on ease of use, fun factor and open platform. LetRetro leads on retro toolkit, value, AI & insights, integrations and enterprise-grade.
Kollabe and LetRetro are evenly matched overall. The right choice comes down to which dimensions matter most to your team.
Scores compared
| Detail | Kollabe | LetRetro |
|---|---|---|
| Category | Retrospectives | Retrospectives |
| Team size | Small | Small |
| Free tier | Yes | Yes |
| Free limit | 10 members per room, limited meetings/month, 7-day history, no data export | 3 boards, 1 team, 20 pooled seats, 2 AI docs/mo, 5 exports/mo, community support |
| Starting price | $29/mo | $15/mo (Pro, flat) |
| Est. 3 teams × 8 people | $87/mo (3 team spaces × $29 Premium; each space allows unlimited members) | $15/mo (Pro — flat plan covers unlimited teams within its 200 pooled-seat cap; 24 users fits) |
| Enterprise | Yes | Yes |
| Founded | 2023 | 2025 |
| HQ | Sydney, Australia | Bengaluru, India |
| Data residency | — | — |
| Languages | English only | English only |
| Export formats | Confluence · CSV · JSON | — |
| Features | 29 | 21 |
| Integrations | 6 | 6 |
Feature & integration comparison
Side-by-side checklist across features, integrations and security. Hover a note for details.
| Capability | Kollabe | LetRetro |
|---|---|---|
| Features | ||
| AI Summaries | ✓ | ✓ |
| AI grouping/clustering | — | — |
| AI action items | — | ✓note |
| Action tracking | ✓ | ✓ |
| Team Insights | ✓note | ✓note |
| Polling | ✓ | ✓note |
| Action dashboard | — | ✓note |
| Custom templates | ✓ | ✓note |
| Anonymous input | ✓ | ✓ |
| Independent voting | — | ✓ |
| Async mode | ✓ | — |
| Agile Estimations | ✓ | — |
| Health Checks | — | ✓note |
| Team Kudos | — | — |
| Whiteboard | — | — |
| Integrations | ||
| Asana | — | — |
| Azure DevOps | ✓ | — |
| Basecamp | — | — |
| ClickUp | — | — |
| Confluence | ✓note | — |
| GitHub | ✓ | ✓ |
| GitLab | — | ✓ |
| Jira | ✓ | ✓ |
| Linear | ✓note | ✓ |
| Microsoft Teams | — | — |
| Monday.com | — | — |
| Notion | — | ✓ |
| Shortcut | — | — |
| Slack | ✓note | ✓note |
| Trello | — | — |
| Security & Privacy | ||
| SOC 2 | — | — |
| GDPR | — | ✓note |
| SSO / SAML | ✓note | ✓note |
| SCIM provisioning | — | — |
| ISO 27001 | — | — |
| On-premises | — | ✓note |
| Public API | ✓note | — |
| Webhooks | — | — |
| MCP server | ✓note | ✓note |
Kollabe — pros
- + Flat per-space pricing — unlimited team members on Premium ($29/mo)
- + Bundles retros, standups, planning poker and icebreakers in one tool
- + No-signup join links lower friction for ad-hoc participants; ease of use rates ~5.0/5 across 31 verified third-party reviews
- + Retro action items become real Jira and GitHub tickets — confirmed in independent user reviews, not just vendor copy
- + Bulk export of retro history to CSV or JSON, plus one-click Confluence pages; public API and MCP server on Premium
Kollabe — cons
- − Slack integration is standup-only (no retro summaries or actions to a channel); no Microsoft Teams
- − Solo-founder operation with no SOC 2, ISO 27001 or published GDPR posture; SSO/SAML and SLA sit behind Enterprise contact-sales
- − No health checks, team radars or longitudinal pulse — no way to track team trends across sprints
- − Several vendor-listed retro mechanics (independent dot voting, drag-to-group, AI grouping) are absent from the changelog and could not be corroborated
- − Free tier caps meetings/month with 7-day history and no data export; carrying actions between retros is paid-only
LetRetro — pros
- + Flat pricing — $15/mo Pro covers unlimited boards and teams within a 200 pooled-seat cap, so a growing org isn't billed per head
- + AI is a genuine focus, not a bolt-on: retro-doc generation, sentiment/trend analysis, key takeaways and improvement suggestions that cut the post-retro write-up burden
- + An <strong>official MCP server actually shipped</strong> in July 2026 — one-command install, 17 tools, 11 clients — so Claude, Cursor or VS Code can read boards and file cards without a bespoke script
- + Dev-stack card linking is real and reasonably deep: Jira, GitHub, GitLab and Linear, with inline issue editing, comments and one card linked across several providers at once
- + Built-in team health checker and sentiment-over-time trend dashboards — longitudinal signal many cheap retro tools skip
LetRetro — cons
- − Thin enterprise story: Google and Microsoft sign-in but no SAML SSO, SCIM only 'in progress', no audit-log access, 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 lists one person (Dhanush Kandhan, Bengaluru) still recruiting, and independent coverage is almost nil (9 Product Hunt upvotes, 2 reviews) — a real durability risk for procurement
- − The vendor's own pages contradict each other on connectors: the homepage badges Jira, Confluence and Asana 'Coming Soon' while the integrations page and comparison FAQ list all three as live. Verify anything you're depending on
- − Retro toolkit lacks facilitator staples: no confirmed timer, recurring/scheduled retros, parking lot, team agreements or async-first mode — it's built around live, real-time sessions
- − No public REST API and no webhooks, and the export formats behind the metered '5 exports/mo' limit aren't documented anywhere — MCP is the only programmatic route in
Keep comparing
Other Kollabe comparisons
Other LetRetro comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.