Skip to content
Apex
Aether Cloud / Networking / Load balancing
Aether Cloud · Networking

Load balancing.

Layer-4 and layer-7 load balancing with health checks, TLS termination and autoscaling backends.

⌗ Networking
Overview

Global and regional load balancing across L4 and L7, with health checking, TLS termination and content-based routing — distributing traffic so a failed instance is never a failed request.

Where it sits
Category
Networking
Deployment
Managed → air-gapped
Governance
IAM · encryption · audit
How it works

Three steps to running.

01
Front your service

Put an L4 or L7 balancer in front of autoscaling backends.

02
Route intelligently

Path and header rules, TLS termination, canary and mirror.

03
Stay healthy

Unhealthy backends are drained automatically; one anycast address routes globally.

What you get

Load balancing, in full.

L4 and L7

TCP/UDP and HTTP-aware routing with path and header rules.

Health-aware

Automatic removal of unhealthy backends and graceful draining.

Managed TLS

TLS termination with auto-renewed certificates and modern ciphers.

Global anycast

One address, routed to the nearest healthy region.

API-first

Provision it in a few lines.

Every service is reachable from the same SDK, CLI and infrastructure-as-code — one identity, one bill, one audit trail across the whole catalog.

# Provision load balancing on Aether Cloud
aether networking create \
  --service load-balancing \
  --name app \
  --region us-1 \
  --deploy managed   # or vpc | on-prem | air-gapped
Specs

At a glance.

Layers
L4 (TCP/UDP) + L7 (HTTP)
TLS
Managed, auto-renewed certs
Routing
Path · header · weight
Health
Auto drain + failover
Reach
Global anycast
Use cases

Built for real work.

01

High-availability web services

02

Blue-green and canary routing

03

Global traffic distribution

Why one platform

On one model, not stitched together.

The usual stack runs load balancing in one product, the model in another and the data in a third — and the seams between them are the cost. Aether Cloud runs it on the same platform that serves the model, governs your identity and deploys into your boundary, with the rest of the catalog one hop away.

One platform

No stitching a vector DB to one place, a warehouse to another and a model to a third — load balancing sits next to the rest of the catalog, one identity, one bill.

The model is here

The provider that runs Aether runs your load balancing — so the data and the model never leave the same governed boundary to talk to each other.

Built on demand

Need a capability that isn’t here yet? The model writes and deploys it into the same boundary — the catalog is a starting point, not a ceiling.

FAQ

Good to know.

How does this compare to AWS ELB?

L4/L7 load balancing with health checks and global anycast — integrated with autoscaling and the mesh.

Does it do canary releases?

Yes — weighted and mirrored routing for canary and blue-green.

Is TLS managed?

Yes — termination with auto-renewed certificates and modern ciphers.

Deploy anywhere

Your boundary, your choice.

Managed
Your VPC
On-prem
Air-gapped / sovereign

Run Load balancing on Aether Cloud.

Layer-4 and layer-7 load balancing with health checks, TLS termination and autoscaling backends. Deployable managed, in your VPC, on-prem or fully air-gapped — talk to us about the configuration your workloads and your boundary require.