notsoPRINT

The printer is on a desk. Your code is in a datacentre.

Warehouse printers sit on private networks behind consumer routers. The usual answers are a VPN somebody has to maintain, a port forwarded on a customer's firewall, or a person walking to a PC to download a PDF and press print.

The usual way

notsoPRINT

A VPN or a forwarded port. Someone technical sets it up, and every printer stops when the tunnel drops.

The PC dials out. Nothing is opened on the customer's network.

Someone types the printer name. One character wrong and jobs vanish silently.

The PC reports the printers it has. You pick one from a list.

"Printed" means the spooler took it. Out of paper still counts as success.

A job is successful when the printer finished it. Otherwise you get the reason.

The PC was asleep, so the job is gone.

The job waits and prints when the PC comes back.

Three steps, once per PC.

After this, printing is one API call and nobody touches the warehouse PC again.

Step 1

Install the agent

Run the installer on the PC the printers are attached to. It needs nothing else installed first.

Step 2

Paste a pairing code

Get a code from your account, type it into the installer. That is the whole setup.

Step 3

Send print jobs

The printers appear in your account with an id. Post a PDF to that id and it prints.

Built for the ways printing actually fails.

Nothing opens on their network

The agent makes an outbound connection and keeps it. There is no inbound port, no VPN, and nothing for a customer's IT to approve.

Jobs survive a dead PC

A job is stored the moment it is accepted. If the PC is off it waits, and prints when the agent reconnects.

Honest outcomes

The agent watches the print queue, so out of paper, offline and jammed come back as failures with a reason, not as success.

Runs as a service

It starts with Windows, survives a reboot and a logout, and restarts itself if it stops. Nobody needs to leave a window open.

Your server can't reach the warehouse printer.