> 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/getting-started/responsibility-matrix.md). # Responsibility Matrix (RACI) Understand the responsibilities of CARTO vs. your organization {% hint style="info" %} This page is under development. Please contact for assistance with deployment planning. {% endhint %} ## Overview This page outlines the shared responsibility model between CARTO and the customer for a Self-Hosted deployment. Understanding these responsibilities helps you provision the right resources and set expectations accordingly. ## Responsibility matrix | Area | CARTO | Customer | Notes | | ---------------------------------- | ----------- | ----------- | ------------------------------------------------------------------------------------------------------------- | | **Infrastructure provisioning** | | | | | Cloud account and billing | | Responsible | | | Kubernetes cluster setup | Consulted | Responsible | | | DNS configuration | Consulted | Responsible | | | TLS certificates | Consulted | Responsible | | | **Application** | | | | | CARTO container images | Responsible | | | | Application updates and patches | Responsible | Accountable | | | Helm chart / Kots configuration | Responsible | Accountable | | | License management | Responsible | | | | **Database** | | | | | PostgreSQL metadata database | Consulted | Responsible | | | Database backups | Consulted | Responsible | | | Database updates and patching | | Responsible | | | **Networking** | | | | | Firewall and network policies | Consulted | Responsible | | | Load balancer configuration | Consulted | Responsible | | | Proxy configuration | Consulted | Responsible | | | **Security** | | | | | Application security patches | Responsible | | | | Infrastructure security | | Responsible | | | Secret and key management | Consulted | Responsible | | | SSO / Identity provider | Consulted | Responsible | | | **Monitoring and support** | | | | | Application-level monitoring | Consulted | Responsible | | | Infrastructure monitoring | | Responsible | | | Log collection and retention | Consulted | Responsible | CARTO services emit logs to stdout/stderr; collecting, aggregating, and retaining them is your responsibility | | Incident response (application) | Responsible | Informed | | | Incident response (infrastructure) | Consulted | Responsible | | --- # 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/getting-started/responsibility-matrix.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.