Redis GTM Unpacked. How did Redis grow?

Redis origin and first customers: Distinguish the project from the company

Redis’s tenth-anniversary account credits Salvatore Sanfilippo with creating the project and David Welton with sharing the initial Hacker News link in 2009. It recognizes early adopters as active participants in the project’s growth. A separate company announcement identifies Ofer Bengal and Yiftach Shoolman as founders of the commercial business in 2011. These are related but different origin stories. [1][2]

[Inference] The project’s adoption supplied an audience already familiar with the technical value. A commercial company still needed to sell something that users would not obtain simply by downloading it. Conflating open-source users with enterprise customers hides the central monetization challenge. The first paid account is not verified here. [1][2]

Redis GTM motion: Managed operation adds a separate buying reason

The current pricing page distinguishes free shared deployment, Essentials and dedicated Pro, alongside on-premises offers and cloud-marketplace routes. Pro includes options such as multi-region active-active operation and private connectivity. The site also exposes professional services, university courses, tutorials and reference architectures. [4]

[Inference] These capabilities address operational complexity beyond basic developer adoption. A team can begin with a small cache, then require more capacity, stronger availability or additional deployment controls as the application becomes important. Technical sales and success become valuable when failure consequences rise, even if the first trial was self-service. [4]

Redis people and process: Licensing exposed the importance of community trust

In May 2025, CEO Rowan Trollope acknowledged that the 2024 move to a source-available license hurt the community relationship. He announced AGPLv3 as an additional option for Redis 8 and credited Sanfilippo, CTO Benjamin Renaud and core developers in the decision. Sanfilippo had returned as a developer evangelist in November 2024. [3]

[Inference] Developer advocacy here was substantive product and licensing work, not only marketing content. A familiar technical leader could help reconnect the company with the project’s users, but that does not prove that trust or lost business was fully restored. No numerical effect on churn is established. [3]

Redis pricing and economics: Usage grows; so do operating obligations

Observed November 2026, the cloud page offers a free 30 MB database, Essentials from approximately $5 monthly, and Pro with a $200 monthly minimum. Deployment and support differ by package; these figures are entry points, not comparable all-inclusive production costs. [4]

[Inference] Expansion follows data, throughput, availability and deployment needs. The economic tradeoff is between monetizing managed expertise and preserving a healthy ecosystem that also includes competing providers. Published prices cannot establish CAC, contribution margin or the share of project users who become customers. [3][4]

Redis experiments and lessons: What should be learned from the correction

[Inference] Redis illustrates both the strength and fragility of open-source distribution. A useful project can create enormous familiarity, while an unpopular commercial boundary can activate alternatives. The company’s own admission makes the licensing episode a documented mistake, rather than a hypothetical objection. [3]

[Inference] A better process would test proposed boundaries with developers, buyers and partners before implementation, then measure support burden and commercial impact separately. The durable paid proposition should remain understandable in operational terms: what responsibility, capability and service the customer receives beyond the freely available project. [3][4]

Redis economics at a glance: Pricing is only half the story.

The people in the Redis GTM story: People & capabilities.

Redis go-to-market FAQ: The questions that matter.