This article explains the different deployment options for our WHINT® Integration Cockpit.
Overall architecture:
Deployment Options
- SaaS (SAP BTP on AWS – fully operated by us)
- Cloud (SAP BTP on AWS / Azure / … – we deploy and run the solution on YOUR subaccount)
- OnPrem/PrivateCloud (you are in charge: you can run in SQLite mode)
The default deployment model is SaaS (1), where we run both the application and the database (PostgreSQL). You receive access via Microsoft AD (Entra) and we take care about everything. Each customer is separated by its own database. The typical deployment is SAP BTP (Cloud Foundry on AWS in Frankfurt, Germany):
You can also run both app and database in your own cloud environment (2). All you need is a SAP BTP subaccount with Cloud Foundry enabled and your own database via PostgreSQL as a BTP service. The following BTP services are required (minimum setup):
- SAP BTP, Cloud Foundry Runtime (Standard): 1 * GB Memory
- PostgreSQL on SAP BTP, hyperscaler option (Storage): 2 * Storage In 5gb Blocks
- PostgreSQL on SAP BTP, hyperscaler option (Standard): 1 * Memory In 2gb Blocks
Here, you can connect your own SSO (XSUAA service), SAP Cloud Connector(s) and deploy our native RFC-Client (implemented as a CAP application)
Lastly, you can run the solution in your own environment: OnPrem (3). You have to make sure that the service is reachable in your network and secure the traffic via SSL/TLS. Here you can also run the database in a SQLite mode where you do not need an extra database installed:
We clearly recommend options (1) or (2). Me manage the operations and updates and you can comfortably use the solution with your data.
However, there are options you can choose from in case you need full control. In this case, you have to allow our technicians to connect and run updates as we are continuously delivering new features…
Last update: 17. Aug 2026
