Why the Redis Founder Quit: Lessons on Open‑Source Maintenance Burnout

Redis founder Salvatore Sanfilippo announced on his personal blog that he will end his direct involvement with Redis.

He clarified that his departure is not due to disappointment with Redis itself, but stems from the exhaustion and frustration caused by the daily demands of open‑source maintenance.

Future maintenance will be handed over to several colleagues, while Sanfilippo plans to join Redis Lab in a more creative role, focusing on ideas, blogging, and video creation, though he has no concrete roadmap yet.

He previously wrote an article titled “The Struggles of an Open‑Source Maintainer,” where he described several challenges:

Handling community feedback consumes a lot of time; full‑time staff for every subsystem would help but is hard to achieve.

As Redis grew popular, the workload shifted to reviewing PRs and issues, with many contributions being merely average fixes.

Time pressure: he never experienced a daily work routine before Redis, and the forced schedule conflicted with his need for creative recharge.

Mental pressure: working on the same project for a decade reduced variety, leading to repetitive tasks despite side projects like Cluster, HyerLogLogs, and a discarded disk storage effort.

Fear: anxiety about losing technical leadership, not because of personal inadequacy, but due to differing expectations between users and the broader IT community.

Despite the founder’s exit, mature open‑source projects like Redis, which have robust governance and many contributors, typically continue operating smoothly.

However, the future direction of Redis depends on the decisions made by the Redis Lab team and whether they continue to support the founder’s vision.

The article invites readers to reflect on how they would feel handling endless PRs if they were in charge of a popular open‑source project.