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

# Concepts

Core concepts behind CARTO Self-Hosted — understand how the platform uses its infrastructure before you configure it

This section explains how CARTO Self-Hosted uses its key infrastructure components. Understanding these concepts helps you make informed decisions when planning, sizing, and configuring your deployment.

<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>Instances, Licenses &#x26; Organizations</strong></td><td>Understand the relationship between CARTO instances, licenses, and organizations — and how to structure dev/prod environments.</td><td><a href="/carto-self-hosted/concepts/instances-tenants-organizations.md">Instances, Licenses &amp; Organizations</a></td></tr><tr><td><strong>How CARTO uses the Metadata Database</strong></td><td>Learn what CARTO stores in PostgreSQL and why an external managed database is recommended for production.</td><td><a href="/carto-self-hosted/concepts/metadata-database.md">How CARTO uses the Metadata Database</a></td></tr><tr><td><strong>How CARTO uses Object Storage</strong></td><td>Understand how CARTO uses blob bucket storage across cloud providers and what data lives there.</td><td><a href="/carto-self-hosted/concepts/object-storage.md">How CARTO uses Object Storage (blob buckets)</a></td></tr><tr><td><strong>How CARTO uses Caches</strong></td><td>Distinguish the user-facing HTTP cache (Varnish) from the internal in-memory store (Valkey), and learn when to configure an external store.</td><td><a href="/carto-self-hosted/concepts/in-memory-cache.md">How CARTO uses Caches</a></td></tr><tr><td><strong>Metadata Database vs. Data Warehouse</strong></td><td>Clarify the distinction between the PostgreSQL metadata database and the data warehouse CARTO connects to.</td><td><a href="/carto-self-hosted/concepts/metadata-database-vs-data-warehouse.md">Metadata Database vs. Data Warehouse</a></td></tr><tr><td><strong>How Configuration Works</strong></td><td>Understand how configuration is managed in CARTO Self-Hosted, and how the Helm (file-based) and Kots (Admin Console) models differ.</td><td><a href="/carto-self-hosted/concepts/configuration-management.md">How Configuration Works</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.carto.com/carto-self-hosted/concepts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.