How Quantive connects to your data source
Quantive enables you to fully automate your Key Results and KPIs by gathering data from external data sources. You can connect to over 150 business systems and databases, some of which are SaaS-based, others hosted on-premises.
When connecting to SaaS-based solutions, you authorize Quantive to sync data on your behalf, involving OAuth 2.0 authorization flow and HTTPS TLS > 1.2 encryption for the data during transmission.
When connecting to an on-premise data source, these resources are usually behind a firewall, thus you must enable Quantive to access them.
Whitelisting the Quantive IPs
When you integrate Quantive with your on-premises data source, we will make platform-specific API requests to fetch the data. In order for our data sync nodes to establish a successful connection to your data source, you must whitelist the IP range assigned to these data sync machines.
EU data center
If your account is hosted in our European data center (your account URL is something like this: https://accountname.gtmhub.com) you must configure your firewall to allow inbound traffic on port 443 to your data sources for the following IPs:
20.56.199.32, 20.56.199.33, 20.56.199.34, 20.56.199.35, 20.56.199.36, 20.56.199.37, 20.56.199.38, 20.56.199.39
or CIDR range: 20.56.199.32/29
US data center
If your account is hosted in our US data center (your account URL is something like this: https://accountname.us.gtmhub.com) you must configure your firewall to allow inbound traffic on port 443 to your data sources for the following IPs:
20.64.129.88, 20.64.129.89, 20.64.129.88, 20.64.129.90, 20.64.129.91, 20.64.129.92, 20.64.129.93, 20.64.129.94, 20.64.129.95
or CIDR range: 20.64.129.88/29
AS (Asia) data center
If your account is hosted in our Asian data center (your account URL is something like this: https://accountname.as.gtmhub.com) you must configure your firewall to allow inbound traffic on port 443 to your data sources for the following IP range:
20.239.32.192, 20.239.32.193, 20.239.32.194, 20.239.32.195, 20.239.32.196, 20.239.32.197, 20.239.32.198, 20.239.32.199
or CIDR range: 20.239.32.192/29
SA (South America) data center
If your account is hosted in our South America data center (your account URL is something like this: https://accountname.sa.gtmhub.com) you must configure your firewall to allow inbound traffic on port 443 to your data sources for the following IPs:
20.201.50.224, 20.201.50.225, 20.201.50.226, 20.201.50.227, 20.201.50.228, 20.201.50.229, 20.201.50.230, 20.201.50.231
or CIDR range: 20.201.50.224/29
Which ports do I whitelist
When you whitelist the above IPs, it is a good practice to allow traffic on specific ports only. Depending on the data source you are connecting to, and your specific internal setup, you must whitelist the port that your data source is accessible on. As a rule of thumb:
All data sources that expose REST APIs (e.g. Jira Server/DC) - port 443, or the custom port on which you host the system.
Databases (e.g. PostgreSQL, MS SQL) - each database specific port, depending on the DB server. For example, the default port for connecting to a PostgreSQL instance is port 5432.
Secure connections via tunnel
Usually, the specific application protocol provides encryption of the data in transit. When this is not the case, network tunneling usually comes into play. To find out the details you need to share with your IT administrator in order to establish access from Quantive to databases or business services behind a firewall using an encrypted tunnel use our article on Database secure tunnel connection.