ITSM and Help Desk

IT service management (ITSM) and help desk platforms provide centralised systems for receiving, tracking, resolving, and reporting on service requests, incidents, problems, and changes. These platforms form the operational core of IT service delivery, enabling structured workflows, service level management, knowledge capture, and performance measurement. For mission-driven organisations, platform selection affects staff productivity, service quality, compliance capability, and total cost of ownership.

This page covers dedicated ITSM and ticketing platforms with at least incident and request management capabilities. Platforms focused exclusively on customer relationship management appear in CRM Platforms. Asset and configuration management databases are covered in ITSM and Help Desk where integrated, and standalone CMDB solutions are addressed separately. Monitoring and alerting platforms that generate tickets but do not manage the full ticket lifecycle appear in Security and Monitoring.

Requirements taxonomy

This taxonomy defines evaluation criteria for ITSM and help desk platforms. Requirements are organised by functional area and weighted by typical priority for mission-driven organisations. Adjust weights based on your specific operational context.

Functional requirements

Core capabilities that define what the platform must do.

Ticket and request management

Service level management

Self-service and portal

ITIL process support

Automation and workflow

Reporting and analytics

Technical requirements

Infrastructure, deployment, and integration capabilities.

Deployment and hosting

Scalability and performance

Integration architecture

Security requirements

Authentication, authorisation, and data protection capabilities.

Authentication and access control

Data protection

Security certifications

Operational requirements

Day-to-day administration and maintenance considerations.

Administration

Backup and recovery

Support and maintenance

Data management requirements

Data portability and lifecycle management.

Import and migration

Export and portability

Commercial requirements

Pricing, licensing, and vendor considerations.

Pricing and licensing

Vendor assessment

Accessibility requirements

Assessment methodology

Tools are assessed against each requirement using the following scale:

Additional notation:

• $ indicates feature requires paid tier
• E indicates enterprise tier only
• P indicates plugin or extension required
• C indicates community-provided (not vendor-supported)

Functional capability comparison

Ticket and request management

Assessment notes:

• osTicket F1.2: Fixed category structure; custom fields available but taxonomy less flexible than alternatives
• osTicket F1.4: Predefined workflow states; limited customisation without code modification
• iTop F1.1: Strong on web and email; chat integration via third-party; phone integration requires configuration
• RT F1.7: No real-time collision detection; displays concurrent ticket access but no locking

Service level management

Assessment notes:

• osTicket: SLA functionality requires Service Level Agreements plugin (free); basic compared to dedicated ITSM platforms
• RT: SLA features via RT::Extension::SLA (community-maintained); requires Perl expertise to configure
• OTOBO F2.5: Full OLA support with ITSM packages installed
• Commercial platforms F2.5: OLA tracking in premium tiers only

Self-service and portal

Assessment notes:

• Zammad F3.2: Knowledge base included; formal service catalogue with workflow requires additional configuration
• osTicket F3.3: FAQ module included; knowledge base plugin adds contextual suggestions
• RT F3.4: Responsive design but no native mobile apps; mobile experience functional but limited
• iTop/OTOBO F3.4: Responsive design; mobile usability varies by complexity of forms

ITIL process support

Assessment notes:

• Zammad: Designed as customer service platform; ITIL processes achievable through workflow customisation but not native
• osTicket: Ticket-centric design; ITIL terminology not native; achievable through custom fields and workflows
• iTop: Full ITIL 4 coverage; integrated CMDB is primary strength; processes tightly coupled with configuration items
• RT: General-purpose ticket system; ITIL extensions available via RT::Extension modules
• OTOBO: Fork of OTRS with full ITSM packages; comprehensive ITIL coverage

Automation and workflow

Assessment notes:

• osTicket F5.1: Basic automation through actions and filters; less flexible than alternatives
• Zammad F5.3: Simple approval via groups; multi-stage approval workflows not native
• RT: Scrips provide powerful automation; steep learning curve for complex workflows

Technical capability comparison

Deployment and hosting

Deployment details:

Assessment notes:

• JSM T1.1: Data Center edition allows self-hosting; minimum 500 users for Data Center licensing
• osTicket T1.3: Multiple community Docker images available; no official images
• iTop/RT T1.3: Community containers exist; not officially maintained
• OTOBO T1.3: Docker is recommended deployment method; well-documented

