LogoLogo
HomeAcademyLoginTry for free
  • Welcome
  • What's new
    • Q2 2025
    • Q1 2025
    • Q4 2024
    • Q3 2024
    • Q2 2024
    • Q1 2024
    • Q4 2023
    • Q3 2023
    • Q2 2023
    • Q1 2023
    • Q4 2022
    • Q3 2022
  • FAQs
    • Accounts
    • Migration to the new platform
    • User & organization setup
    • General
    • Builder
    • Workflows
    • Data Observatory
    • Analytics Toolbox
    • Development Tools
    • Deployment Options
    • CARTO Basemaps
    • CARTO for Education
    • Support Packages
    • Security and Compliance
  • Getting started
    • What is CARTO?
    • Quickstart guides
      • Connecting to your data
      • Creating your first map
      • Creating your first workflow
      • Developing your first application
    • CARTO Academy
  • CARTO User Manual
    • Overview
      • Creating your CARTO organization
      • CARTO Cloud Regions
      • CARTO Workspace overview
    • Maps
      • Data sources
        • Simple features
        • Spatial Indexes
        • Pre-generated tilesets
        • Rasters
        • Defining source spatial data
        • Managing data freshness
        • Changing data source location
      • Layers
        • Point
          • Grid point aggregation
          • H3 point aggregation
          • Heatmap point aggregation
          • Cluster point aggregation
        • Polygon
        • Line
        • Grid
        • H3
        • Raster
        • Zoom to layer
      • Widgets
        • Formula widget
        • Category widget
        • Pie widget
        • Histogram widget
        • Range widget
        • Time Series widget
        • Table widget
      • SQL Parameters
        • Date parameter
        • Text parameter
        • Numeric parameter
        • Publishing SQL parameters
      • Interactions
      • Legend
      • Basemaps
        • Basemap selector
      • AI Agents
      • SQL analyses
      • Map view modes
      • Map description
      • Feature selection tool
      • Search locations
      • Measure distances
      • Exporting data
      • Download PDF reports
      • Managing maps
      • Publishing and sharing maps
        • Map settings for viewers
        • Map preview for editors
        • Collaborative maps
        • Embedding maps
        • URL parameters
      • Performance considerations
    • Workflows
      • Workflow canvas
      • Results panel
      • Components
        • Aggregation
        • Custom
        • Data Enrichment
        • Data Preparation
        • Generative AI
        • Input / Output
        • Joins
        • Parsers
        • Raster Operations
        • Spatial Accessors
        • Spatial Analysis
        • Spatial Constructors
        • Spatial Indexes
        • Spatial Operations
        • Statistics
        • Tileset Creation
        • BigQuery ML
        • Snowflake ML
        • Google Earth Engine
        • Google Environment APIs
        • Telco Signal Propagation Models
      • Data Sources
      • Scheduling workflows
      • Sharing workflows
      • Using variables in workflows
      • Executing workflows via API
      • Temporary data in Workflows
      • Extension Packages
      • Managing workflows
      • Workflows best practices
    • Data Explorer
      • Creating a map from your data
      • Importing data
        • Importing rasters
      • Geocoding data
      • Optimizing your data
    • Data Observatory
      • Terminology
      • Browsing the Spatial Data Catalog
      • Subscribing to public and premium datasets
      • Accessing free data samples
      • Managing your subscriptions
      • Accessing your subscriptions from your data warehouse
        • Access data in BigQuery
        • Access data in Snowflake
        • Access data in Databricks
        • Access data in Redshift
        • Access data in PostgreSQL
    • Connections
      • Google BigQuery
      • Snowflake
      • Databricks
      • Amazon Redshift
      • PostgreSQL
      • CARTO Data Warehouse
      • Sharing connections
      • Deleting a connection
      • Required permissions
      • IP whitelisting
      • Customer data responsibilities
    • Applications
    • Settings
      • Understanding your organization quotas
      • Activity Data
        • Activity Data Reference
        • Activity Data Examples
        • Activity Data Changelog
      • Users and Groups
        • Inviting users to your organization
        • Managing user roles
        • Deleting users
        • SSO
        • Groups
        • Mapping groups to user roles
      • CARTO Support Access
      • Customizations
        • Customizing appearance and branding
        • Configuring custom color palettes
        • Configuring your organization basemaps
        • Enabling AI Agents
      • Advanced Settings
        • Managing applications
        • Configuring S3 Bucket for Redshift Imports
        • Configuring OAuth connections to Snowflake
        • Configuring OAuth U2M connections to Databricks
        • Configuring S3 Bucket integration for RDS for PostgreSQL Exports in Builder
        • Configuring Workload Identity Federation for BigQuery
      • Data Observatory
      • Deleting your organization
    • Developers
      • Managing Credentials
        • API Base URL
        • API Access Tokens
        • SPA OAuth Clients
        • M2M OAuth Clients
      • Named Sources
  • Data and Analysis
    • Analytics Toolbox Overview
    • Analytics Toolbox for BigQuery
      • Getting access
        • Projects maintained by CARTO in different BigQuery regions
        • Manual installation in your own project
        • Installation in a Google Cloud VPC
        • Core module
      • Key concepts
        • Tilesets
        • Spatial indexes
      • SQL Reference
        • accessors
        • clustering
        • constructors
        • cpg
        • data
        • http_request
        • import
        • geohash
        • h3
        • lds
        • measurements
        • placekey
        • processing
        • quadbin
        • random
        • raster
        • retail
        • routing
        • s2
        • statistics
        • telco
        • tiler
        • transformations
      • Guides
        • Running queries from Builder
        • Working with Raster data
      • Release notes
      • About Analytics Toolbox regions
    • Analytics Toolbox for Snowflake
      • Getting access
        • Native App from Snowflake's Marketplace
        • Manual installation
      • Key concepts
        • Spatial indexes
        • Tilesets
      • SQL Reference
        • accessors
        • clustering
        • constructors
        • data
        • http_request
        • import
        • h3
        • lds
        • measurements
        • placekey
        • processing
        • quadbin
        • random
        • raster
        • retail
        • s2
        • statistics
        • tiler
        • transformations
      • Guides
        • Running queries from Builder
        • Working with Raster data
      • Release Notes
    • Analytics Toolbox for Databricks
      • Getting access
        • Personal (former Single User) cluster
        • Standard (former Shared) cluster
      • Reference
        • lds
        • tiler
      • Guides
      • Release Notes
    • Analytics Toolbox for Redshift
      • Getting access
        • Manual installation in your database
        • Installation in an Amazon Web Services VPC
        • Core version
      • Key concepts
        • Tilesets
        • Spatial indexes
      • SQL Reference
        • clustering
        • constructors
        • data
        • http_request
        • import
        • lds
        • placekey
        • processing
        • quadbin
        • random
        • s2
        • statistics
        • tiler
        • transformations
      • Guides
        • Running queries from Builder
      • Release Notes
    • Analytics Toolbox for PostgreSQL
      • Getting access
        • Manual installation
        • Core version
      • Key concepts
        • Tilesets
        • Spatial Indexes
      • SQL Reference
        • h3
        • quadbin
        • tiler
      • Guides
        • Creating spatial index tilesets
        • Running queries from Builder
      • Release Notes
    • CARTO + Python
      • Installation
      • Authentication Methods
      • Visualizing Data
      • Working with Data
        • How to work with your data in the CARTO Data Warehouse
        • How to access your Data Observatory subscriptions
        • How to access CARTO's Analytics Toolbox for BigQuery and create visualizations via Python notebooks
        • How to access CARTO’s Analytics Toolbox for Snowflake and create visualizations via Python notebooks
        • How to visualize data from Databricks
      • Reference
    • CARTO QGIS Plugin
  • CARTO for Developers
    • Overview
    • Key concepts
      • Architecture
      • Libraries and APIs
      • Authentication methods
        • API Access Tokens
        • OAuth Access Tokens
        • OAuth Clients
      • Connections
      • Data sources
      • Visualization with deck.gl
        • Basemaps
          • CARTO Basemap
          • Google Maps
            • Examples
              • Gallery
              • Getting Started
              • Basic Examples
                • Hello World
                • BigQuery Tileset Layer
                • Data Observatory Tileset Layer
              • Advanced Examples
                • Arc Layer
                • Extrusion
                • Trips Layer
            • What's New
          • Amazon Location
            • Examples
              • Hello World
              • CartoLayer
            • What's New
        • Rapid Map Prototyping
      • Charts and widgets
      • Filtering and interactivity
      • Summary
    • Quickstart
      • Make your first API call
      • Visualize your first dataset
      • Create your first widget
    • Guides
      • Build a public application
      • Build a private application
      • Build a private application using SSO
      • Visualize massive datasets
      • Integrate CARTO in your existing application
      • Use Boundaries in your application
      • Avoid exposing SQL queries with Named Sources
      • Managing cache in your CARTO applications
    • Reference
      • Deck (@deck.gl reference)
      • Data Sources
        • vectorTableSource
        • vectorQuerySource
        • vectorTilesetSource
        • h3TableSource
        • h3QuerySource
        • h3TilesetSource
        • quadbinTableSource
        • quadbinQuerySource
        • quadbinTilesetSource
        • rasterSource
        • boundaryTableSource
        • boundaryQuerySource
      • Layers (@deck.gl/carto)
      • Widgets
        • Data Sources
        • Server-side vs. client-side
        • Models
          • getFormula
          • getCategories
          • getHistogram
          • getRange
          • getScatter
          • getTimeSeries
          • getTable
      • Filters
        • Column filters
        • Spatial filters
      • CARTO APIs Reference
    • Release Notes
    • Examples
    • CARTO for React
      • Guides
        • Getting Started
        • Views
        • Data Sources
        • Layers
        • Widgets
        • Authentication and Authorization
        • Basemaps
        • Look and Feel
        • Query Parameters
        • Code Generator
        • Sample Applications
        • Deployment
        • Upgrade Guide
      • Examples
      • Library Reference
        • Introduction
        • API
        • Auth
        • Basemaps
        • Core
        • Redux
        • UI
        • Widgets
      • Release Notes
  • CARTO Self-Hosted
    • Overview
    • Key concepts
      • Architecture
      • Deployment requirements
    • Quickstarts
      • Single VM deployment (Kots)
      • Orchestrated container deployment (Kots)
      • Advanced Orchestrated container deployment (Helm)
    • Guides
      • Guides (Kots)
        • Configure your own buckets
        • Configure an external in-memory cache
        • Enable Google Basemaps
        • Enable the CARTO Data Warehouse
        • Configure an external proxy
        • Enable BigQuery OAuth connections
        • Configure Single Sign-On (SSO)
        • Use Workload Identity in GCP
        • High availability configuration for CARTO Self-hosted
        • Configure your custom service account
      • Guides (Helm)
        • Configure your own buckets (Helm)
        • Configure an external in-memory cache (Helm)
        • Enable Google Basemaps (Helm)
        • Enable the CARTO Data Warehouse (Helm)
        • Configure an external proxy (Helm)
        • Enable BigQuery OAuth connections (Helm)
        • Configure Single Sign-On (SSO) (Helm)
        • Use Workload Identity in GCP (Helm)
        • Use EKS Pod Identity in AWS (Helm)
        • Enable Redshift imports (Helm)
        • Migrating CARTO Self-hosted installation to an external database (Helm)
        • Advanced customizations (Helm)
        • Configure your custom service account (Helm)
    • Maintenance
      • Maintenance (Kots)
        • Updates
        • Backups
        • Uninstall
        • Rotating keys
        • Monitoring
        • Change the Admin Console password
      • Maintenance (Helm)
        • Monitoring (Helm)
        • Rotating keys (Helm)
        • Uninstall (Helm)
        • Backups (Helm)
        • Updates (Helm)
    • Support
      • Get debug information for Support (Kots)
      • Get debug information for Support (Helm)
    • CARTO Self-hosted Legacy
      • Key concepts
        • Architecture
        • Deployment requirements
      • Quickstarts
        • Single VM deployment (docker-compose)
      • Guides
        • Configure your own buckets
        • Configure an external in-memory cache
        • Enable Google Basemaps
        • Enable the CARTO Data Warehouse
        • Configure an external proxy
        • Enable BigQuery OAuth connections
        • Configure Single Sign-On (SSO)
        • Enable Redshift imports
        • Configure your custom service account
        • Advanced customizations
        • Migrating CARTO Self-Hosted installation to an external database
      • Maintenance
        • Updates
        • Backups
        • Uninstall
        • Rotating keys
        • Monitoring
      • Support
    • Release Notes
  • CARTO Native App for Snowflake Containers
    • Deploying CARTO using Snowflake Container Services
  • Get Help
    • Legal & Compliance
    • Previous libraries and components
    • Migrating your content to the new CARTO platform
