On Premise Deployment Notes

Overview / Sales Requirements

Flexopus offers for selected customers an on premise deployment. Providing and supporting an on premise installation needs more support from the Flexopus support team, than using the cloud solution:

• Deployment questions / support
• Architecture questions / support
• Software updates / support

The requirements for an on premise installation are:

• Minimum 5,000 resources are licensed
  You can have less resources in use, but you need to license at least this amount. In some individual cases, we may offer a lower limit.
• Minimum 1 year of commitment
  On premise is not available on the monthly basis.

Technical requirements for deployment

In this case, you can install the Flexopus application on your own server, the data is hosted on your own server.

We offer a docker container based installation, for this you need:

• Linux based OS
  for example, Debian latest stable. Other OS systems are also possible, however we can only support you properly, when you are using a Linux server.
• Docker latest stable
  The docker updates will be provided from a Flexopus registry.

Self-hosted minimum hardware requirements:

• 4 CPU cores (must support 64 bit instructions)
• 8 GB RAM
• 30 GB storage
• Internet connection

This gives you a rough understanding about the required server size that Flexopus needs.

Deployment configuration

Provide an email address for sending and receiving Flexopus emails to your users

• Outgoing emails
  Provide a primary SMTP service to send the emails. (A fallback service can be configured optionally.)
• Incoming emails (optional)
  Provide a way for incoming emails to be processed: (only one of the two)
  • a.) Provide an inbox for the email address and an IMAP connection so that the Flexopus server can fetch the emails.
  • b.) Forward all emails that are sent to the email address to the main Flexopus reservation email address. In this case, incoming emails will be processed by the central Flexopus Gateway software mentioned above.
• Create backups regularly and keep them safely.

Flexopus global services

Some services require a connection to the Flexopus main server infrastructure. These are mainly the so-called “global services”. Enable communication between your on-premise installation and the Flexopus Gateway Server. (Flexopus provides the addresses of the latter.) Some services are routed through a central Flexopus gateway even for on-premise installations because they use a central domain. This central gateway service is taking care of routing following components to your on-premise installation:

Let's see which global services are currently available, which need access to your on premise server:

• PlayStore Application traffic*
• AppStore Application traffic*
• Teams Application traffic*
• Webex Application traffic*
• HRIS integration traffic*

*Traffic means the complete network traffic, we are not saving this traffic only proxy / route to your on premise server. The applications in the mentioned stores are shipped with the Flexopus Gateway server's domain. We are not publishing a new application for each on premise deployment, therefore the Flexopus Gateway is required to use these services.

• oAuth2 login redirects
  Currently: Microsoft OAuth 2.0, Google OAuth 2.0, Webex OAuth 2.0.
  This does not affect SAML2 SSO logins!
• Device pairing redirects
  Meeting room signage display, meeting room board, presence display, visitor kiosk, catering kiosk etc.
• QR Code scanning redirects
  Only when the user is scanning the QR code outside the Flexopus application, for example using the normal camera and not the in-built QR code scanner in the Flexopus application.
• Incoming email traffic
  Only when not using an own inbox with IMAP, see below. This feature is mostly used in case you enable the reservation confirmations with iCal, and the user tries to decline the booking using the iCal invitation.