Yeah, there has been a lot of stuff like performance [1] and efficiency improvements [2]. A lot of the contributors, that didn&#x27;t work for Redis labs but worked on Redis OSS before the fork, moved to Valkey and they continued to contribute.[1] <a href="https:&#x2F;&#x2F;valkey.io&#x2F;blog&#x2F;unlock-one-million-rps-part2&#x2F;" rel="nofollow">https:&#x2F;&#x2F;valkey.io&#x2F;blog&#x2F;unlock-one-million-rps-part2&#x2F;</a>
[2] <a href="https:&#x2F;&#x2F;valkey.io&#x2F;blog&#x2F;new-hash-table&#x2F;" rel="nofollow">https:&#x2F;&#x2F;valkey.io&#x2F;blog&#x2F;new-hash-table&#x2F;</a>

Valkey has RDMA support, which offers significant performance improvements.

Well Valkey has more commits to their repository then Redis does, and more contributors. So it appears to be active.<a href="https:&#x2F;&#x2F;github.com&#x2F;valkey-io&#x2F;valkey">https:&#x2F;&#x2F;github.com&#x2F;valkey-io&#x2F;valkey</a><a href="https:&#x2F;&#x2F;github.com&#x2F;redis&#x2F;redis">https:&#x2F;&#x2F;github.com&#x2F;redis&#x2F;redis</a>

In fact, some of Redis 8’s new features were taken from Valkey source code.

I am thinking the same that going to AGPL may actually push more people to Valkey.Although I haven&#x27;t checked if ValKey any substantial development since the fork.

Why would PaaS providers switch back to offering Redis? They&#x27;ve clearly all already invested a lot in Valkey (AWS, GCP, Heroku).

I very much doubt that anyone will stick with valkey after the PaaS providers switch back to just offering Redis proper.

Are there usage stats available? How do you know this?

I don&#x27;t know about valkey but I got word Nvidia was switching away from Redis.

Amazon really encourages valkey in the elasticache dashboard. There&#x27;s a banner advertising lower prices and it&#x27;s listed first in the dropdown when you go to create one. Default settings do have power.

I&#x27;ve been using Valkey simply because after I updated to the latest Fedora version, it dropped redis and pointed me to Valkey instead. I assume as more distros do this and more people update their systems, the Valkey user base will grow. But perhaps with the AGPL redis that will no longer be the case.

Yeah, all the open source distributions and most open source projects switching to valkey must be &quot;nobody&quot;.

