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

# Supported setups and limits

> Which server and cluster setups Akua supports and tests today, and the limits you should know before you decide

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](https://docs.akua.dev/trust/about.md#contact) and we help you check
it.

## Where apps can run

Every app runs on a Cluster. Akua supports two kinds:

| Setup | What you provide | Requirements |
| - | - | - |
| A hosted Cluster with your own Linux server | A server you run, joined with a one-time command. Akua runs the control plane. | Linux with systemd on x86-64 or ARM64, at least 2 CPUs and 4 GB of memory, root access over SSH, outbound internet access ([server requirements](https://docs.akua.dev/customers/server-requirements.md)) |
| Your own Kubernetes cluster, attached | A cluster you already run. You install the Akua cluster agent with one Helm command. | `kubectl` and `helm` access, and the permissions you choose to grant |

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](https://docs.akua.dev/compute/overview.md) that Akua orders and runs for
you, such as the free trial server.

[Server requirements](https://docs.akua.dev/customers/server-requirements.md) gives the details for a customer's server,
and [Attach your Kubernetes cluster](https://docs.akua.dev/clusters/import.md) 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](https://docs.akua.dev/installs/lifecycle.md#update-an-installation).
* **Local-path storage keeps data on one server.** It doesn't replicate data between servers. See
  [Storage](https://docs.akua.dev/storage.md#local-path).
* **No formal certifications yet.** See [Security](https://docs.akua.dev/platform/security.md#compliance).

Plan limits, such as how many hosted Clusters and Akua servers a Workspace can have, are in
[Pricing](https://docs.akua.dev/pricing.md#plan-comparison) and [Quotas and limits](https://docs.akua.dev/platform/quotas.md).

## Related topics

> [card] [Your data and servers](https://docs.akua.dev/platform/byoc.md)
>
> What Akua stores and who secures what.

> [card] [Reliability and support](https://docs.akua.dev/trust/reliability-and-support.md)
>
> What happens when Akua is unreachable, and how to get help.


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