Piqae combines an Apache-2.0 edge, managed durable queue, completion-based usage, and a self-hosted exit. PrintNode remains the more established service with mature desktop coverage.
Last verified 30 July 2026 · Official source
| Area | Piqae | PrintNode |
|---|---|---|
| Source model | Apache-2.0 node, control plane, web app, and SDK | Proprietary service and clients |
| Deployment | Managed Cloud, complete self-hosting, or local-only | PrintNode Cloud or contact-sales Standalone Server, with local clients |
| Local software | Native Rust agent with thin OS shells | Desktop client and service options vary by OS |
| Formats | PDF and RAW in the tested V1 envelope | PDF and RAW, plus documented platform behaviours |
| Driver options | Installed OS drivers remain authoritative | Client exposes documented printer capabilities |
| Status position | Accepted, reported complete, and uncertain remain distinct | Documented print-job states through the hosted API |
| Billable unit | One job reported complete by the node; jobs that remain failed, jammed, blocked, cancelled, or uncertain do not count | One API print request, regardless of number of pages or print outcome |
| Product embedding | Platform accounts, workspace isolation, open edge, and custom distribution path | Branding and account-provisioning APIs are documented |
| Migration API | Tested subset for computers, printers, jobs, states, whoami, ping, noop | Original API surface |
| Availability posture | 99.95% architecture design target; no contractual beta SLA | Established hosted production service |
| Current native release | Signed and notarised macOS preview; Windows remains behind release gates | Mature signed desktop clients |
PrintNode facts: features, Standalone Server FAQ, downloads, and API documentation. Piqae status comes from the repository support matrix. Checked 30 July 2026.
Piqae Pro lists at $9 per month for 25,000 reported-complete jobs and up to 25 nodes. PrintNode Standard lists at $29 per month for 25,000 API print requests and five computers. PrintNode says a request counts as a print regardless of its outcome.
| Example tier | Piqae displayed price | PrintNode public price |
|---|---|---|
| Free | Free · $0 · 100 reported-complete jobs · 1 node | Lite · $0 · 50 API print requests · 1 computer |
| Pro | Pro · $9 · 25,000 reported-complete jobs · 25 nodes | Standard · $29 · 25k API print requests · 5 computers |
PrintNode USD list prices from its pricing page, checked 30 July 2026. PrintNode defines a print as one API print request regardless of pages or outcome. Taxes, negotiated terms, and overages can change the result. Piqae values come from server catalog 2026-07-30; checkout must match that catalog.
“Reported complete” is the strongest completion signal returned by the node, operating system, driver, or printer. It is the Piqae billable event, but it is not proof that ink physically reached paper when the hardware cannot provide that evidence. A blocked or jammed job that later recovers and reaches reported complete does count.
Piqae Cloud is the low-operations path: we run the control plane, durable document storage, queue recovery, monitoring, backups, and upgrades. The Apache-2.0 node remains auditable and can be adapted for a product-specific distribution, subject to licence, trademark, signing, and update-policy requirements.
Self-hosting keeps the complete printing model, but your team becomes responsible for database and object-store durability, monitoring, backups, failover, and upgrades.
The macOS package is signed and notarised but remains preview support. Windows packaging and physical certification remain behind checked-in release gates. Use controlled canaries until the platform and printer combination you depend on is certified.
Piqae covers the documented migration-critical subset, so supported integrations can change the base URL and credential rather than rewrite their print path. Scales, PrintNode billing APIs, and every historical response quirk are not claimed as compatible.