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, 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 →
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 hosted MCP server exposes 29 read/write tools so Claude, Cursor or VS Code can query boards, health trends and actions directly.
Full review →Summary
Parabol scores 7.4 overall and is best for distributed agile teams that want one open-source tool for retros, poker and team health checks. It offers a free tier.
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.
Parabol leads on retro toolkit, AI & insights, integrations, open platform and enterprise-grade. QRetro leads on value.
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 | Parabol | QRetro |
|---|---|---|
| Category | All-in-One Agile | Retrospectives |
| Team size | Any | Small |
| Free tier | Yes | Yes |
| Free limit | Unlimited users, 2 teams, 10 meetings/month, 30-day history, 2 custom templates, 3 AI retro summaries per team | 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 | $8/active user/mo | Free |
| Est. 3 teams × 8 people | $192/mo | Free (no paid tier) |
| Enterprise | Yes | No |
| Founded | 2015 | 2023 |
| HQ | Remote (San Diego, CA) | — |
| Data residency | United States · European Union · Self-hosted | — |
| Languages | English only | English only |
| Export formats | CSV · Email | Markdown · Email · JSON |
| Features | 54 | 39 |
| Integrations | 8 | 3 |
Feature & integration comparison
Side-by-side checklist across features, integrations and security. Hover a note for details.
| Capability | Parabol | QRetro |
|---|---|---|
| Features | ||
| Custom templates | ✓note | ✓note |
| Anonymous input | ✓ | ✓note |
| Health Checks | ✓note | ✓note |
| Action tracking | ✓ | ✓ |
| Async mode | ✓ | — |
| Whiteboard | — | — |
| Independent voting | ✓ | ✓ |
| Polling | — | ✓note |
| Icebreaker games | — | ✓note |
| Agile Estimations | ✓ | ✓note |
| Team Kudos | — | ✓note |
| AI grouping/clustering | ✓note | ✓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 | ✓ | ✓note |
| Linear | ✓ | ✓note |
| Microsoft Teams | ✓ | — |
| Monday.com | — | — |
| Notion | — | — |
| Shortcut | — | — |
| Slack | ✓ | ✓note |
| Trello | — | — |
| Security & Privacy | ||
| SOC 2 | ✓ | — |
| GDPR | ✓ | ✓note |
| SSO / SAML | ✓note | — |
| SCIM provisioning | ✓note | — |
| ISO 27001 | — | — |
| On-premises | ✓note | — |
| Public API | ✓ | — |
| Webhooks | ✓note | — |
| MCP server | — | ✓ |
Parabol — pros
- + Open source (AGPL-3.0) with Docker/Kubernetes self-host, on-prem and air-gapped deployment, plus a DoD Iron Bank hardened container (IL4 via Platform One, IL5 via Arcus)
- + 40+ meeting templates plus poker, 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 threads, and a public GraphQL API with scoped personal access tokens, both on <em>every</em> plan
- + Recurring retro series with a real recurrence rule and Google Calendar sync, plus an opt-in facilitator rotation queue
Parabol — cons
- − Free Starter capped at 2 teams, 10 meetings/month, 30-day history and 3 AI summaries per team; AI grouping and Team Health need the paid Team tier
- − No native whiteboard, presentation mode or screen-share mode
- − Team Health, as of Oct 2026: 5 Likert questions per check across 5 fixed categories, trend limited to the last five checks in one series (no standalone history view), org-wide reporting still "coming soon", no export of health scores
- − 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
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, cards hidden from everyone else until grouping, a timer, drag-and-drop grouping, presentation mode, up to five in-board surveys, action items with owners and priorities, ROTI and a radar-charted health check that trends across retros
- + 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 hosted MCP server with 29 read, write and delete tools, two analysis prompts and OAuth sign-in, listed in the official MCP Registry as com.qretro/retro, though as of October 2026 its documented address (mcp.qretro.com) returns an error
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
- − The data stays inside the product: export is a Markdown copy of the summary, an email, a Slack or Telegram recap and a JSON dump of your own account, with no PDF, CSV or Excel. There is no cross-team reporting either; the dashboard's Analytics section is still labelled <em>Coming soon</em>
- − Integration set is narrow: Jira, Linear, Slack and Telegram only — nothing for Teams, Confluence, GitHub, GitLab, Azure DevOps or any other tracker
- − Built for a live session: no async mode, no recurring or scheduled retros, a fixed stage order, a 30-minute timer cap and an automatic vote allowance (cards + 3, capped at 10). Once cards are grouped, only the group can be voted on
Keep comparing
Other Parabol comparisons
Other QRetro comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.