Powered by GitBook
On this page
  • Managing Kubernetes: Kots and Helm
  • Single VM deployment (Kots)
  • Orchestrated container deployment with Kubernetes (Kots)
  • Advanced Orchestrated container deployment with Kubernetes (Helm)
  • Installation options: Self-Service and Assisted installations

Was this helpful?

Export as PDF
  1. CARTO Self-Hosted

Overview

PreviousRelease NotesNextKey concepts

Last updated 3 months ago

Was this helpful?

In many scenarios, organizations will need to deploy the whole CARTO platform in their own infrastructure. For example:

  • When access to their data warehouse is very restrictive.

  • When they are not able to configure the credentials to connect with their data warehouse in the CARTO Cloud service.

  • When their data warehouse is within a virtual private cloud (VPC) or behind a virtual private network (VPN)

In order to cover these and other situations, CARTO has made available the option of a self-hosted deployment. This is for example a common option for businesses in the healthcare, telco, insurance, and finance industries to remain compliant to their strict security and network policies.

CARTO Self-hosted can be deployed locally and on several cloud infrastructure providers such as GCP, AWS or Azure. See the deployment overview for a full list of options and installation instructions.

CARTO Self-hosted can run on a variety of platforms using a set of Docker images. The available deployment methods vary in complexity and scalability, so you can choose between a Single VM deployment, an Orchestrated container deployment, or an Advanced Orchestrated container deployment, based on your requirements and use case. There is no better or preferred method, it depends on your needs.

