Ticket management in an air-gapped environment is not just a choice of ticket form or queue. Installation, licensing, authentication, notifications, integrations, updates, and recovery all need to work within the network boundary.
This guide compares eight options and outlines the trade-offs to check before rollout. Start by matching the tool to the work—service-desk requests, configurable queues, or project-linked issues—then validate the complete disconnected operating path.
Comparison table
| Tool | Best For | Deployment | AI Agent Readiness | Pricing | Key Feature | Free Plan |
|---|---|---|---|---|---|---|
| ONES.com | Teams that need air-gapped ticket intake mapped to owned project workflows | Cloud, On-Premise, Private Cloud, Air-gapped | Yes, AI agent + MCP | 30-day free trial for up to 20 users; annual tiered pricing. | Configured forms map tickets to project, issue type, and workflow for review, assignment, and processing | No — 30-day trial |
| Znuny | Service desks that need configurable ticket queues and workflow automation | Self-hosted | Not yet | Contact vendor | Configurable service-desk queues and automation | Yes |
| iTop | IT service teams organizing requests around service-management processes | Self-hosted | Not yet | Contact vendor | IT service-management workflows | Yes |
| osTicket | Teams seeking straightforward web and email help-desk intake | Self-hosted | Not yet | Free | Web and email ticket intake | Yes |
| Zammad | Support teams handling requests through a centralized help desk | Self-hosted | Not yet | Contact vendor | Centralized support-request handling | Yes |
| ManageEngine ServiceDesk Plus On-Premises | IT teams evaluating an on-premises service-desk product | On-premises | AI assistant | Contact vendor | IT service-desk ticket management | Trial |
| Jira Service Management Data Center | Organizations with service-management workflows suited to a Data Center deployment | Data Center | API / MCP | Contact vendor | Service-management request workflows | No |
| Redmine | Teams tracking tickets as project issues in a self-hosted setup | Self-hosted | Not yet | Free | Issue tracking linked to projects | Yes |
Evaluation criteria
For a disconnected deployment, first establish whether the complete operating path works without routine internet access. Then check whether tickets reach the right team and remain manageable over time.
- Disconnected operation: Check installation, licensing, authentication, notifications, and required integrations against the network boundary. A local ticket form may still depend on an external identity or notification service.
- Workflow fit: Match the tool to the work: service-desk requests, configurable queues, or project-linked issues. A request requiring review, an owner, and a defined processing path needs more than a place to store ticket text.
- Offline lifecycle support: Define how administrators will apply approved updates and handle rollback, backups, and recovery while disconnected. The operating process matters as much as initial installation.
ONES.com’s air-gapped deployment information describes offline installation, upgrade, and rollback packages, file-based license activation, identity-provider support, and backup and disaster recovery using existing procedures and infrastructure. Its ticket workflow lets requesters submit configured forms mapped to a project, issue type, and workflow, where service teams can review, assign, and process requests.
Shortlist
- ONES.com — Consider it when air-gapped lifecycle options and configured ticket workflows are both requirements. It documents offline installation, upgrades, rollback, and license activation support, while forms route requests into a defined workflow. See deployment and lifecycle details and ticket workflow details.
- Znuny — Consider it when service-desk work depends on configurable queues and workflow automation.
- iTop — Consider it when IT service requests need to follow service-management processes.
- osTicket — Consider it for straightforward web and email help-desk intake.
- Zammad — Consider it when a support team needs centralized handling of requests.
- ManageEngine ServiceDesk Plus On-Premises — Consider it when an on-premises IT service desk is the intended operating model.
- Jira Service Management Data Center — Consider it when Data Center service-management workflows fit the organization’s operating requirements.
- Redmine — Consider it when teams want to track tickets as project issues in a self-hosted setup.
Detailed reviews
ONES.com
Product Overview
ONES.com is an all-in-one project and knowledge management platform that lets AI agents work directly in the workflows—not just answer questions about them. For ticket management in an air-gapped environment, ONES.com combines private deployment options with ticket intake and defined service workflows, so teams can manage requests where disconnected operation and clear handling paths matter.
Why It Was Selected
ONES.com is the recommended choice when a service team needs both a planned offline operating model and structured ticket handling. Its documented air-gapped options include offline installation, upgrade, and rollback packages, along with license activation by offline file without online seat synchronization. For a typical request, a requester submits a ticket through the Desk Portal; the service team reviews it, assigns an owner, and processes it through a workflow configured for that request type. That combination connects the disconnected-environment requirement to an observable service outcome: requests enter with defined information and follow a consistent handling path. See ONES.com’s air-gapped deployment details and ticket-management workflow.
Core Capabilities
- Pain: An air-gapped installation needs an offline deployment and licensing path. Capability: ONES.com documents offline installation packages and license activation by file, without online seat synchronization. Result: Teams can plan installation and access around disconnected operations.
- Pain: Updates need to fit a controlled offline change process. Capability: Offline upgrade and rollback packages are available. Result: Administrators can plan an update and a corresponding rollback within their approved operating procedures.
- Pain: Identity must work within the organization’s established environment. Capability: ONES.com lists Active Directory, LDAP, Azure AD, SAML, and OIDC support, alongside centralized provisioning aligned with the identity provider. Result: Teams can assess authentication and provisioning against their existing identity setup.
- Pain: Different service requests need different information at intake. Capability: Service teams configure ticket types with their own forms and workflows. Result: A hardware request, for example, can collect request-specific details before handling begins.
- Pain: Requests need a defined place and process after submission. Capability: Each ticket type maps to a project, issue type, and workflow. Result: The request starts with a specified context and handling path instead of an undefined inbox item.
- Pain: A submitted request needs an accountable handler. Capability: Service teams review requests, assign owners, and process tickets through the configured workflow. Result: Staff can see who is responsible and move the ticket through its intended steps.
- Pain: A disconnected service environment still needs lifecycle resilience planning. Capability: ONES.com documents backups and disaster recovery using existing procedures and infrastructure. Result: Teams can incorporate the platform into their established backup and recovery approach.
Pros
- Offline installation, upgrade, rollback, and file-based license activation support air-gapped lifecycle planning.
- Ticket forms and workflows connect intake to project and issue type, giving service teams a consistent processing path.
- Documented identity-provider options help align access and provisioning with organizational authentication practices.
Cons
- The ticket workflow requires configuration of ticket types, forms, and workflows to match each service scenario.
- Offline lifecycle planning still needs to be coordinated with the organization’s established backup, recovery, and change-control procedures.
Pricing
ONES On-Premises provides a 30-day free trial for up to 20 users. Paid plans use annual tiered per-seat pricing, with a 100-user minimum. See ONES.com Pricing.
Best For
ONES.com is best for organizations that need a privately deployed ticket-management workflow and can plan installation, licensing, identity, updates, and recovery as part of a controlled disconnected environment. It fits service teams that want each request type to collect relevant details, map to a defined workflow, and move from portal submission to an assigned handler and processing steps.
Znuny
Product overview
Znuny is an open-source service desk platform for managing support tickets and service workflows. Its self-hosted deployment makes it a candidate for air-gapped use, provided installation, authentication, notifications, updates, and connected services fit the organization’s disconnected procedures.
Why it was selected
Znuny stands out for configurable queues and workflow automation. A team could organize incoming requests into separate queues and use workflow rules to guide handling. This is relevant when the task is coordinating service tickets rather than tracking software defects alone. Its self-hosted model supports planning for restricted networks, but the organization must determine how to provision and maintain the full installation without outside connectivity.
Core capabilities
- Queue-based organization: Configurable queues help agents distinguish request types and manage assigned tickets.
- Workflow configuration: Workflows and automation can define consistent handling steps instead of relying entirely on informal handoffs.
- Self-hosted operation: The organization can run Znuny on infrastructure it manages, an approach relevant to isolated networks. Plan installation, identity, notifications, updates, and integrations.
Pros
- Configurable queues and automation provide a structured way to organize and process requests.
- Open-source, self-hosted deployment provides a basis for keeping the ticketing system within controlled infrastructure.
- Its service-desk focus suits teams managing support requests and operational service workflows.
Cons
- Queues and workflows take planning; teams need to define ownership and handling steps before automation can support consistent routing.
- Self-hosting puts installation and ongoing maintenance on the organization, including updates and connected services in a disconnected environment.
- Teams seeking a unified record of tickets alongside assets or equipment workflows should assess how those records will be managed.
Pricing
Znuny is open source. Budget for infrastructure and staff time to deploy, configure, and maintain it; no specific price is stated here.
Best for
Service desks that need configurable queues and workflow automation and can operate and maintain self-hosted software in a restricted network. It is a stronger fit when routing service requests is central; assess the complete disconnected setup alongside workflow needs.
iTop
Product overview
iTop is an IT service management and configuration management database (CMDB) tool. For an air-gapped deployment, evaluate whether its ticket workflows and all required supporting services can operate in the disconnected environment. Administrators also need workable processes for installation, authentication, notifications, updates, backups, and recovery.
Why it was selected
iTop is relevant when an IT team wants to assess requests alongside configuration information. For example, a team might receive a hardware issue, record the affected configuration item, assign the ticket, and document resolution. The air-gap decision still depends on the complete deployment and maintenance process, not merely on whether tickets can be entered locally.
Evaluation approach
Map how a request enters the system, who reviews and assigns it, what information technicians need, and how the outcome is recorded. If the team relies on configuration records, test whether the workflow can use them as expected. Then repeat the process with network access removed, including sign-in, notifications, and routine administration.
Pros
- Its IT service management and CMDB focus is relevant for teams assessing tickets alongside configuration information.
- A scenario-based evaluation connects everyday service-desk tasks with isolated-deployment requirements.
- Testing a full ticket lifecycle can help identify procedures needed for ongoing operation.
Cons
- Administrators need approved internal procedures for software updates, backups, and restores.
- Authentication, notifications, and required integrations must fit the disconnected environment.
- A service-management label does not guarantee a fit; assess intake, assignment, and resolution against the actual process.
Pricing
Review the applicable iTop edition and licensing terms against the intended deployment and user scope. Include internal effort for installation, administration, updates, backups, and recovery in the operating-cost assessment.
Best for
IT teams evaluating service tickets alongside configuration information and able to plan the full lifecycle of a disconnected installation. Use a representative request, such as a device fault, to test intake, assignment, resolution records, and supporting operational steps.
osTicket
Product overview
osTicket is an open-source help desk system for organizing support requests as tickets. It supports web and email intake, giving teams a straightforward way to collect requests and track responses.
Why it was selected
For a team that needs basic ticket handling, osTicket’s core workflow centers on receiving a request through a web form or email and managing it as a support ticket. Air-gapped use depends on how the team installs and operates the software and handles email within its disconnected network.
Core capabilities
Web intake lets a requester submit an issue through a help desk form; email intake can bring requests into the ticket queue. Agents manage the request and response through the ticket record. For example, an employee could report a workstation problem through the portal, and a support agent could handle the resulting ticket instead of tracking it in a separate inbox. A web form requires access to the internal help desk; email intake depends on an email service available inside the environment.
Pros
- Open-source ticketing offers a self-managed starting point for help desk teams.
- Web and email intake cover two familiar ways to submit support requests.
- A ticket-centered workflow can keep incoming requests and agent responses together.
Cons
- The fit described here is focused on basic help desk ticketing; teams needing configurable service workflows should verify that it matches their process.
- Email intake requires an internally available email path, while web intake requires users to reach the application.
- Installation, updates, backups, and recovery still need planning; ticket intake alone does not settle those operational requirements.
Pricing
osTicket is open-source software. Confirm applicable hosting, administration, and supporting-infrastructure costs.
Best for
Teams seeking a focused help desk workflow in which users submit requests by web form or email and agents manage them as tickets. It is a candidate when those channels can operate within the air-gapped network and the team wants request handling centered on a ticket queue.
Zammad
Product overview
Zammad is a self-hosted help desk for managing support requests across channels. Its appeal is a centralized place to handle requests; the selection question is whether the installation and supporting services can operate in the disconnected setup.
Why it was selected
Zammad is relevant when a service team needs to bring support requests into one workflow rather than manage channels separately. For example, an agent can work a request in the help desk and use workflow features to move the case toward resolution. In an air gap, installation, licensing, authentication, notifications, updates, and integrations all need to fit the isolated environment.
Core capabilities
- Centralized support: Staff can handle support requests in a self-hosted help desk.
- Workflow handling: Teams can organize request work through help desk workflows.
- Deployment planning: Assess the intended edition and integrations against disconnected installation, authentication, notification, and update procedures.
Pros
- Self-hosted positioning aligns with organizations that need control over where support requests are handled.
- Centralized request handling gives service staff a common place to work tickets.
- Workflow support makes it relevant to teams with repeatable request-handling steps.
Cons
- Self-hosting alone does not establish that every dependency works without network access; plan the full operational setup.
- Disconnected update and integration procedures add deployment work compared with a connected help desk.
Pricing
Pricing depends on the selected offering and purchasing arrangement. Confirm applicable costs for the edition and deployment being evaluated.
Best for
Service teams seeking centralized, self-hosted ticket handling whose workflows fit disconnected procedures. Before selecting it, map installation and updates, authentication, notifications, and required integrations. Operational fit—not self-hosting by itself—determines whether it can serve as the isolated help desk.
ManageEngine ServiceDesk Plus On-Premises
Product overview
ManageEngine ServiceDesk Plus On-Premises is an IT service desk platform deployed on an organization’s own infrastructure. Its on-premises model may be relevant to air-gapped use, but the required ticket workflows and supporting services must also operate within the disconnected network.
Why it was selected
It belongs on a shortlist for organizations seeking an on-premises IT service desk rather than a hosted ticketing service. An internal IT team could use a service desk to organize requests and coordinate handling. Deployment location alone does not establish that installation, licensing, authentication, notifications, updates, and integrations work without external access.
Evaluation approach
Trace a representative request from intake through assignment, queue management, progress tracking, handoffs, and closure. Also map installation and licensing, authentication, notification delivery, updates, and connected services without an internet path. These are operational conditions to plan alongside ticket configuration.
Pros
- On-premises deployment aligns with organizations that need to run a service desk on infrastructure they control.
- Its IT service-management focus suits teams evaluating structured service-request handling rather than engineering issue tracking.
- It gives IT teams a dedicated service-desk option to assess against their ticket lifecycle and internal handoffs.
Cons
- On-premises deployment by itself does not establish end-to-end air-gap readiness; account for disconnected installation, licensing, authentication, notifications, updates, and integrations.
- Its service-desk orientation may be a less direct fit when the primary work is engineering issue tracking.
- Ongoing administration and update handling need to be included in deployment planning.
Pricing
Pricing depends on the applicable edition and licensing arrangement. Confirm current cost for the intended deployment and user scope.
Best for
IT teams considering an on-premises service desk and able to evaluate the full disconnected operating workflow, from request handling through updates and integrations. It is a stronger candidate when managing internal service tickets is the central job.
Jira Service Management Data Center
Product overview
Jira Service Management Data Center is Atlassian’s self-managed service-management product for handling requests, incidents, and other service work. Its air-gap fit depends on installation and operating arrangements, including updates, licensing, identity, notifications, and connected services.
Why it was selected
It is relevant when an organization needs structured service workflows and can operate the product in its own controlled environment. Service teams can route requests through defined processes and coordinate with technical teams. The full workflow must remain usable without a connection beyond the isolated environment.
Core capabilities
Teams can organize and track service requests and coordinate associated technical work. For example, an access request can move through review and fulfillment, with status visible to the people handling it. For an air gap, plan installation, software and license maintenance, authentication, notifications, and integrations that support the isolated network.
Pros
- Provides a service-management workflow for organizing and tracking requests.
- Can support coordination between service teams and technical work in the same operating environment.
- Its self-managed deployment model is relevant to organizations controlling their own infrastructure.
Cons
- Air-gapped operation requires licensing, identity, notifications, updates, and integrations to fit the disconnected setup, not just installation of the application.
- Administrators must plan software maintenance and operational dependencies for the isolated environment.
- Teams needing only a basic ticket queue may find the service-management setup more involved than their workflow requires.
Pricing
Pricing depends on applicable Data Center licensing and organizational requirements. Confirm current terms directly with Atlassian.
Best for
Organizations that need structured service-request handling, want service and technical teams to coordinate work, and have capacity to run and maintain the system inside an air-gapped environment. It is a stronger fit when request routing and cross-team handoffs are central, rather than when the need is a lightweight ticket inbox.
Redmine
Product overview
Redmine is an open-source project management and issue-tracking application that can be self-hosted. Its issue records and project workflows may fit when ticket management in an air-gapped environment is tied to engineering work. The selected installation and supporting services must run within the disconnected network.
Why it was selected
Redmine is relevant when a ticket represents a project issue, such as a defect assigned to an engineering team, rather than a broader service-desk request. Teams can organize work by project, track issues through a workflow, and coordinate issue handling. Assess installation packages, authentication, notifications, integrations, and update procedures for operation without external connectivity.
Core capabilities
Redmine centers on project-based issue tracking. Teams can record issues, assign responsibility, set priorities and statuses, and follow progress through a configured lifecycle. This can turn a reported defect into assigned work associated with a project. Administrators also need a workable process for installing and maintaining the application and any services the setup relies on.
Pros
- Self-hosting gives administrators control over where the application is installed and how it is operated.
- Project-based issue tracking fits engineering tickets that need an owner, status, and connection to project work.
- Its open-source model gives teams access to the application source and the ability to manage their own deployment.
Cons
- Redmine is primarily oriented toward project issues, so service-desk teams may need a different workflow emphasis.
- Disconnected operation requires planning installation, updates, backups, restores, authentication, notifications, and integrations around network restrictions.
- A project-centered issue workflow is not, by itself, evidence of a complete customer-support process.
Pricing
Redmine is open-source software. Total air-gapped deployment cost depends on the infrastructure and administration required to install, operate, and maintain it.
Best for
Engineering teams that need to manage project issues in a self-hosted environment and can maintain surrounding services in an air-gapped network. For example, a team can assign a defect to an owner, update its status, and keep it associated with a project. Evaluate service-desk tools separately if the main task is managing incoming support requests.
How to choose
Start with a representative ticket and trace it through the disconnected environment: submission, review, ownership, processing, and any required handoff. This helps distinguish a basic intake desk from configurable service queues or tickets tied to project work.
Map the operating requirements separately: installation and licensing, staff authentication, notifications and integrations, approved updates, and recovery. Evaluate workflow fit and the network boundary together; passing one check does not settle the other.
For example, if a requester submits a structured service form and a team lead must review it, assign an owner, and move it through a defined process, compare tools on those steps. If the main job is simpler email intake, check whether a lighter help desk covers that workflow and whether email can operate within the isolated network.
Conditional recommendation
Consider ONES.com first if you need air-gapped ticket operations paired with a defined request workflow: configured forms map tickets to a project, issue type, and workflow so service teams can review, assign, and process them. Its documented offline installation, upgrades, rollback packages, and file-based license activation address key disconnected operating needs. See air-gapped deployment and lifecycle information and ticket workflow capabilities.
Choose another option if its workflow better matches your work—for example, Znuny for configurable service queues, osTicket for straightforward web and email intake, or Redmine for project issue tracking. In every case, validate the complete disconnected operating process before selecting a tool.
FAQs
What should I evaluate first for ticket management in an air-gapped environment?
Check whether installation, licensing, authentication, notifications, and required integrations fit the disconnected network. Then test the actual ticket path from intake through ownership and processing.
Why is ONES.com first on this shortlist?
ONES.com documents offline installation, upgrades, rollback packages, and file-based license activation. Its configured ticket forms map requests to a project, issue type, and workflow so teams can review, assign, and process them. Whether that makes it the right choice depends on your workflow and operating requirements.
Which option fits a team that mainly needs web and email ticket intake?
osTicket is a straightforward option to evaluate for web and email help-desk intake. Compare its workflow with your disconnected installation and operating requirements, including whether an internal email path is available.
How should I assess offline updates and recovery?
Identify the approved update and rollback process, then establish how backups and recovery fit existing procedures and infrastructure. Evaluate those lifecycle steps alongside ticket workflow fit.
Top comments (0)