Twilio
Twilio is selling trust: branded calls, scoped keys, and stricter sender vetting.
A side-by-side editorial comparison of Discourse and Formbricks — 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.
Formbricks is spending its release candidates on tenancy isolation, not new survey features.
Formbricks ships almost exclusively release candidates across three live branches — 5.1, 5.2 and 5.3 — with the same fixes backported into each. Recent work is dominated by multi-tenant scoping (API keys, surveys, quotas, integrations), auth correctness (Better Auth credential accounts, 2FA tables, Azure SSO), and self-host reliability (Helm ordering, Docker environment validation). New user-facing capability is rare, and when it appears it is narrow: chart tweaks, an MCP scope correction.
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.
Formbricks ships almost exclusively release candidates across three live branches — 5.1, 5.2 and 5.3 — with the same fixes backported into each. Recent work is dominated by multi-tenant scoping (API keys, surveys, quotas, integrations), auth correctness (Better Auth credential accounts, 2FA tables, Azure SSO), and self-host reliability (Helm ordering, Docker environment validation). New user-facing capability is rare, and when it appears it is narrow: chart tweaks, an MCP scope correction.
The pattern points at a product hardening for paid, self-hosted, multi-workspace deployments rather than expanding what a survey can do. Nearly every entry is a fix carrying a backport tag, which means the team is maintaining several supported lines at once — a maintenance load that usually arrives with enterprise customers who cannot upgrade on the project's schedule. The one forward-looking thread is the MCP surface: OAuth consent handling and a surveys:write scope suggest agents are being treated as a real client rather than a demo.
Expect the 5.3 line to stabilize into a general release carrying the workspace-scoping and auth fixes already landed, with MCP scope work continuing alongside it. Whether MCP becomes a headline capability or stays plumbing is not something these entries settle.
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 Formbricks.
Twilio is selling trust: branded calls, scoped keys, and stricter sender vetting.
Comm100 publishes buyer-guide content, not releases — and the guides now lead with AI volume.
The cloud edition's log is mostly repair work, much of it inherited from its on-prem twin.
AI assist is spreading edition by edition and region by region, one data center at a time.
A Teams-native helpdesk whose changelog is mostly a marketing blog.
Every merchant tool Richpanel absorbs is one more thing its AI agent can answer alone
See all Discourse alternatives → · See all Formbricks alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Formbricks is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 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. Formbricks is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 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 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.