Nova allows for easy creation of Load Balancers with simple or advanced configurations for specific protocols - most commonly HTTP(S). You can also create custom TCP Load Balancers with ports mapped as necessary.

All the ADC types can send data to any of the ADC Backends allowed by Nova, including manual IP addresses, Service Discovery and Cloud API conections.

Interface Example



The HTTP ADC is a plain text Layer 7 HTTP to HTTP proxy, supporting sticky sessions, HTTP health checking and web acceleration. This is ideal for websites running plain HTTP (port 80).


The SSL ADC is a Layer 7 SSL HTTPS to HTTP/S proxy, supporting sticky sessions, HTTP health checking and web acceleration. You can terminate SSL on Nova, or re-encrypt after decryption to pass the traffic through.

Most of the advanced HTTP/S functionality in Nova requires being able to read the SSL certificates.

HTTPS Passthrough

The HTTPS ADC is a Layer 4 SSL HTTPS to HTTPS proxy, very similar to a custom TCP ADC. It passes the traffic through without decrypting it, meaning you do not need to load SSL certificates, but your functionality is limited.

Microsoft Exchange

Microsoft Exchange requires a large number of ports and URLs to be load balanced through to work properly. The Exchange ADC type will ensure this is all handled, as well as configuring the right timeouts and properties for your Exchange/DAC cluster.


The RDP ADC allows you to load balance data to any RDP service (typically Microsoft RDS) and can send data to connection brokers or directly to the RDP servers themselves. It automatically supports RDP cookies for user stickiness and handles your timeouts, user migration, etc.


The MySQL ADC allows you to load balance queries to your MySQL (or MariaDB) systems. It supports Layer 7 health checks and requires a user be added to your SQL servers in order for us to check their health.

mysql -u root -p

USE mysql;
INSERT INTO user (HOST, USER) VALUES('192.168.0.%', 'nova');

flush privileges;

The example above adds a user called nova with a source of

API Gateway

The API ADC is a Layer 7 SSL HTTPS to HTTP/S proxy. It's very similar to the SSL ADC type but supports additional API specific features, advanced routing, and most importantly JWT-based authentication.

Agent-based WAF

The agent-based WAF (Web Application Firewall) is a Layer 7 HTTP/S proxy. It's very similar to the HTTP and SSL ADC types, but is intended to run directly on an application server (e.g. webserver) to provide WAF functionality. A docker installation is suitable for this ADC type.

Custom TCP

This ADC is for anything that isn't easily covered by the types above. You can define your own backends, ports and routing behaviour. Visibility is limited compared to other types, especially encrypted traffic.