Already working as it is a Redis Fork.

Start docker:

docker run --name keydb ^
    -v keydb-data:/data ^
    -p 6379:6379 ^
    -d eqalpha/keydb

REDIS_URL
REDIS_HOST=127.0.0.1
REDIS_USERNAME=null
REDIS_PASSWORD=null
REDIS_PORT=6379
REDIS_DB=0

Cache::rememberForever("name", function(){
            return "Key DB Values from Laravel";
});

You can even use "Redis Insigth" to test it. Note that sometimes you might have to choose db1 to see the variables (don't know why yet)

https://prnt.sc/8fYqM0TKoUKB

Yes, there is ongoing work to replace Redis with KeyDB in various contexts. KeyDB, a multithreaded fork of Redis, offers several advantages such as enhanced performance due to its multi-threading capabilities, higher throughput, and features like active replication and FLASH storage​ (KeyDB - The Faster Redis Alternative)​​ (Palark | Blog)​.

KeyDB remains fully compatible with the Redis API, making migration relatively straightforward. The process involves creating a snapshot of the Redis database, shutting down the Redis server, and launching the KeyDB server with the existing configuration file. This approach minimizes downtime and leverages the same setup for both environments​ (KeyDB - The Faster Redis Alternative)​.

Organizations like Snap Inc. have successfully integrated KeyDB into their caching infrastructure, benefiting from its performance enhancements and additional features not available in Redis​ (GitHub)​. Additionally, the Linux Foundation's backing of open-source alternatives like Valkey demonstrates a growing interest in exploring Redis alternatives to provide more flexibility and open-source community support​ (Enterprise Technology News and Analysis)​.