> 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/deployment-methods/choosing-a-deployment-method.md).

# Choosing a Deployment Method

There is no better or preferred deployment method. The right choice depends on your team's experience, your scalability needs, and how much you want to customize the deployment. Use the guidance below to decide.

## Which method is for you?

Start with the [**deployment methods at a glance**](/carto-self-hosted/planning/deployment-methods.md#deployment-methods-at-a-glance) comparison, then match your situation against the table below: find the rows that describe you and pick the column with the most matches.

| Your situation                                           | <p><img src="/files/5KoQqAIFdjmLp1ee8tV1" alt="" data-size="original"></p><p><a href="/pages/RrDOn1ekzI5KcJ6fdoZi">Single Virtual Machine</a></p> | <p><img src="/files/7CB4nZG6kAUHKqcs0AXw" alt="" data-size="original"></p><p><a href="/pages/ug8FFIHjqqG3m3XI2PfA">Standard Orchestrated</a></p> | <p><img src="/files/8gcUtLEi7XgPb1vQuIPr" alt="" data-size="original"></p><p><a href="/pages/RaBB2l7jchf0I0BpExtJ">Advanced Orchestrated</a></p> |
| -------------------------------------------------------- | :-----------------------------------------------------------------------------------------------------------------------------------------------: | :----------------------------------------------------------------------------------------------------------------------------------------------: | :----------------------------------------------------------------------------------------------------------------------------------------------: |
| Evaluating CARTO or deploying for the first time         |                                                                         ✅                                                                         |                                                                                                                                                  |                                                                                                                                                  |
| Limited Kubernetes / DevOps experience                   |                                                                         ✅                                                                         |                                                                                                                                                  |                                                                                                                                                  |
| Want a lightweight, low-cost, low-maintenance deployment |                                                                         ✅                                                                         |                                                                                                                                                  |                                                                                                                                                  |
| Small-scale or single-server environment                 |                                                                         ✅                                                                         |                                                                                                                                                  |                                                                                                                                                  |
| Already run Kubernetes for other applications            |                                                                                                                                                   |                                                                         ✅                                                                        |                                                                         ✅                                                                        |
| Require scalability, high availability, and resilience   |                                                                                                                                                   |                                                                         ✅                                                                        |                                                                         ✅                                                                        |
| Prefer to manage config & maintenance through a UI       |                                                                                                                                                   |                                                                         ✅                                                                        |                                                                                                                                                  |
| Comfortable with Helm charts and terminal-based installs |                                                                                                                                                   |                                                                                                                                                  |                                                                         ✅                                                                        |
| Need full control over advanced customizations           |                                                                                                                                                   |                                                                                                                                                  |                                                                         ✅                                                                        |

{% hint style="info" %}
Both orchestrated methods (**Standard Orchestrated** with Kots and **Advanced Orchestrated** with Helm) run on any standard Kubernetes cluster. See [**Managing Kubernetes: Kots and Helm**](/carto-self-hosted/planning/deployment-methods.md#managing-kubernetes-kots-and-helm) for how the two approaches compare.
{% endhint %}

## Installation options: Self-Service and Assisted

CARTO Self-hosted offers flexibility in the installation process to accommodate a range of customer preferences and infrastructure complexities. For customers with technical expertise and a straightforward setup, we offer a **Self-Service installation** option, enabling you to independently install and configure the product using our comprehensive installation guides.

However, we understand some organizations may have intricate setups such as Virtual Private Cloud (VPC), VPN, restricted network access, HTTPS proxy, or other specialized requirements. In such cases, we offer **Assisted installations**, where our expert team collaborates closely with you to ensure a seamless and tailored deployment.

If you require an **Assisted installation,** please [book time with us](mailto:support@carto.com).

## Next steps

Once you've chosen a method:

1. Review the [**Prerequisites & Checklists**](/carto-self-hosted/planning/prerequisites.md) for your environment.
2. Follow the matching deployment guide:
   * [Single Virtual Machine deployment](/carto-self-hosted/deployment/single-vm-deployment.md)
   * [Standard Orchestrated container deployment](/carto-self-hosted/deployment/kubernetes-kots.md)
   * [Advanced Orchestrated container deployment](/carto-self-hosted/deployment/kubernetes-helm.md)


---

# 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/deployment-methods/choosing-a-deployment-method.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.