Plain
Plain built an autonomous support agent, and has now built the controls to trust it.
A side-by-side editorial comparison of Discourse and Frill — release velocity, themes, recent moves, and the top alternatives to consider.
Monthly releases on time, security out-of-band, and the changelog living somewhere else
Discourse ships a dated minor every month — 2026.4 through 2026.7 in this window — and back-patches several supported branches alongside each one. Critical security fixes travel separately as out-of-band intermediate releases, the most recent on July 31 covering the 2026.8 pre-release line plus the 2026.7, 2026.6 and 2026.1 branches. The release topics carry no detail of their own; each links out to releases.discourse.org. The remainder of the feed is administrator documentation.
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.
Discourse ships a dated minor every month — 2026.4 through 2026.7 in this window — and back-patches several supported branches alongside each one. Critical security fixes travel separately as out-of-band intermediate releases, the most recent on July 31 covering the 2026.8 pre-release line plus the 2026.7, 2026.6 and 2026.1 branches. The release topics carry no detail of their own; each links out to releases.discourse.org. The remainder of the feed is administrator documentation.
The cadence is the signal and it has not wavered: a monthly minor, patches reaching back to branches cut in January, and security decoupled from the feature train. That is the maintenance posture of self-hosted software whose installs upgrade on their own schedule, and the branch count is the tell — still patching 2026.1 at the end of July means an install that has sat still for six months is covered. Where the product is actually heading surfaces in the documentation instead, where the AI bot's support for external MCP servers is the only entry in the last ten describing a capability rather than a version number.
The August 2026 monthly release is the near-certain next entry, in the same pointer-topic shape. What lands inside it cannot be read from this feed — these topics are links, so any call on direction would have to come from the linked changelog.
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 Discourse 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 Discourse alternatives → · See all Frill alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. 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 Discourse alternatives in Support are ranked by recent ship velocity. Browse the "Discourse alternatives" section above for the current picks, or visit /alternatives/discourse 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.