On-Premises
How to request on-premises operation in your own data center.
The page “On-Premises Operation Request Guide” covers the function identified by this URL. The existing summary is expanded with the actual workflow, prerequisites and known limitations. On-premises operation is not self-service. It is handled under the Individual package through a request and consultation. The licensing mechanism still contains a placeholder key, so the feature must be described only as “available on request, being introduced”. The recorded price is EUR 299 per month plus EUR 399 setup.
On-premises operation is not a dashboard self-service feature. It is handled for the Individual package through a request and technical consultation. The known commercial model is EUR 299 per month plus a EUR 399 setup fee.
The current licence mechanism still contains a placeholder key. The service must therefore be described as provided on request and being introduced, not as a fully production-ready instant deployment.
Infrastructure, network access, maintenance, backups, updates and responsibilities must be clarified for each project. The public page must not make unsupported SLA, security or feature-parity promises.
A useful request includes the target environment, expected scale, required channels and specific compliance needs. Credentials must not be included in the request. Activation is performed after assessment, not automatically from the tenant dashboard.
For “On-Premises Operation Request Guide”, the expanded text must remain specific to https://zentor-app.de/en/hilfe/on-premises, use only verified facts and clearly separate tenant self-service from actions performed by Zentor. Any support case is best advised to identify this exact page, the active tenant and the observed step without disclosing credentials.
When using “On-Premises Operation Request Guide”, test one controlled scenario at a time and compare the visible setting, the actual system status and the expected result. If the outcome differs, record the exact time, tenant, channel and unchanged error message. Screenshots and support notes must exclude passwords, tokens and unnecessary personal data so that troubleshooting remains both useful and safe.