Integration architecture

API details:

Security capability comparison

Authentication and access control

Authentication methods:

Data protection

*Self-hosted: encryption and residency controlled by deployment configuration

Assessment notes:

• FOSS platforms S2.1/S2.5: Encryption at rest and data residency are deployment-controlled; organisations using self-hosted options control these directly
• osTicket S2.3: Basic logging; comprehensive audit trail requires customisation
• Data masking: Commercial platforms offer configurable masking; FOSS platforms require custom implementation

Security certifications

Assessment notes:

• Self-hosted FOSS deployments: certifications depend on hosting organisation’s own compliance posture
• Commercial SaaS platforms maintain certifications for their infrastructure
• FOSS vendors with SaaS offerings (Zammad, iTop, OTOBO) have varying certification coverage

Operational capability comparison

Backup and recovery

*Self-hosted: backup and DR are deployment responsibilities; documentation provided for database and file backup

Assessment notes:

• FOSS platforms provide documentation for backup procedures; implementation is operator responsibility
• Commercial SaaS platforms include backup and DR in service

Support comparison

Data management comparison

Import and export

Migration complexity from common platforms:

Commercial comparison

Pricing models

Cost notes:

• Self-hosted costs exclude infrastructure (servers, database, storage, backup, SSL certificates)
• Typical infrastructure cost for self-hosted: £50-300/month for 10 agents; £150-800/month for 50 agents
• Commercial platform costs vary by tier; ranges shown cover entry to mid-tier plans
• Enterprise features and premium support add 50-200% to base commercial costs

Detailed pricing: Commercial platforms

Jira Service Management Cloud

Nonprofit programme: 75% discount through Atlassian Community License; requires registered charity status.

Freshservice

Nonprofit programme: Discounts available through TechSoup; discount level varies by region.

Zendesk

Nonprofit programme: Up to 50% discount through Tech Impact/Benevity; requires verification.

Vendor details

Jurisdictional considerations:

• US-headquartered (osTicket, RT, JSM, Freshservice, Zendesk): Subject to US CLOUD Act; government can compel data access regardless of storage location
• German/EU-headquartered (Zammad, OTOBO): GDPR as primary framework; no CLOUD Act exposure
• French-headquartered (iTop): GDPR as primary framework; no CLOUD Act exposure
• Self-hosted options: Jurisdictional concerns mitigated by organisational control of infrastructure

Accessibility comparison

Assessment notes:

• Commercial platforms invest significantly in accessibility compliance; VPATs available on request
• FOSS platforms have variable accessibility; Zammad and OTOBO lead among open source options
• Organisations with accessibility requirements should evaluate agent and portal interfaces during trial

Detailed tool assessments

Zammad

Type

Open source

Licence

AGPL-3.0. Requires source disclosure if modified versions are distributed or provided as a service to third parties.

Current version

6.5 (April 2025); 7.0 in development

Deployment options

Self-hosted (Linux), Docker, Kubernetes, SaaS

Source repository

github.com/zammad/zammad

Documentation

docs.zammad.org

Overview

Zammad is a web-based open source helpdesk and customer service platform developed by Zammad GmbH in Germany, with source code owned by the independent Zammad Foundation. Originally created by Martin Edenhofer (founder of OTRS), Zammad provides a modern ticketing system with emphasis on multichannel communication, real-time updates, and user experience. The platform uses Ruby on Rails with PostgreSQL, Elasticsearch for search, and Redis for caching.

Zammad focuses on customer service and support desk use cases rather than full ITIL compliance. The interface is modern and intuitive, requiring minimal training for agents. The system handles email, chat, phone (via CTI integration), Twitter, Facebook, and Telegram natively. Real-time updates via WebSockets create a responsive agent experience.

Capability assessment for ITSM

Zammad excels at ticket management, multichannel intake, and agent productivity. The knowledge base integrates with ticket creation for article suggestions. Workflow automation through triggers and schedulers handles routing, escalation, and notifications effectively.

For formal ITIL processes, Zammad requires configuration. While incident, request, and basic problem management work through ticket types and custom workflows, native change management, release management, and CMDB are not included. Organisations requiring formal ITIL alignment should consider OTOBO or iTop, or plan for significant customisation.

