From the cloud to the right printer. No manual hand-offs.

It is the desktop agent that securely connects Nebulas Cloud Printing to print queues installed on a local workstation.

No. Native packages include the Java 17 runtime required by the application.

No. The client starts outbound HTTPS connections to the Print Gateway and needs no inbound cloud connection to the LAN.

The current version processes PDF documents and sends each job to the local queue selected by the business application.

The client pauses its loop, applies controlled retries and resumes automatically when the service is reachable.

In the Nebulas Portal, assign two or more clients to one group and set their priority; the lower number is preferred. The gateway gives jobs to one leader, and an eligible standby takes over automatically when that leader is unavailable.

If a client stops while downloading, the job returns to pending when its recovery lease expires. After submission to the spooler, an uncertain result becomes DELIVERY_UNKNOWN and is not automatically reprinted, avoiding possible duplicates.

Yes. Device grants are checked periodically and can be centrally revoked; revocation stops polling and heartbeat activity.

For the first version, configure one operating-system queue for each required combination and route the job to that exact queue.