System Structure & Architecture<\/h1><\/div><\/div><\/div>HybridForms is a forms and process platform made up of two components: the HybridForms Core Server as the backend and the client apps for iOS, Android, Windows and as a Progressive Web App (PWA).<\/strong><\/p>\nOne platform. Every device. Every infrastructure. HybridForms consists of the central HybridForms Core Server (backend) and the client apps for iOS, Android, Windows, and as a Progressive Web App (PWA) in the browser. The server backend runs on-premises or in the cloud \u2013 on Windows Server or Linux, optionally as a Docker container, with Microsoft SQL Server or PostgreSQL.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
General System Structure & Concepts<\/h2><\/div><\/div><\/div>The system consists of two central components: the HybridForms Core Server<\/strong> as the central backend and the HybridForms Client Apps<\/strong> for iOS, Android, Windows and as a Progressive Web App (PWA) for web browsers.<\/p>\nAs a database backend, HybridForms supports both Microsoft SQL Server<\/strong> and PostgreSQL<\/strong> \u2013 operated on Windows Server, Linux, as a Docker container, or in the Microsoft Azure Cloud<\/strong>. PostgreSQL offers a cost-efficient, open-source-based alternative for organisations that rely on vendor-independent infrastructure.<\/p>\nA HybridForms Server Licence<\/strong> is required for operation. Every user of a client app additionally requires a User Licence (Client Access Licence \/ CAL)<\/strong>, which is centrally managed and administered on the HybridForms Core Server.<\/p>\n<\/div><\/div><\/div>![\"HybridForms:](\"https:\/\/www.hybridforms.net\/en\/wp-content\/uploads\/sites\/3\/2026\/03\/HybridForms-System-App-Server-EN-60.png\")
<\/a><\/span><\/div><\/div><\/div><\/div>Try Demo Apps for free<\/span><\/i><\/a><\/div><\/div><\/div><\/div><\/div>HybridForms Core Server: Multi System Architecture<\/h2><\/div><\/div><\/div>The HybridForms Core Server supports a multi-system architecture (client, tenant). The HybridForms Server is available in three editions: Business, Enterprise and Operator Edition<\/strong>. By default, one system is operated; the Operator Edition also supports multiple systems (operator mode with tenants).<\/p>\n<\/div><\/div><\/div>HybridForms Core Server<\/strong><\/p>\n\n- System 1<\/strong>\n
\n- Form Templates<\/li>\n
- Form Areas<\/li>\n
- Area 1\u2026n | Form Items<\/li>\n<\/ul>\n<\/li>\n
- System 2 (Operator Edition only)\u00a0<\/strong>\n
\n- Form Templates<\/li>\n
- Form Areas<\/li>\n
- Area 1\u2026n | Form Items<\/li>\n<\/ul>\n<\/li>\n
- System n (Operator Edition only)\u00a0<\/strong><\/li>\n<\/ul>\n<\/div><\/div><\/div>
Systems (Clients, Tenants)<\/strong><\/p>\nEach system can be managed independently and configured flexibly for individual departments or customers. The system concept enables granular, delegable administration by local or department-specific administrators.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
Forms: Templates | Areas | Items<\/h2><\/div><\/div><\/div>Templates<\/strong><\/p>\nForm definitions (form data fields, layout, etc.) are stored as so-called templates. Each system has its own set of templates. Templates are first created by an administrator of the respective system, then assigned to the responsible developers and form designers. The administrator also creates users and permissions, as well as the assignment to an \u00bbarea\u00ab.<\/p>\n<\/div>
<\/div>Areas<\/strong><\/p>\nEach template is assigned to an \u00bbarea\u00ab. Areas are displayed in the mobile clients apps under \u00bbSettings\u00ab and serve to structure and organize the available templates and form types.<\/p>\n<\/div>
<\/div>Items<\/strong><\/p>\nThe actual form data is stored as form elements (\u00bbitems\u00ab) instantiated from the template \u2013 for example, manually by a user creating a new form in the HybridForms App. The form entry is assigned to the area of its form template.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
User Roles & Administration Levels<\/h2><\/div><\/div><\/div>HybridForms has several administration or access levels for different types of users:<\/p>\n<\/div>
<\/div>Core Server Admin<\/strong><\/p>\nHas access to all elements, in particular the central server settings at the top level as well as administrative access to all systems, templates and user licences. Can add systems and assign them to System Administrators. Can assign user licences from the central licence pool to a system and transfer unused licences back.<\/p>\n<\/div>
<\/div>System Admin (Tenants)<\/strong><\/p>\nHas full administrative rights within a specific system. Can manage templates, user licences, groups and areas. Can also view and manage catalogues assigned to the respective system.<\/p>\n<\/div>
<\/div>Group-based roles<\/strong><\/p>\nGroup Portal Admin:<\/strong> Can view and manage all groups (e.g. create, delete). Has no access to forms.
\nGroup Portal Read-Only User:<\/strong> Can view all groups but make no changes. Also has no access to forms.
\nGroup Admin:<\/strong> Limited to their assigned group. Can manage most group functions, view and edit their own forms, and access all forms within their group.
\nGroup Read-Only Admin:<\/strong> Read-only access to their assigned group. Can view their own forms and all other forms within the same group, but cannot make changes.
\nGroup Status Admin:<\/strong> Can display and update the status of their own forms, and view and update the status of all forms within their group.<\/p>\n<\/div><\/div>Template Designer<\/strong><\/p>\nRead-only access to their assigned templates. Cannot edit templates. Has no access to forms.<\/p>\n<\/div>
<\/div>Catalog Manager<\/strong><\/p>\nCore Catalog Manager:<\/strong> Full access to all catalogs across the entire platform. Can create and manage catalogues.
\nSystem Catalog Manager:<\/strong> Access only to catalogues assigned to their respective system. Cannot create new catalogues.<\/p>\n<\/div><\/div>API\u2011 and template\u2011based access roles<\/strong><\/p>\nFull Access (or Read-Only) & API:<\/strong> Access to all forms within a template, both via the admin UI and the API.
\nCreate Forms:<\/strong> Can create new forms in the app and edit their own forms.
\nUpdate Forms:<\/strong> Can edit their own forms.<\/p>\n<\/div><\/div>Standard User<\/strong><\/p>\nThe standard users are outside the administration hierarchy listed above, but are included here for the sake of completeness.<\/strong> Can use the HybridForms App, create forms, and access forms assigned to them or their group. Can access the HybridForms Admin Web App exclusively for their own form entries. No access to administrative functions.<\/p>\n<\/div><\/div><\/div><\/div><\/div>HybridForms Server: System Requirements<\/h2><\/div><\/div><\/div>HybridForms Core Server V10<\/strong><\/p>\n\n- Operating System:<\/strong>\n
\n- Microsoft Windows Server 2019+ <\/strong>(recommended 2022\/2025 \u2013 Standard)<\/li>\n
- or Linux<\/strong><\/a><\/li>\n
- Container (optional): ca be run as a Docker container<\/li>\n<\/ul>\n<\/li>\n
- Runtime dependencies:<\/strong>\n
\n- .NET 8.x + Hosting, Node.js 20+LTS, WebDeploy 3.6+<\/li>\n<\/ul>\n<\/li>\n
- Hardware (minimum):<\/strong>\n
\n- 2+ Core | 8+ GB RAM (test: 4 GB) | 100+ GB HDD<\/li>\n<\/ul>\n<\/li>\n
- Hardware (recommended):<\/strong>\n
\n- 4 Core | 16 GB<\/li>\n<\/ul>\n<\/li>\n
- ReachOut Server:<\/strong>\n
\n- 4 Core | 8 GB (optional cluster)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/div><\/div><\/div>
Database Service<\/strong><\/p>\n\n- Database:<\/strong>\n
\n- Microsoft SQL Server 2017+ <\/strong>(recommended 2019\/2022 \u2013 Standard or SQL Azure)<\/li>\n
- or PostgreSQL<\/strong><\/li>\n
- Database deployment: Windows Server or Linux<\/strong><\/a><\/li>\n<\/ul>\n<\/li>\n
- Hardware:<\/strong>\n
\n- 4 cores | 16+ GB RAM (optional cluster)<\/li>\n<\/ul>\n<\/li>\n
- Collation:<\/strong>\n
\n- SQL_Latin1_General_CP1_CI_AS<\/li>\n<\/ul>\n<\/li>\n
- Storage:<\/strong>\n
\n- Base dataset: 5 GB | Working dataset: 50+ GB<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/div><\/div><\/div>
Deployment: Azure Cloud or On-Premises<\/strong> (virtual servers)
\nADFS (optional):<\/strong> Server 2016+ ADFS 4 (OpenID Connect)<\/p>\n<\/div><\/div><\/div><\/div><\/div>Secure AI Servers: Sovereign AI Infrastructure<\/h2><\/div><\/div><\/div>HybridForms supports running AI models on dedicated, self-controlled servers \u2013 on-premises or in a private cloud.<\/strong> Sensitive form data, voice input and AI processing never leave your own infrastructure. Instead of public AI services, certified, locally hosted language models (LLMs) are integrated, fitting seamlessly into the existing HybridForms Core Server architecture. This model meets the requirements of GDPR, NIS2 and sector-specific compliance regulations \u2013 making HybridForms a trusted AI platform<\/strong><\/a> for public authorities, critical infrastructure operators and regulated enterprises.<\/p>\n<\/div><\/div><\/div><\/div><\/div>![\"Logo](\"https:\/\/www.hybridforms.net\/en\/wp-content\/uploads\/sites\/3\/2026\/07\/Logo-Windows-Server-02.png\" "\\"Logo")
<\/span><\/div><\/div><\/div><\/div>![\"Logo](\"https:\/\/www.hybridforms.net\/en\/wp-content\/uploads\/sites\/3\/2026\/07\/Logo-Linux-Server-02.png\" "\\"Logo")
<\/span><\/div><\/div><\/div><\/div>![\"Logo](\"https:\/\/www.hybridforms.net\/en\/wp-content\/uploads\/sites\/3\/2026\/07\/Logo-Docker-Container-02.png\" "\\"Logo")
<\/span><\/div><\/div><\/div><\/div>![\"Logo](\"https:\/\/www.hybridforms.net\/en\/wp-content\/uploads\/sites\/3\/2025\/01\/Logo-Microsoft-SQL-Server-02.png\" "\\"Logo")
<\/span><\/div><\/div><\/div><\/div>![\"Logo](\"https:\/\/www.hybridforms.net\/en\/wp-content\/uploads\/sites\/3\/2025\/01\/Logo-Microsoft-SQL-Azure-01.png\" "\\"Logo")
<\/span><\/div><\/div><\/div><\/div>![\"Logo](\"https:\/\/www.hybridforms.net\/en\/wp-content\/uploads\/sites\/3\/2026\/03\/Logo-PostgreSQL-60.png\" "\\"Logo")
<\/span><\/div><\/div><\/div><\/div><\/div><\/div>
HybridForms is a forms and process platform made up of two components: the HybridForms Core Server as the backend and the client apps for iOS, Android, Windows and as a Progressive Web App (PWA).<\/strong><\/p>\n One platform. Every device. Every infrastructure. HybridForms consists of the central HybridForms Core Server (backend) and the client apps for iOS, Android, Windows, and as a Progressive Web App (PWA) in the browser. The server backend runs on-premises or in the cloud \u2013 on Windows Server or Linux, optionally as a Docker container, with Microsoft SQL Server or PostgreSQL.<\/p>\n<\/div><\/div><\/div><\/div><\/div> The system consists of two central components: the HybridForms Core Server<\/strong> as the central backend and the HybridForms Client Apps<\/strong> for iOS, Android, Windows and as a Progressive Web App (PWA) for web browsers.<\/p>\n As a database backend, HybridForms supports both Microsoft SQL Server<\/strong> and PostgreSQL<\/strong> \u2013 operated on Windows Server, Linux, as a Docker container, or in the Microsoft Azure Cloud<\/strong>. PostgreSQL offers a cost-efficient, open-source-based alternative for organisations that rely on vendor-independent infrastructure.<\/p>\n A HybridForms Server Licence<\/strong> is required for operation. Every user of a client app additionally requires a User Licence (Client Access Licence \/ CAL)<\/strong>, which is centrally managed and administered on the HybridForms Core Server.<\/p>\n<\/div><\/div><\/div> The HybridForms Core Server supports a multi-system architecture (client, tenant). The HybridForms Server is available in three editions: Business, Enterprise and Operator Edition<\/strong>. By default, one system is operated; the Operator Edition also supports multiple systems (operator mode with tenants).<\/p>\n<\/div><\/div><\/div> HybridForms Core Server<\/strong><\/p>\n Systems (Clients, Tenants)<\/strong><\/p>\n Each system can be managed independently and configured flexibly for individual departments or customers. The system concept enables granular, delegable administration by local or department-specific administrators.<\/p>\n<\/div><\/div><\/div><\/div><\/div> Templates<\/strong><\/p>\n Form definitions (form data fields, layout, etc.) are stored as so-called templates. Each system has its own set of templates. Templates are first created by an administrator of the respective system, then assigned to the responsible developers and form designers. The administrator also creates users and permissions, as well as the assignment to an \u00bbarea\u00ab.<\/p>\n<\/div> Areas<\/strong><\/p>\n Each template is assigned to an \u00bbarea\u00ab. Areas are displayed in the mobile clients apps under \u00bbSettings\u00ab and serve to structure and organize the available templates and form types.<\/p>\n<\/div> Items<\/strong><\/p>\n The actual form data is stored as form elements (\u00bbitems\u00ab) instantiated from the template \u2013 for example, manually by a user creating a new form in the HybridForms App. The form entry is assigned to the area of its form template.<\/p>\n<\/div><\/div><\/div><\/div><\/div> HybridForms has several administration or access levels for different types of users:<\/p>\n<\/div> Core Server Admin<\/strong><\/p>\n Has access to all elements, in particular the central server settings at the top level as well as administrative access to all systems, templates and user licences. Can add systems and assign them to System Administrators. Can assign user licences from the central licence pool to a system and transfer unused licences back.<\/p>\n<\/div> System Admin (Tenants)<\/strong><\/p>\n Has full administrative rights within a specific system. Can manage templates, user licences, groups and areas. Can also view and manage catalogues assigned to the respective system.<\/p>\n<\/div> Group-based roles<\/strong><\/p>\n Group Portal Admin:<\/strong> Can view and manage all groups (e.g. create, delete). Has no access to forms. Template Designer<\/strong><\/p>\n Read-only access to their assigned templates. Cannot edit templates. Has no access to forms.<\/p>\n<\/div> Catalog Manager<\/strong><\/p>\n Core Catalog Manager:<\/strong> Full access to all catalogs across the entire platform. Can create and manage catalogues. API\u2011 and template\u2011based access roles<\/strong><\/p>\n Full Access (or Read-Only) & API:<\/strong> Access to all forms within a template, both via the admin UI and the API. Standard User<\/strong><\/p>\n The standard users are outside the administration hierarchy listed above, but are included here for the sake of completeness.<\/strong> Can use the HybridForms App, create forms, and access forms assigned to them or their group. Can access the HybridForms Admin Web App exclusively for their own form entries. No access to administrative functions.<\/p>\n<\/div><\/div><\/div><\/div><\/div> HybridForms Core Server V10<\/strong><\/p>\n Database Service<\/strong><\/p>\n Deployment: Azure Cloud or On-Premises<\/strong> (virtual servers) HybridForms supports running AI models on dedicated, self-controlled servers \u2013 on-premises or in a private cloud.<\/strong> Sensitive form data, voice input and AI processing never leave your own infrastructure. Instead of public AI services, certified, locally hosted language models (LLMs) are integrated, fitting seamlessly into the existing HybridForms Core Server architecture. This model meets the requirements of GDPR, NIS2 and sector-specific compliance regulations \u2013 making HybridForms a trusted AI platform<\/strong><\/a> for public authorities, critical infrastructure operators and regulated enterprises.<\/p>\n<\/div><\/div><\/div><\/div><\/div>General System Structure & Concepts<\/h2><\/div><\/div><\/div>
<\/a><\/span><\/div><\/div><\/div><\/div>HybridForms Core Server: Multi System Architecture<\/h2><\/div><\/div><\/div>
\n
\n
\n
Forms: Templates | Areas | Items<\/h2><\/div><\/div><\/div>
User Roles & Administration Levels<\/h2><\/div><\/div><\/div>
\nGroup Portal Read-Only User:<\/strong> Can view all groups but make no changes. Also has no access to forms.
\nGroup Admin:<\/strong> Limited to their assigned group. Can manage most group functions, view and edit their own forms, and access all forms within their group.
\nGroup Read-Only Admin:<\/strong> Read-only access to their assigned group. Can view their own forms and all other forms within the same group, but cannot make changes.
\nGroup Status Admin:<\/strong> Can display and update the status of their own forms, and view and update the status of all forms within their group.<\/p>\n<\/div>
\nSystem Catalog Manager:<\/strong> Access only to catalogues assigned to their respective system. Cannot create new catalogues.<\/p>\n<\/div>
\nCreate Forms:<\/strong> Can create new forms in the app and edit their own forms.
\nUpdate Forms:<\/strong> Can edit their own forms.<\/p>\n<\/div>HybridForms Server: System Requirements<\/h2><\/div><\/div><\/div>
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\nADFS (optional):<\/strong> Server 2016+ ADFS 4 (OpenID Connect)<\/p>\n<\/div><\/div><\/div><\/div><\/div>Secure AI Servers: Sovereign AI Infrastructure<\/h2><\/div><\/div><\/div>
<\/span><\/div><\/div><\/div><\/div><\/span><\/div><\/div><\/div><\/div><\/span><\/div><\/div><\/div><\/div><\/span><\/div><\/div><\/div><\/div><\/span><\/div><\/div><\/div><\/div><\/span><\/div><\/div><\/div><\/div><\/div><\/div>