CloudPrint is a free PrintNode alternative when you integrate API printing for your own account and printers. It is not a drop-in endpoint replacement, and SaaS integrations that operate customer accounts use a commercial B2B agreement. Compare deployment, API ownership, printer mapping, formats and statuses before moving one controlled workflow at a time.
## Start free with your own account Create a CloudPrint account, connect its agents and printers, and use same-account API credentials without a consumer subscription or paid printing plan. This free model covers printing for your own account. If your product connects or manages printing for customer accounts, review the Developer Platform terms for production access. ## Compare the operating model first CloudPrint uses a local agent at each printing environment and a server-side Public API. Your backend owns authentication, routing, idempotency and status handling. Review the current CloudPrint pricing and agent downloads alongside your existing PrintNode plan, operating systems and support requirements before estimating a migration. ## Inventory the current integration List every location, computer, printer, document type, print option and failure path used with PrintNode. Record where IDs are stored, how offline devices are handled and whether retries can create duplicates. This becomes the acceptance checklist for CloudPrint. ## Map PrintNode concepts to CloudPrint A PrintNode computer maps operationally to a CloudPrint agent installation, but identifiers are not portable. A PrintNode printer becomes a newly discovered CloudPrint `printer_id`; a print job becomes a prepared document plus a CloudPrint print job. Connect each agent, inspect printer capabilities and let an administrator confirm every new assignment. ## Rebuild the API boundary Obtain an OAuth2 Client Credentials token, call `GET /api/v1/printers`, upload a PDF or RAW document, create the job and persist `print_job_id`. Keep the client secret on the backend. Treat `printed`, `failed` and `cancelled` as terminal outcomes instead of translating provider-specific states by name. ## Change authentication and retries Use OAuth2 Client Credentials with minimal scopes and keep the secret in your backend. Add one stable `Idempotency-Key` per business print operation. After a timeout, recover or repeat the same request instead of creating an unrelated second job. ## Validate formats and printer capabilities Test every production combination of PDF or RAW language, media, DPI, copies and printer queue. A ZPL route needs a printer advertising ZPL and RAW passthrough; a PDF route needs system printing or a supported renderer. Do not infer compatibility from the printer model name. ## Run a representative pilot Choose one location, one printer model and one important document. Compare page size, copies, label alignment, time to terminal status and behavior when the agent or printer goes offline. Include operator training and support identifiers in the pilot, not only a successful test page. The staged CARRO.Business rollout shows the same low-risk migration pattern. ## Cut over without double sending Keep a rollback window, but route each business operation to exactly one provider. Monitor failure rate, time to print and manual reprints. Once the CloudPrint path is stable, revoke old credentials, remove unused clients and delete dual-provider branches that could send the same document twice. ## Common questions ### Is CloudPrint a free PrintNode alternative? Yes, for API printing through your own CloudPrint account and its printers. A B2B agreement is required when your product connects or manages customer accounts. ### Is CloudPrint a drop-in replacement for PrintNode? No. The business outcome is similar, but authentication, identifiers, endpoints, capabilities and statuses must be mapped explicitly. ### Can the migration run gradually? Yes. Pilot one location or document type, keep a tested rollback path and ensure each business operation is routed to only one provider. ### Can CloudPrint print PDF and ZPL? CloudPrint accepts ready-to-print PDF and explicit RAW formats such as ZPL when the selected printer advertises a compatible route. ### How should we compare pricing? Compare the current vendor plan with CloudPrint's published account and B2B models, then include migration, support and operational requirements in the decision. ### What prevents duplicate prints during cutover? Use a stable `Idempotency-Key` for retries and a single routing decision per business operation. A deliberate reprint receives a new key and an audit reason. ## Next steps