What should count toward the bill?
Piqae counts a job only when the node reports it complete. Jobs that remain failed, jammed, blocked, cancelled, or uncertain do not count; PrintNode says each API print request counts regardless of outcome.
PrintNode alternative
Remote printing that is easier to adopt—and easier to leave.
Piqae offers a familiar API, lower list pricing, an Apache-2.0 edge, and a managed durable Cloud queue. Use the Cloud without giving up a self-hosted exit or the ability to adapt the node for your own product.
Five deciding questions 01 02 03 04 05
Do you need to inspect or modify the edge?
Piqae’s durable node and native boundaries are Apache-2.0, enabling audit and product-specific distributions subject to signing and trademark requirements.
Who should operate queue durability?
Piqae Cloud operates storage, queue recovery, monitoring, backups, and upgrades. Self-hosters keep every core feature and own that operational work themselves.
Are you serving many customer tenants?
Platform accounts and workspace boundaries let one integration manage customer printers and jobs without mixing operating contexts.
Do you need an established client fleet today?
PrintNode is the more mature service and now offers a contact-sales Standalone Server. Keep it where that history or unsupported API behaviour outweighs Piqae’s cost and control benefits.
- You want the managed queue without a closed-source edge.
- Lower list pricing and reported-complete usage improve your economics.
- Your product needs tenant-scoped printers, profiles, jobs, keys, and webhooks.
- A credible self-hosted or custom-distribution path matters.
- You need generally available signed clients before Piqae passes its gates.
- Your workflow relies on PrintNode scales or unsupported API quirks.
- Its contact-sales Standalone Server already satisfies your deployment requirement.
- The migration effort is larger than the operating or commercial benefit.
PrintNode product details were checked against official features and pricing, plus its Standalone Server FAQ, on 30 July 2026.
Reported completion is Piqae’s strongest available OS, driver, or device signal; it does not
prove ink reached paper when the hardware cannot report that evidence.
Start with one endpoint, then move the fleet.
The documented compatibility subset is designed to make the first change as small as a base URL and credential. Inventory your actual endpoints and driver dependencies, then use a virtual printer or explicitly authorised canary hardware before expanding.