How Varibill Connects to Your Private Infrastructure

Overview

This guide explains how Varibill securely connects to your private compute instance — such as a virtual machine, database server, or application server — when required for integrations, source data collection, implementation support, or troubleshooting.

Varibill connects using a managed VPN model and a static source IP address that your organization allow-lists for secure, predictable access without exposing services publicly.

For general instructions on creating and running Source Collectors, see: Varibill Cloud Source Collectors – Setup and Configuration Guide

How Varibill Connects

Varibill establishes secure connections through managed VPN infrastructure with a single static IP address, enabling controlled firewall configuration on your side.

Key characteristics of the connection model:

• Encrypted VPN connectivity
• Static source IP address (provided by Varibill)
• No public inbound exposure required on your infrastructure
• Access restricted to explicitly allow-listed ports and services
• Least-privilege access model

When Is Private Infrastructure Access Required?

Varibill may require access to your private infrastructure for the following activities:

• Connecting to on-premise or private-cloud databases
• Accessing customer-hosted virtual machines
• Collecting data from internal systems
• Accessing internal databases for integration configuration, validation, or troubleshooting
• Configuring source collectors or integrations
• Troubleshooting integration or connectivity issues

Customer infrastructure may include virtual machines, databases, file servers, API endpoints, and private cloud instances.

Prerequisites

Before proceeding, ensure that:

• A target private service is provisioned and reachable within your internal network
• Firewall rules explicitly allow inbound access from Varibill’s static IP on the required service ports only
• Credentials have been created for the required access type
• Access is approved per your organizational security policies

Varibill will provide the static source IP address and required ports for your specific integration.

Varibill Connectivity Details

For firewall configuration, allow inbound access from the following:

VPN Endpoint (FQDN)

openvpn-za-north-1.varibill.com

Static Source IP Address

102.37.112.88

Network Configuration Requirements

Allow-Listing Varibill’s Static IP

On your firewall or cloud security group, allow inbound access from Varibill’s static IP address only. Do not allow broad internet access to the target service.

The following table shows a typical firewall rule structure:

Required Ports by Protocol

Only open the ports necessary for your specific integration.

Security Considerations

Least Privilege

• Use a dedicated service account for Varibill access
• Avoid admin or root access unless explicitly required and agreed
• Limit database access to the required schemas or datasets only

Encryption

• Use encrypted database connections (TLS/SSL) where supported
• Use SSH keys instead of passwords where possible
• Disable insecure or deprecated protocols

Logging and Monitoring

• Enable login auditing on target services
• Enable connection logging to maintain a record of access activity

Credential Rotation

• Rotate passwords in line with your organizational policies
• Revoke unused accounts promptly
• Apply key expiration policies where supported

Validation and Support

Once your firewall configuration is complete, email support@varibill.com with the following details:

• Target FQDN or private IP address
• Relevant port number
• Protocol (RDP, SSH, SQL, etc.)
• Environment (preproduction or production)

Varibill will perform a connection test and confirm the result.