Comment on page
In order to run CARTO on your own infrastructure setup, the following requirements must be met at a minimum:
The hardware and software requirements below must be met to ensure an optimal performance of the CARTO platform:
- Ubuntu 20.04 or above
- Docker version 20.10 or above
- Docker Compose standalone version 1.29 or above.
- 60 GB disk
- 4 CPUs (x86)
- 16 GB memory
CARTO requires a dedicated PostgreSQL database to manage its metadata. The metadata information stored in this database is the following:
- Configuration of Maps: data sources, layers, tooltips, legends, etc.
- Configuration of Workflows.
- Configuration of Applications.
- Connection credentials to other data warehouses like BigQuery, Snowflake, PostgreSQL, Redshift, or Databricks.
- Other CARTO internal metadata
The CARTO metadata PostgreSQL database is only used to store CARTO metadata. This database is not the database to be used with CARTO to store your geospatial data.
This metadata database must be maintained (in terms of updates, backups, high availability, ...) by you. Our recommendation is to use the managed service provided by your cloud provider:
The current PostgreSQL recommended version is 14 or above.
An admin user with permission to create users and databases is required during the installation process.
CARTO Self-hosted includes containers with PostgreSQL, but they are only for debugging purposes and will be removed in future versions
CARTO might need to be accessible to other people in your company (or the internet if you desire it) who needs using it. In order to do that, you need to configure:
- A full domain/subdomain that will be pointing to the machine.
- (Optional) A TLS certificate for the domain/subdomain. If no TLS certificate is provided, a self-signed certificate will be generated. The TLS certificate private key can't be protected with a passphrase.
- Access to HTTPS port (443). HTTP port (80) is optional and is going to redirect to HTTPS.
A full domain is required. You cannot install CARTO in a domain path like https://my.domain.com/carto
If you would like to use some advanced features of Analytics Toolbox like LDS or some Wokflows features like import/export, your domain should be publicly accessible from the internet
The CARTO Self-Hosted deployment requires access to some external services. Some of them are required for the software to work, and others depend on the cloud and data warehouse you will run and connect CARTO to. Finally, there is a set of optional services that you will need to open in case you will use those services with CARTO. For these services, HTTP/HTTPS domains must be “accepted”.
pubsub.googleapis.comUsed as a message broker between CARTO servers and the Self-Hosted to transfer information about the license and telemetry.
Additional services required for Self-Hosted deployment:
storage.googleapis.comAccess to download the client package and the containers required to run CARTO Self-Hosted.
cloudresourcemanager.googleapis.comThis is a necessary step solely for downloading the essential containers needed to operate CARTO Self-Hosted.
Cloud/Data warehouse specific requirements:
Depending on the cloud you are deploying and the data warehouse you are using, you will also need to open certain services to connect your data.
- Google Cloud
bigquerydatatransfer.googleapis.comIf you are going to use BigQuery. Mandatory if you are going to use the CARTO Data Warehouse.
*.snowflakecomputing.comIf you are going to use Snowflake.
*.databricks.comIf you are going to use Databricks.
LDS specific requirements:
api.tomtom.comUsed for geocoding and routing.
isoline.router.hereapi.comUsed for isolines.
clientstream.launchdarkly.comThese are used to activate/deactivate features on the software.
A CARTO installation package that contains your environment configuration and a license key is required during the installation process. If you don't have these, you should request them at [email protected].