> 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/faqs/deployment-options.md).

# Deployment Options

[What are the different deployment options for the CARTO platform?](https://docs.carto.com/faqs/categories/deployment-options/#what-are-the-different-deployment-options-for-the-CARTO-platform)

[Where can I find information about the requirements for deploying CARTO as Self-hosted?](https://docs.carto.com/faqs/categories/deployment-options/#where-can-i-find-information-about-the-requirements-for-deploying-CARTO-as-self-hosted)

[How are updates and product releases managed in a Self-hosted deployment?](https://docs.carto.com/faqs/categories/deployment-options/#how-are-updates-and-product-releases-managed-in-a-self-hosted-deployment)

[Where can I find information about deploying CARTO with Snowflake Container Services?](#where-can-i-find-information-about-deploying-carto-with-snowflake-container-services)

***

#### **What are the different deployment options for the CARTO platform?**

There are two different deployment options for the CARTO platform:

* **CARTO Cloud**: A fully managed SaaS deployment that CARTO hosts on our own cloud. When you use CARTO in our cloud, we manage configuration, updates, and versioning. This option is available in different regions that you can select when [creating your organization](https://docs.carto.com/carto-user-manual/overview/getting-started/#create-a-new-organization).
* **Self-Hosted**: With this option, you host your own CARTO tenant. That means it can be deployed in your virtual private cloud (VPC) or behind your virtual private network (VPN).
* **(BETA) Snowflake Container Services:** Fully deploy CARTO inside Snowflake by leveraging Snowflake Native Apps and Container Services.

#### **Where can I find information about the requirements for deploying CARTO as Self-hosted?**

Find links to the documentation and technical requirements [here](https://github.com/CartoDB/gitbook-documentation/blob/master/faqs/broken-reference/README.md).

#### **How are updates and product releases managed in a Self-hosted deployment?**

While in CARTO Cloud updates and product releases are continously added to the platform, if you’re self-hosting your own CARTO tenant, it will need to be updated periodically to enjoy the latest version of the platform.

The CARTO team publishes versioned releases on the public Self-hosted repositories that can be used to upgrade your deployment. Find the latest releases for [Docker](https://github.com/CartoDB/carto-selfhosted/releases/latest) and [Kubernetes](https://github.com/CartoDB/carto-selfhosted-helm/releases/latest)

#### **Where can I find information about deploying CARTO with Snowflake Container Services?**

Find links to the documentation [here](https://github.com/CartoDB/gitbook-documentation/blob/master/faqs/broken-reference/README.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 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/faqs/deployment-options.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.