Downloads

The software to try out and the language packs for the interface – all in one place.

30 days of testing. No restrictions.

The demo includes the full Professional feature set. After 30 days you decide whether to buy a license – your data is preserved. The demo becomes the full version with your license key, no reinstall required.

Both packages contain the same software – just pick your target system.

For automatic HTTPS on a public domain the ticket system needs ports 80 and 443 – they cannot be replaced by a different port, this is dictated by the Let’s Encrypt certificate procedure. If they are already taken on your server, for example by a running web server, you have two options: stop or remove that program first, or install the ticket system on a different server. A port of your own choosing is only an option if you run without automatic HTTPS. The installer checks the ports before installing and names the program that is holding them.

Installing on Windows

About 6 minutes, subtitles in English.

Installing on Linux

About 5 minutes, subtitles in English.

Ready in 3 steps

Download

Download and unpack the demo package.

Install

Start with Docker Compose – the included guide walks you through it.

Get going

Create a team, connect a mailbox, create your first ticket.

Important commands (Linux)

Ready to copy. Everything with sudo – installer and containers need root.

Install the prerequisite

sudo apt install -y unzip

Without unzip the installer cannot unpack the package.

Install the ticket system

curl -fsSL https://files.smitey.eu/download/get-smitey.sh | sudo bash

Downloads the package and walks you through the questions. Running it again is safe: configuration and data are kept.

Check HTTPS

sudo /opt/smitey/smitey-install check-https

Only with a public domain. Tells you whether the certificate is there – and if not, the reason from the log. The certificate can still arrive minutes after the installation.

Look up the first login

sudo cat /opt/smitey/SMITEY-credentials.txt

After the first login change the password and delete the file.

Are the containers running?

sudo podman ps

Shows every part of the system with its state.

Follow the log

sudo podman logs -f container-backend-1

Shows live what the backend reports. Stop with Ctrl+C.

Check the supervisor

systemctl status smitey-supervisor

This service keeps the system running and applies updates you trigger inside the application.

Create a support bundle

sudo /opt/smitey/install.sh --support-bundle

Collects logs and system state into one zip file. Passwords and keys are removed.

Change the public address

sudo /opt/smitey/install.sh --reconfigure

Sets a new domain and restarts, so the certificate is requested for the new name.

Remove it

sudo /opt/smitey/install.sh --uninstall

Asks about data and about Podman separately – nothing is deleted without asking.

Backups are handled by /opt/smitey/Backup/TicketSystemBackup (list, backup, restore); the daily backup runs on its own. Details are in /opt/smitey/docs/en/BACKUP-RESTORE.txt.

System requirements

Linux: Ubuntu 24.04 or 26.04 LTS – those are the tested releases. Other distributions with Podman 4.1 or newer, systemd and apt should work, but are untested
Windows 11 Professional (tested) – Windows Server 2022 or newer should work (that is where WSL2 arrived), but is untested
Not recommended: Windows 10. It works (tested from 21H2 on), but has received no security updates since 14 October 2025 – the wrong foundation for a system holding customer data
x86_64/amd64 only – ARM systems such as a Raspberry Pi or an ARM VPS will not work
The PostgreSQL database and the container runtime ship with the package; the installer sets both up
Linux: at least 2 CPU cores and 2 GB RAM, 4 cores and 4 GB recommended
Windows: at least 4 CPU cores and 8 GB RAM, 6 cores and 16 GB recommended – on Windows the stack runs inside its own virtual machine (WSL2) that shares memory and cores with Windows
One free network port: the HTTP port you choose (8088 by default) or 80 – on port 80 you can also reach the system directly by IP address
Automatic HTTPS (Let’s Encrypt) needs a public domain and ports 80 and 443 reachable from the internet – port 80 permanently, not just during installation, because the certificate is renewed every 60 days. On your own network without a public domain, HTTPS works with a certificate of your own; the installation ships with instructions for it
Modern browsers: Chrome, Edge, Firefox, Safari

Network & ports

The ticket system runs on your own server. For every feature to work, your firewall has to allow these connections – on a VPS that includes your hosting provider’s firewall, not just the one on the server.

Inbound (to your server)

Inbound · allowTCP 8088 (or whichever HTTP port you choose)Access to the ticket system on your local network.
Inbound · allowTCP 80 and 443Only for automatic HTTPS. Port 80 has to stay open permanently, not just during installation: Let’s Encrypt renews the certificate through it every 60 days.
Inbound · allowTCP 22 (SSH)Only for your own administration on Linux. The ticket system itself does not need it.
Inbound · denyTCP 5432 (PostgreSQL)The database runs on the container network and never needs to be reachable from outside.

Outbound (from your server to the internet)

Outbound · allowUDP/TCP 53 (DNS), UDP 123 (NTP)Name resolution and an accurate clock. A clock that is off makes TLS connections fail.
Outbound · allowTCP 443 (HTTPS)Installation, updates and the licence check.
Outbound · allowTCP 587 or 465 (SMTP)Sending e-mail: notifications, invitations, password resets. Your e-mail provider decides which of the two applies.
Outbound · allowTCP 993 (IMAP)Fetching e-mail, if incoming messages should turn into tickets automatically.
Outbound · denyTCP 25 (SMTP)Not needed – sending goes through 587 or 465. Leave it blocked: port 25 is how a compromised server would send spam.

Important if you want to use e-mail: many hosting providers block outbound mail traffic (ports 25, 465 and 587) in their default firewall – at netcup the rule is called “Mail block”. The symptom is unmistakable: fetching works, sending runs into a timeout. That block sits with your provider, not on your server, and can only be lifted in their control panel. You do not need port 25 for this – leave it blocked.

Connecting a mailbox: which providers work directly, and what Microsoft 365 needs →

Language packs

Every installation starts in English. A language pack is a JSON file with the translated interface texts – download, import, done. Your own content such as tickets, teams or categories is not affected.

Bulgarian
Updated: 2026-08-30 · JSON
Download
Chinese
Updated: 2026-09-01 · JSON
Download
Croatian
Updated: 2026-09-01 · JSON
Download
Czech
Updated: 2026-09-01 · JSON
Download
Danish
Updated: 2026-09-01 · JSON
Download
Dutch
Updated: 2026-09-02 · JSON
Download
Finnish
Updated: 2026-09-02 · JSON
Download
French
Updated: 2026-09-02 · JSON
Download
German
Updated: 2026-08-30 · JSON
Download
Greek
Updated: 2026-09-02 · JSON
Download
Hungarian
Updated: 2026-09-03 · JSON
Download
Indonesian
Updated: 2026-09-03 · JSON
Download
Italian
Updated: 2026-09-03 · JSON
Download
Japanese
Updated: 2026-09-03 · JSON
Download

Missing your language?

More language packs are on the way. Tell us which language you need – and if you want to translate yourself: the ticket system exports the complete text list as JSON, you fill in the entries in your language and import the file again.

How to import a language pack

Download the file
Download the language pack above and save it as a JSON file – do not unpack, rename or edit it.
Sign in as an administrator
Sign in to the ticket system as an administrator and open Settings → Language.
Import
Choose “Import” there and upload the downloaded file. After the import, the system shows how many entries were applied.
Enable the language
Enable the new language. From then on, every user picks their own language in their personal menu, and each team can have a default language.

Does the pack match my version?

Yes. Language packs are not tied to a specific version: entries your installation does not know are simply skipped by the import. Features newer than the pack show English until the next pack. The import can be repeated at any time.

Note: the import overwrites existing translations with the pack contents. If you have customized texts yourself, export your current state as a backup first.