Open-Source IT Asset Tracking and Ticket Management: The Best Tools in 2026

Open-source IT asset tracking now splits into two problems that need different tools. Traditional ITSM platforms – Snipe-IT, GLPI, Ralph, iTop – handle physical hardware and software licences well, and several are more active than they’ve ever been (GLPI 11 shipped in 2026, Snipe-IT continues weekly releases). They were not built to track cloud infrastructure that spins up, scales, and terminates inside a single shift. For that, you need cloud-native asset tracking: tools that read Terraform state, query cloud provider APIs, and flag drift in real time. Most hybrid teams end up running one of each.

This guide compares the leading open-source options in both categories, fixes a few errors floating around in older roundups (yes, OTRS Community Edition is dead – Znuny is the active fork), and shows how ticketing fits between the two.

Why the Physical/Cloud Split Matters

Snipe-IT and GLPI assume an asset has a serial number, a purchase order, and a lifecycle measured in years. That model works for laptops, monitors, and on-prem servers. It collapses when a VM exists for six hours, a Kubernetes namespace creates and destroys 40 resources overnight, or Terraform replaces an entire VPC because someone bumped a module version.

Cloud assets need a different discovery model. Industry data from 2026 puts the operational cost of this gap in plain terms: 86% of organisations cite infrastructure drift as a significant operational challenge, and teams spend roughly 40% of their infrastructure time on manual remediation (dev.to IaC security analysis, 2026). No physical-asset tool detects drift. None of them read Terraform state. If your inventory is built on a database of serial numbers, your cloud is invisible to it.

The implication is simple. Pick a traditional tool for physical and licence inventory. Pair it with a cloud-native tracker that reads from IaC and provider APIs. Don’t try to make one tool do both – the architectures are incompatible.

How to Choose: Four Questions That Settle It

Before comparing tools, answer these:

1. Asset mix. Is the inventory mostly physical (laptops, servers, on-prem network gear) or mostly cloud (VMs, managed services, containers)? Mostly-physical teams start with Snipe-IT or GLPI. Mostly-cloud teams start with a cloud-native tracker. Hybrid teams need both.
2. Team size and ITIL maturity. Under 20 IT staff with no formal ITIL process? Snipe-IT or osTicket. 20-100 staff, some ITIL? GLPI. Enterprise with full ITIL (incident, problem, change, CMDB)? iTop.
3. Ticketing requirement. Do you need ticketing in the same tool as assets, or are you happy to integrate? GLPI and iTop bundle both. Snipe-IT and Ralph leave ticketing to a separate tool.
4. Multi-tenancy. Single org or MSP serving multiple clients? Multi-tenant requirements push you toward platforms with native hierarchical org models rather than bolted-on permission layers.

Most teams stop second-guessing after question one. The physical/cloud answer dictates the rest.

Open-Source IT Asset Tracking Tools in 2026

Snipe-IT

The default for teams primarily tracking physical hardware and software licences. Check-in/check-out, depreciation schedules, warranty alerts, full audit log. The REST API is well-documented and stable, and most teams sync it with Active Directory on a cron job and feed asset assignments back from HR onboarding tools. Where it shows its age is anything cloud: no AWS/Azure/GCP discovery, no Terraform integration, no drift concept. If your inventory is 80%+ physical, Snipe-IT is hard to beat. For a Snipe-IT alternative with broader ITSM, look at GLPI or iTop.

Ralph

Built by Allegro for data centre operations. Strong on rack layouts, network hardware, IP address management, and DC asset lifecycle. Less general-purpose than Snipe-IT, deeper for teams running their own DCs. Smaller community and slower release cadence, which is fine if your needs match its scope and frustrating if you want an active plugin ecosystem.

GLPI

The strongest single-platform option when you want asset management and ticketing in one tool. GLPI 11 shipped in 2026 with a redesigned UI, faster search, and a revised plugin model. The marketplace adds inventory agents, network discovery, and a handful of cloud connectors, but none of them do IaC-aware discovery. GLPI’s helpdesk scales comfortably to around 100 agents. Beyond that, teams typically split assets and tickets across separate platforms.

iTop

Enterprise ITSM with a CMDB at its core. Models relationships between assets, services, and teams in a way Snipe-IT and Ralph don’t. The CMDB can hold cloud resources, but populating it is manual or semi-automated – no native Terraform reader, no live API sync. iTop fits organisations that already operate ITIL processes and need the relationship modelling. It is heavier to deploy than the alternatives.

Open-Source Ticket Management Tools

If your asset tracker doesn’t include ticketing (Snipe-IT, Ralph, InfraView), you’ll need a standalone tool. Three open-source options are worth comparing.

Zammad

The most developer-friendly of the three. Clean interface, well-designed REST API, multi-channel (email, chat, phone, social). Zammad is owned by the Zammad Foundation rather than a commercial entity, which keeps the AGPL-3.0 licence in place and removes any SaaS-only pivot risk (Zammad Foundation, 2026). For teams running Snipe-IT or Ralph for assets, Zammad fills the ticketing gap without ITSM overhead.

Znuny (the actual current option, not OTRS Community)