Key strengths:

• Modern, responsive interface reduces agent training time
• Strong multichannel support including social media and chat
• Active open source community with regular releases
• German/EU hosting available; GDPR-friendly deployment
• Two-factor authentication and SSO built-in

Key limitations:

• Limited native ITIL process support; requires workflow customisation
• No integrated CMDB or asset management
• Formal change management requires custom implementation
• Enterprise features (reporting, advanced automation) require SaaS or development

Deployment and operations

Self-hosted requirements:

Operating system: Ubuntu 22.04+, Debian 12+, RHEL 8+ (with EPEL)
Database: PostgreSQL 14+ (PostgreSQL only from v7.0)
Runtime: Ruby (bundled), Node.js (bundled)
Dependencies: Elasticsearch 8.x, Redis 7+
Minimum resources: 4 CPU, 8GB RAM, 40GB storage
Recommended (100 agents): 8 CPU, 16GB RAM, 100GB storage

Deployment complexity: Medium. Package installation straightforward; Elasticsearch and Redis add operational overhead.

Operational overhead: Medium. Elasticsearch requires monitoring and index management. Regular updates released; upgrade process documented.

Upgrade path: Regular releases (approximately monthly). Major versions (6.x to 7.x) require migration steps. Breaking changes documented in release notes.

Integration capabilities

API coverage: Comprehensive REST API covering tickets, users, organisations, tags, and system configuration. GraphQL API in development.

Key integrations:

Cost analysis

Direct costs:

• Licence: Free (AGPL-3.0)
• SaaS: From €5/agent/month (hosted by Zammad GmbH)
• Support: Available through Zammad GmbH; pricing on request

Infrastructure costs (self-hosted):

Hidden costs:

• Elasticsearch expertise or managed service
• SSL certificate management
• Backup infrastructure

Organisational fit

Best suited for:

• Customer service and support desk operations
• Organisations prioritising modern UX and multichannel support
• Teams wanting EU-hosted open source solution
• Environments where formal ITIL compliance is not required

Less suitable for:

• Organisations requiring formal ITIL change and release management
• Environments needing integrated CMDB
• Teams requiring enterprise reporting without development

Migration considerations:

• Native import from OTRS, Zendesk, Kayako, Freshdesk
• CSV/API import for other platforms
• Full data export available

osTicket

Type

Open source

Licence

GPL-2.0. Permits modification and distribution; derivative works must use compatible licence.

Current version

1.18.2 (February 2025)

Deployment options

Self-hosted (Linux/Windows), SaaS

Source repository

github.com/osTicket/osTicket

Documentation

docs.osticket.com

Overview

osTicket is a widely-deployed open source support ticket system developed by Enhancesoft. First released in 2003, osTicket provides essential ticketing functionality with low resource requirements and straightforward deployment. The platform uses PHP with MySQL, making it deployable on standard LAMP/LEMP stacks and most shared hosting environments.

osTicket focuses on core ticketing rather than comprehensive ITSM. The system handles email, web portal, and API intake, with plugins adding additional channels. Custom forms and fields allow adaptation to various use cases. The extensive plugin ecosystem (some free, some commercial) extends functionality.

Capability assessment for ITSM

osTicket provides solid ticket management for help desk operations. Tickets flow through customisable statuses with assignment, collaboration, and response capabilities. The FAQ module offers basic knowledge management. Custom forms enable organisation-specific data capture.

For ITIL processes, osTicket is limited. The platform does not distinguish incident from service request natively, and problem, change, and release management are not included. The SLA plugin adds service level tracking. Organisations requiring ITIL alignment should consider alternatives or plan significant customisation.

Key strengths:

• Low resource requirements; runs on shared hosting
• Simple installation and administration
• Long track record and extensive deployment base
• Plugin ecosystem extends core functionality
• Low barrier to entry for basic help desk

Key limitations:

• Limited native ITIL support; no change or problem management
• Basic automation compared to alternatives
• No integrated CMDB
• Plugin quality varies; some commercial, some unmaintained
• Interface dated compared to modern platforms

Deployment and operations

Self-hosted requirements:

