Parabol

Parabol is an open-source agile meeting platform spanning retrospectives, sprint poker, async standups, team check-ins and lightweight team health, with deep backlog sync to Jira, GitHub, GitLab, Azure DevOps and Linear, recurring meeting series, and a built-in knowledge base (Pages) that auto-publishes every meeting summary and runs AI queries across past retros.

Parabol pitches itself as the open-source agile meeting platform — retros, sprint poker, standups and check-ins under one roof, AGPL-3.0 on GitHub, with an on-prem option for shops that can't send retro data to someone else's cloud.

"Semantic search, cross-meeting insight generation, automatic sentiment analysis, and theme detection are built in — not a $10/seat/month add-on."

The 2026 messaging chases two new audiences. Pages — the knowledge base that auto-publishes a summary after every meeting — targets teams leaving Confluence Server. A separate public-sector track leads with a hardened container on DoD Platform One's Iron Bank. Voice stays engineer-flavoured: public repo, releases most weeks, no sales theatrics.

Parabol is the most complete open-source retro stack you can buy, and this pass turned up more toolkit than we had credited. Recurring retros are real — a recurrence rule that spawns the next meeting and writes a Google Calendar series — and every tier gets CSV export of reflections, groups, vote counts and discussion threads, not just the emailed summary. Also new: Inspiration Items pull Jira issues and prior standups into the reflect phase, plus synced background music. Team-dashboard Insights was retired for a Pages slash command that queries up to 500 past meetings across several teams.

The gaps are unchanged: health checks are one emoji poll, there's no whiteboard, presentation or screen-share mode, no Confluence, and "webhooks" stop at Mattermost/MS Teams notification URLs. Enterprise is the real story now — SOC 2 Type II, SAML, SCIM, an Org Admin role, an Iron Bank container cleared to IL4 — but Pages Insights needs org-level enablement, so ask for it in the demo. Best fit: distributed teams already living in Jira or Azure DevOps, and regulated orgs needing on-prem.