Book an IT reviewOngoing IT support under subscription
Business systems
Data and AI
Our apps
NNexa Hub 1.2 · a ticketing system by NexaIT
A fault reported on the spot, fixed within a deadline everyone can see. One portal for Facility, IT, security, WMS support and every department you add. A QR code on the door or a PIN kiosk on the shop floor, a queue with an SLA clock for the team, numbers for management.
200k
tickets in the pre-release performance test
c. 300 MB
of memory at idle, on a server from 2 vCPUs and 2 GB RAM
ASVS L2
OWASP security review before release
PL and EN
interface, e-mails and Polish public holidays in the SLA calendar
Nexa Hub is a multi-department ticketing system (service desk) that you install on your own server. We built it at NexaIT for companies where tickets are not only about computers: warehouses, distribution centres, manufacturing plants and offices with several support departments.
Employees have one address and one portal. They choose a department and a request type and fill in a short form, and the ticket lands in the right team's queue with the location, equipment, photo and SLA deadline. Each department has its own forms, statuses, response times, team and analytics, and management sees all departments in one table.
The system works in Polish and English, counts deadlines in shift hours with Polish public holidays and runs on a single server with Docker. Ticket data, photos and accounts stay in your infrastructure.
Department, request type, form. Fields that fit the request, a location from the site tree, a photo pasted from the clipboard.
Mine, unassigned, at risk of breaching the deadline. Reply, internal note, status and assignment without taking your hands off the keyboard.
Columns are the department's statuses. Cards are dragged with a mouse, touch or keyboard, and the change can be undone.
The current state, 10 period indicators with comparison, flow, speed and SLA, backlog age. Clicking a number opens exactly those tickets in the desk.
A shared screen on the shop floor for people without a company mailbox. After a minute of inactivity the kiosk signs out by itself.
The department administrator sets request types, fields, statuses and SLA times. A department template carries its configuration over to another site.
Screenshots from a Nexa Hub 1.2 demo installation. The company, people and tickets are fictitious.
This is the path of a dock 5 door fault in a distribution centre. The screens come from a Nexa Hub 1.2 demo installation, and the company, people and tickets are fictitious.
1. Reporting
The sticker opens a form with the location and request type filled in. Before submitting, the employee sees that someone has already reported the same problem, so the department does not get five copies of one fault.
2. Handling
Agents see their own tickets, unassigned ones and those close to their deadline. They reply to the requester, add a note for the team, change status and assignment. Frequent actions have keyboard shortcuts.
3. Deadline
Three shifts, Saturdays until 2 pm, Polish public holidays added automatically. The deadline does not run at night when the shop floor is idle, and it pauses while a ticket waits for parts or for the requester's reply.
4. Numbers
Created and closed, median first response, share of deadlines met, the locations and equipment that fail most often. Every indicator compared with the previous period of the same length.
Request types, form fields, statuses with names for the team and for the requester, SLA times, team, macros, QR codes and webhooks are set by the department administrator. Nothing that concerns a single department requires code changes.
You download a department's configuration as a template and create a department from it at another site or in another installation. The demo installation has four departments set up for a distribution centre.
FIX-001947IT-001685LP-001383WMS-001616We install Nexa Hub in your network or on a server you rent in the cloud. Below are the differences compared with a ticketing system bought as a subscription service (SaaS).
| Aspect | Nexa Hub | Subscription system (SaaS) |
|---|---|---|
| Where the data lives | On your server, in your backup | In the provider's data centre |
| Updates | When you decide, after a backup | When the provider decides |
| Shop floor sign-in | Kiosk with employee number and PIN | Depends on the provider and plan |
| SLA calendar | Shifts and Polish public holidays built in | Depends on the provider and plan |
| Departments beyond IT | Each department with its own form, statuses and SLA | Depends on the provider and plan |
Before release 1.0 the system passed a performance test on 200k tickets and a security review against OWASP ASVS 4.0.3 level 2, and the analytics dashboards from version 1.1 were measured on the same database. The figures below come from the release documentation.
| Operation | p50 | p95 | p95 budget |
|---|---|---|---|
| Desk: overview with queue counters | 50 ms | 96 ms | 300 ms |
| Desk: “In progress” queue (11k tickets) | 95 ms | 134 ms | 150 ms |
| Desk: “All” queue (50k tickets) | 96 ms | 132 ms | 150 ms |
| Full-text search | 143 ms | 211 ms | 250 ms |
| Ticket details | 36 ms | 68 ms | 100 ms |
An IT helpdesk usually serves a single department. Nexa Hub is a ticketing system for many departments at once: Facility, IT, security, WMS support, HR. Each department has its own request types, forms, statuses, SLA times and analytics, and employees raise everything in one portal.
On your server. We install it in your company network or on a server you rent in the cloud. All it needs is Linux with Docker, 2 vCPUs, 2 GB RAM and 20 GB of disk, plus space for attachments and backups.
We set the price after the demo, because it depends on the number of departments and sites, the scope of deployment and whether you want us to maintain the system. The quote covers the licence, deployment and optional support.
Yes. You place a kiosk on the shop floor and employees sign in with their employee number and PIN. On the kiosk everyone acts only as a requester, and the screen signs out automatically after a minute of inactivity.
Yes. Nexa Hub supports sign-in with Microsoft Entra ID, Google Workspace and other OpenID Connect providers. Local accounts with a password and two-factor authentication work alongside.
The interface, e-mails and notifications are in Polish and English. You enter the names of departments, request types and fields in both languages, and each user chooses their own.
Online demo · no obligation