Networking

A public URL the moment you expose a port.

Every exposed port gets an HTTPS address on akua.run, with no DNS and no certificates to set up. Preview builds get their own. Your own domain comes through your own Cloudflare account, and the gateway underneath is yours to choose.

Docs
Managed hostname https://dispatch-northgate.akua.run the moment you expose a port
Preview build https://pr-142-dispatch-northgate.akua.run per pull request
Your own domain https://app.northgate.example your Cloudflare, your rules
TLS at the edge, a tunnel to your cluster · no DNS, no certificates, no public IP

The question

Do I need a public IP?

No. Traffic enters at Cloudflare’s edge and reaches your cluster through a tunnel, so your servers stay closed to the internet. Your app still runs on your infrastructure, not on ours. Want full control? Bring your own tunnel, or point your DNS straight at your nodes.

What is in it

Networking, piece by piece.

What each part does, and whether you can use it today.

Custom domains

Beta

Bring your own apex / subdomain; managed TLS.

Managed hostnames

Beta

Instant *.akua.run URL for every exposed port. No DNS, no certificates.

Preview hostnames

Beta

Short-lived *.akua.run URLs for preview builds.

Gateway / HTTPRoute

Beta

Multi-provider Gateway API: Cloudflare Tunnels, Nginx, Traefik, Envoy, Kong.

Cloudflare DNS + WAF

Beta

Edge security and DNS for delivered products.

Enterprise bypass

Soon

Take the dispatch Worker out of the data path for enterprise contracts.

What it costs

The platform is a flat fee. Compute is at cost.

Free to start with one managed cluster and one machine. Pro is €20 per workspace and month. Your own cloud key removes every limit, and Akua never marks up compute.

See the plans

Start with networking
on your own terms.

Free to begin, on Akua-managed machines or your own cloud key.

Docs