Managing Kubernetes: Kots and Helm

KOTS (Kubernetes Off-The-Shelf) and Helm are both tools for managing Kubernetes deployments, but they serve different purposes depending on ease of use and customization requirements:

  • KOTS focuses on simplifying the deployment of pre-packaged Kubernetes applications, particularly for self-hosted environments. It includes features like built-in admin consoles, automated updates, and configuration management aimed at non-expert Kubernetes users. KOTS simplifies deploying CARTO Self-hosted by providing an Admin Console with key features such as:

    • Updates can be applied with a single click, streamlining maintenance.

    • Configuration changes are managed through a user-friendly UI with built-in versioning, ensuring easy tracking and rollbacks.

    • Support bundles can be generated instantly, simplifying troubleshooting.

    • Additionally, license synchronization is automated, reducing manual overhead and ensuring compliance effortlessly.

  • Helm is a package manager for Kubernetes, allowing users to define, install, and upgrade applications using charts—pre-configured Kubernetes resources. It excels at templating and managing app lifecycles in a declarative manner. Helm provides full control over advanced customizations of the CARTO Self-hosted deployment, allowing users to tailor deployments beyond the options available in the KOTS UI, making it ideal for complex, highly specific configurations.

As it has been mentioned before in this document, CARTO Self-hosted is distributed in different ways depending on customer requirements. Continue reading for more details about each deployment type.

