Plain
Plain built an autonomous support agent, and has now built the controls to trust it.
A side-by-side editorial comparison of Formbricks and Frill — release velocity, themes, recent moves, and the top alternatives to consider.
The 5.3 line reached stable and immediately dropped into single-fix patch-RC mode.
Formbricks runs three release branches at once — 5.1, 5.2 and 5.3 — publishing release candidates almost daily, most carrying a single backported fix. The 5.3 line has moved past its feature RCs: 5.3.0-rc.1 through rc.3 delivered MCP scope corrections, Helm volume extension points and an accessibility pass, and the branch is now on 5.3.4-rc.1, a one-line fix stopping no-overlay surveys from blocking the host page they sit on. Workspace and organization scoping remains the recurring thread, with the contact detail page the latest surface re-tied to its authorizing workspace.
Frill is turning its feedback board from a destination into something machines read on demand.
The MCP server is the centrepiece: ten tools, one API key, no configuration, callable from Claude, ChatGPT, Cursor or Intercom Fin, and included on every plan rather than gated. The Chrome extension follows the same instinct from the capture side — grab an idea wherever you spot it, and collapse a long help desk thread into a clean idea with an AI summary in one click. Behind both sits the June groundwork: a public npm SDK, multiple API keys, webhook handling, and MCP in public beta.
Formbricks runs three release branches at once — 5.1, 5.2 and 5.3 — publishing release candidates almost daily, most carrying a single backported fix. The 5.3 line has moved past its feature RCs: 5.3.0-rc.1 through rc.3 delivered MCP scope corrections, Helm volume extension points and an accessibility pass, and the branch is now on 5.3.4-rc.1, a one-line fix stopping no-overlay surveys from blocking the host page they sit on. Workspace and organization scoping remains the recurring thread, with the contact detail page the latest surface re-tied to its authorizing workspace.
The multi-tenancy audit is still running and still backported everywhere rather than only forward — API keys, surveys, quotas, integrations, response imports and now the contact detail page have each been re-scoped in turn. Alongside it, the agent-facing surface built out in 5.2.0 is being refined rather than extended: the 5.3 MCP work is scope correction, not new capability. With 5.3 now issuing patch RCs a day or two apart, that branch has crossed from feature development into maintenance.
Expect 5.3 to keep issuing single-fix patch release candidates while the next feature drop opens a 5.4 line, and 5.1 and 5.2 to continue receiving only security and billing backports.
The MCP server is the centrepiece: ten tools, one API key, no configuration, callable from Claude, ChatGPT, Cursor or Intercom Fin, and included on every plan rather than gated. The Chrome extension follows the same instinct from the capture side — grab an idea wherever you spot it, and collapse a long help desk thread into a clean idea with an AI summary in one click. Behind both sits the June groundwork: a public npm SDK, multiple API keys, webhook handling, and MCP in public beta.
Frill is systematically removing the requirement to be in Frill. Capture moves to wherever the conversation already happens; retrieval moves to whatever assistant the team already uses. That reframes the product as the feedback store rather than the feedback interface, and the pricing decision reinforces it — putting MCP on every plan optimises for the corpus being queried, not for upsell. The earlier enterprise work (EU hosting, EntraID SSO, CSP) is what makes that store trustworthy enough to hold the data.
Expect write paths to follow the read paths — an assistant that can already ask what users want will next be expected to file, merge and status ideas — and expect more capture surfaces beyond the browser extension.
Other Support products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Formbricks or Frill.
Plain built an autonomous support agent, and has now built the controls to trust it.
Sleekplan rebuilt itself around AI triage, then put the feedback board inside ChatGPT.
Comm100 publishes steadily about AI support — none of it is Comm100 shipping anything.
respond.io is layering an agent-authoring copilot and consumption billing on top of its omnichannel inbox.
Hatz sells through MSPs, and its roadmap has started to serve the partner more than the end user
A teaser-only content feed making one argument: AI in the contact center fails on knowledge, not models.
See all Formbricks alternatives → · See all Frill alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcp — within Support. Frill is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Frill is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Support products to evaluate alongside.
Top Formbricks alternatives in Support are ranked by recent ship velocity. Browse the "Formbricks alternatives" section above for the current picks, or visit /alternatives/formbricks for the full list with editorial commentary on each.
Top Frill alternatives in Support are ranked by recent ship velocity. Browse the "Frill alternatives" section above for the current picks, or visit /alternatives/frill for the full list with editorial commentary on each.