Skip to main content
When you run apps for customers, you need to know what keeps working when something goes wrong and who helps you. This page states what Akua does today and what it doesn’t promise yet.

When Akua is unreachable

Your apps run on the servers in your Clusters, not inside Akua’s own platform. These parts depend on Akua being reachable:
  • Public app addresses. Visitors reach an app’s akua.run address through Akua’s edge and a tunnel your Cluster opened. If that path is down, the address doesn’t answer, even when the app itself runs. See App addresses.
  • Changes. Installing, updating and removing apps go through Akua. On an attached cluster, if the cluster agent stops connecting, the Cluster shows agent-offline: workloads keep running, and nothing new rolls out until the agent reconnects. See Attach your Kubernetes cluster.
  • The control plane of a hosted Cluster. Akua runs it. What the apps on a hosted Cluster do while its control plane is unreachable isn’t documented yet.
Akua doesn’t publish an uptime commitment or a public status page yet.

Support by plan

See Pricing for what else each plan includes.

How to reach us

Supported setups and limits

What Akua supports and tests today.

About Akua

The company behind Akua and how to reach it.