System Requirements

Document Workflows

Zebraworks Bridge for the

Outlook add-in and Mobile App

ScanQ, MailQ, PrintQ, CostQ

These nQzw applications can run on-premise or in a virtual private cloud, optionally working with the nQzw Outlook Add-in and/or Mobile App via the Zebraworks bridge to the cloud.

Identity Provider

  • On-premises Active Directory
  • Hybrid Azure Active Directory
  • Azure Active Directory Domain Services (AD DS) within an Azure Virtual Network


Recommend using https with a trusted SSL certificate; http optional

Database Server

  • MS SQL 2016+
  • Workgroup, Standard or Enterprise Editions
  • SQL Express may be used in small installations, please discuss with your implementation consultant

Application Servers

Your implementation consultant will review specific requirements based on your expected usage and environment.

Operating System

Windows Server 2022 / 2019 / 2016

Utility Application Server 
For backend application services
  • 2xCPU Cores (2.6GHz+), 4GB RAM
  • C: drive for Windows
  • D: (100GB+) for application
  • 1GB connectivity

Single Application Server
One nQzw application per server

  • 4xCPU Cores (2.6GHz+), 6GB RAM
  • C: drive for Windows
  • D: (100GB+) for application
  • 1GB connectivity

Multi-Application Server
Multiple nQzw applications per server

  • 6xCPU Cores (2.6GHz+), 8GB RAM
  • C: drive for Windows
  • D: (150GB+) for application
  • 1GB connectivity
  • When implementing CostQ and ScanQ, Enterprise Platform and Command Center are typically installed together

High Volume Application Server
Used for scanning and OCR

  • 8xCPU Cores (2.6GHz+), 16GB RAM
  • C: drive for Windows
  • D: (300GB+) for applications
  • 1GB connectivity


ScanQ Command Center (no CostQ)

Single Application Server

ScanQ Command Center (with CostQ)

Multi-Application Server

ScanQ InfoRoute
InfoRoute has several components: the service, orchestrator, import agent and engines. They can all run on one server. ABBYY is licensed to use 4 cores by default but can be increased up to 6 cores per server with additional licensing.

  • High Volume Application Server
  • 2 cores in addition to the 4-6 required by ABBYY

ScanQ InfoRoute Engines
Additional InfoRoute servers can be deployed with just the engines to optimize scanning and OCR time.

  • High Volume Application Server
  • 1 core in addition to the 4-6 required by ABBYY


Single Application Server


Utility Application Server


Single Application Server

CostQ Replication

Single Application Server

Multiple Applications
Depending on usage and environment, nQzw applications can be combined on single server instances

  • Multiple Application Server to support two or more applications
  • Customize with your implementation consultant

SQL Server

  • Microsoft SQL Server 2019 / 2017 / 2016
  • Alternatively, we can use SQL Server Express on the ScanQ Command Center server. Work with your implementation consultant to account for the necessary additional resources.


Port Usage



Engine to Orchestrator


8086 (https recommended, http optional)

Service via SMBv2 to watch folders



Orchestrator, Engine, Agent and Command Center Service to Command Center


443 (https recommended) or 80 (http optional)


Embedded / Tablet to InfoRoute


8085 (https recommended, http optional)


Embedded / Tablet to Data Services


81 (https recommended, http optional)

Embedded / Tablet to Command Center


443 (https recommended) or 80 (http optional)

Browser to Command Center


443 (https recommended) or 80 (http optional)

Browser to Enterprise Platform


443 (https recommended) or 8080 (http optional)

Browser to Embedded Web


4443 (https recommended) or 83 (http optional)

Embedded Web to Data Services



Embedded Web to Command Center



Embedded Web to Konica


50003, 50002

Konica/Xerox to FTP on Embedded Web



Browser to Konica (remote panel)



FTP on Embedded Web to Konica/Xerox



FTP on Embedded Web to Konica/Xerox



Orchestrator, Engine, Agent, InfoRoute, Command Center to SQL



Print Manager to Data Services


81 (https or http)

Desktops to Print Agent



Mobile Print to Command Center



Print Agent UPD Listening



Embedded / Tablet to Print Agent






IIS to Command Center



Zebraworks Bridge for
Outlook Add-in and Mobile Application

The nQzw Outlook add-in, which shows a user’s ScanQ in Outlook, including Outlook web and Outlook mobile apps. The nQzw Mobile Application enables scanning to your ScanQ and printing / secure release with PrintQ.

iOS and iPadOS Version


Android Version


Identity Provider
Sign-on to the nQzw app is via your existing access control system

  • Uses Auth0 to authenticate with your identity provider of choice, including Active Directory, Azure AD, ADFS, LDAP, SAML and others


All incoming traffic is validated using Auth0 and only valid https connections are accepted. The firm’s firewall will need to be configured to only accept incoming connections from the Zebraworks Platform egress IP.

  • SSL TLS 1.2 or greater with a trusted certificate on a public domain is required
  • All information in transit is encrypted over TLS
  • Documents are only stored in the firm’s repository within the firm’s firewall
  • During transfer, documents are encrypted with runtime generated cycled keys and files are promptly and permanently deleted after transfer
  • Documents are removed from local storage
  • Zebraworks Bridge Admin UI is only accessible to the localhost

Zebraworks Bridge Server

nQzw Mobile Application

The Bridge is responsible for securely moving documents from the Mobile App, via the Gateway and Azure Blob Storage, to ScanQ and PrintQ. The Bridge also securely relays print requests from the Mobile App via the Gateway to PrintQ.


nQzw Outlook Add-in

The Bridge securely delivers documents to the Outlook Add-in via the Gateway, caching from the original document repository inside the firm’s firewall. Blob storage is not used.

  • Utility Application Server
  • .NET V6 runtime
  • Trusted access to Zebraworks IP address
  • Network communication access to ScanQ Command Center

Mobile App Privacy Policy

Refer to the privacy policy for detailed information on how the app handles data.

Zebraworks Bridge Architecture

Scroll to Top