Single VM deployment (Kots)

CARTO is deployed in a single VM using an embedded cluster and Kots. This deployment is the easiest and fastest.

Follow the Guides (Kots) and Maintenance (Kots) documentation pages for this type of deployment. Take a look at the Quickstart page for an installation guide using this method.

This method might be appropriate if you and your team:

  • Are currently evaluating CARTO or deploying CARTO for the first time.

  • Have less experience with Kubernetes or DevOps concepts.

  • Need a lightweight, low-cost, and low-maintenance deployment method.

  • Would like to deploy CARTO on a small-scale or single-server environment.

Orchestrated container deployment with Kubernetes (Kots)

CARTO can be deployed in an orchestrated environment using Kubernetes. This method uses Kots to manage the configuration and maintenance of the deployment.

Follow the Guides (Kots) and Maintenance (Kots) documentation pages for this type of deployment.

Take a look at the Quickstart page for an installation guide using this method.

This method might be appropriate if you and your team:

  • Already use Kubernetes to deploy other applications.

  • Have experience with Docker or DevOps concepts.

  • Require scalability, high availability, and resilience.

  • Prefer to use a UI for most configuration and maintenance tasks.

We support deployments with the following Kubernetes vendors:

  • Google Kubernetes Engine (GKE)

  • Amazon Elastic Kubernetes Service (EKS)

  • Microsoft Azure Kubernetes Service (AKS)

  • Red Hat OpenShift

  • IBM Cloud Kubernetes Service

