Configure an external in-memory cache

For CARTO Self-Hosted

Valkey replaces Redis as of CARTO Self-Hosted 2026.04. Valkey is an open-source fork of Redis 7.2 and is fully wire-compatible: existing external Redis instances continue to work as a drop-in cache without configuration changes. For versions earlier than 2026.04, see the legacy documentation.

CARTO Self-Hosted requires Valkey (version 6 or above) to work. This Valkey instance does not need persistence, as it is used solely as a cache.

Both Single VM deployment and Orchestrated container deployment come already with an internal Valkey deployment, but they lack any backups, autoscaling, or monitoring. Cloud vendors already offer Valkey deployments at scale as a service:

• Google Memorystore for Redis.

• Amazon ElastiCache for Redis.

• Azure Cache for Redis.

Configuration

Kots

Kots

In this section, you will see how to configure the Self-hosted to use an external Valkey provided by your cloud vendor. The needed changes can be applied from the Admin Console, as you'll have to update the following config:

Configure TLS

By default, CARTO will try to connect to your Valkey without TLS enabled. In case you want to connect via TLS, you can enable it and configure your SSL certificate if it's a selfsigned one or it's signed by a custom CA.

Helm