← Back to home
Comparison · Support

Request Tracker vs Xurrent

A side-by-side editorial comparison of Request Tracker and Xurrent — release velocity, themes, recent moves, and the top alternatives to consider.

Request Tracker vs Xurrent: at a glance

FeatureRequest TrackerXurrent
SectorSupportSupport
Velocity score0.06.3
Sparks · 30d01
Top themesticketing, security-releases, multi-branch, cveitsm, ai-workflow, enterprise-automation, service-management
Last editorial update20d ago5d ago
WebsiteVisit →Visit →

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.

Read the full Request Tracker trajectory →

What is Xurrent?

Xurrent is weaving Sera AI deeper into its ITSM automation layer while opening iPaaS connectivity to third-party builders.

Xurrent is an enterprise ITSM platform shipping consistent weekly batches, with Sera AI becoming the defining feature thread across classification, guardrails, fallback templates, and an AI Studio guide. The platform handles reservations, tickets, SLAs, and knowledge management for large IT organizations. Its cadence is high and disciplined.

Read the full Xurrent trajectory →

Request Tracker vs Xurrent: editorial side-by-side

R0.0

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.

X
Xurrent
SUPPORT
6.3

Xurrent is weaving Sera AI deeper into its ITSM automation layer while opening iPaaS connectivity to third-party builders.

◆ Current state

Xurrent is an enterprise ITSM platform shipping consistent weekly batches, with Sera AI becoming the defining feature thread across classification, guardrails, fallback templates, and an AI Studio guide. The platform handles reservations, tickets, SLAs, and knowledge management for large IT organizations. Its cadence is high and disciplined.

◆ Where it's heading

The iPaaS Connector SDK, launched in August, is the most strategic move in recent months — it shifts Xurrent from a closed ITSM tool to an integration platform that third parties can extend. Sera AI is simultaneously maturing from experimental to governed, with guardrails and agent audit logs signaling preparation for enterprise compliance requirements around AI-assisted ticket handling.

◆ Prediction

The most likely next move is a connector library or template marketplace built on the new iPaaS SDK. The Sera AI guardrails and audit log also suggest a compliance certification announcement is in preparation.

Alternatives to Request Tracker and Xurrent

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 Request Tracker or Xurrent.

See all Request Tracker alternatives → · See all Xurrent alternatives →

Recent activity from Request Tracker and Xurrent

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 6d agoXurrentXurrent ITSM - September 2026 Product Updates
  2. 13d agoXurrentXurrent ITSM - September 2026 Product Updates
  3. 20d agoXurrentXurrent ITSM - August 2026 Product Updates
  4. 27d agoXurrentXurrent ITSM - August 2026 Product Updates
  5. 1mo agoXurrentXurrent ITSM - August 2026 Product Updates
  6. 1mo agoXurrentXurrent IMR Q3 2026 (in progress)
  7. 3mo agoRequest TrackerSecurity release fixes REST 2.0 credential disclosure and SQL injection
  8. 3mo agoRequest TrackerSame security fixes as 5.0.10, plus dashboard and accessibility work
  9. 10mo agoRequest TrackerCalendar view for saved searches and memory management work
  10. 10mo agoRequest TrackerCSV injection fix in TSV export, with assorted updates
  11. 10mo agoRequest TrackerFinal RT 4.4 release closes the branch with one security fix
  12. 1y agoRequest TrackerRelease exists mainly to support RTIR 6.0.1

Frequently asked questions

What is the difference between Request Tracker and Xurrent?

They serve adjacent needs but don't currently overlap on shipped themes. Xurrent is currently shipping more aggressively (velocity 6.3 vs 0.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.

Is Request Tracker better than Xurrent?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Xurrent is currently shipping more aggressively (velocity 6.3 vs 0.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.

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.

What are the best alternatives to Xurrent?

Top Xurrent alternatives in Support are ranked by recent ship velocity. Browse the "Xurrent alternatives" section above for the current picks, or visit /alternatives/xurrent for the full list with editorial commentary on each.