Older roundups still list “OTRS Community Edition”. That codebase was discontinued by OTRS AG at the end of 2020. Znuny picked up the fork and has been the active project since. The latest releases shipped in May 2026 (Znuny 7.3.3 and the 6.5 LTS line at 6.5.21). It provides ITIL-aligned workflows out of the box: incident, problem, and change management. Znuny pairs well with iTop or GLPI for teams building an open-source ITSM stack with no vendor lock-in.

osTicket

The simplest option. Basic ticket routing and tracking without ITIL ceremony. Plugins handle external integrations, though less polished than Zammad or Znuny. osTicket works when you need a support queue, not a service management platform.

Cloud Asset Tracking: Why It Needs a Different Tool

Cloud resources are provisioned programmatically through Terraform, Pulumi, Ansible, or Helm, and they change state continuously. A VM scales from two instances to eight overnight. Containers live for minutes. None of that fits the procurement-to-disposal lifecycle that traditional asset trackers were built around.

Cloud asset tracking needs three capabilities traditional tools don’t provide:

• API-driven discovery that reads directly from AWS, Azure, GCP, and Kubernetes APIs – not manual entry, not CSV imports
• IaC state reconciliation that parses Terraform state files and flags when deployed infrastructure diverges from declared configuration
• Cost and ownership attribution that ties each resource back to a team, project, environment, and budget line

InfraView from Cycloid addresses the cloud half of the problem. Built on the open-source InfraMap project, it generates a live visual map of cloud infrastructure from Terraform state – every resource Cycloid manages tracked automatically across AWS, Azure, and GCP, with cost and environment tags attached. The discovery is GitOps-first: state is the source of truth, drift is surfaced, and no one is asked to keep a spreadsheet in sync with reality.

For teams operating an Internal Developer Platform, cloud asset tracking is a property of the platform, not a separate tool to deploy and maintain. Our cloud asset inventory guide covers the architecture in more depth.

IT Asset Tracking for MSPs

Managed service providers face a different problem: tracking assets across dozens of client environments with hard isolation between tenants. Each client expects an inventory view, access controls, and reports tied to their own organisation. Running a separate tool instance per client doesn’t scale.

What MSP-grade multi-tenant asset tracking actually requires:

• Per-client organisation boundaries with isolated permissions and credentials
• Automated cloud discovery across every client account, no manual reconciliation
• Consolidated reporting for internal ops alongside per-client views for customer-facing reports
• Audit trails that hold up to client and regulatory review

GLPI and Snipe-IT can be configured for multi-tenancy through user groups and permission layers, but the model is retrofitted. Every new client adds permission management overhead. Cycloid’s cloud management platform supports hierarchical child organisations natively: each client gets an isolated organisation with its own projects, credentials, and asset inventory, all managed from a single parent platform. The structure is designed for the MSP use case, not bolted on.

What This Looks Like in Practice

A common hybrid setup in 2026:

• Snipe-IT for laptops, peripherals, and software licences – synced with HR and identity providers
• Zammad or GLPI for the helpdesk queue, integrated with Snipe-IT via REST API
• Cycloid InfraView for cloud infrastructure – live inventory across AWS, Azure, and GCP, with drift detection and cost attribution
• iTop if ITIL compliance is mandatory and CMDB relationship modelling is non-negotiable

That stack covers physical, software, cloud, and ticketing without vendor lock-in. Total licence cost: zero. Operational cost: real, but bounded by what your team needs.

Frequently Asked Questions

What are the best open-source IT asset tracking tools?

For physical hardware and software licences, Snipe-IT is the most widely adopted open-source option. GLPI adds built-in ticketing and ITIL workflows. For cloud infrastructure, Cycloid InfraView provides automated asset discovery from Terraform state and cloud provider APIs. Most hybrid environments combine a traditional tool with a cloud-native tracker.

What is the best open-source alternative to Snipe-IT?

GLPI is the closest match: asset management plus a full helpdesk in one platform. For data centre hardware specifically, Ralph offers deeper rack-level and network inventory features. iTop is the stronger option for enterprises needing a full CMDB with relationship mapping between assets, services, and teams.

How do you track cloud infrastructure assets?

Cloud asset tracking requires tools that read directly from cloud provider APIs and Infrastructure as Code state files. Cycloid InfraView parses Terraform state to generate a real-time inventory of all managed cloud resources, including VMs, databases, storage, and networking, with drift detection that flags when live infrastructure diverges from declared configuration.

What open-source tools combine IT asset tracking and ticket management?

GLPI is the strongest single-platform option, bundling asset management with a helpdesk module and ITIL workflows. iTop also combines CMDB-based asset tracking with incident and change management. Teams that prefer separate best-of-breed tools usually pair Snipe-IT (assets) with Zammad (tickets) connected via REST API.

Is OTRS Community Edition still maintained?

No. OTRS AG discontinued the Community Edition at the end of 2020. The active fork is Znuny, maintained by Znuny GmbH under AGPL-3.0. If a tool comparison still recommends “OTRS Community”, check whether it’s been updated since 2020. Most haven’t.

Asset tracking is one piece of a broader platform engineering practice.