Operating system: Linux or Windows with web server
Web server: Apache 2.4+ or IIS 8+
Database: MySQL 8+ or MariaDB 10.4+
Runtime: PHP 8.2-8.4
Dependencies: PHP extensions (imap, json, mbstring, etc.)
Minimum resources: 1 CPU, 2GB RAM, 10GB storage

Deployment complexity: Low. Standard PHP application; installs via web wizard.

Operational overhead: Low. Minimal maintenance required for basic operation.

Upgrade path: Regular releases. Upgrade via file replacement; database migrations automatic.

Integration capabilities

API coverage: REST API for ticket, user, and organisation operations. Adequate for basic integrations.

Key integrations:

Cost analysis

Direct costs:

• Licence: Free (GPL-2.0)
• Plugins: Various (free and commercial)
• SaaS: From $15/agent/month (via osTicket Cloud)

Infrastructure costs (self-hosted):

Hidden costs:

• Commercial plugins if required
• Custom development for ITIL processes

Organisational fit

Best suited for:

• Small teams needing basic ticket management
• Organisations with limited IT resources
• Environments where simple email-to-ticket workflow suffices
• Budget-constrained deployments

Less suitable for:

• ITIL-aligned IT service management
• Complex workflow automation requirements
• Organisations requiring integrated asset/configuration management
• Teams needing modern, responsive interface

iTop

Type

Open source

Licence

AGPL-3.0. Requires source disclosure for modifications; commercial extensions available under separate licence.

Current version

3.2.2 LTS (2025); 3.3 STS branch active

Deployment options

Self-hosted (Linux), SaaS

Source repository

github.com/Combodo/iTop

Documentation

itophub.io

Overview

iTop (IT Operational Portal) is an open source ITSM platform developed by Combodo in France. The platform differentiates itself through its CMDB-centric architecture: configuration items and their relationships form the foundation, with ticket management built around configuration data. This design supports impact analysis, dependency mapping, and service-aware incident management.

iTop provides comprehensive ITIL coverage including incident, problem, change, and release management. The low-code CMDB allows organisations to model their specific infrastructure and services without programming. Extensions available through iTop Hub add capabilities including SLA management, reporting, and integrations.

Capability assessment for ITSM

iTop’s CMDB is its primary strength. Organisations can model complex infrastructure with configuration items, relationships, and impact rules. When incidents occur, the system displays affected CIs and downstream impacts. Change management links changes to affected configurations, enabling impact assessment before implementation.

The ticketing system supports full ITIL processes with separate workflows for incidents, service requests, problems, and changes. The service catalogue defines available services linked to SLAs and supporting CIs. The interface is functional but dated compared to modern platforms; Combodo’s development focuses on capability rather than aesthetic refinement.

Key strengths:

• Comprehensive CMDB with relationship modelling
• Full ITIL process coverage in open source version
• Impact analysis links incidents and changes to affected services
• Low-code customisation via ITSM Designer (commercial extension)
• French/EU vendor; GDPR-friendly

Key limitations:

• Interface dated; learning curve for new users
• Mobile experience limited
• Documentation extensive but assumes technical knowledge
• Some advanced features require commercial extensions
• Performance tuning required for large CMDB

Deployment and operations

Self-hosted requirements:

Operating system: Linux (RHEL/CentOS, Debian, Ubuntu)
Web server: Apache 2.4+ with mod_php or PHP-FPM
Database: MySQL 8+ or MariaDB 10.5+
Runtime: PHP 8.1+
Dependencies: Graphviz (for impact diagrams)
Minimum resources: 2 CPU, 4GB RAM, 20GB storage
Recommended (50 agents): 4 CPU, 8GB RAM, 100GB storage

Deployment complexity: Medium. Standard PHP application; CMDB configuration requires planning.

Operational overhead: Medium. Database performance critical for large CMDB; periodic optimisation required.

Upgrade path: LTS branch (3.2.x) supported for 2 years; STS branch (3.3.x) for early features. Upgrade wizard handles database migrations.

Integration capabilities

API coverage: REST/JSON API for all objects; comprehensive CRUD operations on any CI or ticket type.

Key integrations:

Cost analysis

Direct costs:

