Label design and printing software for Linux and Unix
Native Linux/Unix application: full editor, printing through CUPS or native printer languages, database connectivity and a print connector that runs as a systemd service or daemon — for plants and servers that do not run Windows.
Plants that standardized on Linux for their line PCs, servers and kiosks usually have one exception forced on them: the label software. EtikStudio removes it. The Linux edition is a native application with the same editor as Windows and Mac, prints through CUPS or straight in the printer's language, reads your databases and runs the print connector as a headless service — ideal for print servers, industrial PCs and container hosts.
What the Linux / Unix edition includes
| Capability | Available | Notes |
|---|---|---|
| Full label editor | Yes | GTK desktop application; same templates as every other platform. |
| Printing via CUPS | Yes | Any CUPS queue, local or remote. |
| Native printer languages | Yes | Direct to USB or network printers; no driver required. |
| Queue manager and load balancing | Yes | |
| Database connectivity | Yes | unixODBC to PostgreSQL, MySQL/MariaDB, SQL Server, Oracle, DB2; CSV. |
| Print connector | Yes | systemd service on Linux; daemon on Unix. Runs headless. |
| Private cloud storage | Yes | |
| Offline mode | Yes |
Supported systems
Linux: current Ubuntu, Debian, RHEL/Rocky/AlmaLinux and SUSE releases on x86-64; ARM64 on request. Unix: FreeBSD and Solaris/illumos; AIX on request. The connector is the component most often deployed on Unix, since it needs no desktop session — it shares the printers attached to that host with the rest of the organization.
Typical setups
- Print server: the connector on a Linux server next to the ERP, receiving jobs from SAP, Odoo or a watched folder and printing on the plant's printers.
- Line kiosk: the editor on an industrial Linux PC with a touch screen, printing container labels from the MES database.
- Legacy Unix host: the connector on the AS/400-adjacent Unix box that already talks to the old printers.
Problems it solves on Linux and Unix
- No vendor drivers: most thermal printer manufacturers do not ship Linux drivers. Native printer languages make the driver unnecessary.
- Headless servers: the connector runs as a systemd service or daemon on a machine with no desktop, next to the ERP or the MES.
- Mixed fleets: one Linux print server can drive Zebra, SATO and TSC printers of different resolutions from the same templates.
- Scripting: watched folders and the REST API let cron jobs, shell scripts and Python print labels without a GUI.
Printers and connections on Linux / Unix
Any CUPS queue — local, IPP or remote — prints through CUPS. Thermal printers connect over USB or TCP/IP and receive native ZPL, TSPL, SBPL, DPL, IPL, CPCL, TPCL or ESC/POS directly, which is the recommended path on Linux: no driver to find, no bitmap rendering, exact barcodes. Serial connections are supported for older industrial units.
Compared with the usual alternatives
| Alternative | What you get | With EtikStudio |
|---|---|---|
| Hand-written ZPL in scripts | Works until the printer brand or the label changes; no preview, no design tool. | Visual design, any brand, and the same script keeps calling the API or dropping files. |
| Windows print server for a Linux plant | One more OS to license, patch and secure. | Everything stays on Linux, including the print service. |
| Generic CUPS filters | Raster output; barcodes lose module accuracy. | Native language output with exact modules. |
Frequently asked questions
Is there a graphical editor on Linux or only the service?
Both. The full GTK editor for design stations and the headless connector for servers.
Which distributions are supported?
Current Ubuntu, Debian, RHEL/Rocky/AlmaLinux and SUSE on x86-64; ARM64 on request.
Does it run on FreeBSD, Solaris or AIX?
FreeBSD and Solaris/illumos are supported; AIX is available on request depending on the environment.
Can it run in a container?
The connector can run headless in a container with access to the printer network; ask for the deployment guide.
How do my scripts trigger a label?
Drop a CSV, JSON or XML into a watched folder, or call the REST API; both return job status you can log.