What is it?How it worksDemoTechnical Specifications
Technical Specifications

docuBridge ONE is installed locally on your workstation. Once purchased, you will be able to download the software and install it yourself. A basic IQ script helps you keep record of your setup.

Local Deployment

Following are the current technical requirements for LORENZ docuBridge. Please note that just because LORENZ has not officially released docuBridge for a different version of an operating system does not mean that it does not work! However, LORENZ has tested docuBridge ONE in the following environments:

LORENZ docuBridge ONE Workstation

Operating Systems:

Microsoft Windows 8.1 (certified)

Microsoft Windows 10 (supported)

Microsoft Windows 8 (supported)

Microsoft Windows 7 SP1 (supported)

Microsoft Windows 7 (supported)

Microsoft Windows Vista (supported)

CPU: Dual-Core (Minimum)

Disk Space: 500MB (Minimum)

RAM: 4 GB (Minimum)

Resolution: 1280 x 1024 (Minimum)


Internet Explorer: 9, 10, 11 / Firefox: 27.0 - 37.0 / Chrome: 34.0 - 43.0

Please note: docuBridge ONE setups checks for an appropriate Microsoft SQL Database. If needed the setup installs a Microsoft SQL Express database and downloads the necessary components. Usage of the database in a different than from the setup created configuration is not recommended.

Microsoft´s .NET Framework version 4.5 or higher is required. The docuBridge ONE setup checks for the appropriate .NET version and downloads and installs it if needed.

Use in Virtualized Environments: LORENZ supports Virtual Environments as transparent. In other words: we do expect the virtualization environment with an installed supported or certified operating system to perform identically when compared to the same operating system being installed into a physical environment. LORENZ would like to remind customers that there are certain techniques that can be applied to virtualized environments which may cause issues with the Product activation of docuBridge: the hardware code for docuBridge is calculated based upon a combination of characteristics of the system it is operated on. Should these identifiers change through the use of specific procedures, (e.g. when moving a virtualized environment to a different node) then the system may consider the activation invalid.