If you use the latest versions of Redis, you are benefiting from the continued efforts of the Valkey development community. [1]This is Open Source working well.Unfortunately, the reverse flow does not work.[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;redis&#x2F;redis&#x2F;pull&#x2F;13638">https:&#x2F;&#x2F;github.com&#x2F;redis&#x2F;redis&#x2F;pull&#x2F;13638</a>

That kind of assertion really needs some backup or it&#x27;s just noise. I&#x27;ll be honest and say that I have no idea what the usage stats for Valkey are -- and it may be that it&#x27;s a drop in the bucket compared to Redis. But I don&#x27;t know. Can you back this up or is this just your gut feeling?

Yet. It&#x27;s a drop-in replacement, and both faster and cheaper.

what do you mean? i work at a FAANG-adjacent company and our entire engineering org was told to switch to valkey, with an internal deadline from ops. My team supports a public facing service and we made the switch 2 months ago.It was pretty easy, a small config change and some performance testing to make sure it worked well at scale.Maybe nobody is talking about it online but some people have definitely switched.

The team of sales was, AFAIK, rebuilt from scratch recently. Please if this happened recently tell me, and I&#x27;ll make sure to report back. Thanks.

All of this aside, Redis-the-company has some of the least tactful salespeople I&#x27;ve come across in my long stint in this industry. Used car sales level tactics.Between that and the licensing, I would never consider dealing with them.

I imagine there is quite a large, quiet fraction (majority) of users who were the same way.Not to say it’s not an important discussion!

Same here. The response from the community was valid, but basically didn&#x27;t affect us.

From the blog post it seems like existing users kept using Redis but new users adopted alternatives instead.

We kept using redis, the license change never affected us. We had no reason to switch.

We switched to Valkey on our Elasticache instances and immediately noticed a performance improvement in our usecase that allowed us to reduce number of instances. Not really interested in moving back to Redis at this point.

I&#x27;m curious whether the community will trust Redis-the-company again after this, or if they&#x27;ll choose to stick with Valkey. The other concern is at least some big company legal departments are wary of AGPL software, which makes Valkey, still BSD, more attractive to them.Edit: Regardless, thank you and the rest of the folks inside Redis for pushing to bring this back to OSS!

Also PaaS like Heroku adopted Valkey as a drop-in replacement for Redis.

It is a fork of the latest oss release right? I thought some completely new implementations were introduced.

Valkey has replaced redis in a few distros

During this time I believe a lot of alternatives (mostly protocol compatible to redis so they would be drop in replacements) came into light.Has there been a consensus on one? Is there a winner?I love redis and will probably keep using it. Just curious.

In word, but not in deed. I&#x27;ll say it over and over again: COSS startups don&#x27;t adopt the AGPL because they want to prioritize user freedom, they adopt it as a means of defense.

The difference is how compliance is handled for cloud providers. Complying with the AGPL requires releasing the source code for the program you&#x27;re hosting as a service. Complying with the SSPL requires releasing the source code for &quot;all programs that you use to make the Program or modified version available as a service, including, without limitation, management software, user interfaces, application program interfaces, automation software, monitoring software, backup software, storage software and hosting software&quot; under the terms of the SSPL. This is effectively impossible for any cloud provider to comply with (it would require a massive engineering effort to rewrite every single piece of software used to convey the service), which is why the OSI didn&#x27;t approve it as an open source license.

Of course it&#x27;s the AGPL, which is essentially the SSPL in practice.

If by desired outcome you mean split the developer community and then chase them away to a newly forked competitor that is now widely used by all the cloud providers and users that prefer open source; complete success!But I doubt that was the outcome that they hoped for. They created a large and successful competitor that by nature of being a fork does exactly the same thing. It&#x27;s pretty hard to compete with yourself and the differentiate from your own product.Honestly, I think Redis Inc. was better off when there was just one code base. AGPL just marginalizes them further. It&#x27;s not an acceptable license for many corporate legal departments. So, it would necessitate buying a commercial license for such companies. I.e. Fortune 500 companies, public companies, and pretty much anything with a legal department worthy of the name. Note how Redis advertises AGPLv3 as &quot;one&quot; of the available licenses. The whole point of that license is selling commercial licenses.Valkey is at this point stable and supported and a drop in replacement. It&#x27;s pretty much the default choice for anyone not interested in buying a commercial license. That genie isn&#x27;t going back in the bottle with this license choice.More importantly, Valkey is a pretty active Github project with dozens of contributors in the last month. More than double those in Redis. Those commits aren&#x27;t going to Redis. And Redis still requires the right to re-license your commits if you try to contribute. That&#x27;s how they were able to pull this stunt to begin with. I doubt a lot of the Valkey contributors will be moving back to that status quo.

Not sure how the hyperscale clouds switching to a compatible&#x2F;competing project from which Redis Labs gets no value or contribution is a win.

How did you come to that conclusion? GCP is still offering Memorystore for Redis, Valkey and Memcached. <a href="https:&#x2F;&#x2F;cloud.google.com&#x2F;memorystore" rel="nofollow">https:&#x2F;&#x2F;cloud.google.com&#x2F;memorystore</a>

It did yield the desired outcome: Google and AWS are no longer using it.

A bit more info from CEO: <a href="https:&#x2F;&#x2F;redis.io&#x2F;blog&#x2F;agplv3&#x2F;" rel="nofollow">https:&#x2F;&#x2F;redis.io&#x2F;blog&#x2F;agplv3&#x2F;</a>Sounds like SSPL did not yield the desired outcome.Glad AGPL is an option now.

why? The investment into it has already been done, and quite a few places will be happier with its license still. I think enough has happened&#x2F;too much time passed that its not a given everyone will just quietly move back to Redis.

I&#x27;m guessing valkey will be dead now?

I can understand problems with SSPL license, but i cannot understand the problems with AGPL. If you use software for your SAAS service for free, and made changes in it, you should share the changes with others. Is free software, not a gift for your business.

Sure, but the damage is done already, and it&#x27;s AGPL too.

Extra instance and developer overhead.

&gt; Rails 8 has moved Redis functionality into the database by default, which works fine.Databases could always do what redis did. Redis doesn&#x27;t bring functionality to the table, it brings speed. If database caching, pub&#x2F;sub, and streams are good enough for your use case, there was never a reason to pay for an extra instance just to stand up redis.

AGPL isn’t cancer. It’s a license that exists to solve a particular problem: the proliferation of free software in a world of network services.If you don’t like it, don’t use AGPLv3 software. Those of us who do like it will keep writing AGPLv3 software.

AGPL is cancer[0] in exactly the same way GPL is cancer, in that it&#x27;s intentionally designed to *BE* cancer (or, congenital at least).If you modify GPL code you are expected to open source the changes, AGPL adapts that to the networked world, if you modify AGPL code to serve something, you should open source those changes too, otherwise you&#x27;re violating the original spirit of GPL which was designed in a time that was not as perpetually internet (and SaaS) driven as today.If you want a true free license, BSD or MIT have you covered, but then you shouldn&#x27;t expect corporations to give back.A good example of what happens if companies don&#x27;t give back is Linux VS the various BSD&#x27;s. BSD is a lot more popular in appliances than you might otherwise believe but the popularity is starting to wane as Linux (despite GPL) has improved so much with companies giving back that the &quot;free license&quot; BSD is no longer being seen as good enough in some cases. People do not tend to give back to the BSD&#x27;s.[0]: <a href="https:&#x2F;&#x2F;blog.jamesbayley.com&#x2F;2014&#x2F;01&#x2F;17&#x2F;gpl-living-with-cancer&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.jamesbayley.com&#x2F;2014&#x2F;01&#x2F;17&#x2F;gpl-living-with-canc...</a>

RMS was not convinced that the Affero clause was a good idea as a general rule, though he approved the Affero-sponsored fork of the GPL that created AGPLv1. Hence, he did not support the addition of network copyleft obligations in GPLv3 during its drafting.RMS has long expressed concerns about &quot;Service as a Software Substitute&quot; [1], and I think he hesitated to endorse the AGPL because it would conflict with his philosophy on the dangers of &quot;Service as a Software Substitute&quot;.Henry Poole should be given credit for raising the concern; Bradley M. Kuhn and Eben Moglen should be given the credit for advancing the license to address the concern.It took a long time for the Free Software Foundation to accept Affero versions of the GPL under their stewardship with the release of AGPLv3.So, perhaps he did understand before many people that services posed some challenges for his social movement. But it&#x27;s my belief that he favored self-reliance and maximum &quot;freedom&quot; by running computer programs on hardware you own yourself as the remedy, rather than extending copyleft obligations to reach over the network.[1] <a href="https:&#x2F;&#x2F;www.gnu.org&#x2F;philosophy&#x2F;who-does-that-server-really-serve.en.html" rel="nofollow">https:&#x2F;&#x2F;www.gnu.org&#x2F;philosophy&#x2F;who-does-that-server-really-s...</a>

RMS was enough of a genius to understand the potential of open source software, and basically gave us, with GPL and his evangelism (and his code! plenty of it), and the free software movement, the software world we are living now. AGPL reflects the fact that he understood before everybody else that something was happening with software as a service.I love the BSD license, but now who says that AGPL is a cancer is making a big favor to the few huge companies that want to abuse the original dream that spawned modern and open software. Times changes, the best license to use change with times.

I agree it&#x27;s better than their previous made up license.  It won&#x27;t win back everyone who left though.  The ship has sailed.  They should have gone GPL.

&gt; AGPL is cancer.Good, you can think it is cancer and stay away from it. You don&#x27;t like it, don&#x27;t use it. It&#x27;s like those bright colored poisonous frogs from the Amazon. That&#x27;s better than some newly made up license that&#x27;s different than anything else, and you have to wonder how it would hold up in practice.

AGPL is cancer. Valkey already exists, people already switched, it&#x27;s already landed in a bunch of distros. I don&#x27;t see anyone moving back, especially when Valkey has some big corporate support.And for my personal usage, Rails 8 has moved Redis functionality into the database by default, which works fine.

I can easily see this for a midsize company.While it&#x27;s likely an easy process to drop in valkey, creating the new instances, migrating apps to those new instances, and making sure there&#x27;s not some hidden regression (even though it&#x27;s &quot;drop in&quot;) all takes time.At a minimum, 1 or 2 hours per app optimistically.My company has hundreds of apps (hurray microservices). That&#x27;s where &quot;hundreds of hours&quot; seems pretty reasonable to me.We don&#x27;t have a lot of redis use in the company, but if we did it&#x27;d have taken a bit of time to switch over.Edit: Dead before I could respond but I figured it was worthwhile to respond.&gt; It&#x27;s literally just redis with a different name, what is there to test?I&#x27;ve seen this happen quite a bit in opensource where a &quot;x just named y&quot; also happens to include tiny changes that actually conflict with the way we use it. For example, maybe some api doesn&#x27;t guarantee order but our app (in a silly manor) relied on the order anyways. A bug on us, for sure, but not something that would surface until an update of redis or this switch over.It can also be the case that we were relying on an older version of redis, the switchover to valkey necessitates that we now bring in the new changes to redis that we may not have tested.These things certainly are unlikely (which is why 1 or 2 hours as an estimate, it&#x27;d take more if these are more common problems). Yet, they do and have happened to me with other dependency updates.At a minimum, simply making sure someone didn&#x27;t fat finger the new valkey addresses or mess up the terraform for the deployment will take time to test and verify.

By switch I mean that all new projects use Valkey instead of Redis, and we&#x27;ve invested hundreds of hours into those new projects.

At the very least you have to validate everything that touches redis, which means finding everything that touches redis. Internal tools and docs need to be updated.And who knows if someone adopted post-fork features?If this is a production system that supports the core business, hundreds of hours seems pretty reasonable. For a small operation that can afford to YOLO it, sure, it should be pretty easy.

I believe it. There are companies that invested hundreds of engineering hours to rename master to main.

There are companies using many thousands of Redis instances storing petabytes of data with millions of users.Now consider a no-down-time migration. How long do you think that&#x27;ll take to engineer and execute?

Even the infrastructure switch and testing should take a lot of time, yet the application level tests etc.

Your company invested hundreds of engineering hours switching from Redis to a clean fork of Redis?

What? Isn&#x27;t Valkey a &quot;drop in&quot; replacement? I switched a couple of deployment, it &quot;just worked&quot; but maybe I&#x27;m just too simple.

By switch I mean that all new projects use Valkey instead of Redis, and we&#x27;ve invested hundreds of hours into those new projects. We&#x27;ve also tried stuff with the Valkey Glide client.

Hundreds could be 200 which, at 10 hours a day 5 days a week, is like a week and a half for a team of 3. It seems quite possible if you had to do testing&#x2F;benchmarking, config changes, deploy the system, watch metrics, etc.

I think you might underestimate how little time hundreds of hours is. It&#x27;s very, very easy to reach your first hundred hours in a task, e.g. taking a 40 hour week, 3 engineers = 120 hours.If valkey is working, why spend that time reverting to redis, when you could be spending it on things that are actually going to provide value?

My company is relatively small. With probably 6 separate redis instances deployed in various places (k8s, bare metal, staging and prod environments) and dozens of (micro)services using them it&#x27;s probably at least 40 hours (one person-week) to migrate everything at this point. Also there are things like documentation, legacy apps that keep working but nobody wants to spend time updating them, naming problems everywhere (renaming &quot;redis&quot; everywhere with zero downtime would be a huge pain), outdated documentation, possibly updates in CI, CD, and e2e tests, and probably more problems that ight become apparent in scale.And we&#x27;re honestly not large. For a mid size company, hundreds hours sound reasonable. For a big company the amount of work must be truly staggering.

how does it take hundreds of hours to swap out a back end when you&#x27;re using a trivial protocol like redis?did you switch out the client or something? maybe the problem is not using pluggable adapters? is your business logic coupled to the particular database client API? oof.I know the cluster clients are different (been there, done that) but hundreds of hours, seriously? or was that just hyperbole?

Why did you not pay Redis for a licence instead? I&#x27;m genuinely curious. Did you feel uncomfortable being tied to a license fee that might increase in the future, or was it just too expensive?

Our company made the switch over to Valkey, and we&#x27;ve invested hundreds of engineering hours into it already. I don&#x27;t see us switching back at this point especially when it&#x27;s clear Redis could easily pull the bait-and-switch again.

No thanks, going to stick with Valkey for all future projects.

Heh! While I appreciate what you&#x27;re saying, I see this as the opposite of WordPress. It&#x27;s basically a CEO saying oops, we messed up, let&#x27;s fix this, which is fundamentally different than doubling down and ending up in court.

Sorry, you&#x27;re right. ICs, CTOs, and CEOs. Oh my. Pardon me for not subscribing to another accountability shell game. I again call Mullenweg.&#x2F;s in case I haven&#x27;t piled it on thick enough to make an impact.Read the last link of TFA [0], the last time this came up [1] (noting the timespan), and extrapolate as necessary.0: <a href="https:&#x2F;&#x2F;redis.io&#x2F;blog&#x2F;agplv3&#x2F;" rel="nofollow">https:&#x2F;&#x2F;redis.io&#x2F;blog&#x2F;agplv3&#x2F;</a> (CEO)1: <a href="https:&#x2F;&#x2F;redis.io&#x2F;blog&#x2F;redis-license-bsd-will-remain-bsd&#x2F;" rel="nofollow">https:&#x2F;&#x2F;redis.io&#x2F;blog&#x2F;redis-license-bsd-will-remain-bsd&#x2F;</a> (CTO)Or don&#x27;t, I don&#x27;t care. Point&#x2F;fix has been made.

After what Mullenweg has pulled, in the era of Blogging CEOs I have to be cynical.Valkey.

They were obviously making a tongue in cheek comment instead of seriously suggesting Valkey may go proprietary.

fool me can&#x27;t get fooled againBut in seriousness, the chances of valkey going closed source are low. It&#x27;s run by Linux Foundation. It would be like suggesting that Node.js might go closed source...

Valkey is a Linux Foundation project. Talking about license changes is just pure irrational FUD.

This will be very relevant when Valkey decides to go closed source.It&#x27;s better than the previous state of course, but it would have been even better if the previous license change didn&#x27;t happen.As the french people say: fool me once, shame on you...

Good luck to them, everyone is moving to Valkey, especially with its major backing and already better performance.

I am not sure what that would achieve?  Combining programs under GPLv3 and AGPLv3 is possible (the resulting work is under AGPLv3).

Why? They can already just copy the code they want from Valkey, since Valkey is 3 clause BSD...But maybe Valkey should switch to GPLv3 instead to correct this imbalance.<a href="https:&#x2F;&#x2F;github.com&#x2F;redis&#x2F;redis&#x2F;pull&#x2F;13638">https:&#x2F;&#x2F;github.com&#x2F;redis&#x2F;redis&#x2F;pull&#x2F;13638</a>

Redis should step up and fund an independent foundation now and encourage Valkey to contribute where relevant.Some code under a 3 clause BSD and some under AGPLv3 could be interesting.

Similar move to Elasticsearch, tacking on AGPL with their existing source available licenses. [1]The products (commercialized open source) that are often chosen by and championed by developers as opposed to executives see the harm that a bait and switch has on their popularity. With their competitors being more permissive, I don&#x27;t see many devs moving back unless Valkey loses significant feature parity.[1] <a href="https:&#x2F;&#x2F;ir.elastic.co&#x2F;news&#x2F;news-details&#x2F;2024&#x2F;Elastic-Announces-Open-Source-License-for-Elasticsearch-and-Kibana-Source-Code&#x2F;default.aspx" rel="nofollow">https:&#x2F;&#x2F;ir.elastic.co&#x2F;news&#x2F;news-details&#x2F;2024&#x2F;Elastic-Announc...</a>

This doesn&#x27;t solve anything, Redis has proved that it is willing to do a rug pull, and how much they are willing to hurt the community when they do (taking over client libraries, etc). I don&#x27;t see a reason to go back from valkey. Again and again, Redis Labs has been the worst thing about Redis, I&#x27;m glad we now have an other option.

The Vector Sets, omg. Thank you, so much thank you :)

