Architecture overview

HP Insights replaces print servers with a cloud-managed service. HP runs the platform for you. Your existing printers keep working, and printing works largely the same for end users.

This document explains the architecture of HP Insights, what it is, how the pieces fit together, and where work actually happens. It is written for IT administrators, solution architects, and onboarding engineers who need a mental model of the platform before configuring it, troubleshooting it, or designing a deployment.

The big picture

At the conceptual level, HP Insights is organized in four layers, top to bottom: users and their access points, the HP Insights platform, on-premises agents, and the printer fleet.

Layer 1: Users and access points

Users access HP Insights through Print Scout, the mobile app, the User Portal, and the Admin Console. Only Print Scout requires deployment to user workstations for Secure Print Direct and Secure Print. The Portal and Console are browser-based, and the mobile app is installed on the user's device.

Access point What it's for
Desktop A Windows or macOS workstation with Print Scout installed. Users print as usual; Print Scout handles job submission and routes jobs to the appropriate destination.
Mobile The iOS and Android app for submitting print jobs and releasing them at a printer.
User portal A self-service web interface where users can release held jobs, view activity, and manage personal settings.
Web admin console A browser-based interface where administrators configure printers, manage users, and define policies.

Layer 2: The HP Insights platform

HP Insights is a collection of cloud-native services managed by HP, with no cloud servers for customers to install, patch, or maintain. The platform provides centralized administration, identity management, device management, reporting, analytics, and workflow coordination across the printing environment. When a print job is submitted, HP Insights authenticates the user, records and tracks job information, and coordinates the workflow through to release.

Identity, job processing, device management, and analytics operate as independent services, allowing the platform to scale and evolve without disrupting the overall service. HP Insights determines what should happen and when, while print capture, job delivery, and print release are performed by local components and printers.

Service What it provides
Identity & access Sign-in and authorization, integrated with your existing identity provider. Users log in with the credentials they already have, and access follows Zero Trust principles — no user or device is trusted by default. Supports SAML, OIDC, and SCIM provisioning.
Print job pipeline Receives, routes, queues, and records every print job. Applies policy rules before the job reaches the printer.
Policy & cost control Enforces print rules and quotas. Tracks spending by user, department, or cost center.
HP Insights Fleet analytics, usage reporting, and cost visibility. Available in the admin console with no additional setup.
Open APIs & integrations Connects to ITSM tools, HR systems, Microsoft Universal Print, and campus platforms.
Fleet & device management Manages the site agents on your network remotely: registration, configuration, and updates from the cloud.
Secure job storage & release The platform services that power the Secure Print workflow: holding jobs in encrypted cloud storage, confirming the user authenticated at the printer, and releasing them. Active only when Secure Print is enabled.
Cloud Connector Facilitates communication between the platform and cloud-connected devices without requiring inbound firewall rules on your network.

Layer 3: Site agents

A set of lightweight software components run within your network and connect outbound to HP Insights over HTTPS, eliminating the need to open inbound firewall ports. Once registered, these components are centrally managed by HP Insights for configuration and coordination.

Agent What it does Needed?
Print Scout Installed on each user's workstation. Captures print jobs and routes them to the printer (Secure Print Direct) or the cloud (Secure Print), and installs the centrally defined queues for the user plus the HP Secure Print app. Required for most workstation-based printing workflows. Installed on user devices that submit print jobs to HP Insights
Device Scout

Discovers and monitors printers and collects device data for analytics and reporting. For Secure Print Direct, it also discovers the printers that you then add as direct printers.

Required for Fleet Analytics, for discovering printers for Secure Print Direct, and for Secure Print deployments that use the Local Connector
Local Connector

Secures printers and provides the Secure Print services used by supported devices. Installed with Device Scout.

Optional for HP and Ricoh cloud-connected fleets; required for Secure Print on other manufacturers’ devices
HP-managed and customer-managed componentsPrint Scout and Device Scout run within your environment but are centrally registered and configured through HP Insights. The Cloud Connector and Local Connector are the same underlying service (the iMFP Site Service) deployed in different ways. When hosted by HP, it operates as the Cloud Connector and forms part of the HP Insights platform. When installed on customer-managed infrastructure, it operates as the Local Connector and resides within the customer’s network.

Layer 4: Your printer fleet

HP Insights works with a wide range of printer manufacturers. Existing printers can continue to be used, helping organizations modernize print management without replacing their hardware.

How printers connect How it works
Secure Print Direct Print Scout sends jobs directly from the workstation to the printer using standard printing protocols. The document remains on the local network and does not pass through HP Insights.
Secure Print Users submit jobs to a secure queue and release them after authenticating at a printer. Depending on the deployment configuration, jobs may be stored in encrypted cloud storage or on the user's workstation until release.

Coordination vs. execution

A key architectural principle of HP Insights is the separation of coordination and execution.

HP Insights coordinates printing by managing identity, configuration, policies, workflow decisions, and reporting. The actual handling of documents occurs within the customer environment, where components such as Print Scout, Device Scout, Local Connectors, and printers perform the work required to capture, store, deliver, and release print jobs.

How this separation works depends on the print workflow being used. In Secure Print Direct, documents are delivered directly from the workstation to the printer. In Secure Print, documents are securely stored until the user authenticates and releases them. In both cases, HP Insights provides centralized coordination and management while local components execute the workflow.

What the cloud handles

  • Identity and authentication
  • Job routing and policy
  • Secure job storage (Secure Print)
  • Queue definition and configuration (centrally managed)
  • Audit and analytics

What happens on your network

  • Job capture and submission (Print Scout)
  • Queue installation and updates (Print Scout)
  • Direct delivery to the printer (Secure Print Direct)
  • Job release and output (Secure Print)
  • Device discovery and monitoring (Device Scout)

Key architectural differences

  • Secure Print Direct: Print Scout sends jobs directly to the printer. The cloud provisions and manages printing but is not in the document data path.

  • Secure Print: Jobs are uploaded to encrypted cloud storage and remain there until the user authenticates and releases them at a printer.

  • Data flow differs between modes: Secure Print Direct delivers jobs directly to printers, while Secure Print stores and manages jobs through cloud services before release.

Print flows

Secure Print Direct

  1. The user prints from their workstation.
  2. Print Scout sends the job directly to the printer.
  3. The printer outputs the job; the cloud records the event.

Secure Print

  1. The user prints from a workstation or mobile device.
  2. The document is uploaded to encrypted cloud storage and held for release.
  3. The user authenticates at a printer (badge, PIN, QR, or embedded app).
  4. The job is released and printed.