Send the job once.
Submit PDF, RAW content, or a secure URI. A unique key makes retries safe when a response gets lost on the network.
Idempotency guide →How it works
From your app to the right printer—without the guesswork.
One API connects your workflow to printers at every site. Piqae manages the journey, the local agent works with installed drivers, and your application gets clear status back.
live workflow Agent online
01 Application PDF or RAW
02 Piqae API Idempotent request
03 Durable queue Lease + recovery
04 Native agent Local handoff
05 OS spooler Accepted ≠ printed
Keep it moving safely.
Piqae stores the job before routing it to an eligible printer and agent, so a brief outage does not mean starting the workflow again.
Job API →Reach the printer’s network.
A securely enrolled native agent receives the job and saves it locally before taking responsibility for the final handoff.
Node enrolment →Keep every local capability.
Piqae reads printer options from Windows or CUPS. PDF follows the native print path, while RAW bytes reach the driver unchanged.
Printer capabilities →Recover with context.
After a restart, the agent checks its local queue against the operating system. If it cannot prove a retry is safe, it asks for attention instead of risking a duplicate.
Job statuses →Status semantics 01 02 03 04 05
A useful answer at every stage.
Queued
The control plane has durably accepted the job and its idempotency key.
Dispatched
A lease has been offered to an eligible enrolled agent.
Accepted
The agent durably owns the job or the OS spooler has accepted the handoff.
Uncertain
The system cannot safely prove the final result after a boundary failure.
Failed
A terminal, explainable failure occurred and can be acted on explicitly.
Physical delivery boundary. “Accepted by spooler” means the operating system accepted the handoff. It does not prove
paper moved, ink landed, or a person received the output.
Deployment topologies Cloud Self-hosted Local-only
The same simple model, wherever you run it.
Your app → Piqae Cloud → agent → OS Managed control plane and billing, with the native execution boundary on your network.
Your app → your Piqae stack → agent → OS Operate the control plane and storage yourself under the Apache-2.0 licence.
Your app → local agent → OS Keep the workflow inside a trusted network when cloud coordination is unnecessary.