• Licence: Free (AGPL-3.0)
• Extensions: Many free; advanced extensions commercial
• ITSM Designer (low-code): Commercial licence
• Support: Through Combodo partners

Infrastructure costs (self-hosted):

Hidden costs:

• ITSM Designer if low-code customisation needed
• Database performance optimisation expertise

Organisational fit

Best suited for:

• Organisations requiring CMDB-centric ITSM
• IT departments managing complex infrastructure
• Environments where impact analysis is critical
• Teams seeking full ITIL coverage in open source

Less suitable for:

• Simple help desk requirements (over-engineered)
• Organisations prioritising modern UX
• Mobile-first environments
• Teams without database administration capability

Request Tracker (RT)

Type

Open source

Licence

GPL-2.0. Permits modification and distribution under compatible terms.

Current version

6.0.2 (October 2025); 5.0.9 maintenance

Deployment options

Self-hosted (Linux), Cloud RT (managed service)

Source repository

github.com/bestpractical/rt

Documentation

docs.bestpractical.com

Overview

Request Tracker (RT) is a mature open source ticket tracking system developed by Best Practical Solutions since 1996. RT serves diverse use cases from IT help desk to security incident response (via RT for Incident Response). The platform uses Perl with PostgreSQL, MySQL, or Oracle, and runs on Apache with mod_perl or Plack/Starman.

RT emphasises flexibility and extensibility. The system’s “scrips” (scripts triggered by ticket events) enable complex automation. Custom fields, lifecycle states, and workflows accommodate varied requirements. The RT ecosystem includes extensions for SLA management, approvals, assets, and integrations.

Capability assessment for ITSM

RT provides comprehensive ticket management with configurable lifecycles and workflows. Different queues can have different workflows, enabling separation of incident, request, and other ticket types. The scrip system handles complex automation including notifications, field updates, and external integrations.

RT for Incident Response (RTIR) extends RT specifically for security teams with incident states, constituencies, and investigation workflows. For general ITSM, RT requires configuration and extension installation to match platforms with native ITIL coverage.

Key strengths:

• Mature codebase with 25+ years of development
• Highly flexible workflow and automation system
• Strong security incident response variant (RTIR)
• Comprehensive audit trail and history
• Active commercial support from Best Practical

Key limitations:

• Perl expertise required for customisation
• Interface functional but not modern
• Extensions required for ITIL processes
• Steeper learning curve than alternatives
• Limited mobile experience

Deployment and operations

Self-hosted requirements:

Operating system: Linux (RHEL/CentOS, Debian, Ubuntu)
Web server: Apache with mod_perl or nginx with Plack
Database: PostgreSQL 13+ (recommended), MySQL 8+, MariaDB
Runtime: Perl 5.18+
Dependencies: Various CPAN modules
Minimum resources: 2 CPU, 4GB RAM, 20GB storage

Deployment complexity: Medium-High. Perl environment setup; CPAN dependency management.

Operational overhead: Medium. Stable in production; upgrades require attention to extension compatibility.

Upgrade path: Major versions (5.x to 6.x) require review of extensions. LTS available for enterprises.

Cost analysis

Direct costs:

• Licence: Free (GPL-2.0)
• Cloud RT: Managed service pricing on request
• Support: Enterprise support from Best Practical

Infrastructure costs (self-hosted):

Organisational fit

Best suited for:

• Organisations with Perl expertise
• Security teams (RT for Incident Response)
• Environments requiring extensive customisation
• Long-term stable deployments

Less suitable for:

• Teams without Perl skills
• Organisations prioritising modern UX
• Simple help desk requirements
• Mobile-centric environments

OTOBO

Type

Open source

Licence

GPL-3.0. Permits modification and distribution; derivative works under compatible licence.

Current version

11 (2025)

Deployment options

Self-hosted (Linux), Docker, SaaS

Source repository

github.com/RotherOSS/otobo

Documentation

doc.otobo.org

Overview

OTOBO is an open source ITSM platform forked from OTRS Community Edition in 2020 by Rother OSS GmbH after OTRS AG restricted the open source version. OTOBO maintains compatibility with OTRS workflows and configurations while adding features and maintaining the open source development model. The platform uses Perl with PostgreSQL, Redis, and Elasticsearch.

