Plain
Plain built an autonomous support agent, and has now built the controls to trust it.
A side-by-side editorial comparison of Xurrent and Zammad — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Zammad inches toward 7.x on a slow alpha cadence with little feature signal
Zammad's visible changelog is sparse and maintenance-only. The recent entries are alpha version markers spaced months apart — 7.0.0-alpha in September 2025, 7.1.0-alpha in February 2026, 7.2.0-alpha in May 2026 — carrying little beyond version-info bumps and an earlier note about improved sensitive-data handling.
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.
Zammad's visible changelog is sparse and maintenance-only. The recent entries are alpha version markers spaced months apart — 7.0.0-alpha in September 2025, 7.1.0-alpha in February 2026, 7.2.0-alpha in May 2026 — carrying little beyond version-info bumps and an earlier note about improved sensitive-data handling.
The only clear signal is a slow march toward a 7.x release line, tagged through infrequent alpha cuts. What is actually changing inside this open-source help desk is not visible in these entries, so the substantive direction of 7.x remains unclear from the changelog alone.
A 7.x stable release is the likely eventual destination, but the alpha tags here do not reveal which features will define it.
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 Xurrent or Zammad.
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 Xurrent alternatives → · See all Zammad 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 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.
Top Zammad alternatives in Support are ranked by recent ship velocity. Browse the "Zammad alternatives" section above for the current picks, or visit /alternatives/zammad for the full list with editorial commentary on each.