Skip to main content
Datum Cloud exposes the Gateway API — an open, portable standard for routing service traffic. Rather than a single monolithic object, the Gateway API splits traffic handling into a small set of composable resources, so you can describe the infrastructure, the entry points, and the routing rules independently and let them reference one another.
These resources follow the Gateway API standard and are served at the stable v1 version.

​
How the resources compose

The Gateway API resources build on one another, from the underlying infrastructure up to the individual routing rules:
  • Gateway binds listeners and addresses. It instantiates a GatewayClass, opening one or more listeners (protocol, port, and hostname) at network addresses where traffic arrives.
  • HTTPRoute routes HTTP requests to backends. It attaches to a Gateway and describes how matching requests are filtered and forwarded to backend services.
  • BackendTLSPolicy configures TLS to backends. It describes how a Gateway establishes a TLS connection to the backends that an HTTPRoute forwards to.

Gateway

Bind listeners and addresses where traffic enters the platform.

HTTPRoute

Route HTTP requests to backends with matches, filters, and forwarding rules.

BackendTLSPolicy

Configure the TLS connection a Gateway makes to its backends.
Platform-provided: the GatewayClass referenced by a gateway lives under Platform resources. You create and update these resources declaratively with datumctl apply -f, and inspect them with datumctl get and datumctl describe.

​
Relationship to HTTPProxy

The Gateway API resources and Datum’s higher-level HTTPProxy are both ways to expose HTTP services on Datum Cloud. HTTPProxy builds on top of Gateway API resources to cover simple reverse-proxy use cases without configuring the underlying gateway resources directly, while the Gateway API resources give you direct control over classes, listeners, routes, and backend TLS. Which fits depends on how much of the routing surface you need to manage yourself.

​
Learn more

Last modified on July 2, 2026