Thank you so much for your kind words! I tried hard, with Vector Sets, to follow exactly the &quot;wave&quot; you are referring here, I hope I was able to. Thanks.

Redis is in SQLite and Wireguard league of simplicity and elegance.

Could you please link any blog post which goes into what you are talking about, I feel I am also at the high barrier to enter situation about this stuff

One of the big things I love about Redis is that it’s become this tool for me to learn new techniques and explore data. Like, the new vector sets feature has let me really explore dense vectors and custom search and taxonomy mapping and all sorts of areas that seemed like a high barrier to entry for me, but now I’m just streaming stuff into llama.cpp with an embedding model and storing it in Redis and being able to do mappings between different data sets super efficiently.A big part of that is API design - I can’t think of another system that is as well thought out as the Redis API - it’s deceptively simple and because of that I didn’t have to wait for client libraries to incorporate the new Redis features - they just work cause they all speak RESP and I can just send raw commands.All of this is to say that I was really happy to hear Antirez was back working on Redis and it’s paying off in more ways than I could have imagined. People can use valkey or whatever they want as an alternative - but I like Redis because it’s always pushing forward and letting me explore new things that otherwise wouldn’t feel as “at my fingertips” as it does in Redis.

All advantage accrues to hyperscaler &quot;managed&quot; versions. That&#x27;s so much more fucked than a rug pull.Amazon gets to make millions off of the thing you built.&quot;Equitable source&quot; licenses with MAU &#x2F; ARR limits, hyperscaler resale limits, and AGPL-like &quot;entire stack must be open&quot; clauses is the way to go. It&#x27;s a &quot;fuck you&quot; to Amazon, Google, and Microsoft in particular and leaves you untouched.Open source today is hyperscaler serfdom. Very few orgs are running Redis on bare metal, and a equitable source license can be made to always support the bare metal case.

You do realize the owners of the copyright can relicense it under any terms they want, even if it&#x27;s a copyleft license like GPL, right?

There are good legal reasons to avoid the GPL; there are open legal questions about whether the GPL and its variants are enforceable.

A copyleft license like the AGPL didn&#x27;t stop MongoDB from rugpulling. I&#x27;d argue that the AGPL, and the copyright assignment that tends to go with it, makes it easier to rugpull because forking entities would be at an extreme disadvantage in keeping the lights on compared to the closed-sourcing company. A non-copyleft license, on the other hand, makes it much easier for a forking company to cover all the same niches as the original company, making a rugpull that much more difficult.

&gt; The only real reason to use non-copyleft licenses for these kinds of projects is to be able to do the rug pullThat’s an exaggeration. The vast majority of permissively licensed projects have never “rug pulled” and never will. It might be one possible reason to choose such a license but it’s very far from the only one.

The only real reason to use non-copyleft licenses for these kinds of projects is to be able to do the rug pull, so you should have expected it instead of feeling betrayed.I imagine they will now require copyright assignment or something like that for external contributors to be able to relicense new code under a commercial license.

You do see how that&#x27;s even worse, right?

Garnet fascinates me. Their benchmarks even claim that it is better than Redis and also Dragonfly. Are there any papers or write ups explaining what makes Garnet fast? (I do know its based on FASTER)

