System Requirements
Hardware and software requirements for a successful Docuflair installation — on Windows and Linux
- Windows
- Linux
- macOS
- Android
- Browser
Supported Operating Systems
Docuflair is cross-platform — server and client applications run on all common operating systems
Docuflair is built on .NET 10 throughout and is therefore not tied to a single operating system. The server applications Docuflair and Docuflair Core run on Windows Server and on Linux, with an identical feature set and an identical administration interface. The workstation applications additionally run on macOS.
Windows Server
- Windows Server 2019, 2022, 2025 (Standard or Datacenter)
- Windows 10 / 11, 64-bit — for test and single-workstation installations
- Installation through the Docuflair installer
- Operated as a Windows service
No Internet Information Server is required — the web server is part of the application.
Linux
- Debian 12 and newer
- Ubuntu 22.04 LTS and newer
- Package installation (.deb, amd64)
- Operated as a systemd service, one unit per instance
Further distributions (RHEL, Rocky Linux, SUSE) on request — the prerequisites are .NET 10 and systemd.
macOS
- macOS 12 (Monterey) and newer
- Apple Silicon and Intel
- All workstation applications
- Background services through launchd
macOS is a client platform. Server operation runs on Windows Server or Linux.
Mobile & Browser
- Android 10 and newer
- iOS 14 and newer
- Web interfaces in any current browser
- Device interface directly at the MFP
Mobile capture, release and printing without any local installation.
Print submission is platform-neutral
Follow-me printing, print rules and release at the device work the same way on both server platforms. The only difference is how a job enters the queue:
- CUPS queue with the Docuflair backend — the standard route on Linux, shareable to Windows workstations through Samba
- IPP and IPPS (port 631) — a Windows workstation prints directly to the Linux server, no Samba required
- LPD (port 515) and raw printing (port 9100) — for devices and systems without IPP
- Print Agent over HTTPS — for workstations without domain membership
- Windows print queue — the familiar route on Windows Server
Docuflair Server - Hardware
Minimum requirements for the Docuflair Server — identical on Windows and Linux
| Component | Requirement | Notes |
|---|---|---|
| Processor | 64-bit processor: Intel (Intel 64 architecture) or AMD (AMD64 platform) | Intel Itanium IA64 processors are not supported. Recommended: up to 2 processor sockets. |
| Memory | Min. 8GB (up to 256GB) | Dependent on the activated licence and document throughput |
| Page File | At least 25% of system memory | Important for system stability |
| Disk Space | At least 30 GB free space | System drive: at least 2 GB free |
| Screen Resolution | 1024 x 768 pixels (XGA) or higher | Full HD recommended |
| File System | NTFS (Windows) · ext4 or XFS (Linux) | On Linux the installation directory /opt/docuflair must reside on a file system with POSIX permissions |
Software Requirements
Runtime environment, database and web server for the server applications
| Component | Windows | Linux |
|---|---|---|
| Operating system | Windows Server 2019, 2022 or 2025 (Standard or Datacenter) or 64-bit edition of Windows 10 / 11 for test installations |
Debian 12 and newer Ubuntu 22.04 LTS and newer further distributions on request |
| Runtime environment | .NET 10 — included in the delivery, no separate installation required | |
| Web server | Built in (Kestrel). No IIS and no Apache required. A reverse proxy (nginx, IIS ARR) can optionally be placed in front, for example to terminate TLS centrally. | |
| Database (Standard) | SQLite – built-in, no separate installation required | |
| Database (Enterprise) | Microsoft SQL Server 2016 or higher — usable from either server platform | |
| Service management | Windows service | systemd (docuflair@<instance>) |
| Installation | Docuflair installer | Package installation (.deb, amd64) or installation script |
| Directory service | Active Directory or LDAP — on both platforms through LDAP/LDAPS, plus OpenID Connect | |
Database Recommendation: SQLite or SQL Server?
SQLite is built into Docuflair and sufficient for most installations. Microsoft SQL Server is recommended for:
- More than 10 connected devices
- Licences with 16 or more CPU cores
- More than 1,000 users
Depending on the use case and document volume, SQLite may still be sufficient even in these scenarios. We recommend starting with SQLite and migrating if needed – the built-in migration tool makes switching to SQL Server easy at any time.
Client Applications
Which application runs on which workstation operating system
| Application | Platforms | Purpose |
|---|---|---|
| Docuflair Desktop |
|
Capture from locally attached scanners, redact and pseudonymise individual documents — directly at the workstation, without a server |
| Print Agent |
|
Submit print jobs over HTTPS — including without domain membership, for example from home offices |
| Docuflair Mobile |
|
Photograph receipts, capture metadata, send print jobs and release them at the device |
| Administration & self-service |
|
Web interface for configuration, users, rules and reporting — independent of the operating system |
| Tools |
|
Database migration, log monitoring, device registration, QR label printing, device simulator |
Mixed environments are the norm
The server platform and the workstation operating system are independent of each other. A Linux server serves Windows, Linux and macOS workstations equally — and the other way round. Switching the server platform later is possible too: configuration, database and document repository stay the same, because both installations use the same directory structure and the same data model.
Supported Hardware Platforms
Compatible scanner and MFP platforms
Epson Open Platform
EOP
Kyocera HyPAS
Hybrid Platform for Advanced Solutions
Kodak Alaris
Scan Station EX Plus
Canon
Scan Front 400
Sharp OSA
Open Systems Architecture
Xerox EIP
Extensible Interface Platform
Lexmark eSF
Embedded Solutions Framework
Virtualisation & Containers
Running Docuflair in virtualised environments
Docuflair is fully qualified for operation in virtualised environments. The following hypervisors are supported:
| Platform | Status | Notes |
|---|---|---|
| Microsoft Hyper-V | Fully supported | Windows Server 2019–2025, incl. Failover Cluster |
| VMware vSphere / ESXi | Fully supported | Version 6.5 or higher recommended |
| Citrix XenServer | Supported | Version 7.0 or higher |
| Proxmox VE / KVM | Fully supported | Virtual machines and LXC containers |
| Containers (Docker, Podman) | Supported | Linux containers, one container per instance; persistent volumes for database, spool and documents |
Recommendations for Virtual Environments
- Dedicated resources: CPU and RAM should be exclusively assigned to the Docuflair VM (no overcommitment) to ensure consistent performance under high document throughput.
- Storage: SSDs or NVMe storage recommended for the VM, particularly for the database and document archive.
- Snapshots: Create a VM snapshot before updates or configuration changes – enables quick rollback.
- Network: At least 1 Gbit/s virtual network adapter. For high throughput, consider SR-IOV (Single Root I/O Virtualisation).
The hardware requirements listed above also apply to virtual machines. Contact us for individual consultation regarding your specific infrastructure.
Multi-Site Architecture
Cross-location working with Master/Member concept
Docuflair supports distributed environments with multiple locations through a Master/Member Server architecture. The Master Server centrally manages all licences, configurations and users. Member Servers at individual sites handle local processing and automatically synchronise with the Master.
| Component | Role | Requirement |
|---|---|---|
| Master Server | Central management (licences, configuration, users) | 1× per environment, recommended at the main site |
| Member Server | Local processing (scanning, printing, workflows) | 1× per site, same hardware requirements as above |
| Network Connection | Synchronisation between Master and Member | Stable internet connection or VPN, min. 10 Mbit/s recommended |
| Database | Independent per server | SQLite or SQL Server – each server has its own database |
Failover Protection & Cross-Site Working
- Autonomous operation: Each Member Server can continue operating autonomously if the connection to the Master fails. Scans, print jobs and workflows continue running locally – with no interruption for users.
- Automatic synchronisation: Once the connection to the Master is restored, configuration changes, user updates and job data are automatically synchronised.
- Cross-site Pull Print: Print jobs can be submitted at one location and collected at any other location worldwide. Example: An employee submits a print job in Mexico and picks it up upon arrival in Germany at the nearest MFP.
- Central management: All settings, licences and user permissions are configured on the Master and automatically distributed to all Members – no manual configuration effort per site.
- Mixed platforms: Master and Member do not have to run the same operating system. A Master on Linux manages Members on Windows Server and the other way round – synchronisation uses the same encrypted connection.
Frequently asked questions about platforms and system requirements
The questions asked most often before an installation
Does Docuflair run on Linux?
Yes. The Docuflair server runs fully on Linux — tested on Debian 12 and Ubuntu 22.04 LTS and newer, installed as a package (.deb, amd64) and operated as a systemd service. Further distributions such as RHEL, Rocky Linux or SUSE are available on request; the prerequisites are .NET 10 and systemd. There is no functional difference to a Windows installation: the same administration interface, the same modules, the same database.
Which operating systems do the Docuflair client applications support?
Docuflair Desktop — scanning, redaction and pseudonymisation in one application — plus Print Agent and the tools for database migration, log monitoring, device registration and QR label printing run on Windows 10/11, Linux and macOS 12 or newer — on Apple Silicon as well as on Intel. The mobile app is available for iOS 14+ and Android 10+, and the web interfaces run in any current browser.
Does Docuflair require IIS?
No. Docuflair ships with its own web server (Kestrel, part of .NET 10). No Internet Information Server is installed or configured, and there is no web.config. This simplifies hardening and operations considerably, because there is no additional server role to maintain. A reverse proxy such as nginx can optionally be placed in front to terminate TLS centrally or to serve several applications behind one address.
How are print jobs submitted to a Linux server?
Through a CUPS queue with the Docuflair backend, through IPP and IPPS (port 631), LPD (port 515), raw printing (port 9100) or through the Print Agent over HTTPS. A Windows workstation can print directly to a Linux server over IPP without requiring Samba — Windows has supported IPP natively since version 10. Follow-me printing, print rules, accounting and release at the device are identical on both platforms.
Can an existing Windows server move to Linux later?
Yes. Both installations create the same directory structure and use the same data model. Configuration, database, users, rules and the document repository are carried over; connected devices keep their registration. The only item to plan is the print submission route — instead of the Windows print queue, CUPS or the network intake over IPP takes over.
Does Docuflair support the requirements of ISO/IEC 27001?
Docuflair supports the technical requirements of an information security management system in line with ISO/IEC 27001 — including role-based access control, audit-proof logging, encryption of data at rest and in transit, tenant separation, key management and documented retention periods. This allows Docuflair to be integrated into an existing ISMS and included in its evidence base. The product itself does not carry an ISO 27001 certification: certification applies to the management systems of organisations, not to software products.
Can Docuflair run in containers?
Yes. Linux operation is container-ready — one container per instance, with persistent volumes for the database, the spool directory and the document repository. LXC containers under Proxmox VE work as well. In containerised operation the print submission route needs planning: CUPS usually runs on the host, whereas the network intake over IPP, LPD or raw works directly inside the container.
Need Assistance?
Our experts are happy to assist you with planning and implementing your Docuflair installation.