Skip to content
Odinex Cloud
DELog inSign up

Networking

Load balancers for TCP and HTTP with health checks

An Odinex load balancer has its own public IPv4 and IPv6 address and forwards TCP or HTTP traffic to a group of servers. It checks the health of every target and only sends traffic to healthy ones. Targets can be single servers, every server with a given label, or public IP addresses.

Get started Read the docs

At a glance

Protocols
TCP, HTTP
Addresses
Own public IPv4 and IPv6
Targets
Server, label selector, IP
Algorithms
Round robin, least connections
Billing
Hourly by type, capped monthly

Key features

  • TCP and HTTP

    Forward any TCP port, or HTTP with sticky sessions. For HTTPS, pass TCP 443 through to your servers.

  • Health checks

    TCP or HTTP checks with your own path, interval and expected status codes.

  • Targets by label

    Point the load balancer at role=web and new servers with that label are added automatically.

  • Client addresses

    Send the PROXY protocol header so your servers see the real client IP.

  • Private targets

    Attach the load balancer to a private network and balance servers that have no public address.

  • Two algorithms

    Round robin or least connections, per load balancer.

What it is used for

  • Scale a web app

    Run several application servers behind one address and add more by giving them the right label.

  • Zero-downtime deploys

    Replace servers one at a time; health checks keep traffic away from servers that are not ready.

  • Private backends

    Keep application servers off the internet and expose only the load balancer.

Try it

odx CLI
odx load-balancer create --name lb-1 --type lb11 --location fra1
odx load-balancer add-service --protocol http --listen-port 80 --destination-port 8080 lb-1
odx load-balancer add-target --label-selector role=web lb-1

Documentation

Works well with

Load balancers: questions and answers

Clear answers about location, infrastructure and billing.

Does the load balancer terminate TLS?
No. For HTTPS, use a TCP service on port 443 and terminate TLS on your servers. Add the PROXY protocol if they need the client address.
Can it balance servers without public IPs?
Yes. Attach the load balancer to the private network; server targets are then reached on their private addresses.
How do label targets work?
A label selector such as role=web matches every server in the project with that label, and the list is kept up to date as servers come and go.
Can I change the size later?
Yes. Change the load balancer type at any time, as long as the current services and targets fit the new type.

Build it in Frankfurt today

Create an account, top up from €5 and pay by the hour, never more than the monthly price.

Deploy your first server See all plans