Private IP and Load Balancer Addon

Under normal circumstances, the Servd platform groups projects into a number of clusters with each cluster operating a single, public inbound traffic load balancer, handling all of the traffic for the cluster. This addon allows you to create a separate private load balancer with its own IP address to handle your project's traffic. This ensures that any large scale attack against Servd's standard infrastructure will not have a knock on impact on your project's availability.

We recommend adding CloudFlare in front of your private IP address in order to ensure it remains hidden from any potential attackers. This setup provides the most robust defence against any potential attackers. Servd's direct integration with CloudFlare also allows any necessary DNS changes to be made automatically on your behalf in order to get your Private Load Balancer up and running.

This addon is applied only once. If a private load balancer is already included in your Servd plan, you will not be able to select this addon.

Applying this addon

To add this addon to your project, do the following:

  1. Visit the "Addons" section your project's Plan page.

  2. Under the "Private IP and Load Balancer" row, click the "Add" button to view the price breakdown (no change will be made or charge taken at this point)

  3. Click the confirm button to apply the addon. This will take a charge from your team's billing card and then immediately perform a sync afterwards to deploy the upgrade.

  4. If any of your project's DNS domains are using A records, then you will need to manually update them to the new IP address referenced in the "DNS Instructions" section of your project's Domains page.

    If all DNS domains pointing to your Servd project are CNAME records, or you have connected your project to your CloudFlare account, then no further changes are required. We'll automatically update things so that your project's traffic goes via your new private load balancer.

Once the addon is applied, traffic will still route correctly via the cluster's public load balancer to your project. This means you won't see any downtime if you need to change any of your DNS records.