Sleekplan
Sleekplan is making the public feedback board safe to run with real customers on it
A side-by-side editorial comparison of Hatz AI and Request Tracker — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Hatz AI | Request Tracker |
|---|---|---|
| Sector | Support | Support |
| Velocity score | 7.5 | 0.0 |
| Sparks · 30d | 2 | 0 |
| Top themes | msp, ai-platform, phone-agents, training | ticketing, security-releases, multi-branch, cve |
| Last editorial update | 4d ago | 6d ago |
| Website | — | Visit → |
Hatz pulls its training platform off TalentLMS and runs it inside the tenant.
Hatz is an AI platform sold through managed service providers. Hatz Learn now runs natively in the tenant dashboard instead of a separate TalentLMS site, with completed courses and certifications migrated across. Tenant admins can also request a phone agent themselves, with MSP admins reviewing the exact configuration and billing starting on approval, and GLM-5.3-Flash joins the model selector.
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.
Hatz is an AI platform sold through managed service providers. Hatz Learn now runs natively in the tenant dashboard instead of a separate TalentLMS site, with completed courses and certifications migrated across. Tenant admins can also request a phone agent themselves, with MSP admins reviewing the exact configuration and billing starting on approval, and GLM-5.3-Flash joins the model selector.
Since Hatz Activate, the work has been about making the MSP-to-tenant boundary self-service rather than manual: tenants request phone agents instead of asking, PSA imports become selective rather than all-or-nothing, and phone agents start from templates that write their own instructions. Absorbing the learning platform fits that pattern — one fewer vendor and one fewer login between the customer and the product. Model additions continue on their usual cadence.
With training in-house and phone agents self-requested, expect the next releases to extend the same request-and-approve pattern to other provisioning that still requires an MSP admin to act.
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.
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.
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.
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 Hatz AI or Request Tracker.
Sleekplan is making the public feedback board safe to run with real customers on it
ServiceDesk Plus moved upstream of the ticket, then spent the week tidying the sidebar
Chatway's bot learned to read the store; now the store can listen back
ManageEngine's cloud service desk drips small fixes; its AI arrives data center by data center
Asset management is the real build; the feed is mostly an interview series.
Formbricks spends a whole RC train on making enterprise SSO stop breaking.
See all Hatz AI alternatives → · See all Request Tracker alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Hatz AI is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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. Hatz AI is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 Hatz AI alternatives in Support are ranked by recent ship velocity. Browse the "Hatz AI alternatives" section above for the current picks, or visit /alternatives/hatz-ai for the full list with editorial commentary on each.
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.