Redis expansion opportunity within customer base
Redis
Redis’s next leg of growth is less about adding net new logos and more about getting existing teams to run more critical workloads on the platform. At roughly $300M of ARR with an implied average of about $25,000 per customer, Redis already has a very broad base, yet only 50 plus customers spend more than $1M a year. That spread usually means many accounts still use Redis for one narrow cache or session store, before expanding into multi-region, larger datasets, and managed enterprise deployments.
-
The upsell path is concrete. A team can start with basic caching, then add Active-Active for always on apps across regions, Flex when hot data needs to stay in memory but colder data can spill to cheaper storage, BYOC for stricter security, and Iris for higher level services. Each step attaches to a bigger production workflow and a larger bill.
-
The customer mix shows that Redis has both breadth and headroom. Serving 58% of the Fortune 50 proves the product is already inside large enterprises, while 50 plus customers over $1M shows a subset has expanded far beyond the average account. The gap between those cohorts is the expansion opportunity.
-
This is a familiar pattern in infrastructure software. Database companies like Neo4j and ClickHouse have built large revenue bases by becoming more deeply embedded in expensive production use cases over time, not just by landing developers early. Redis is following that same land small, expand with workload criticality motion.
Going forward, Redis is positioned to turn developer adoption into larger enterprise contracts as customers standardize on fewer data systems and push more real time and AI workloads into production. The biggest wins will come from moving from utility cache spend to platform spend, where one account can grow from thousands to millions in annual revenue.