> ## Documentation Index
> Fetch the complete documentation index at: https://datum.net/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# ALB limitations and roadmap

> Review what the Datum Application Load Balancer doesn't support yet and where to follow what comes next.

The Application Load Balancer is still being built. This page lists known limitations and where to follow what comes next.

## Limitations

* There is no single composite ALB API yet. An ALB is an `HTTPProxy`, a `TrafficProtectionPolicy`, and optional authentication resources. See [What an ALB is made of](https://datum.net/docs/alb/overview.md#what-an-alb-is-made-of).
* Public traffic is HTTP and HTTPS only. Raw TCP and UDP exposure isn't available.
* Rule exclusions, score thresholds, rate limiting, and circuit breaking aren't available through `datumctl alb`. Use manifests. See [Web application firewall](https://datum.net/docs/alb/configuration/waf.md).
* A `connector` backend must be the only backend in its rule.
* You can't choose which Datum locations serve a load balancer or set its capacity. [Envoy](https://datum.net/docs/platform/envoy.md) in every location serves every load balancer, and Datum scales the fleet.
* Envoy connects to Compute Instances over plain HTTP. TLS ends at the load balancer.
* For limits on load balancers attached to Compute workloads, see [Compute and ALB](https://datum.net/docs/compute/compute-and-alb.md#limitations).

## Roadmap

For what Datum is building next across the platform, see the [Platform roadmap](https://datum.net/docs/platform/roadmap.md).

> [!NOTE]
>
> Plans can change. This list isn't a commitment to deliver any feature or to meet any timeline.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.