OTOBO provides comprehensive ITSM functionality through core ticketing and optional ITSM packages. The modular architecture allows organisations to enable features as needed. Docker is the recommended deployment method, simplifying installation and updates.

Capability assessment for ITSM

OTOBO’s ITSM packages provide full ITIL coverage including incident, problem, change, and configuration management. The CMDB (via ITSMConfigurationManagement) links CIs to services and tickets. Version 11 introduced a redesigned CMDB with tree views, formula fields, and improved CI access controls.

The workflow engine handles complex processes with states, transitions, and automated actions. Generic agents (scheduled automation) and event-based notifications provide comprehensive automation. The customer portal supports self-service and service catalogue presentation.

Key strengths:

• Full ITIL process coverage with ITSM packages
• Modern CMDB redesign in version 11
• Docker deployment simplifies operations
• Active development and regular releases
• German/EU vendor; GDPR-friendly
• Migration path from OTRS

Key limitations:

• Perl-based; customisation requires Perl knowledge
• Interface improved but not as modern as some alternatives
• ITSM packages add complexity
• Elasticsearch required for search performance

Deployment and operations

Self-hosted requirements:

Operating system: Linux (RHEL 9+, Debian 12+, Ubuntu 22.04+)
Container: Docker and Docker Compose (recommended)
Database: PostgreSQL 14+
Dependencies: Redis 7+, Elasticsearch 8.x
Minimum resources: 4 CPU, 8GB RAM, 50GB storage
Recommended (50 agents): 8 CPU, 16GB RAM, 200GB storage

Deployment complexity: Low-Medium. Docker deployment well-documented; traditional install more complex.

Operational overhead: Medium. Elasticsearch and Redis require monitoring; Docker simplifies updates.

Upgrade path: Regular releases; Docker deployment enables straightforward container updates.

Integration capabilities

API coverage: Web services (REST/SOAP) for comprehensive ticket and CI operations; GenericInterface for custom integrations.

Key integrations:

Cost analysis

Direct costs:

• Licence: Free (GPL-3.0)
• Packages: Most free; some commercial
• SaaS: Through Rother OSS; pricing on request
• Support: Through Rother OSS and partners

Infrastructure costs (self-hosted):

Organisational fit

Best suited for:

• OTRS migrations seeking open source continuity
• Organisations requiring full ITIL coverage
• Environments comfortable with Docker deployment
• Teams seeking EU-hosted open source ITSM

Less suitable for:

• Simple help desk requirements
• Organisations without Perl/Linux expertise
• Teams requiring extensive mobile access
• Environments preferring simpler architecture

Jira Service Management

Type

Commercial

Licence

Proprietary; subscription-based

Current version

Cloud (continuous updates); Data Center 11.3 LTS (December 2025)

Deployment options

Cloud (SaaS), Data Center (self-hosted)

Vendor

Atlassian

Documentation

support.atlassian.com/jira-service-management-cloud

Overview

Jira Service Management (JSM) is Atlassian’s ITSM platform, evolved from Jira Service Desk. JSM builds on Jira’s project and issue tracking foundation, adding ITSM-specific workflows, customer portal, SLA management, and integration with Atlassian’s ecosystem (Confluence, Opsgenie, Statuspage). The platform serves IT, HR, legal, and other service teams.

JSM Cloud receives continuous updates with AI features and advanced automation. Data Center edition provides self-hosted deployment for organisations with data residency or infrastructure control requirements, though Atlassian encourages cloud adoption.

Capability assessment for ITSM

JSM provides comprehensive ITSM with incident, problem, change, and request management. Integration with Opsgenie (included in Premium/Enterprise) adds on-call scheduling, alerting, and incident response. Assets (Premium+) provides CMDB functionality with discovery and dependency mapping.

The platform excels when combined with other Atlassian tools: Confluence for knowledge base, Jira Software for development team integration, and Statuspage for communication. Automation rules handle complex workflows. The Atlassian Marketplace offers 1,000+ apps for extended functionality.

Key strengths:

• Deep integration with Atlassian ecosystem
• Advanced automation and AI features
• Comprehensive on-call and alerting (Premium+)
• Large marketplace for extensions
• Strong knowledge base via Confluence
• Development team integration

Key limitations:

