Skip to main content
Before you commit, you want to know exactly where Akua works today and where it doesn’t. This page lists the setups Akua supports, the ones it tests from start to finish, and the current limits. Anything not listed here isn’t tested yet; ask us and we help you check it.

Where apps can run

Every app runs on a Cluster. Akua supports two kinds: Tested from start to finish: a Hetzner Cloud CPX22 server with Ubuntu 24.04 joined to a hosted Cluster, and an attached Kubernetes cluster. Other Linux systems, processors and providers aren’t tested yet. A hosted Cluster can also use an Akua server that Akua orders and runs for you, such as the free trial server. Server requirements gives the details for a customer’s server, and Attach your Kubernetes cluster describes the agent’s access.

Current limits

  • Public addresses use akua.run. Every app gets an HTTPS address on akua.run; custom domains aren’t available yet.
  • Customers update their own copy. When you share an app, the customer’s Workspace belongs to the customer. A new version you publish doesn’t change their copy automatically. The customer can move their copy to any version you publish later, without a new invite link. You can’t sign in to their Workspace or update their copy for them.
  • Updates run from the CLI. The dashboard has no update control yet. You and your customers update an Install with akua installs update; see Update an installation.
  • Local-path storage keeps data on one server. It doesn’t replicate data between servers. See Storage.
  • No formal certifications yet. See Security.
Plan limits, such as how many hosted Clusters and Akua servers a Workspace can have, are in Pricing and Quotas and limits.

Your data and servers

What Akua stores and who secures what.

Reliability and support

What happens when Akua is unreachable, and how to get help.