> 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/overview.md).

# Overview

CARTO Self-Hosted is a deployment of the full CARTO platform on infrastructure you control. It is designed for organizations that need data to remain within their network — common in healthcare, finance, insurance, and telco industries — and for scenarios where cloud-managed CARTO cannot reach your data warehouse due to VPC or VPN restrictions.

CARTO Self-Hosted runs on any major cloud provider (GCP, AWS, Azure) or on-premises, using either a Single Virtual Machine or a Kubernetes cluster.

***

## Is CARTO Self-Hosted right for you?

We recommend CARTO Self-Hosted if **any** of the following apply:

* Your data warehouse is inside a private VPC or VPN and cannot be reached from CARTO Cloud.
* Your organization has regulatory or contractual requirements that prevent data from leaving your network.
* You need full control over the deployment environment, infrastructure, and upgrade cadence.

If none of the above apply, [CARTO Cloud](/faqs/deployment-options.md#what-are-the-different-deployment-options-for-the-carto-platform) may be a simpler option.

***

## Your journey

Every Self-Hosted deployment follows the same path. Click any step to jump to that section.

|        Step       | What you do                                                                | Where to go                                                                                                                     |
| :---------------: | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **1. Understand** | Learn key concepts and architecture before you commit to a method          | [Getting Started](/carto-self-hosted/getting-started.md) · [Concepts](/carto-self-hosted/concepts.md)                           |
|    **2. Plan**    | Choose a deployment method, verify prerequisites, size your infrastructure | [Plan Your Deployment](/carto-self-hosted/planning.md)                                                                          |
|   **3. Deploy**   | Follow the step-by-step guide for your chosen method                       | [Quickstarts](/carto-self-hosted/quickstarts.md) *(POC)* · [Deployment Guides](/carto-self-hosted/deployment.md) *(production)* |
|  **4. Configure** | Set up storage, networking, authentication, and integrations               | [Configuration Guides](/carto-self-hosted/configuration.md)                                                                     |
|   **5. Operate**  | Upgrade, back up, monitor, and troubleshoot over time                      | [Operations & Maintenance](/carto-self-hosted/operations.md)                                                                    |

***

## Documentation sections

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Getting Started</strong></td><td>Architecture overview, glossary, and responsibility matrix.</td><td><a href="/pages/EOVpuGWyK0BXk3bXroZc">/pages/EOVpuGWyK0BXk3bXroZc</a></td></tr><tr><td><strong>Concepts</strong></td><td>Understand how CARTO uses the metadata database, object storage, and in-memory cache.</td><td><a href="/pages/mvTwhhvlCGRqWCvLsu9j">/pages/mvTwhhvlCGRqWCvLsu9j</a></td></tr><tr><td><strong>Plan Your Deployment</strong></td><td>Choose a deployment method, review prerequisites, and plan for capacity.</td><td><a href="/pages/GgChwq1mf20MostD5ht1">/pages/GgChwq1mf20MostD5ht1</a></td></tr><tr><td><strong>Quickstarts</strong></td><td>Fast, copy-paste deployments for POCs and evaluations.</td><td><a href="/pages/dfL5QtzvMVoeGhUXmrei">/pages/dfL5QtzvMVoeGhUXmrei</a></td></tr><tr><td><strong>Deployment Guides</strong></td><td>Step-by-step production install instructions for the Single Virtual Machine, Standard Orchestrated, and Advanced Orchestrated deployment methods.</td><td><a href="/pages/y4RxPCOh1w06u5ANtHyN">/pages/y4RxPCOh1w06u5ANtHyN</a></td></tr><tr><td><strong>Configuration Guides</strong></td><td>Configure storage, networking, authentication, integrations, and advanced options.</td><td><a href="/pages/o9z4sy5HiC5f9FqeBTmX">/pages/o9z4sy5HiC5f9FqeBTmX</a></td></tr><tr><td><strong>Operations &#x26; Maintenance</strong></td><td>Manage updates, backups, monitoring, key rotation, scaling, and troubleshooting.</td><td><a href="/pages/mQQvlCvTmcclsbQHlS3F">/pages/mQQvlCvTmcclsbQHlS3F</a></td></tr><tr><td><strong>Technical Reference</strong></td><td>Component catalog, Helm chart values, environment variables, and network ports.</td><td><a href="/pages/75Q6HURjjz3o29wxF3nl">/pages/75Q6HURjjz3o29wxF3nl</a></td></tr><tr><td><strong>Best Practices</strong></td><td>Recommendations for deployment, security, and ongoing operations.</td><td><a href="/pages/vYXerVWh4nF5exe3UHwa">/pages/vYXerVWh4nF5exe3UHwa</a></td></tr><tr><td><strong>Release Notes</strong></td><td>Changes introduced in each CARTO Self-Hosted release version.</td><td><a href="/pages/bDddXkUezz5UkejnQDMd">/pages/bDddXkUezz5UkejnQDMd</a></td></tr></tbody></table>


---

# 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/overview.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.