• Pricing scales quickly with agents and tiers
• Data Center minimum 500 users
• US-headquartered; CLOUD Act applies to SaaS
• Asset/CMDB requires Premium tier
• Learning curve for non-Atlassian users

Deployment and operations

Cloud: Fully managed; no infrastructure management required.

Data Center requirements:

Operating system: Linux (RHEL 8+, Ubuntu 20.04+)
Database: PostgreSQL 13-16
Runtime: Java 11 (bundled)
Search: OpenSearch or Elasticsearch
Minimum resources: 8 CPU, 16GB RAM, 100GB storage
Recommended: 16+ CPU, 32GB RAM, SSD storage

Deployment complexity: Cloud: Low. Data Center: Medium-High; requires Atlassian expertise.

Operational overhead: Cloud: Low (managed). Data Center: Medium-High; backup, updates, performance tuning.

Cost analysis

Cloud pricing:

Nonprofit programme: 75% discount via Atlassian Community License; registered charities and qualifying nonprofits.

Data Center: Annual licence based on user tiers; minimum 500 users; starts ~$42,000/year.

Organisational fit

Best suited for:

• Organisations already using Atlassian products
• Development-heavy environments needing dev/IT integration
• Teams requiring advanced on-call and alerting
• Enterprises with budget for Premium tier

Less suitable for:

• Small teams (pricing)
• Organisations avoiding US cloud providers
• Simple help desk requirements
• Budget-constrained nonprofits (despite discount)

Freshservice

Type

Commercial SaaS

Licence

Proprietary; subscription-based

Current version

Continuous updates (SaaS)

Deployment options

Cloud only

Vendor

Freshworks

Documentation

support.freshservice.com

Overview

Freshservice is a cloud-based ITSM platform from Freshworks, designed for straightforward deployment and ease of use. The platform provides ITIL-aligned processes with a modern interface and gamification elements to encourage adoption. Freshservice emphasises quick time-to-value with pre-configured workflows and AI-assisted features.

Freshworks’ product suite includes Freshdesk (customer service), Freshsales (CRM), and other tools that integrate with Freshservice. The platform serves IT, HR, and facilities teams with a unified approach to service management.

Capability assessment for ITSM

Freshservice provides comprehensive ITSM with incident, problem, change, and release management. The service catalogue enables self-service with approval workflows. Asset management includes discovery and software licence tracking. Project management (Pro tier+) enables project ticket integration.

The platform excels at usability; agents can be productive with minimal training. Workflow automation handles routing, escalation, and notifications. AI features assist with categorisation and knowledge article suggestions. The mobile apps provide full functionality for remote agents.

Key strengths:

• Intuitive interface; minimal training required
• Quick deployment with pre-configured workflows
• Integrated asset management with discovery
• Strong mobile experience
• Freddy AI for automation and insights
• Extensive integration marketplace

Key limitations:

• SaaS only; no self-hosted option
• US-headquartered; CLOUD Act applies
• Advanced features (project management, AI) require higher tiers
• Pricing increases significantly with tier and agents
• Customisation depth limited compared to FOSS

Cost analysis

Nonprofit programme: Discounts via TechSoup; varies by region.

Organisational fit

Best suited for:

• Organisations prioritising ease of use
• Teams needing quick deployment
• IT departments wanting integrated asset management
• Environments comfortable with SaaS

Less suitable for:

• Organisations requiring self-hosted deployment
• Entities avoiding US cloud providers
• Budget-constrained organisations (smaller teams)
• Environments needing deep customisation

Zendesk

Type

Commercial SaaS

Licence

Proprietary; subscription-based

Current version

Continuous updates (SaaS)

Deployment options

Cloud only

Vendor

Zendesk (private equity-owned since 2022)

Documentation

developer.zendesk.com

Overview

Zendesk is a leading customer service and support platform used by organisations across industries. While primarily positioned for customer service, Zendesk’s flexibility enables internal IT help desk use. The platform provides omnichannel support, AI-powered automation, and extensive integration options.

Zendesk was acquired by private equity in 2022, transitioning from public company to private ownership. The platform continues active development with focus on AI features and enterprise capabilities.

Capability assessment for ITSM

