6. What are the technical requirements and how do updates work?

A fixed, universal hardware configuration is not part of this documentation, because sizing depends on the specific deployment. The decisive factors are primarily the number of concurrent users, the number and frequency of automations, the volume of synchronized data, the models used, and the required integration connectors. The final CPU, RAM, disk, and network capacity are therefore determined according to the client's target operation.

Updates are performed primarily centrally on the server side. This usually means rolling out a new version of the backend, the frontend application, the gateway layer, plugins, and auxiliary runtime components. User definitions, such as automations and their history, remain stored separately in the user environment. If the solution also includes a client-side synchronization service, its update is planned separately, because it runs on a machine designated by the client.