Plain
Plain built an autonomous support agent, and has now built the controls to trust it.
A side-by-side editorial comparison of ITFlow and Xurrent — release velocity, themes, recent moves, and the top alternatives to consider.
ITFlow ships a dated release every month, and spent 2026 rebuilding its mail plumbing.
ITFlow runs an MSP business on one stack — tickets, clients, assets, networks, documents, invoicing and payments — and cuts a CalVer release almost every month. The July 2026 release replaced the Webklex IMAP library with IMAPEngine and rewrote the mail settings page around Microsoft 365 and Google OAuth2, including which licensed user the connection runs as. Recent months have also made asset statuses, note types and rack types into user-editable categories, and added network import.
Sera AI crosses from assistant to autonomous agent while the ITSM core keeps its monthly grind.
Xurrent ships on a disciplined monthly cadence, and the last quarter splits cleanly in two. One half is steady ITSM plumbing — shared tags across Requests, Problems, Workflows and Projects, CMDB reconciliation that a human can actually read, iPaaS connectors, self-service reservations. The other half is Sera AI, which moved from a chat widget to a configurable studio and then, on 10 July, to two agents that act without a person in the loop.
ITFlow runs an MSP business on one stack — tickets, clients, assets, networks, documents, invoicing and payments — and cuts a CalVer release almost every month. The July 2026 release replaced the Webklex IMAP library with IMAPEngine and rewrote the mail settings page around Microsoft 365 and Google OAuth2, including which licensed user the connection runs as. Recent months have also made asset statuses, note types and rack types into user-editable categories, and added network import.
Two threads run through these releases. One is grinding the email path into something reliable for an MSP: a new ticket parser, subject-based auto-merge, CC'd recipients becoming watchers, and now a library swap and OAuth2 rewrite. The other is steadily converting hardcoded enumerations into things administrators can edit. Underneath both, the project keeps migrating raw queries to prepared statements and adding CSRF checks release by release.
The monthly cadence and the run of security fixes in the July notes point to another dated release in August continuing the prepared-statement and CSRF cleanup. Whether the IMAPEngine migration is finished or still shedding bugs is not visible from these entries.
Xurrent ships on a disciplined monthly cadence, and the last quarter splits cleanly in two. One half is steady ITSM plumbing — shared tags across Requests, Problems, Workflows and Projects, CMDB reconciliation that a human can actually read, iPaaS connectors, self-service reservations. The other half is Sera AI, which moved from a chat widget to a configurable studio and then, on 10 July, to two agents that act without a person in the loop.
The two tracks are converging rather than running in parallel. Knowledge article readiness, CI location hints and reconciliation legibility are not standalone features — they are the data-quality preconditions an agent needs before it can be trusted to close a request. Xurrent is building the substrate first and letting Sera consume it, which is why the agent work has landed without the usual rollback noise. Agent Designer success metrics suggest the next constraint is proving the agents work, not shipping more of them.
Expect the agent count to grow slowly and the governance surface around it to grow faster — more Golden Set tooling, more per-agent success reporting, and tighter scoping of which request types an agent may close unaided.
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 ITFlow or Xurrent.
Plain built an autonomous support agent, and has now built the controls to trust it.
Sleekplan rebuilt itself around AI triage, then put the feedback board inside ChatGPT.
Comm100 publishes steadily about AI support — none of it is Comm100 shipping anything.
respond.io is layering an agent-authoring copilot and consumption billing on top of its omnichannel inbox.
Hatz sells through MSPs, and its roadmap has started to serve the partner more than the end user
A teaser-only content feed making one argument: AI in the contact center fails on knowledge, not models.
See all ITFlow alternatives → · See all Xurrent alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Xurrent is currently shipping more aggressively (velocity 6.3 vs 2.5), 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. Xurrent is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 ITFlow alternatives in Support are ranked by recent ship velocity. Browse the "ITFlow alternatives" section above for the current picks, or visit /alternatives/itflow for the full list with editorial commentary on each.
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.