Open source is a fair option to consider, especially if you have developers on the team or want to change how the system works. The software has no licence fee, but it is not free to run: the cost moves from a subscription to your own time, your own server and your own fixes. Knowing that trade before you start saves a lot of rework later.
Which Open-Source Queue Systems Can You Look At?
Two projects with public code and active development:
- NovoSGA: a queue and service management system first released in 2012, available under the MIT licence. It is written in PHP, has translations in English, Spanish and Portuguese, and is maintained by the company Mangati with contributors from its community. It has separate client apps for the token display panel and for triage, where tokens are issued. Its project site also offers professional hosting for those who do not want to run it themselves.
- FQM (Free Queue Manager): a web-based queue management system built with Python Flask, available under the Mozilla Public License 2.0. Its code repository lists support for POS USB printers on major operating systems, customisable interfaces and text-to-speech announcements. The project describes itself as a beta, and recommends a Docker setup for production.
Both are real, working projects. Before you pick either, read its own documentation and make sure it does what your counters need today.
What Does Running One Yourself Involve?
With open source, you become the provider. That means:
- A server: NovoSGA's installation guide, for example, asks for a Linux server with PHP 8.2, a MySQL 8.0 or PostgreSQL 13+ database and an Apache2 or NGINX web server, or a Docker setup instead.
- Installation and setup: someone has to install it, then configure the services, counters, users and screens.
- Updates and security: new releases and security fixes are yours to apply and test. Open-source licences such as the MIT licence provide the software "as is", without warranty.
- Printers and screens: you connect the token printers and the waiting area screens and keep them working.
- Backups: the token history and the reports live in your database, so your team backs it up.
- Support: help comes from your own team and the project's community, such as NovoSGA's forum and Telegram group.

When Does Open Source Make Sense?
Open source suits an organisation with a developer or an IT team that has time to install and look after it. It also helps if the setup can start small, and if there is a reason to change the code, such as a custom step that no product offers. It is also a sensible way to learn how a queue system works before buying one.
Where Does a Managed Queue System Fit?
A managed system fits when you would rather not run servers, or when the queue has to work across many counters and branches from the first day. With Wilyer's queue management system, for example, customers take a token at the counter, at a kiosk or on their phone, and staff call the next token from a tablet or phone. A voice announces it in more than one language, and one dashboard shows every branch. It runs in the cloud or on your own server. Every client starts from a standard setup, and Wilyer handles any industry-specific integration on request.
The cost model is different too. Open source has no licence fee but costs staff time and server bills. A managed system is usually priced by counters, branches or screens, and Wilyer's queue system is priced on request.
What Should You Ask Before You Choose?
- Who will install it, update it and fix it when something stops working?
- Where will the data live, and who backs it up?
- Does it work with the printers, kiosks and screens you plan to use?
- Can announcements play in the languages your visitors speak?
- How many counters and branches will it need to handle in two years?
- What will it cost over three years, counting staff time?
Our guide to what a queue management system is covers the types and the costs, which makes the comparison easier whichever way you go.




