What it is
RocketPrint Station signs in to your account, reports every printer that computer can see, and keeps one encrypted connection open to us. Jobs arrive down that connection, and results go back up it.
- Runs as a normal desktop app with a menu-bar or tray icon.
- Needs nothing to connect in — no port forwarding and no VPN.
- Prints only jobs for the printers it reported, on the account it signed in to.
- Keeps its own record of finished jobs so a redelivered job is never printed twice.
Installing
Install it on a machine that already prints to the printers you care about, and that stays awake during your working hours. One agent covers every queue that machine can see — you do not need one per printer.
- macOS — install the
.dmg, then open RocketPrint Station from Applications. - Windows — run the
.exeinstaller, then launch it from the Start menu. - Linux — mark the
.AppImageexecutable and run it.
On first launch it asks for your RocketPrint email and password. Sign in and the station registers itself to your organization, then reports its printers within a few seconds.
Platform support and the current signing status are on the download page.
How it authenticates
You sign in inside the app with your RocketPrint account. It receives a token and presents it when it opens its connection — authentication happens at the connection upgrade, before any job is routed. There is no API key to copy onto the machine, which means a compromised workstation does not hand someone your backend credential.
How printers register
On connect, and periodically afterwards, the app lists the operating system's print queues and reports them. Each queue becomes a printer with a stable ID scoped to your organization, keyed on the station and the OS queue name.
- Rename a printer and its ID stays the same — safe to store in your database.
- A printer shows as
offlinewhen the app disconnects. - Jobs for an offline printer wait rather than fail, and print when it reconnects.
How it prints
For raw_base64, the app writes your decoded bytes straight to the print queue with no driver rendering — that is how ZPL keeps its fidelity. For pdf_base64 and text, the job goes through the station's own print system using whatever driver is installed.
It then reports the outcome: printing when the OS accepts the job, then completed or failed with the reason.
Troubleshooting
| Symptom | Likely cause and fix |
|---|---|
| A printer is missing | The station's OS cannot see it either. Print a test page locally first, then restart the app to make it check again. |
| The computer shows offline | Computer asleep, or outgoing HTTPS blocked. The app reconnects on its own and queued jobs print automatically. |
Jobs stuck at pending | That computer has not reconnected yet. This is the queue working as intended. |
| A PDF printed oddly on Windows | Windows document printing uses the file's document association today, which the installed viewer controls. Raw label printing is unaffected — it goes to the spooler directly. |
| Job failed with a queue error | The print queue is paused or the printer is unreachable from the station. The job carries the exact message the print system returned. |
Multiple stations and locations
Install an agent per location, all signed in to the same organization. Every printer across every site appears in one console and one API, distinguished by printer ID and station. Adding a warehouse is an install plus a row in whatever map you keep between your locations and printer IDs.
Install it on one bench.
Five minutes, and its printers appear as soon as it connects.
Download RocketPrint Station