If your Kubernetes vendor is not listed, please reach out to our support team for assistance: support@carto.com

Advanced Orchestrated container deployment with Kubernetes (Helm)

CARTO can be deployed in an orchestrated environment using Kubernetes. This method uses a Helm chart to manage the configuration and maintenance of the deployment.

Follow the Guides (Helm) and Maintenance (Helm) documentation pages for this type of deployment.

Take a look at the Quickstart page for an installation guide using this method.

This method might be appropriate if you and your team:

  • Already use Kubernetes to deploy other applications.

  • Have experience with Docker or DevOps concepts.

  • Require scalability, high availability, and resilience.

  • Are familiar with Helm charts and can fully handle an installation process from a terminal.

We support deployments with the following Kubernetes vendors:

  • Google Kubernetes Engine (GKE)

  • Amazon Elastic Kubernetes Service (EKS)

  • Microsoft Azure Kubernetes Service (AKS)

  • Red Hat OpenShift

  • IBM Cloud Kubernetes Service

If your Kubernetes vendor is not listed, please reach out to our support team for assistance: support@carto.com

Installation options: Self-Service and Assisted installations

CARTO Self-hosted offers flexibility in the installation process to accommodate a range of customer preferences and infrastructure complexities. For customers with technical expertise and a straightforward setup, we offer a Self-Service installation option, enabling you to independently install and configure the product using our comprehensive installation guides.

However, we understand some organizations may have intricate setups such as Virtual Private Cloud (VPC), VPN, restricted network access, HTTPS proxy, or other specialized requirements. In such cases, we offer Assisted installations, where our expert team collaborates closely with you to ensure a seamless and tailored deployment. Our goal is to provide a solution that fits your specific needs, regardless of the level of installation assistance required.

If you require an Assisted installation, please book time with us.

Architecture

Learn more about the different possible architectures for deploying CARTO Self-hosted.

Deployment requirements

Gather more information about the requirements for your deployment.

Quickstarts

Deploy CARTO Self-Hosted in GCP, AWS, Azure.

Guides

Detailed guides to configure different components of a Self-hosted deployment.

Maintenance

Manage updates, backups and details on how to get support for your Self-hosted deployment.

Release Notes

Relevant changes that are introduced in each specific CARTO Self-hosted release version.