← Back to home
Comparison · Support

Kayako vs Discourse

Side-by-side trajectory, velocity, and editorial themes.

K
Kayako
SUPPORT
0.0

Kayako's public changelog has been silent since mid-2022 — the radar is showing a stalled product.

◆ Current state

Kayako has not posted a public changelog entry since June 2022. The most recent communication was a CEO apology over a performance incident and a series of link-only release-notes posts pointing to a Help Center article. The visible operational picture is an established customer-support product no longer broadcasting product motion.

◆ Where it's heading

Direction is hard to read from public changelog activity alone, but the trajectory implied by the silence is unmistakable: either the product moved its release communication elsewhere, or development pace slowed enough to stop justifying a regular changelog. Either way, prospects watching only the public surface see no momentum.

◆ Prediction

Without renewed public activity, Kayako will continue to be perceived as legacy in a category where Zendesk, Intercom, and HelpScout are publishing prominently. A customer-facing changelog refresh would be the lowest-effort signal to send, and is the most likely next move if the product is in fact still under active development.

Discourse logo
Discourse
SUPPORT
5.0

Discourse opens its AI bot to any external MCP server, treating the forum as an agent host.

◆ Current state

Discourse runs on a monthly main release plus periodic security intermediates, and the editorial focus across recent posts is clearly AI plumbing. March added Bring-Your-Own MCP server support to the Discourse AI Bot, alongside documented AI credentials management and SSO auto-provisioning for forum admins. The team has also been adjusting its release-communication process, with backdated intermediate-release topics filling earlier gaps.

◆ Where it's heading

Discourse is positioning the forum as an environment that hosts agents, not just a place that uses AI features. By accepting any MCP-compatible tool provider as a backend, it makes itself the substrate community managers extend with arbitrary external capabilities — search, ticketing, knowledge bases, whatever the host wires in. SSO auto-provisioning and structured form templates round out the admin surface that this agent-host posture needs.

◆ Prediction

Expect deeper agent UX inside topics — more entry points and persona configuration — alongside audit and observability tooling for what external MCP tools do on a forum. Community trust depends on that side staying explainable.

See more alternatives to Kayako
See more alternatives to Discourse