AI summary by TwinMind

The Redis Rug Pull Is Worse Than You Think

Theo - t3․gg

35m 37s

Redis License Change Announcement

  • Redis adopts dual "source available" licensing under RSAL V2 and SSPL V1
  • Starting with Redis 7.4, no longer distributed under BSD 3-clause license
  • Company creates new term "source available" to avoid calling it open source
  • OSI (Open Source Initiative) does not consider this open source
  • Future releases will combine advanced data types/processing engines from Redis Stack
  • Redis will be dual licensed under Redis Source Available License V2 and Server Side Public License V1

Company Justification and Background

  • Redis has been BSD licensed for 15 years, serving millions of developers
  • More than 50% of Redis downloads from version 6+ come from Redis Stack
  • Company claims majority of commercial sales channeled through largest cloud providers who "commoditize Redis investments"
  • Cites need to "sustainably provide permissive use of source code"
  • Claims this enables continued evolution as "real-time data platform"

Historical Context and Broken Promises

  • Antirez (original Redis creator) left company in 2020
  • Company promised Redis core would "remain under BSD license" when Antirez departed
  • 2018: Redis modules initially relicensed from AGPL to Apache 2.0 with Commons Clause
  • 2021: Modules moved to RSAL (Redis Source Available License)
  • 2022: Modules dual licensed under RSAL V2 and SSPL V1
  • 2024: Core Redis follows same licensing path as modules

Community Response and Contributor Backlash

  • Over 700 contributors to Redis project
  • Contributors claiming their BSD-licensed contributions being relicensed without permission
  • No CLA (Contributor License Agreement) signed for Redis core project
  • Red Hat employee contributor explicitly states employer holds copyright, refuses permission for license change
  • Recent major contributor from Tencent, Alibaba also affected
  • Contributors demanding removal of their contributions from codebase
  • Linux distributions likely to remove Redis due to licensing incompatibility

Impact on Services and Competitors

  • Railway, AWS, other cloud providers can no longer offer Redis-as-a-service with new versions
  • Upstash unaffected - built Redis-compatible implementation from scratch without using Redis code
  • Microsoft partnering with Redis despite licensing change
  • Companies like Upstash investigating trademark implications for using "Redis" in product names

Alternative Solutions and Forks

  • KeyDB: Multi-threaded Redis fork, 2x+ performance improvement, remains open source
  • Dragonfly: Newer alternative claiming better performance
  • SkyTable: Another Redis alternative
  • Most alternatives showing significantly better performance than Redis

Comparison to Other License Changes

MongoDB SSPL Precedent

  • MongoDB successfully changed to SSPL, maintained business model
  • Reduced adoption in third-party services
  • Users primarily use MongoDB Atlas or self-deploy

PlanetScale vs Redis Comparison

  • PlanetScale removed free tier but kept underlying Vitess open source
  • Redis changing core technology licensing, not just service offering
  • PlanetScale didn't restrict competition, Redis explicitly does

Better Licensing Models: Sentry's FSL

  • Functional Source License (FSL) converts to MIT/Apache 2.0 after 2 years
  • Provides competitive advantage while ensuring eventual open source status
  • Incentivizes continued innovation through 2-year lead time
  • Used by Sentry, GitButler (co-founded by GitHub co-founder Scott Chacon)
  • Addresses same competitive concerns as Redis without permanent restrictions
  • Much simpler than Business Source License (BSL) with fewer parameters

Technical and Business Implications

  • Redis described as "hashmap as a service" - simple key-value store
  • Difficulty monetizing due to ease of hosting anywhere
  • Company losing business to AWS, Upstash, Railway, other providers
  • New license prevents competitors from offering Redis-as-a-service
  • Performance issues compared to alternatives like KeyDB
  • Multi-threading limitations making Redis slower than competitors

Legal and Copyright Concerns

  • Contributors never signed CLAs for license changes
  • Red Hat employee explicitly refusing permission for their contributions
  • Potential DMCA issues with "mangled license headers"
  • Copyright holders may pursue legal action
  • 80+ commits from single Red Hat contributor would need removal/reimplementation

Long-term Consequences

  • Redis removed from most Linux distributions
  • Community trust permanently damaged
  • Reduced adoption in open source ecosystem
  • Incentivizes migration to alternatives like KeyDB
  • Similar pattern to Oracle JDK vs OpenJDK, MySQL vs MariaDB

TwinMind

Get summaries like this for your own meetings

TwinMind takes notes in the background during meetings, lectures, and calls, then writes the summary for you.

Free plan to get started

No bot joins your calls

Phone, desktop & Chrome apps

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome