Most retro tools forget everything the moment the call ends. retromate keeps a living memory of your team — patterns, actions, sentiment — and an AI agent that uses it to prepare every next session.
Three steps, then it loops. Every retro feeds the team profile, which feeds the next retro. The longer you use it, the sharper the recommendations get.
Realtime board with hidden cards until reveal — groupthink prevention enforced at the database level. Cards stay anonymous, even to facilitators.
Retromate AI clusters themes, writes action items, embeds every card to pgvector, and updates your team profile. Tool calls are logged and auditable.
Unresolved items surface at the next retro. Recurring themes get escalated. The template that drove the highest follow-through gets recommended.
Retromate AI doesn't summarize and disappear. It reads your history, writes to your action board, flags stagnant patterns, and updates the team's memory layer.
pgvector semantic search across every retro you've ever run. Themes that appear in 2+ consecutive sprints get auto-escalated to the facilitator.
Items belong to the team, not the session. Open items show up on next retro's pre-flight with their original sprint, owner, and overdue status.
Author IDs are stripped at the row-level security layer — never returned through any API. Cards stay hidden until the facilitator reveals, by design.
Every template's follow-through rate is tracked. Recommendations are weighted by what actually drives action for this team, not generic best practices.
Tool calls, reasoning, and writes are stored against each retro summary. Trust is built by being inspectable — start with Retromate-AI-proposes-human-approves, relax to autonomous when you're ready.
Pattern detection, action continuity, and unlimited history. Most tools cap one or skip another. We built around all three.
Simple per-seat, billed monthly. No history caps on any plan — we mean it.
Every tool call Retromate AI makes — querying history, writing actions, updating the team profile — is logged with timestamps and reasoning. You can run Retromate AI in propose-only mode and approve every write until you trust it.
No. Author IDs are blocked at the row-level security layer in Supabase, not just hidden in the UI. They're never returned through any API route, including admin tools.
A plugin runs once and forgets. Retromate AI reads from and writes to a persistent team memory across every retro — pattern detection, action continuity, template scoring. Miro plus AI is decoration; this is orchestration.
Yes. Unlimited retro history is the entire point of a self-improving system, so capping it would defeat the product. Neatro and Parabol cap free tiers at 30 days — we don't.
Slack two-way and Jira one-way export are in today. Linear, GitHub Issues, and bidirectional Jira ship next quarter. Async retros (Loom-style) are on the v2 roadmap.
Hosted is on Supabase cloud (US or EU regions). Enterprise can run on their own Supabase Postgres and bring their own Anthropic key — full data residency control.
Spin up a workspace in 90 seconds. Free for teams of 5 or fewer. No credit card, no history cap, no nonsense.