Architecture and delivery options in PaperCut Hive

PaperCut Hive offers several key architectural components to control how print jobs are stored, routed, and delivered across an organization. Unlike traditional on-premises solutions that rely on local print servers, PaperCut Hive is a cloud-native platform that eliminates the need for dedicated print server infrastructure by using an intelligent Edge Mesh.

Understanding how to use Super Nodes, Print Delivery Profiles, the Cloud Node, and Cloud Pull Delivery helps optimize print reliability, simplify network configurations, and scale effectively across different office environments.

Super Nodes

Super Nodes provide a dedicated local anchor to maintain print job availability on-premises. ASuper Node is a standard edge node (such as a desktop PC or laptop) promoted by an administrator because the host machine is almost always switched on and accessible on the local network. As part of the Edge Mesh, the Super Node receives preferential replication of all print jobs so that print jobs remain available for release even if user laptops disconnect.

Primary use cases

• Small sites and highly mobile environments: In branch offices where users frequently close their laptops or leave the office, a Super Node ensures print jobs stay available on-premises for release.
• Local iOS printing: iOS print profiles route print submissions directly to IP addresses. A Super Node acts as the local anchor for iOS submissions. (Note: Enabling the Cloud Node is an alternative to using Super Nodes for iOS printing).
• Specific embedded MFDs: Certain printer embedded applications rely on an active, online edge node with line-of-sight to the printer to handle functions like swipe-card authentication, access control, and native tracking.

Pros and cons

• Pros: Keeps print data and job replication local to your on-premises network without requiring cloud job storage.
• Cons: Requires a dedicated machine that is kept powered on and awake.

Best practices

• Static IP address: Always assign a static IP address to the Super Node when using it for iOS printing so that mobile print profiles do not lose connectivity.
• Power management: Configure the host machine’s power settings to ensure the machine does not enter sleep or hibernation mode.

Print Delivery Profiles

Print Delivery Profiles give administrators explicit, deterministic control over the route a print job takes to the physical printer.Print Delivery Profiles bypass automatedAutopilot routing.

Primary use cases

• Segmented networks and subnets: Environments with separate VLANs, isolated subnets, or routing restrictions where workstations cannot communicate directly with printer subnets.
• Multi-site deployments: Prevent print traffic from crossing slow WAN connections by binding specific printers to local subnet gateways or specific edge nodes.
• Specific embedded devices: Ensure reliable delivery for device brands (such as Konica Minolta, Xerox, Toshiba, or Fujifilm) that have inbound connection dependencies.

Pros and cons

• Pros: Provides predictable delivery paths and simplifies troubleshooting in complex, segmented enterprise environments.
• Cons: Requires manual administrative configuration per printer or network profile compared to automated Autopilot routing.

Best practices

• Inbound dependency printers: For devices that require direct local inbound connections, configure a Print Delivery Profile without Autopilot fallback.
• Edge node redundancy: Assign reliable, always-on edge nodes within the profile to ensure uninterrupted job release.

Cloud Node

The Cloud Node extends printing capability beyond physical network boundaries. TheCloud Node is an optional PaperCut-hosted edge node that integrates directly into your Edge Mesh to enable off-network, remote, and cross-site printing.

Primary use cases

• Remote and hybrid workers: Users can send print jobs from home, guest Wi-Fi, or cellular connections to the Cloud Node and release them securely when arriving at the office.
• Cross-site printing (Find-Me Roaming): Allows users to submit a job at one site and release the job at another without needing site-to-site WAN connectivity.

Pros and cons

• Pros: Extends printing beyond physical network boundaries and provides redundant cloud replication for environments with low edge-node density.
• Cons: Print job contents leave the local network. While print data is securely encrypted in transit and at rest and automatically purged upon release or timeout, organizations bound by strict data residency laws might require the Cloud Node to remain disabled (for more information, seePrint job data that gets uploaded to the cloud). Note that even with the Cloud Node disabled, non-content print metadata—such as job names and usernames—is still processed by PaperCut Cloud Services (for more information, seeSecurity considerations). The Cloud Node enforces a 200 MB per-job size limit.

Replication behavior and local dependencies

• Local edge node requirement (Standard Printing): When using standard push printing via the Cloud Node, at least one local edge node must remain online on the printer’s network to pull the job from the cloud and deliver the job locally to the printer.
• Replication logic:
  • 2 or more local edge nodes online: The job replicates locally across the Edge Mesh and does not travel to the Cloud Node (when printing from within the local network).
  • 1 local edge node online: The job is retained locally and replicated to the Cloud Node for redundancy.
  • 0 local edge nodes online: Local replication does not occur; the job is sent directly to the Cloud Node.

Cloud Pull Print Delivery

Cloud Pull Print Delivery allows supported Multifunction Devices (MFDs) to retrieve print jobs directly without local server infrastructure.Pull Delivery (available under the Printer pulls job delivery method) is an infrastructureless delivery option where supported MFDs running the Full Embedded app retrieve print jobs directly from the Cloud Node at release time.

Primary use cases

• Infrastructureless deployments: Eliminates the requirement for dedicated print servers, local gateway appliances, or always-on local edge nodes.
• Segmented and Zero Trust networks: Printers securely download jobs directly from the Cloud Node over an outbound HTTPS connection (Port 443), removing the need for direct client-to-printer network routes or plain-text RAW 9100 communication.

Pros and cons

• Pros: Decouples print delivery from local client availability and secures print traffic using end-to-end HTTPS.
• Cons: Requires the Cloud Node to be enabled and depends on supported printer hardware running the latest Full Embedded app.

Prerequisites and brand compatibility

• Enable Cloud Node: In the PaperCut Hive admin console, select Manage > Edge Mesh, then enable the Cloud Node. Note that replication of all jobs to the Cloud Node can take up to 12 hours after enabling.
• Embedded app: Ensure the latest version of the Full Embedded app is installed on the MFD.
• Supported brands: Pull Delivery rollout is actively expanding. To check the latest list of supported printer manufacturers and rollout phases, visit thePaperCut Percolator Pull Delivery page (external site).

Architectural Decision Summary