ManageEngine ServiceDesk Plus Cloud
The cloud edition's only real news is Slack, restated twice in four days.
A side-by-side editorial comparison of Frill and Issuetrak — release velocity, themes, recent moves, and the top alternatives to consider.
Frill just made its feedback board readable by any AI assistant, on every plan.
Frill is a feedback, roadmap, and changelog tool that has spent the past year on distribution plumbing — EU hosting, SSO for Okta and EntraID, multi-language, custom domains, a public npm SDK, and a Chrome extension. Releases arrive as monthly bundles rather than continuous drops. As of August 2, the MCP server that had been in public beta since June is generally available with ten tools and no setup beyond an API key.
Issuetrak hardens for serious enterprise deployment — HA support, Azure hosting, off-web-folder attachments.
The visible window is a coherent enterprise-deployment push: high-availability deployment is now supported, Azure joins the hosting-environment list, attachments can live on UNC or local paths outside the web folder, API v2 has new endpoints, Magic Sign-In session length is admin-configurable up to 30 days, and Sys Admins can block risky file types across Windows/Mac/Linux. Smaller UX moves include attachment-count and billing-line indicators on issues and bulk entity import.
Frill is a feedback, roadmap, and changelog tool that has spent the past year on distribution plumbing — EU hosting, SSO for Okta and EntraID, multi-language, custom domains, a public npm SDK, and a Chrome extension. Releases arrive as monthly bundles rather than continuous drops. As of August 2, the MCP server that had been in public beta since June is generally available with ten tools and no setup beyond an API key.
The shape of the work has shifted from making Frill reachable by humans in more places to making its data readable by machines: SDK, multiple API keys, webhook hardening, then MCP. Frill is betting that the value of a feedback board is not the board but the corpus behind it, and that the corpus is most useful when a product manager can query it from wherever they already work. Bundling MCP into every plan rather than the Growth tier says they want adoption volume, not a pricing lever.
Expect the next release notes to extend MCP from read tools toward write actions — creating ideas or updating roadmap status from an assistant — and to surface usage of it in the admin dashboard.
The visible window is a coherent enterprise-deployment push: high-availability deployment is now supported, Azure joins the hosting-environment list, attachments can live on UNC or local paths outside the web folder, API v2 has new endpoints, Magic Sign-In session length is admin-configurable up to 30 days, and Sys Admins can block risky file types across Windows/Mac/Linux. Smaller UX moves include attachment-count and billing-line indicators on issues and bulk entity import.
Issuetrak is repositioning itself from a small/mid-market self-hosted issue tracker into something deployable inside large IT estates. The combination of HA, Azure, off-web-folder attachments, and API v2 expansion is exactly the deployment-shape work that a procurement team would gate-keep on. Nothing in the feed points to AI features yet — the bet is on owning the regulated/on-prem buyer who can't or won't move to cloud-only ITSM.
Expect AWS hosting support (mirror of the Azure work), more API v2 surface, and probably an SSO/IdP hardening pass to round out the enterprise-deployment story. AI surfaces — agent-assist for ticketing, summarization — are a plausible 2026/2027 add but absent from current signals.
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 Frill or Issuetrak.
The cloud edition's only real news is Slack, restated twice in four days.
A near-daily fix stream, with Slack and Teams becoming where help desk work happens.
Canny is quietly turning customer conversations into a feedback pipeline nobody has to maintain.
A mature help desk in pure maintenance, shipping the same fixes twice across two support branches.
A content-marketing feed arguing that AI in the contact center fails on knowledge, not models
respond.io is monetizing AI usage directly while putting an assistant that builds agents in every workspace.
See all Frill alternatives → · See all Issuetrak 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 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.
Top Issuetrak alternatives in Support are ranked by recent ship velocity. Browse the "Issuetrak alternatives" section above for the current picks, or visit /alternatives/issuetrak for the full list with editorial commentary on each.