Sleekplan
Sleekplan is making the public feedback board safe to run with real customers on it
Comparison · Support
Formbricks vs Request Tracker
A side-by-side editorial comparison of Formbricks and Request Tracker — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:self-hosting
Formbricks vs Request Tracker: at a glance
What is Formbricks?
Formbricks spends a whole RC train on making enterprise SSO stop breaking.
The 5.4 branch is deep in RC hardening and the subject is authentication. Three release candidates landed on 28 August, each a cumulative restatement of the last: Microsoft multi-tenant authorities failing on both native SSO and generic OIDC, local auth factors surviving an SSO recovery, OAuth state rejections no longer paging on-call, and MCP OAuth resource seeding made recoverable. The one piece of new capability is observability — every SSO callback outcome is now recorded.
What is Request Tracker?
Request Tracker maintains three branches in lockstep, and security is what sets the release calendar.
Best Practical ships RT across three concurrent branches, 4.4, 5.0 and 6.0, and coordinates security releases across all of them on the same day. The most recent pair, 5.0.10 and 6.0.3, both landed on 2026-05-20 carrying the same fixes: a privilege escalation and credential disclosure through the REST 2.0 user collection endpoint (CVE-2026-44231), SQL injection via the entry_aggregator parameter in JSON search (CVE-2026-41075), and an LDAP authentication bypass. Feature work rides along on the 6.0 branch, while 5.0 and 4.4 receive security fixes and little else.
Formbricks vs Request Tracker: editorial side-by-side
Formbricks
5.0SUPPORT
Formbricks spends a whole RC train on making enterprise SSO stop breaking.
◆ Current state
The 5.4 branch is deep in RC hardening and the subject is authentication. Three release candidates landed on 28 August, each a cumulative restatement of the last: Microsoft multi-tenant authorities failing on both native SSO and generic OIDC, local auth factors surviving an SSO recovery, OAuth state rejections no longer paging on-call, and MCP OAuth resource seeding made recoverable. The one piece of new capability is observability — every SSO callback outcome is now recorded.
◆ Where it's heading
The substance of 5.4 shipped in 5.4.0-rc.1 — metered workflow runs, Hub feedback filters, the unify-feedback surface — and everything since is the cost of that release meeting real identity providers. Nearly all of it is backported by a single engineer, which suggests a branch being nursed to a final rather than a team still building. Notably the MCP OAuth path is now being maintained alongside human SSO, so agent access is carrying the same auth burden as user access.
◆ Prediction
The pattern points at a 5.4.1 final once the multi-tenant fixes stop arriving, with the new SSO callback telemetry the most likely source of the next round of fixes. Substantive product work should resume on the Hub and the metered workflow_runs price rather than on this branch.
Request Tracker
0.0SUPPORT
Request Tracker maintains three branches in lockstep, and security is what sets the release calendar.
◆ Current state
Best Practical ships RT across three concurrent branches, 4.4, 5.0 and 6.0, and coordinates security releases across all of them on the same day. The most recent pair, 5.0.10 and 6.0.3, both landed on 2026-05-20 carrying the same fixes: a privilege escalation and credential disclosure through the REST 2.0 user collection endpoint (CVE-2026-44231), SQL injection via the entry_aggregator parameter in JSON search (CVE-2026-41075), and an LDAP authentication bypass. Feature work rides along on the 6.0 branch, while 5.0 and 4.4 receive security fixes and little else.
◆ Where it's heading
The branch structure is consolidating. RT 4.4 reached its last planned release at 4.4.9 in October 2025, with users pointed at 5 or 6, and 6.0 is where features now land: dashboard saved searches gained pagination and sorting, statuses take colors from lifecycle configuration, custom fields display multi-column by default, and keyboard menu navigation improved. The 5.0 line still gets real work but of a narrower kind, such as the inline CSS handling in ticket history that shipped with 5.0.10. Expect the same-day multi-branch security release to remain the pattern for as long as two branches are supported.
◆ Prediction
The next release is most likely another coordinated security pair on 5.0 and 6.0, with feature work continuing to accumulate only on 6.0.
Alternatives to Formbricks and Request Tracker
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 Request Tracker.
ManageEngine ServiceDesk Plus
ServiceDesk Plus moved upstream of the ticket, then spent the week tidying the sidebar
Chatway
Chatway's bot learned to read the store; now the store can listen back
ManageEngine ServiceDesk Plus Cloud
ManageEngine's cloud service desk drips small fixes; its AI arrives data center by data center
Desk365
Asset management is the real build; the feed is mostly an interview series.
Hatz AI
Hatz pulls its training platform off TalentLMS and runs it inside the tenant.
See all Formbricks alternatives → · See all Request Tracker alternatives →
Recent activity from Formbricks and Request Tracker
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5d agoFormbricks5.4.1 closes the Microsoft multi-tenant SSO gaps
- 5d agoFormbricksIntermediate 5.4.1 candidate, superseded the same day
- 5d agoFormbricksSingle-fix 5.4.1 candidate, superseded the same day
- 6d agoFormbricksSSO recovery and OAuth state rejection fixed on 5.4
- 7d agoFormbricksSSO loop, Valkey image and survey placeholder fixed on 5.4
- 12d agoFormbricks5.4 opens with metered workflow runs and Hub feedback filters
- 3mo agoRequest TrackerSecurity release fixes REST 2.0 credential disclosure and SQL injection
- 3mo agoRequest TrackerSame security fixes as 5.0.10, plus dashboard and accessibility work
- 10mo agoRequest TrackerCalendar view for saved searches and memory management work
- 10mo agoRequest TrackerCSV injection fix in TSV export, with assorted updates
- 10mo agoRequest TrackerFinal RT 4.4 release closes the branch with one security fix
- 1y agoRequest TrackerRelease exists mainly to support RTIR 6.0.1
Frequently asked questions
What is the difference between Formbricks and Request Tracker?
Both compete on the same themes — self-hosting — within Support. Formbricks is currently shipping more aggressively (velocity 5.0 vs 0.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.
Is Formbricks better than Request Tracker?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Formbricks is currently shipping more aggressively (velocity 5.0 vs 0.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.
What are the best alternatives to Formbricks?
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.
What are the best alternatives to Request Tracker?
Top Request Tracker alternatives in Support are ranked by recent ship velocity. Browse the "Request Tracker alternatives" section above for the current picks, or visit /alternatives/request-tracker for the full list with editorial commentary on each.