Inventory
Record the endpoints, credential scopes, printers, formats, options, status dependencies, and retry policy your current integration actually uses.
PrintNode migration
Keep the request shape. Change who owns the print path.
For the documented compatibility subset, move by changing the base URL and API key—not by rebuilding your integration. Then canary real printer profiles before moving production traffic to Piqae’s managed durable queue.
Compatibility envelope
| Surface | V1 posture | Migration action |
|---|---|---|
| Computers / nodes | Compatible V1 subset | Map identity and online semantics |
| Printers | Compatible V1 subset | Resolve IDs from enrolled Piqae nodes |
| Print jobs | Compatible V1 subset | Keep supported request shapes and test state fixtures |
| whoami, ping, noop | Covered subset | Run client health checks |
| Scales | Not claimed | Keep existing path or build separately |
| Integrator subaccount APIs | Not wire-compatible | Map to Piqae platform customers and service accounts |
| Historical response quirks | Not universally replicated | Fixture-test your exact client |
Scope reflects the checked-in V1 execution ledger. PrintNode’s original API is documented at printnode.com. Verified 30 July 2026.
Migration runbook 01 02 03 04 05 06
Map
Keep compatible request shapes, change the base URL and key, then map only the behaviours outside Piqae’s documented subset.
Prepare
Enrol a Piqae node, resolve its printer and profile IDs, create a scoped key, and define success and rollback thresholds.
Canary
Route a bounded, non-critical job set. Compare API responses, native queue results, webhooks, and operational recovery.
Expand
Increase traffic in stages while preserving the old base URL and credentials for immediate rollback.
Close
Retire the prior path only after a complete operating cycle, incident drill, and evidence review.
Rollback contract
Define “stop” before the canary begins.
- Keep the prior base URL and credentials available during the migration window.
- Stop expansion on duplicate risk, unexplained uncertainty, or unsupported driver options.
- Never automatically reprint an ambiguous job while rolling traffic back.
- Record the final disposition of every canary job across both systems.
Only reported-complete jobs count.
Jobs that remain failed, jammed, blocked, cancelled, expired, or delivery-uncertain do not consume Piqae usage. A recovered job counts only if it reaches reported complete, which remains a device or OS signal—not physical proof.
Offline nodes can receive the job later.
The managed queue retains durable work for reconnection while the local node maintains its own durable handoff state. Self-hosters keep the model and operate its availability.
The new edge is Apache-2.0.
Audit it, adapt it, or preserve a self-hosted exit. Product-specific distribution remains subject to code-signing, update-policy, licence, and trademark requirements.