Yup, it’s a complete reimplementation in pure C#. It’s built on top of FASTER KV &#x2F; Tsavorite project from MSR.

Nice. I&#x27;ve been using Memurai (<a href="https:&#x2F;&#x2F;www.memurai.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.memurai.com&#x2F;</a>) for development on Windows (native, no WSL or Docker - for reasons), but this looks much better.EDIT: Weird that being a program from Microsoft (well, it&#x27;s Microsoft Research, so that probably explains it?) it has no installer and doesn&#x27;t run as a service on its own.

Wow. First time hearing about Garnet. MS should package and deploy it as a service in the Azure SAAS offerings.

Microsoft made one called Garnet, I wouldn&#x27;t say its a fork though, its basically compatible with Redis and implemented mostly in C#. It supports the RESP wire protocol from Redis for ease of compatibility.<a href="https:&#x2F;&#x2F;github.com&#x2F;microsoft&#x2F;garnet">https:&#x2F;&#x2F;github.com&#x2F;microsoft&#x2F;garnet</a>

&gt; The transitions Redis made are pristine on a legalYes, of course.&gt; and moral level. Feeling betrayed is absolutely uncalled for.Er, no, that&#x27;s an unsubstantiated leap.

I mean isn&#x27;t lying bad? They literally made public statements saying they &quot;will always remain BSD.&quot; <a href="https:&#x2F;&#x2F;redis.io&#x2F;blog&#x2F;redis-license-bsd-will-remain-bsd&#x2F;" rel="nofollow">https:&#x2F;&#x2F;redis.io&#x2F;blog&#x2F;redis-license-bsd-will-remain-bsd&#x2F;</a>

I think we need to get back to state where we take software licenses serious in letter and in spirit. The transitions Redis made are pristine on a legal and moral level. Feeling betrayed is absolutely uncalled for.

Not quite. Company can easily change license at any time. No string attached.

Good decision, I hope the best for Redis!

Anyway: thanks for having contributed to Redis :)

Nothing wrong in checking other alternatives, but Redis the company didn&#x27;t call me to rejoin. I approached them to do something like an evangelist and bring back some kind of community vision inside. Then... if you can code, you end coding often times, and instead of doing the evangelist I wrote the Vector Set data type :D Just to clarify that me rejoining was not some kind of &quot;winning back the community plan&quot;. I wrote at large about all that, even clearly stating that even the paycheck is modest (to avoid that kind of conflict of interest of the economical motivation).

