Host Whatfix Content On-Premise

Your title goes here

Reach out to your Whatfix representative or contact support@whatfix.com for information

Whatfix enables you to host your content in a few different ways: on the Whatfix cloud, on your own servers, or in an on-premise setup.

What is On-Premise Hosting?

With on-premise hosting, all operations are managed on private servers, meaning content is stored and accessed within the organization’s infrastructure. Whatfix generates a separate Studio extension that facilitates content creation and management, functioning independently from the Whatfix cloud to ensure there’s no direct connection between the two.

After creating content in Whatfix, a decision must be made about where to host and serve it. Whatfix supports multiple platforms for hosting, whether on the Whatfix cloud or on private servers.

Updates and Features

In an on-premise setup, new features do not automatically come from Whatfix. When an update or new feature is needed, a request is submitted, and Whatfix packages it for the IT team to install.

Updates can be scheduled at the organization’s convenience, with most opting for upgrades every few months. When an update occurs, the IT team handles the installation, and end users follow specific steps to access the latest features.

Access and Configuration Needs

To successfully set up and manage on-premise hosting, you need the following:

• Special access to configure and troubleshoot your servers.

• To allow Whatfix’s servers through your firewall for remote setup and updates.

• (Optional) To allow certain IP addresses for monitoring events.

Additional Requirements

You also need to prepare a few things, including:

• A Fully Qualified Domain Name (FQDN). The following is an example of what an FQDN looks like: www.google.com. In this example, the “www” is the hostname, “google” is the second-level domain and “com” is the top-level-domain (TLP).

• An HTTPS certificate for secure connections.

• A storage solution (like AWS S3 or Azure Blob) for daily backups of your data (this is optional).

• If you're using a desktop application, your IT team will need to install the Whatfix Player on all user machines.

Limitations and considerations

The primary consideration for on-premise installations is that no data should enter or exit the on-premise network due to specific firewall rules. This means features relying on third-party cloud services may not work. For example:

• Calling a ZenDesk API for feedback collection will not work.

• Integrating with services like Amplitude, Google Analytics, or Vimeo is also not feasible.