← All write-ups

ITSM

Faveo Helpdesk: Self-Hosted ITSM

Jun 29, 2026~9 min readFaveo . TurnKey . ITSM
FaveoTurnKey LinuxLaravel / PHPMariaDBITSMProxmox

Faveo Helpdesk is an open-source IT service management and support-ticketing system built on the Laravel PHP framework. It is the piece of the small-business stack that answers a different question than identity or HR: when something breaks or someone needs help, where does that request go, who owns it, and how do you make sure it does not fall through the cracks?

I deployed the open-source Community Edition as a TurnKey Linux appliance on Proxmox — the same fast-path approach I used for OrangeHRM. This write-up covers the problem a helpdesk actually solves, how to stand Faveo up, how to configure it like a real deployment, and what it gives a growing company.

On this page
  1. Why a helpdesk
  2. Deploying it on Proxmox
  3. First-boot configuration
  4. Setting it up
  5. What it gives a business
  6. Running it responsibly

Why a helpdesk

As a solutions architect, the problem here is easy to recognize: support requests that arrive as a scatter of emails, chat messages, and hallway conversations. Nothing is tracked, priorities are guesswork, the same questions get answered over and over, and there is no record of what was done or how long it took. That does not scale past a few people, and it makes it impossible to tell whether IT is actually keeping up.

An ITSM tool fixes that by turning every request into a ticket with an owner, a status, a priority, and a history. Faveo brings the core of that discipline — ticketing, assignment, service-level targets, and a self-service knowledge base — in an open-source package a small business can actually afford to run.

01 Template TurnKey LXC 02 Create CT on Proxmox 03 First boot set secrets 04 Faveo Laravel app 05 Configure agents + SLA 06 Go live tickets

Deploying it on Proxmox

TurnKey Linux publishes a ready-made Faveo Helpdesk appliance: a hardened Debian base with the full Laravel application stack, MariaDB, Apache, and SSL already configured. Proxmox carries TurnKey appliances as LXC container templates, so you can have Faveo running in minutes with no manual stack setup.

In the Proxmox web UI, open your storage, go to CT Templates > Templates, and search for faveo. Download it and create a container, or do the same from the node shell:

# Refresh the catalog and find the Faveo template
pveam update
pveam available --section turnkeylinux | grep faveo

# Download it to local storage
pveam download local debian-12-turnkey-faveo-helpdesk_18.0-1_amd64.tar.gz

# Create an unprivileged container from the template (VMID 131)
pct create 131 local:vztmpl/debian-12-turnkey-faveo-helpdesk_18.0-1_amd64.tar.gz \
    --hostname faveo --memory 2048 --cores 2 \
    --net0 name=eth0,bridge=vmbr0,ip=dhcp --unprivileged 1 --start 1

Match the exact template filename to whatever pveam available lists, and point the bridge and storage at your environment.

First-boot configuration

TurnKey appliances run an interactive setup on first boot. Open the container console from Proxmox and you will set:

  • A root password for the appliance (also used for SSH, Webmin, and MySQL).
  • An Adminer database password.
  • The Faveo admin account — the admin login for the helpdesk itself.
  • An email address for notifications and security alerts.
  • Optional automatic security updates and cloud backup, which you can enable or skip.

TurnKey deliberately ships with no default passwords — everything is set at initialization. When it finishes, Faveo is served over HTTPS at the container IP, with the usual TurnKey admin tools on dedicated ports:

https://<container-ip>/        # Faveo Helpdesk (log in as admin)
https://<container-ip>:12321/  # Webmin (system administration)
https://<container-ip>:12322/  # Adminer (database)
https://<container-ip>:12320/  # Web shell

The certificate is self-signed at first, so expect a browser warning until you put a real certificate or a reverse proxy in front of it.

Setting it up

Log into Faveo as admin and shape it around how support actually flows in the business:

  • Departments and teams — the groups that tickets get routed to (IT, Facilities, HR support).
  • Agents — the staff who work tickets, each with a role that scopes what they can see and do.
  • Help topics — the categories users pick from, which drive routing and priority.
  • SLA plans — response and resolution targets so urgent issues are visibly urgent and nothing quietly ages out.
  • Email integration — point a support mailbox at Faveo so inbound email becomes tickets automatically and replies thread back to the requester.
  • Knowledge base — published articles so people can self-serve the common questions instead of opening a ticket.

What it gives a business

Stood up and configured, Faveo turns ad-hoc support into a process:

  • Accountability — every request has an owner and a status, so nothing disappears.
  • Prioritization — SLAs and priorities make sure the important things are handled first.
  • Self-service — a knowledge base deflects repeat questions and frees up staff.
  • Visibility — reporting shows volume, response times, and where the bottlenecks are, which is how you justify hiring or spot a recurring problem.
  • Cost — the Community Edition is open source, so you are not paying per agent per month for basic ticketing.

Running it responsibly

A helpdesk holds a surprising amount of sensitive context — internal systems, user details, and sometimes credentials people should not have pasted but did — so treat it accordingly:

  • Front it with real TLS. Replace the self-signed certificate, ideally with a reverse proxy that manages certificates for you.
  • Restrict the admin ports. Webmin, Adminer, and the web shell should not be reachable from the whole network — limit them to a management subnet or VPN.
  • Keep it patched. Both the TurnKey base and Faveo get updates; stay current.
  • Back up the database. Ticket history is institutional memory — back it up and test restores.
  • Scope agent roles. Give agents the least access they need, and plan to centralize those accounts in Active Directory over LDAP so access follows the same identity as everything else.

Wrap-up

Faveo took an afternoon to deploy and turned support from a pile of emails into something you can actually manage. For a small business it is a credible, low-cost answer to a real operational problem — and as part of the wider stack it is the place where the work of keeping everything else running gets tracked. The next step is pointing its agent logins at Active Directory so identity stays in one place.