Echometer
5.3Psychology-backed retros and team health checks for engineering teams
Echometer is a German retrospective and 1:1 meeting platform built around recurring health-check pulses, structured retros, and longitudinal team development tracking. It pitches itself to engineering managers, scrum masters and agile coaches who want research-grounded surveys rather than a blank whiteboard.
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
Echometer scores 5.3 overall and is best for engineering managers and agile coaches who want recurring health-check pulses tied to retros, with EU data residency and a research-flavoured question library. 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.
Echometer leads on retro toolkit, fun factor and enterprise-grade. LetRetro leads on ease of use, value, AI & insights, integrations and open platform.
Across our eight scoring dimensions, LetRetro edges ahead with an overall score of 5.6. That said, the right pick depends on your team — see the dimension-by-dimension breakdown below.
Scores compared
| Detail | Echometer | LetRetro |
|---|---|---|
| Category | Retrospectives | Retrospectives |
| Team size | Mid-market | Small |
| Free tier | Yes | Yes |
| Free limit | Starter: 1 team, 25 workspace members, unlimited retro guests, 1 retro/month after trial, 2-retro archive per team | 3 boards, 1 team, 20 pooled seats, 2 AI docs/mo, 5 exports/mo, community support |
| Starting price | €29/team/mo | $15/mo (Pro, flat) |
| Est. 3 teams × 8 people | €87/mo billed annually (3 teams × €29 Pro) | $15/mo (Pro — flat plan covers unlimited teams within its 200 pooled-seat cap; 24 users fits) |
| Enterprise | Yes | Yes |
| Founded | 2019 | 2025 |
| HQ | Münster, Germany | Bengaluru, India |
| Data residency | Germany | — |
| Languages | 2 (English, German) | English only |
| Export formats | PDF · Markdown · Email | — |
| Features | 43 | 21 |
| Integrations | 1 | 6 |
Feature & integration comparison
Side-by-side checklist across features, integrations and security. Hover a note for details.
| Capability | Echometer | LetRetro |
|---|---|---|
| Features | ||
| AI Summaries | — | ✓ |
| AI grouping/clustering | — | — |
| AI action items | ✓note | ✓note |
| Action tracking | ✓ | ✓ |
| Team Insights | — | ✓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 | — | — |
| GitHub | — | ✓ |
| GitLab | — | ✓ |
| Jira | ✓ | ✓ |
| Linear | — | ✓ |
| Microsoft Teams | — | — |
| Monday.com | — | — |
| Notion | — | ✓ |
| Shortcut | — | — |
| Slack | — | ✓note |
| Trello | — | — |
| Security & Privacy | ||
| SOC 2 | — | — |
| GDPR | ✓ | ✓note |
| SSO / SAML | ✓note | ✓note |
| SCIM provisioning | — | — |
| ISO 27001 | — | — |
| On-premises | — | ✓note |
| Public API | — | — |
| Webhooks | — | — |
| MCP server | — | ✓note |
Echometer — pros
- + 200+ research-grounded health-check items, custom models and automated pulse rotation
- + Longitudinal team radars, heatmaps and workspace dashboards tied to retros
- + EU-only data residency (Open Telekom Cloud, Germany) with GDPR DPA
- + Open actions resurface automatically in the next retro, with email reminders to owners
- + Per-team pricing — €87/mo covers three teams of eight, billed annually
Echometer — cons
- − Thin integrations — Jira and calendar sync only; no Slack, Teams or Confluence
- − No public API or webhooks; export is PDF and Markdown only
- − No SOC 2 — the ISO 27001 certificate covers the datacenter, not Echometer itself
- − Retro-side AI stops at suggesting measures; transcript coaching is a separately-priced 1:1 product
- − No scheduled or recurring retros — you copy a past format and start each session manually
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 Echometer comparisons
Other LetRetro comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.