Edge Network: load-balancing, TLS, and caching

Understand the Koyeb edge network and how to access your Apps from the internet.

All your Apps automatically benefit from our global edge network. Apps get a free subdomain of koyeb.app looking like <appname-orgname>.koyeb.app which is routed via our Global Edge Network. Our Global Edge network provides native load-balancing, TLS encryption, and caching (like a CDN).

HTTP Load-balancing

Our edge network provides global load-balancing capabilities.

If you deploy a service in multiple regions, requests will be routed to the nearest edge location to the end-users. The request will then be routed to the nearest core location where you deployed your service.

Proxy Routing and HTTP Path

When you deploy a new Service and want to make it accessible publicly, you need to define through which HTTP Path requests should be routed to your Service.

Routing rules are evaluated at the Edge to route requests to the right core location depending on where the service lives.

All requests will be proxyfied to the port you selected and load-balanced between your nodes.

Health Checks

To make sure your Services are always up and running, Koyeb automatically perform health checks on your services.

Koyeb currently performs TCP connection and the TCP handshake must fully complete to detect the service as healthy.

Built-in TLS

When you create an app with a public service, end-users connections to your service are automatically encrypted with TLS.

The TLS connections are terminated at the edge to increase performances and are securely transported inside of our encrypted Service Mesh to your application.

CDN and Caching at the Edge

Koyeb caches content according to your headers. Your content is automatically cached in 55 edge locations depending on your users' locations.

Koyeb headers

Koyeb automatically sets standard x-forwarded-for and x-forwarded-host headers for your application to know the IP of the client and the domain which was requested.