Ok so now it seems like Redis is back to the opensource world

After the rug pull took place, I tried limiting my usage of Redis as Valkey, its opensource replacement had some issues with my installation

But now... Should it be the sign to finally try again a Valkey operator and remove all my redis instances ?!

Damn, Valkey is cooking Redis

https://www.youtube.com/watch?v=9hDvWVJtljE

LMAO look who came crawling back, after I already switched to Valkey. There is no way I am switching back, but good for the folks who are still on Redis, and get to live through a seamless transition back to open code.

https://linuxiac.com/welcome-back-to-the-open-source-family-redis/ #Redis #Valkey #FOSS

Good News! Redis is Open Source Again but ... too late #valkey #redis

https://news.itsfoss.com/redis-open-source-again/

What I learned during the license switch —Creator of Redis

https://antirez.com/news/152

Redis is now available under the AGPLv3 open source license

#redis #valkey

https://foojay.io/today/redis-is-now-available-under-the-agplv3-open-source-license/

I'm glad that Redis is open source again, but what prevents them from rug pulling the license in the future again?

At this point it's a better choice to stay with the successful fork developed in an open collaboration under a neutral governance, Valkey.

Fool me once. You can't fool me twice. I'm now using Valkey everywhere. Redis is trying to go back to an open source license.... Little too late now.

https://redis.io/blog/agplv3/

So #Redis changed its license again and returned to #FOSS by adopting #AGPL. I'm curious to see how it will go against #valkey. Is it too late to regain credibility in the community? Maybe a possible future for other projects that share the same destiny. There was once upon a time Hashicorp...

Redis in-memory data store returns to its open-source roots by adopting AGPLv3 in Redis 8 to address community concerns.
https://linuxiac.com/welcome-back-to-the-open-source-family-redis/

https://blog.gslin.org/archives/2025/05/02/12380/redis-%e5%ae%a3%e4%bd%88%e5%b0%87%e4%bd%bf%e7%94%a8-agplv3-ssplv1-rsalv2/

Redis 宣佈將使用 AGPLv3/SSPLv1/RSALv2

Last year, #Redis changed its license to the #SSPL, which is neither an #OpenSource nor a #FreeSoftware license. This led to #Valkey, a fork and drop-in replacement.

Now Redis has decided to go back to a real Free Software license, the #GNU #AGPL. This is a great decision, although it remains to be seen if they reverted their decision in time, or if it is too late and the community will continue with Valkey and not look back.

https://redis.io/blog/agplv3/

Looks like Redis is open-source again.

1. DB starts as open-source to get community goodwill and free labor
2. They pull a bait-and-switch, and change their license to a non-open-source one
3. Open-source community instantly creates a fork
4. User base gradually moves to fork
5. Original project becomes less and less relevant
6. They decide to switch back to an open-source license, but now all the users are on open-source forks

Happens every single time.

Even if it’s @antirez saying this, it’s just too late and It doesn’t solve the issue with CLA and the trust in the organisation.

https://antirez.com/news/151 «Redis is open source again »

Let’s go for https://valkey.io/

Under pressure from #valkey, Redis goes back to open source license.

"After I joined the company, and a year of evaluating alternatives, in March 2024, we decided to move Redis to the SSPL license. This achieved our goal—AWS and Google now maintain their own fork—but the change hurt our relationship with the Redis community. SSPL is not truly open source..."

https://redis.io/blog/agplv3/

I spent probably a weeks worth of hours learning more #kubernetes so I could save $60 a month.

I have a nice 3 node kube cluster with a 2 node #keepalived #haproxy TCP load balancer. All on #ARM VPS.

Haproxy ingress
#ExternalDNS operator
#CertManager
#RookCeph
#ArgoCD
#KeyCloak
#ValKey
#Mastodon
#CloudNativePG #Postgresql