By Znuny

Znuny

What it does

Znuny is an open-source help desk and IT service platform for turning requests into trackable tickets. A support team can collect requests from email, a portal or other channels, route them through a defined process, work against service targets, and retain useful answers in an FAQ. The core software is free to use, while the vendor also sells support and hosted service.

Category
Help Desk
Last updated
Oct 20, 2026
Znuny · Editorial illustration
Conceptual editorial illustration of a blank service requests moving through routing to a resolved case folder.

Work at Znuny?

Help customers find accurate information about your software.

Manage this listing →

Find your fit

Who it is for

Znuny fits a support team that needs one place to follow customer or internal service requests across several entry points. Its help desk and product-support examples cover both technical issue handling and ongoing customer service, provided the team is willing to set up queues, processes and access rules.

It may also suit organizations that prefer to run a service desk on their own infrastructure. The vendor offers managed hosting and professional support when an organization wants those responsibilities covered by a contract; the free software alone does not include those services.

Back to sections

The work it supports

Core capabilities

A request can enter through customer self-service, email, an agent handling a phone call, a web service or a monitoring tool. Znuny groups interactions in a ticket history, giving agents a common record for the work instead of separate channel-specific threads. Confirm which intake channels a team will actually configure before promising them to users.

Administrators can set up routing, classification, escalation, notifications and ticket-state changes. Email filters cover simpler rules, while process tickets support more involved steps. A useful pilot is one request that changes owner or queue so the team can check each handoff.

The customer portal lets users create requests and see their earlier tickets and status. Support answers can be stored centrally in the FAQ and exposed in the portal for repeat questions. Before launch, check the portal's access and article visibility with a test customer account.

Znuny can track first response, update and solution targets against service-level agreements, with escalation and working-time calendars. These controls are most useful after the team defines its service hours and verifies how an overdue ticket appears to an agent.

Customer information can appear alongside a ticket. Znuny lists directory services, SQL databases and web services as possible sources for existing customer data, plus custom fields for users and companies. Mapping and permissions deserve a trial before importing a large customer list.

Reporting includes user-defined statistics, dashboards and on-demand or scheduled reports. A team can start with request volume and overdue work, then confirm that the available fields match the measures it needs to review.

Back to sections

Understand the offer

Pricing and getting started

The vendor describes Znuny itself as open source and free to use. Organizations may run it on their own server, but they must then arrange hosting, installation, maintenance and operational support appropriate to their environment.

Professional support is a separate subscription with Silver, Gold and Platinum tiers. The public plans vary by service window and request allowance, include an associated test system, and do not limit the number of agents. Check the current quote and support terms for the team's location and severity needs.

Znuny also sells dedicated managed hosting. Its published hosting plans include a test system and matching support subscription, display monthly rates billed annually, and show a one-time setup fee on the Silver tier. Confirm total term, setup and storage needs with the vendor before treating a posted rate as a complete budget.

Back to sections

Look a little closer

Before you choose

Pilot the actual path from request to resolution: create a ticket from each intended channel, route it, update its state, test an escalation, and let the customer check its status. This will expose configuration work that a feature list cannot show.

Decide who maintains the system and what support level is needed. Free self-hosting, paid support and paid managed hosting are distinct choices; compare their service responsibilities, contract windows and test-system arrangements before deployment.

If the team connects existing customer data or exposes the FAQ through the portal, test record mapping and visibility with representative accounts. Check that reports use the right ticket fields and that business-hour calendars align with stated service commitments.

Back to sections

10 distinct sources behind this profile. Research observed Oct 20, 2026. Features and offers can change.
View sources and research →

Help keep this profile useful

Spotted an outdated detail? Send the correction with a supporting source. A verified account is needed to submit.

Suggest a correction ↗