> 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/license.md). # License / Customer Package License and customer package requirements for CARTO Self-Hosted ## Overview To deploy CARTO Self-Hosted, you need a valid license and customer package provided by CARTO. If you don't have one yet, contact . ## What's in the customer package The CARTO Support team will provide your customer package and guide you through the initial setup. **Contact** [**support@carto.com**](mailto:support@carto.com) to request your package and receive deployment instructions specific to your environment. Depending on your deployment method, the package includes different files: {% tabs %} {% tab title="☸️ Kots (Admin Console)" %} Kots * A **license file** (`.yaml`) β€” provided by CARTO Support and uploaded to the Kots Admin Console during installation The CARTO Support team will share the license file and provide the Replicated channel URL and any environment-specific instructions needed to complete your installation. {% endtab %} {% tab title="πŸ›ž Helm (customizations.yaml)" %} Helm * `carto-values.yaml` β€” base configuration values for your CARTO release * `carto-secrets.yaml` β€” your license credentials and private registry access The CARTO Support team will share these two files along with the Helm chart version to use and any environment-specific instructions needed to complete your installation. {% endtab %} {% endtabs %} ## License validation CARTO Self-Hosted validates your license against CARTO licensing servers. The license is tied to the domain you configure for your deployment. {% hint style="warning" %} If your license expires, CARTO Self-Hosted will stop working entirely. Ensure you have a renewal process in place before the expiry date. {% endhint %} ## Viewing your license How to view your license details depends on your deployment method: {% tabs %} {% tab title="☸️ Kots (Admin Console)" %} Kots Open the Admin Console and navigate to **License**. The license card shows the license name, type, channel, and expiry status. Click **See license details** to view the full list of entitlements. For any questions about your license (renewals, entitlements, or domain changes), contact . {% endtab %} {% tab title="πŸ›ž Helm (customizations.yaml)" %} Helm Your license is contained in the `carto-secrets.yaml` file provided by CARTO. For any questions about your license (renewals, entitlements, or domain changes), contact . {% endtab %} {% endtabs %} ## Checklist * [ ] You have received your CARTO customer package from support * [ ] You have verified your license is valid for your deployment domain * [ ] You know where to check your license status (Admin Console or via support) --- # 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/planning/prerequisites/license.md?ask=&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.