I use Redis in basically every project, and this &quot;ridiculous&quot; move had literally zero impact on my usage of Redis, so maybe that is a bit hyperbolic.SSPL is not as bad as the OSS community pretends it is (unless you&#x27;re a hyperscaler).

Likewise. Respect for antirez and all of that he is doing, but his hiring back feels like just trying to lure developers back after ridiculous move by the Redis corporation.Given there are viable alternatives out there, I see no reason why someone should invest any time in Redis (we are using Valkey as a replacement).

This seems to be accelerating. I guess the era of lighting investment money on fire and pretending that the flames equal success is coming to an end.Unless of course you are an AI startup.

Interestingly their CEO states that AWS an Google forking redis and maintaining it separately was their &quot;goal&quot; all along. Because fragmentation is apparently good?

This keeps happening:1. People put a lot of work into building databases. The license choice is OSS &#x2F; FOSS.2. Some people in the community (original authors, community leads) make a company around the database and continue developing it for years on end. They sometimes raise venture capital to expand the business.3. Amazon &#x2F; Google &#x2F; Microsoft offer managed versions of the database and make bank on it. Easily millions in revenue. Original creator &#x2F; company doesn&#x27;t get anything, and the hyperscaler isn&#x27;t obliged to pay.4. The company decides to change the license to force Amazon &#x2F; Google &#x2F; Microsoft to pitch in and pay a fee.5. Amazon &#x2F; Google &#x2F; Microsoft fork the database. The community revolts. Sometimes the people revolting are employees of the hyperscalers, other times these are just FOSS fans that hate &quot;source available&quot; licenses or relicensing.6. Database company is forced to walk back the changes. Still no revenue.---The solution is clear: start your new database with an &quot;equitable source &#x2F; source available&quot; license from day one. Nobody will complain about a relicense since your license will handle the hyperscalers right off the bat.Basically your license needs one of a few things if you want to prevent Amazon from walking off with your money:- A hyperscaler clause such that any managed offering has to (1) be fully open source, (2) has to pay a fee, or (3) is prevented outright.- A MAU &#x2F; ARR clause such that hyperscalers are in the blast radius. Note that this also hits your customers.

Dunno about Redis, but for Elastic I still feel sorry for them being thrown around like a rag doll by Amazon. On principal I will not use the Amazon fork, because I don’t want to support a company that would prefer to fork a project rather than fork over some cash. Amazon is more than willing to sell you their Elasticsearch fork at a loss as long as they can eventually recoup the losses when Elastic inevitably dies. At which point they will naturally abandon the open sources side of their fork and continue development in private, at a much slower rate, while doubling the price of the AWS service. At which point you’ll have no choice but the pay up, cause there aren’t any competitors left.

NATS almost ended up doing it recently, too. Fortunately they caved in just today, after the CNCF and the community protested. [1] While the outcome is great, it was a bunch of drama for nothing, and their reputation has been harmed.[1] <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=43863721">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=43863721</a>

&gt; Neither company has built in a legal safety mechanism to prevent themselves from pulling the rug again laterPrevious versions are still available under the original license, right? So if you don&#x27;t want to use it with a new license, you&#x27;re in the same situation as if company went out of business or stopped support and development for any other reason. There are no safety mechanisms for that either.

The legal safety mechanism is the license. They gave you software under a certain license and you&#x27;re in the clear as long as you follow it. You don&#x27;t have to delete it if they give different software under a different license.If you do need constant updates, you may trust forks more not to switch license, but forks tend to disappear at about the same rate that originals switch license, so why does it matter? Such is the nature of relying on free stuff - you&#x27;re at the mercy of the one who hands it out.

Yeah, we just did this whole ride with Elastic [0]: company changes the license out from under the community, community revolts, company gives up and changes it back. Both companies even pulled the same &quot;it worked&quot; excuse (&quot;while it was painful, it worked&quot;, &quot;this achieved our goal&quot;).Neither company has built in a legal safety mechanism to prevent themselves from pulling the rug again later and both companies have shown themselves to be untrustworthy stewards. They came groveling back when it turned out that community goodwill really did matter after all, but this is definitely a &quot;fool me twice, shame on me&quot; situation.[0] <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=41394797">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=41394797</a>

I agree. That ship has sailed, at least for the foreseeable future. We switched to Valkey and it&#x27;s our choice for a couple upcoming projects as well. To switch back now after this whole ordeal would make no sense at all.

They require a Contributor License Agreement [0] whereby you grant them the copyright to your contribution. Which means they become the ultimate decision-maker for all contributions and can relicense however and whenever they wish.[0] <a href="https:&#x2F;&#x2F;redis.io&#x2F;legal&#x2F;redis-software-grant-and-contributor-license-agreement&#x2F;" rel="nofollow">https:&#x2F;&#x2F;redis.io&#x2F;legal&#x2F;redis-software-grant-and-contributor-...</a>

&gt; contributed a minor improvement to Redis under its original license [...] feeling betrayed as a contributor to a properly-FOSS-codebaseHow does this work legally? You write some code, contribute it under a certain license... and... a company can just re-license your code under any license they like?

If you contributed before the license change&#x2F;fork, you&#x27;ve also contributed to valkey and redict ;)

I get the feeling. I also live in the real world and know that nobody except for a few (most notably RedHat) have figured out how to make sustainable money in open source. These closed licenses didn’t come out of nowhere. They came in response to places like AWS using the open source license to make a mint with a project — and doing so legally (it’s there in the license to do so) — but then the project suffers. So the license change is done to prevent that so the project — ostensibly — can survive. It makes sense. And so does wanting to live up to the promises of open source. It’s a tough situation for sure.

If anyone betrayed the spirit of Open Source, it is those who were trying to siphon off the entire commericial value of these projects while contributing little back to the project.Companies have to pay people to work on it. Hell, they are even entitled to profit from it. A world with commerically viable Open Source is way better than without it. Ditching OSS companies for trying to survive 90% of revenues going to $1T cloud vendors is counter productive.

I am wondering why did you choose Redict over Valkey? The latter seems to be more popular.

Due to license rug pull, I started an org wide movement from Redis to Valkey early this year and now there’s no turning back. It also does not help Redis that Valkey is cheaper offering by AWS (at least through Elasticache).

If you&#x27;re the most active contributor, you could&#x27;ve just forked it yourself, launched it as a SaaS, and been the CEO.

Come on, at least give us a hint what it is!

Did you sign a Contributor License Agreement?
If not, then I&#x27;m pretty sure it&#x27;s illegal to keep your changes while relicensing, without obtaining your consent.

I contributed heavily to a project during its early days and spent almost 2.5 years helping it grow. For awhile i was one of the most active contributors.Then there was talk of turning the project into an actual business, and myself and a few of the original contributers were offered extremely poor paying jobs. That no one took. Then they got a CEO, investors and we were basically forced out of the project unless we joined the company.I distinctly remember being in a call where we were told they would be relicensing it eventually and launching a SaaS. To protect our work from being used by large companies. I laughed and pointed out the irony in that call that you were doing the same thing.After that they changed their policy such they do not accept outside PR&#x27;s. It has killed any interest in supporting open source projects outside personal stuff.

Lost trust for sure. Who knows if Redis would be AGPL now if Valkey did not exist.

I contributed a minor (but imho still neat :p) improvement to Redis under its original license, and personally moved to using redict when the unexpected license change to SSPL was announced - and I was feeling betrayed as a contributor to a properly-FOSS-codebase. (Had they switched to AGPL right away, I&#x27;d have been perfectly fine with that change from a moral perspective, ftr.)I have a great deal of respect for antirez and recgnize him as a kind and benevolent member of the FOSS community, but no matter what Redis, Inc. announced or does, they have lost my trust for good, and I will continue to use Redis forks for as long as they exist.

It&#x27;s a bold strategy, let&#x27;s see if it works out for them.<a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=9HVejEB5uVk" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=9HVejEB5uVk</a>

I think you are not describing the difference between open source and free software but the difference between copyleft and permissive license.Open source and free software licenses are basically the same (there are a few exceptions). For me, the difference is the focus. Free software cares about user freedom first.

User freedom means not giving someone else the freedom to take away user freedom though, which is what doormat licenses (can we call them cuck licenses or is that too far for HN?) do.

Open source is a gift to everyone (including Jeffrey Bezos); free software is a sharing economy. The difference is whether the sharing is reciprocal. With open source it&#x27;s a one way gift from you to Jeffrey. He could have paid you for that. At the very least you can make him pay with reciprocal sharing.

,,for companies rooted in open source, it has posed a fundamental challenge: how do you keep innovating and investing in OSS projects when cloud providers reap the profits and control the infrastructure without proportional contributions back to the projects that they exploit?&#x27;&#x27;I don&#x27;t see any exploitation happening. As DHH said, the main reason engineers open source their work is to give a gift to the world.

Copyleft does not mean fake-open-source, I&#x27;d not consider Linux fake-open-source for example. Though plenty of reason to use permissive licenses instead of copyleft and vice versa depending on your situation.

Copyleft is Free Software, free as in freedom. Pushover licenses (such as MIT) are working for free for Amazon, Google and Oracle. Which is fine if your boss is paying you money to work for free for Amazon, Google and Oracle - it&#x27;s their money. If it&#x27;s your own spare time, you might not like it as much.

Wishing all real-open-source projects best of luck, including valkey, OpenTofu and so on. These are my clear first choice!

Congrats antirez! I&#x27;m sure this was a huge effort internally, and I hope the Redis team can be successful releasing software under SSPL+AGPL.

<pre><code> s&#x2F;can&#x27;t&#x2F;choose not to&#x2F;
 s&#x2F;&#x27;re forced to&#x2F;&#x2F;</code></pre>

the alternative is&#x2F;was BSD.enterprise hates AGPL. AGPL is generally not a serious alternative to BSD&#x2F;MIT in corpoland, because something something (A)GPL-poisoning.whether it&#x27;s true or not doesn&#x27;t matter. what matters is whether big tech considers AGPL infectious - which they do.

The goal of free software (noting that &quot;open source&quot; is a watered down version of &quot;free software&quot;) is for everyone to share their sohrce code. To that end, licenses that require sharing of source code are used. LGPL says, roughly, you must share the source code of this software to anyone you shared the binary to. GPL is more extensive: anyone you shared the binary or the binary of something built on this software to. AGPL is even more aggressive: anyone you shared it to or gave access to it over a network. And SSPL is currently the most aggressive: you have to share the whole thing you built, not just what&#x27;s linked with this software.The more aggressive a license you pick, the more likely a corporation won&#x27;t want to use it. But that&#x27;s by design. They&#x27;re allowed to use it, even commercially - they just have to give the source code back. If the software is useful enough, they will. We should make software useful enough for corporations to consider the be benefits of using it to outweigh the cost of having to share their source code. (Also the more source you make them share, the less likely this is. The Linux kernel succeeded at this.SSPL is controversial and untested (and goes against the business interests of the OSI so will never be box-tick certified compliant) and likely counterproductive if it means you have to share things like Windows. AGPL is the normal &quot;aggressively free&quot; license. GPL is mostly for those who haven&#x27;t discovered AGPL yet and MIT is for those who don&#x27;t agree in the goal of source code freedom to begin with.

&gt; Edit: Doubled checked with gpt, no cases of “infection” yet, there has also been many talks about this license being very goodwhat? why would you ask an LLM to generate some random text instead of looking up the actual answer?

Wait, AGPL is a good license for enterprise, they don’t need to buy unless they want to modify source without releasing, am I wrong about this?Edit: Doubled checked with gpt, no cases of “infection” yet, there has also been many talks about this license being very good

I think you&#x27;re thinking of the LGPL. The AGPL is basically GPL plus some additional requirements. I could see a company being OK with ~AGPL~ GPL but not ~GPL~ AGPL. I can&#x27;t imagine the opposite.Edit: Oops, typoed the license names.

I think you are thinking of GPL. Many companies are happy to use AGPL licensed software in their stack.

&gt; Enterprise customers can&#x27;t use software under AGPL because it risks infecting their IPThis is factually untrue. If you want to link an AGPL blob into your app and ship it to customers, sure. In the vastly more common case where you&#x27;re using a permissive client library[0] to connect to an AGPL server, there&#x27;s no risk whatsoever.At most, you might need to make your local changes to that server available to clients if they connect to it directly, as opposed to hosting a cloud SaaS setup where everything is internal to you. However, that&#x27;s not the worst thing in the world. &quot;Oh no, we improved a Free server our company depends on, and we have to share those improvements so that the person who gave us the server for free can also benefit from them&quot; is pretty hard for me to sympathize with.This is vastly more business-friendly than the non-FOSS SSPL.[0]<a href="https:&#x2F;&#x2F;github.com&#x2F;redis-rb&#x2F;redis-client&#x2F;blob&#x2F;master&#x2F;LICENSE.md">https:&#x2F;&#x2F;github.com&#x2F;redis-rb&#x2F;redis-client&#x2F;blob&#x2F;master&#x2F;LICENSE...</a>

For the type of software that Redis is intended for, integration over network is a must. Hence &quot;just using it&quot; isn&#x27;t a viable option. AGPL isn&#x27;t LGPL, it infects anything that uses it over a network. If Redis was AGPL when it was released, nobody would touch it.Most of the readers of HN make their living from closed source software. You know well enough that non-hostile open source is just a market entry strategy and the type of copyright-driven maximally selfish capitalist markets just force open source to be not viable for a single company to thrive. Projects like Linux kernel are exceptional infrastructure projects that external companies support not build businesses just to ship.

&gt; Enterprise customers can&#x27;t use software under AGPL because it risks infecting their IPYeah, this is BS.If you simply use AGPL software, it doesn&#x27;t &quot;infect&quot; anything. If you *change* the AGPL software, you have to release the changes. It forces the big clouds to open source their Redis improvements.

&gt; Enterprise customers can&#x27;t use software under AGPL because it risks infecting their IP, so they&#x27;re forced to buy an enterprise license.This is a lie. It&#x27;s FUD. And it should be disregarded with extreme prejudice. Stop it.First and foremost, AGPL&#x27;d software must remain free. They could use it in their stack. The rule is they must point to the sources of the AGPL&#x27;d software. If they make a change to the AGPL&#x27;d software and users interact with that (even over a network) then they must disclose the changes to the AGPL&#x27;d software. That&#x27;s it. They don&#x27;t have to open their whole stack. That&#x27;s SSPL, so stop spreading this FUD.Second, it&#x27;s not their IP. They didn&#x27;t write the AGPL&#x27;d software. They must abide by its terms.Third, even if they chose (emphasize on &quot;chose&quot; and not &quot;forced&quot;) to use AGPL&#x27;d software, they could simply disclose the changes they made to it. There is little to no excuse not to. The fact is that if the software meets their needs, they have little reason not to. The AGPL exists to protect Software Freedom so if they find that objectionable it can only be concluded that they intend to harm Free Software.

Here&#x27;s the play: Open source with AGPL, then offer an enterprise license. You get two wins. The OSS community applauds your adoption of an agressive OSS license. Enterprise customers can&#x27;t use software under AGPL because it risks infecting their IP, so they&#x27;re forced to buy an enterprise license.

Notably, Redis is about to sue Dragonfly for deliberate trademark confusion.

My personal opinion: we shouldn&#x27;t let Google&#x27;s bad policy poison our brains. The people who wrote that policy had their reasons for taking this position. It might have been the right thing for Google at the time the policy was written.That doesn&#x27;t mean it&#x27;s the right position for you, or for every situation. Many organizations with a higher levels of maturity in open source matters will take a more nuanced approach when it comes to AGPLv3 licensed software.

Their loss, at some point…I&#x27;m quite fed up with this GAFAM FUD against the AGPL and the GPLv3.

That&#x27;s the license working as intended, isn&#x27;t it?

So a hyperscaler bans the AGPL? Shocking.
Seems to be working as intended.

While I applaud the effort to repair developer trust, do note that many organizations prohibit the use of AGPL.Linked below is Google&#x27;s own stance on why AGPL is banned:<a href="https:&#x2F;&#x2F;opensource.google&#x2F;documentation&#x2F;reference&#x2F;using&#x2F;agpl-policy" rel="nofollow">https:&#x2F;&#x2F;opensource.google&#x2F;documentation&#x2F;reference&#x2F;using&#x2F;agpl...</a>

I think the big drop in trust was the change in licensing away from permissive in the first place, but AGPL-today is a much better choice than SSPL-forever.You probably can&#x27;t recover from a loss of trust in low single digit years unfortunately, but this is a good first step towards the project rebuilding the OSS community that existed around redis initially.Thanks for fighting for this. Hopefully this shows more companies stuck on source-available that you can achieve similar goals with OSS licenses.

The Valkey implementation of multi-threading is fundamentally different than what existed in Redis. The history dates back to work done in ElastiCache that was released as &quot;Enhanced IO&quot;, <a href="https:&#x2F;&#x2F;aws.amazon.com&#x2F;about-aws&#x2F;whats-new&#x2F;2019&#x2F;03&#x2F;amazon-elasticache-for-redis-503-enhances-io-handling-to-boost-performance&#x2F;" rel="nofollow">https:&#x2F;&#x2F;aws.amazon.com&#x2F;about-aws&#x2F;whats-new&#x2F;2019&#x2F;03&#x2F;amazon-el...</a>. The version released in Redis could only do about 350k RPS because of poor memory locality of operations, the inability to do command processing while handling I&#x2F;O, and the inability to offload much of the TCP read path. The new version in Valkey can achieve 1.2M RPS.&quot;They made certain improvements later&quot;, should be &quot;we threw away the old implementation and built a better one.&quot;

&gt; So this is actually another case of the benefits ValKey got for being able to clone Redis, receiving money from the hyper-scalers that just want to maximize their revenues...I don&#x27;t think you want to sling that mud, unless Redis switched to being a nonprofit when I wasn&#x27;t looking.

The I&#x2F;O threading was initially implemented by myself, when I was still working on the core before rejoining, and is also available in Redis. So this is actually another case of the benefits ValKey got for being able to clone Redis, receiving money from the hyper-scalers that just want to maximize their revenues...They made certain improvements later, but Redis 8 (see the release notes in my blog post if you are curious) improved this stuff a lot, too.Also, Redis 8 contains a new data structure, Vector Sets, that allows to do many useful things, together with more probabilistic data structures, single hash fields expires, and many other stuff. It is not factually correct that ValKey has any features edge over Redis I believe. We will see in the next year which project takes the best development path: this is what really matters.

Gladly, Valkey has other benefits besides its more permissive license compared to Redis. One of them is multi-threading support, which makes it pretty easy for someone like me—who has a bit of a skill issue with DevOps—to actually utilize all CPU cores for my caching layer.

<a href="https:&#x2F;&#x2F;redis.io&#x2F;blog&#x2F;redis-license-bsd-will-remain-bsd&#x2F;" rel="nofollow">https:&#x2F;&#x2F;redis.io&#x2F;blog&#x2F;redis-license-bsd-will-remain-bsd&#x2F;</a>

Cool, I&#x27;m definitely hoping for a sensible outcome. NATS has been a great tool to work with, and Synadia has also been great to work with.

<a href="https:&#x2F;&#x2F;www.cncf.io&#x2F;announcements&#x2F;2025&#x2F;05&#x2F;01&#x2F;cncf-and-synadia-align-on-securing-the-future-of-the-nats-io-project&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.cncf.io&#x2F;announcements&#x2F;2025&#x2F;05&#x2F;01&#x2F;cncf-and-synadi...</a>

apparently synadia is working with the linux foundation now to find a better way forward, and will release a joint statement soon. (CEO mentioned in their slack)

Why? Have you actually ready Synadia&#x27;s comments where they made it clear that they always intended to maintain the Apache 2 Version by contributing the stuff they build back to the main repo? It just won&#x27;t be as fast, so they can make some money first which will fund them giving it away.You said &quot;I also built a lot&quot; Are you making money off those projects or get paid for your services for that use?

Context:- <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=43829008">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=43829008</a>- <a href="https:&#x2F;&#x2F;github.com&#x2F;cncf&#x2F;toc&#x2F;issues&#x2F;1632">https:&#x2F;&#x2F;github.com&#x2F;cncf&#x2F;toc&#x2F;issues&#x2F;1632</a>- <a href="https:&#x2F;&#x2F;github.com&#x2F;nats-io&#x2F;nats-server&#x2F;issues&#x2F;6832">https:&#x2F;&#x2F;github.com&#x2F;nats-io&#x2F;nats-server&#x2F;issues&#x2F;6832</a>I also built a lot on NATS Jetstream, and I&#x27;m questioning my decision in light of the threatened license change.

Very interesting that this is happening at the same time that NATS is going proprietary. Obviously Redis is way more well known, but as someone who has built a bunch on NATS over the last few years, this makes Redis an interesting choice to migrate to again.

- 8.0 - Tri-licensed under RSALv2&#x2F;SSPLv1&#x2F;AGPLv3- 7.4 - Dual licensed under RSALv2&#x2F;SSPLv1- 7.2 and earlier - 3BSD

I am starting a new web app project and I wanted an in-memory store for session data. I just defaulted to Redis, literally yesterday doing the `npm install`.I mean, I remembered the whole Valkey saga after the license switch. I guess I&#x27;m just not as ideological as some here? I just thought &quot;I need a fast in memory object store&quot; and went with Redis as my default. I treat it like an appliance within my infrastructure.I also vaguely recall antirez going back to Redis (the company) during the AI boom to work on vector extensions to Redis. I believe he is a big part of why Redis is such a rock-solid piece of tech. I am more confident in this product with him influencing the trajectory.I also have the decision on license in the back of my mind. As I said, I am not an OSS zealot, but I do like the idea of an OSS license that has some protection against someone completely ripping off the code with no recourse. AGPL might be a decent compromise, especially with a dual license.

We need to stop taking the OSI or FSF&#x27;s positions on anything as particularly valuable.The OSI is captured entirely by corporate sponsors. Amazon was paying a full-time salary a year to the OSI when the SSPL issue happened, the OSI had no ability to take a moral pro-labor stance without crippling their own operations. They still do not meaningfully answer to individual users: The OSI recently refused to disclose who won their board election and installed their preferred candidates.And it will be inherently unethical to even consider the position of the FSF as long as it lacks the moral fortitude to permanently punt RMS from the board.If the OSI wasn&#x27;t owned by corporate interests, and had rightfully declared SSPL as a copyleft license... nobody would argue it isn&#x27;t. The problem is we&#x27;ve let an extremely problematic organization &quot;define&quot; something in a way that does not serve our interests.

This is not a widely accepted claim. I do not see SSPL as open source, and neither do OSI[0] or FSF[1] or Debian[2].[0]<a href="https:&#x2F;&#x2F;opensource.org&#x2F;blog&#x2F;the-sspl-is-not-an-open-source-license" rel="nofollow">https:&#x2F;&#x2F;opensource.org&#x2F;blog&#x2F;the-sspl-is-not-an-open-source-l...</a>[1]<a href="https:&#x2F;&#x2F;www.gnu.org&#x2F;licenses&#x2F;license-list.en.html" rel="nofollow">https:&#x2F;&#x2F;www.gnu.org&#x2F;licenses&#x2F;license-list.en.html</a>[2]<a href="https:&#x2F;&#x2F;www.debian.org&#x2F;legal&#x2F;licenses&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.debian.org&#x2F;legal&#x2F;licenses&#x2F;</a>

The difference is that SSPL is a license that was written in bad faith with the explicit intent that people can&#x27;t comply with the parts about running a hosted service.<a href="https:&#x2F;&#x2F;www.mongodb.com&#x2F;legal&#x2F;licensing&#x2F;server-side-public-license" rel="nofollow">https:&#x2F;&#x2F;www.mongodb.com&#x2F;legal&#x2F;licensing&#x2F;server-side-public-l...</a>See section 13, &quot;Offering the Program as a Service&quot;. To comply with that you need to release all software used &quot;to make the Program or modified version available as a service&quot; under the SSPL.For something like redis this includes: redis itself, the os you are using to host redis, the drivers and firmware for the hardware you are using to host redis, and more. Also your whole deployment stack up to and including the mouse drivers you use to click on the &quot;deploy&quot; button.It is an absurd condition that effectively makes section 13 say &quot;you can&#x27;t offer a hosted version&quot; and the OSI and FSF are right to reject that fig leaf of &quot;it is like the agpl, but more&quot;.

Flagged for misleading headline. SSPL is open source. It&#x27;s just not the open source you want.It meets all the criteria and the only difference from AGPL is how much source code you have to release and when - which is also the difference between GPL and AGPL. It has problems, but being closed source isn&#x27;t one of them.The OSI will never certify it, of course, because that would go against the business interests of the OSI members. The OSI is a consortium of companies who receive free labour from permissively licensed projects and to a lesser extent GPL projects, and it would like that to continue, which it cannot in practice under SSPL. The OSI article linked in a reply does not make a single point against the open-sourceness of the SSPL, and essentially just says they don&#x27;t like it, and that some companies won&#x27;t be able to comply, which is true of every free software license.The FSF, Debian, etc haven&#x27;t decided one way or another because it&#x27;s not a very widespread license and they can just use valkey instead of wasting the effort.

If you care about open source, and would like Llama 3 to also be open source (instead of the current license which, like Redis&#x27; SSPL, isn&#x27;t, depite Meta saying it is), you might want to add your vote to:<a href="https:&#x2F;&#x2F;github.com&#x2F;meta-llama&#x2F;llama3&#x2F;issues&#x2F;156">https:&#x2F;&#x2F;github.com&#x2F;meta-llama&#x2F;llama3&#x2F;issues&#x2F;156</a>

Mesmerizing number of views. I must admin I refreshed the page multiple times to see the count increase. If I increased the view count several times, I must admin I did not read the article multiple times.

I fairly recently dodge a bullet; I rewrote a large chunk of code I was working on using Akka because my idea lent itself fairly well to an actor system. I got it working fine with Akka on my local machine, I was about to make a PR for it at work, and then saw that it was using BUSL instead of Apache, which I had assumed it was using (since a lot of stuff in the Java world seems to use Apache).I did get my stuff working with Pekko (the Apache fork of Akka), and it did work, but I was so pissed off at the entirety of this that I ended up rewriting the entire thing again using Vert.x, which I double checked the license for before doing more work.I do understand why Akka feels like they have to use something like BUSL, it&#x27;s hard to make money as a smaller software company, doubly so for open source software, and I also realize me complaining that &quot;this free product made with free labor isn&#x27;t free enough for me&quot; is pretty entitled, but fundamentally I really don&#x27;t think that the BUSL (and its similar licenses) are the right way forward. Whether or not it&#x27;s fair, stuff like Akka does have competition from stuff that has more OSS-friendly stuff, and fundamentally I&#x27;m just going to use those, and if they&#x27;re not up to snuff I&#x27;ll augment them myself.

That&#x27;s a good point, traditional OSS licenses, we can like them or not, but they are &quot;understood&quot;.

That&#x27;s great news. I never liked the newly sprung up licenses. I understand the background but always felt a burden having to read and understand them, and wonder how they&#x27;d hold up in practice. GPL licenses have been around for decades and is something people, including legal teams, know more about.And when I say &quot;know&quot;, I don&#x27;t mean &quot;like&quot;: it could be that this will just make it easier for a particular team to decide that it doesn&#x27;t want to deal with the AGPL, and they should go find something else, but at least it&#x27;s clear what it is. As opposed to some BSSXYZWL license that you never heard of, which kind sounds like it&#x27;s open source but kind of isn&#x27;t...

&gt; AGPL+CLA is not a license I&#x27;d contribute under,Why not? Is it because only one company can make proprietary fork?Would you rather contribute to MIT software where everyone can make proprietary fork?
Or AGPL without CLA where nobody can make proprietary fork?

That&#x27;s sort of fine. As a personal user, someone could fork and maintain redis in that case, which wasn&#x27;t true in the SSPL era.Now AGPL+CLA is not a license I&#x27;d contribute under, but also Redis is so far down my priorities that it wasn&#x27;t a project I was going to be issuing PRs for anyway.

They still require a CLA [1] so there&#x27;s nothing stopping them from doing another relicense to a proprietary license tomorrow.The only way this remains open source forever is to accept AGPL-only licensed patches.[1]: <a href="https:&#x2F;&#x2F;github.com&#x2F;redis&#x2F;redis&#x2F;blob&#x2F;d65102861f51af48241f607afa678c4c2a0f894c&#x2F;CONTRIBUTING.md">https:&#x2F;&#x2F;github.com&#x2F;redis&#x2F;redis&#x2F;blob&#x2F;d65102861f51af48241f607a...</a>

Thanks, maybe this will be exemplary behavior for Elastic and Mongo.

Dismayingly, the CEO misspelled antirez&#x27;s last name in this press release, <a href="https:&#x2F;&#x2F;redis.io&#x2F;blog&#x2F;agplv3&#x2F;" rel="nofollow">https:&#x2F;&#x2F;redis.io&#x2F;blog&#x2F;agplv3&#x2F;</a>. That&#x27;s so incredibly disrespectful:&gt; Following our license change, in November of 2024 Salvatore Sanfillipo (antirez) decided to rejoin Redis as a developer evangelist. Collaborating with Salvatore on new capabilities, company strategy and community engagement has been a true privilege that has made a major impact that will pay dividends into the future.If it&#x27;s a true privilege, you should earn it by not misspelling his name. Actions speak louder than words.Pink Floyd has a song about this:Well, I&#x27;ve always had a deep respect and I mean that most sincereThe band is just fantastic, that is really what I thinkOh, by the way, which one&#x27;s Pink?And did we tell you the name of the game, boy?We call it riding the gravy trainWe&#x27;re just knocked out, we heard about the sell-outYou gotta get an album out, you owe it to the peopleWe&#x27;re so happy we can hardly countEverybody else is just green, have you seen the chart?It&#x27;s a hell of a start, it could be made into a monsterIf we all pull together as a team.

From this post on the Redis blog <a href="https:&#x2F;&#x2F;redis.io&#x2F;blog&#x2F;agplv3&#x2F;" rel="nofollow">https:&#x2F;&#x2F;redis.io&#x2F;blog&#x2F;agplv3&#x2F;</a> it looks like they&#x27;ve made a bunch of new features available under the new AGPL license too:&gt; Integrating Redis Stack technologies, including JSON, Time Series, probabilistic data types, Redis Query Engine and more into core Redis 8 under AGPLRedis Query Engine is new-to-me (I stopped following Redis closely after the license change) - it looks like an in-memory alternative to a lot of the things you might do with Elasticsearch: <a href="https:&#x2F;&#x2F;redis.io&#x2F;docs&#x2F;latest&#x2F;develop&#x2F;interact&#x2F;search-and-query&#x2F;" rel="nofollow">https:&#x2F;&#x2F;redis.io&#x2F;docs&#x2F;latest&#x2F;develop&#x2F;interact&#x2F;search-and-que...</a>With syntax that looks something like this:<pre><code> FT.SEARCH places &quot;museum @city:(san francisco|oakland) @shape:[CONTAINS $poly]&quot; PARAMS 2 poly &#x27;POLYGON((-122.5 37.7, -122.5 37.8, -122.4 37.8, -122.4 37.7, -122.5 37.7))&#x27; DIALECT 3
</code></pre>
(This is a smart move in terms of answering the question &quot;Why would I switch back to Redis if I&#x27;ve moved to Valkey&quot; - Redis just grew a bunch of new interesting features.)

I just read the AGPL and the FAQs and it&#x27;s not entirely clear to me either.Probably why many companies find AGPL toxic.

This is my number one objection to the AGPL.  Still way better than the SSPL or BUSL, but I will stick with valley for now.

I think this is correct, at least I hope so.I wish it were common for projects to explain in common language how they expect the license to work, with examples of how it applies to their project.

No. Users of Redis are the ones connecting to it. Furthermore, the Redis client library that you link into your program is MIT licensed. Unless you embed Redis directly into your app, you&#x27;d never have to release your own code to use it.

So with redis being AGPL, who counts as a user?If you have a webapp that uses redis on the backend for a task queue, do the users of the webapp count as users of redis, and you then have to provide source to redis? Is there a chance that you might have to release your apps code to be compliant?

Not a differentiated one.The AGPL, in its quest to be a EULA, violates free software Freedom 0 (&quot;The freedom to run the program as you wish, for any purpose&quot;).<a href="https:&#x2F;&#x2F;www.gnu.org&#x2F;philosophy&#x2F;free-sw.en.html" rel="nofollow">https:&#x2F;&#x2F;www.gnu.org&#x2F;philosophy&#x2F;free-sw.en.html</a>The AGPL literally demands specific functionality be present in the software that cannot be removed without breaking the license. The anticapitalist FSF zealots got so in love with the idea of closing what they call &quot;the ASP loophole&quot; that they wrote themselves a EULA.

You can run a SaaS company with AGPL-licensed software, no problem.What do you think is nonfree about AGPL?

You should stop imagining things like &quot;the AGPL is non free.&quot;The GNU Affero General Public License (GNU AGPL) is a free, copyleft license published by the Free Software Foundation.<a href="https:&#x2F;&#x2F;en.m.wikipedia.org&#x2F;wiki&#x2F;GNU_Affero_General_Public_License" rel="nofollow">https:&#x2F;&#x2F;en.m.wikipedia.org&#x2F;wiki&#x2F;GNU_Affero_General_Public_Li...</a>

This is disappointing. The AGPL is a nonfree (and nonsensical) license.The fact that the FSF wants a EULA but can’t have a EULA without violating Freedom 0 doesn’t make the AGPL suddenly logically sound.marcan has written about it in more detail than I care to: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=30044019">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=30044019</a>Stop using the AGPL. It violates the basic principles of free software.The ability to run a SaaS company with free software is a feature, not a bug.

cool, does this means it works on Windows now?

I am bit confused by the comments here.  Sure, it remains to be seen whether Redis Ltd. can be trusted again, but cannot we just be a happy for a bit that we (again) have a good software under a free license?

It&#x27;s a win for the community over and against the corporations that are Redis and Elastic. They&#x27;re not the good guys for giving in to the pressure. They tried to ride FOSS to prominence and then extract wealth on the backs of the community and found that the community mattered more than they did.So sure, let&#x27;s celebrate, but celebrate the community, not those who tried to pull the rug out from under them.

I’d say that open source definitely lost, and lost real bad.Free Software won, as you ended up adopting the AGPL.It’s an important distinction.

Thank you, Simon. I believe that cases like Elastic and Redis returning back to an open source license is like writing on the rock: &quot;open source won&quot;, at least in the system software space. Companies get created, prosper and fail over time, but this message is here to stay with us for a long time, and shapes the society of tomorrow. It&#x27;s a win of the software community itself.

I also appreciate this perspective because you never know what&#x27;s going on in the board room. I have seen some morally upstanding leaders make questionable decisions that were totally out of character for them, all for the sake of appeasing a narrow-minded investor.

&gt; it would be great if other companies with janky licenses could see &quot;Redis relicensed to open source and had a great boost out of it&quot;, not &#x27;Redis relicensed to open source and it didn&#x27;t help them at all&quot;.If the other companies can&#x27;t figure out that adopting a janky license and alienating the community is the self-inflicted problem, then they are beyond help. Relicensing to open source not helping the company may serve as a cautionary tale for other companies and may prevent them from repeating the same mistake. As an open source enthusiast, the worst case scenario is companies switching licenses tactically and frequently to test the waters and walking back with no consequences; I&#x27;d prefer the cost of such actions to be swift and severe.

&gt;Lots of cynical takes in this thread - and I get it, there isn&#x27;t a guarantee they won&#x27;t relicense again in the future (they have a CLA that would let them) and people feel betrayed by the last license change.Oh good. There is still hope of it returning to the original BSD license. 
( I am still using good old Memcached )

I don&#x27;t want companies to see, &quot;re-licensing to janky licenses is risk-free, because we can always go back to the old license if people react too negatively&quot;. I would like them to see, &quot;re-licensing to janky licenses is a death sentence which immediately makes your product almost completely irrelevant and causes the community to switch to a fork and never switch back&quot;.

It could be cynical, but I think it is important to show severe consequences for breaking trust between a company and its community. Anyone that saw their history and contributes to it must be aware they are doing unpaid work for a company.

Lots of cynical takes in this thread - and I get it, there isn&#x27;t a guarantee they won&#x27;t relicense again in the future (they have a CLA that would let them) and people feel betrayed by the last license change.I think we should celebrate this anyway. It&#x27;s a smart decision, it&#x27;s what the community wanted to happen and it would be great if other companies with janky licenses could see &quot;Redis relicensed to open source and had a great boost out of it&quot;, not &#x27;Redis relicensed to open source and it didn&#x27;t help them at all&quot;.I&#x27;m delighted. Thank you, team Redis.

Redis is open source again