← Back to home
Comparison · Support

osTicket vs LiveAgent

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

O
osTicket
SUPPORT
2.5

osTicket runs in steady maintenance mode — security patches and PHP compatibility, little net-new

◆ Current state

osTicket's release feed is pure maintenance. The recent stable line (v1.18.x) ships security updates, bug fixes, and ongoing PHP 8.3/8.4 compatibility, with refreshed language packs and plugins each time. Release cadence is slow and irregular — the latest, v1.18.4, followed v1.18.3 by roughly five months. This is a mature open-source helpdesk being kept current, not actively reinvented.

◆ Where it's heading

The throughline is keeping a long-lived codebase safe and runnable on current PHP, plus the multi-year push to get installs onto OAuth2/Modern Authentication as Microsoft and Google retire Basic Auth for email. Expect continued patch-and-compatibility releases rather than feature expansion; the project's value is stability and self-hostability, and the changelog reflects that posture.

◆ Prediction

The next release will most likely be another v1.18.x maintenance drop with security fixes and PHP/library compatibility, timed to a disclosed vulnerability or a new PHP version. A feature-led release isn't indicated by this history.

LiveAgent logo
LiveAgent
SUPPORT
6.3

LiveAgent runs a heavy maintenance cadence while quietly wiring in AI-agent billing

◆ Current state

LiveAgent ships frequent, dense point releases dominated by bug fixes, security hardening, and performance work across its ticketing, chat, and call surfaces. Underneath the maintenance stream, it is standing up the plumbing for AI agents: credit-pool provisioning, AI budgets and top-ups, recent LLM model support, and signed MCP download links so agents can reach ticket attachments. A parallel API v3-to-v4 transition is underway, with datetime standardization and relabeled API keys.

◆ Where it's heading

The direction is incremental on two tracks: keep grinding down a long bug and access-control backlog, and build the commercial and integration scaffolding for AI agents rather than a headline AI feature. Expect the v4 API to keep firming up and the AI budget/credit system to move from provisioning toward customer-facing usage. This is groundwork, not a pivot.

◆ Prediction

Next releases likely continue the fix-heavy cadence while extending AI-agent capabilities on top of the now-provisioned credit pools, and advancing the v4 API surface.

See more alternatives to osTicket
See more alternatives to LiveAgent