> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-self-hosted/planning/prerequisites/hardware-requirements.md).

# Hardware & Software Requirements

The hardware and software requirements below must be met to ensure optimal performance of the CARTO platform. Requirements differ by [deployment method](/carto-self-hosted/planning/deployment-methods.md).

## Recommended background

Before proceeding with the installation, it is recommended that the individual performing the setup is familiar with cloud environments, specifically [GCP](https://cloud.google.com/) (Google Cloud Platform), [AWS](https://aws.amazon.com/) (Amazon Web Services), or [Azure](https://azure.microsoft.com/) (Microsoft Azure). This prior experience ensures a smoother deployment process and a better understanding of the underlying infrastructure.

1. **Cloud Platform Proficiency:** Basic proficiency in the chosen cloud platform is recommended. This includes the ability to navigate the respective console, manage instances or clusters, and configure networking settings.
2. **Account Authorization:** Ensure that you have the necessary permissions and access rights within your cloud platform account. This typically involves appropriate role assignments.
3. **Resource Understanding:** A grasp of fundamental concepts such as virtual machines, Kubernetes, storage, and networking within your chosen cloud environment will enhance your ability to deploy and manage resources effectively.

Select your deployment method below.

{% tabs %}
{% tab title="Single Virtual Machine" %}
**Operating system**

| Requirement | Value                            |
| ----------- | -------------------------------- |
| OS          | Ubuntu 22.04, Debian 11 or above |

**CPU, memory and disk**

| Requirement  | AI Features disabled | AI Features enabled |
| ------------ | -------------------- | ------------------- |
| CPU (x86)    | 8                    | 16                  |
| Memory       | 32 GB                | 64 GB               |
| Disk size    | 60 GB                | 60 GB               |
| {% endtab %} |                      |                     |

{% tab title="Orchestrated (Kubernetes — Kots & Helm)" %}
**Cluster**

| Requirement                                 | Value                                                  |
| ------------------------------------------- | ------------------------------------------------------ |
| Kubernetes                                  | 1.29 or above                                          |
| [Helm](https://helm.sh/docs/intro/install/) | 3.6.0 or above                                         |
| Nodes                                       | At least 3 nodes with 4 vCPUs and 16 GB of memory each |
| Namespace                                   | An isolated namespace per CARTO installation           |

**Kots only:** persistent volumes must be configured in your cluster, because the Admin Console stores configuration changes in a persistent volume.
{% endtab %}
{% endtabs %}

## Checklist

* [ ] Your deployment method is chosen ([Choosing a deployment method](/carto-self-hosted/planning/deployment-methods/choosing-a-deployment-method.md))
* [ ] Host OS / Kubernetes version meets the minimums above
* [ ] CPU, memory, and disk meet the minimums for your method (and AI features, if enabled)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.carto.com/carto-self-hosted/planning/prerequisites/hardware-requirements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.