Ivanti vs Discourse
Side-by-side trajectory, velocity, and editorial themes.
Ivanti's Secure Access Client ships weekly mobile point releases — 22.7.4 through 22.8.7 — with documentation as the only visible signal.
The visible Ivanti feed is dominated by weekly Supported Platforms Guides for the Ivanti Secure Access Client (formerly Pulse Secure) on iOS, Android, and ChromeOS, spanning versions 22.7.4 through 22.8.7. A cumulative Android release notes index for 22.2.1–22.8.6 and accompanying admin and MDM deployment guides confirm steady mobile-client cadence. The captured content is documentation landing pages, not detailed change descriptions.
With only documentation pages observable, product trajectory is hard to read concretely. The frequent point releases suggest active maintenance of the mobile security client; the historical Pulse Secure → Ivanti rebrand and the Classic UI / New-UI dual maintenance both indicate gradual consolidation rather than a fresh directional move.
Expect continued weekly point releases on 22.8.x and a likely transition to 22.9.x or a 23.x line later in 2026. Substantive product moves probably exist in detailed release notes the crawler isn't reaching — a different ingestion path (the per-version release notes endpoints, not the SPG landing pages) would surface more useful signal.
Discourse opens its AI bot to any external MCP server, treating the forum as an agent host.
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.
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.
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 Ivanti →
See more alternatives to Discourse →