> 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/quickstarts/quickstart-single-vm-kots.md). # Single Virtual Machine deployment Single Virtual Machine deployment This quickstart walks you through the minimum steps to deploy CARTO Self-Hosted on a single virtual machine using Kots. For a production-ready installation with full options and explanations, use the [Single Virtual Machine deployment guide](/carto-self-hosted/deployment/single-vm-deployment.md). {% hint style="warning" %} Quickstarts are not suitable for production. For a production-grade installation with full configuration options, use the [Deployment Guides](/carto-self-hosted/deployment.md). {% endhint %} ## Before you begin Complete every item below before starting. Each prerequisite has a dedicated setup guide. Do not skip them. * [ ] **License & customer package** (including `license.yaml`) received from CARTO Support → [License / Customer Package](/carto-self-hosted/planning/prerequisites/license.md) * [ ] **Virtual machine** provisioned and meets the hardware requirements for Single VM deployments (Ubuntu 22.04 / Debian 11+, HTTPS port 443 open) → [Hardware & Software Requirements](/carto-self-hosted/planning/prerequisites/hardware-requirements.md) * [ ] **Metadata database** (PostgreSQL 14+) provisioned and accessible from the VM → [Metadata Database prerequisites](/carto-self-hosted/planning/prerequisites/metadata-database.md) * [ ] **Object storage buckets** created, CORS configured, and permissions set (**Temp Bucket** + **Assets Bucket**) → [Object Storage prerequisites](/carto-self-hosted/planning/prerequisites/object-storage.md) * [ ] **Network egress** open for all required CARTO services → [Network egress requirements](/carto-self-hosted/planning/prerequisites/network/egress.md) * [ ] A domain with DNS control and an SSL/TLS certificate (key **without** passphrase) ## Steps 1. **Provision the VM** and point a DNS record at its external IP. A full domain is required (not a path like `my.domain.com/carto`). 2. **Download and extract the package.** From the customer package URL, select the **CARTO Embedded Cluster** installation and download the binary, then: ```bash tar -xvf carto.tgz ``` 3. **Install the Admin Console** and set a password when prompted: ```bash sudo ./carto install --license license.yaml ``` When it finishes, open the Admin Console at `http://your-server-ip:30000` and configure its SSL certificate.

The Admin Console runs over plain HTTP on port 30000 until you configure a TLS certificate. Restrict this port to your operations team's IP range via firewall/security group rules. Do not leave it open to the public internet. The console holds database credentials, storage keys, and API keys.

To set up HTTPS for the Admin Console, see Updating TLS Certificates in the Replicated documentation.

4. **Configure required settings** in the Admin Console: * **Metadata database** — host, database, and credentials for your external PostgreSQL (plus its CA certificate for TLS). * **Access to CARTO** — your domain and its `.crt` / `.key` certificate. * **Cloud Storage** — your own buckets (see [Configure your own buckets](/carto-self-hosted/configuration/data-and-storage/configure-your-own-buckets.md)). 5. **Deploy.** Click **Continue** to reach the dashboard, review the environment checks, then click **Deploy**. {% hint style="info" %} For optimal load balancer configuration in front of your Single VM, see [Load balancing best practices](/carto-self-hosted/best-practices/deployment/load-balancing-best-practices.md). {% endhint %} ## Verify first success Once deployment completes, confirm the following: * [ ] The CARTO application loads at your configured domain over HTTPS * [ ] You can log in with your admin credentials * [ ] A basic map renders successfully If any check fails, see [Troubleshooting](/carto-self-hosted/operations/troubleshooting.md) and [Debug mode and logs](/carto-self-hosted/operations/troubleshooting/debug-mode-and-logs.md). ## Next steps For a production-ready installation with full configuration options and post-install validation, follow the [Single Virtual Machine deployment guide](/carto-self-hosted/deployment/single-vm-deployment.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 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/quickstarts/quickstart-single-vm-kots.md?ask=&goal= ``` `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.