Zendesk provides strong ticket management with multichannel support (email, chat, voice, social, messaging). The platform supports ITIL-style workflows through ticket types, automations, and macros. Knowledge base (Zendesk Guide) integrates with ticket creation for article suggestions.

For formal ITIL processes, Zendesk requires configuration. The platform lacks native change management, problem management, and CMDB. Organisations requiring these capabilities should consider Zendesk in combination with other tools, or evaluate ITSM-specific platforms.

Key strengths:

• Leading omnichannel support platform
• Extensive AI features for automation
• Large integration marketplace (1,500+ apps)
• Strong analytics and reporting
• Mature, stable platform

Key limitations:

• Customer service focus; ITIL processes require configuration
• No native CMDB or asset management
• No change/problem management without extensions
• SaaS only; no self-hosted option
• US-headquartered; CLOUD Act applies

Cost analysis

Nonprofit programme: Up to 50% discount via Tech Impact; verification required.

Organisational fit

Best suited for:

• Customer service operations
• Organisations already using Zendesk for external support
• Environments prioritising omnichannel support
• Teams needing strong analytics

Less suitable for:

• ITIL-aligned IT service management
• Organisations requiring change/problem management
• Entities needing CMDB integration
• Environments requiring self-hosted deployment

Selection guidance

Decision framework

                                      +------------------+
                                      | ITSM platform    |
                                      | needed?          |
                                      +--------+---------+
                                               |
                  +----------------------------+-------------------------+
                  |                                                      |
                Full ITIL                                        Help desk /
                coverage needed?                                 Customer support
                      |                                                  |
         +------------+------------+                        +------------+------------+
         |                         |                        |                         |
        Yes                       No                  Internal IT                External CS
         |                         |                        |                         |
    +-----+-----+           +------+------+          +------+------+           +------+------+
    |           |           |             |          |             |           |             |
Self-hosted    SaaS      Self-hosted     SaaS      Self-hosted    SaaS      Self-hosted    SaaS
    |           |           |             |          |             |           |             |
 iTop         JSM        Zammad         JSM        Zammad        JSM        Zammad        Zendesk
 OTOBO        Fresh-     osTicket       Fresh-     osTicket      Fresh-     osTicket      Fresh-
 RT           service                   service                  service                  service

Recommendations by organisational context

For organisations with minimal IT capacity

Primary recommendation: Freshservice (Starter) or osTicket (self-hosted)

Rationale: Freshservice provides quick deployment with minimal administration; pre-configured workflows reduce setup time. For organisations with existing web hosting and budget constraints, osTicket provides essential ticketing with low overhead.

Alternative: Zammad SaaS provides modern interface with straightforward administration; German hosting addresses EU data residency concerns.

Avoid: iTop, OTOBO, RT without dedicated IT staff; complexity exceeds benefit for simple requirements.

For organisations with established IT capacity

Primary recommendation: OTOBO or iTop (self-hosted) for full ITIL; Zammad for service desk focus

Rationale: OTOBO and iTop provide comprehensive ITIL coverage with CMDB integration. Docker deployment (OTOBO) simplifies operations. Organisations with Perl or PHP expertise can customise extensively.

Alternative: Jira Service Management (Cloud) if Atlassian ecosystem already deployed; Premium tier for Assets and advanced features.

Avoid: Basic platforms that require significant customisation to meet ITIL requirements.

For organisations with specific constraints

Data sovereignty/EU requirements:

• Recommended: Zammad, OTOBO, or iTop (German/French vendors; self-hosted or EU SaaS)
• Avoid: US-headquartered SaaS (Zendesk, Freshservice) for sensitive data

CMDB-centric operations:

• Recommended: iTop (CMDB is foundational); JSM with Assets (Premium)
• Avoid: Zammad, osTicket, Zendesk (no native CMDB)

Security incident response:

• Recommended: Request Tracker with RTIR
• Alternative: OTOBO with ITSM packages

Maximum budget constraint:

• Recommended: osTicket (lowest resource requirements); Zammad (balanced capability/simplicity)
• Avoid: Commercial platforms without nonprofit discounts

Migration paths

Resources and references

Official documentation

Related standards

See also

• Security and Monitoring
• Service Management Framework
• Incident Management
• Service Desk Operations