IAianm218·Jul 24, 2026
https://github.com/ianm199/valdr
I made a Rust version of Valkey/ Redis was wondering if this would become relevant.
In Kimi K3 exploited the latest Redis serverianm199
valdr
Rust2026–2026
ianm199 / valdr
valdr
A Valkey-compatible cache/store in safe Rust. ~98% drop-in for non-clustered single-node deployments.
2Distinct people
8Mentions
0Explicit recommenders
11GitHub stars
What to know before exploring
What it is
A Valkey-compatible cache/store in safe Rust. ~98% drop-in for non-clustered single-node deployments.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week8 dated mentions
Observed mentions: 2026-06-01 16:23:47 UTC to 2026-07-24 22:09:02 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jun 1 | 2026-06-01 00:00:00 UTC | 2026-06-08 00:00:00 UTC | 5 | 1 | 4 |
| Jun 8 | 2026-06-08 00:00:00 UTC | 2026-06-15 00:00:00 UTC | 1 | 0 | 1 |
| Jun 15 | 2026-06-15 00:00:00 UTC | 2026-06-22 00:00:00 UTC | 0 | 0 | 0 |
| Jun 22 | 2026-06-22 00:00:00 UTC | 2026-06-29 00:00:00 UTC | 0 | 0 | 0 |
| Jun 29 | 2026-06-29 00:00:00 UTC | 2026-07-06 00:00:00 UTC | 1 | 0 | 1 |
| Jul 6 | 2026-07-06 00:00:00 UTC | 2026-07-13 00:00:00 UTC | 0 | 0 | 0 |
| Jul 13 | 2026-07-13 00:00:00 UTC | 2026-07-20 00:00:00 UTC | 0 | 0 | 0 |
| Jul 20 | 2026-07-20 00:00:00 UTC | 2026-07-27 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
8 sources> Maybe the takeaway is that 20% is about all the LLM can muster
At this point there's a long list of projects that have used LLMs to rewrite a system in Rust including:
- Bun (https://github.com/oven-sh/bun/pull/30412)
- Valkey (https://github.com/ianm199/valdr)
- Git (https://github.com/gitbutlerapp/grit)
- Postgres (https://github.com/malisper/pgrust)
With the exception of Bun, these projects were done pre-fable too, so I bet Fable will make these types of rewrites even easier.
In My AI-built PHP engine in Rust passes 17% of PHP-src tests, renders WordPressI have been working on the same problem in other areas. My ultimate goal is to rewrite nginx in Rust passing as much as the upstream tests as possible while leveraging the strongest aspects of Ruts ecosystem - i.e. rustls (modern memory safe OpenSSL), Tokio (async runtime), h2 (http 2 impl) rather than implementing from scratch like the upstream. I started with Lua, then porting over Valkey, and now working on nginx. The reason was because I wanted to learn the ins and outs before taking on the most complex portion.
[1]. https://github.com/ianm199/lua-rs/tree/main Lua
[2]. https://github.com/ianm199/valdr Valkey/ Redis
[3]. https://github.com/ianm199/nginx-rs-port nginx
Happy to answer any questions on the approach! When I started a few weeks ago the harnesses on their own were not good enough to get very far without a "meta harness" of s
Read the rest
orts but that is changing largely with Claude Workloads and Mythos. A lot of the work is developing some custom tooling to move these along faster.
Posted this in a thread yesterday but seems relevant, I have been working on similar open source rewrites. Starting with Lua and Nginx. Trying to target idiomatic/ performant safe Rust from the start than straight porting and adding safety/ performance later.
- Valkey/ Redis port here https://github.com/ianm199/valdr (passes ~99% of single node test suite, real prod features like replication/ clustering/ HA early or not implemented)
- Further along port of Lua 5.1-5.5 https://github.com/ianm199/lua-rs-port/tree/main
- I have a less developed nginx version that would be the North Star
- These projects are very alpha at the moment.
The thought was that we might need many “shots on net” in terms of software safety in the future so worth exploring.
In Bun has been converted to rust. Now what?In case the topic of memory safety is interesting to anyone I've been experimenting with using AI agents to port common web infra projects to safe/ performant Rust. Somewhat inspired by the Bun port - was thinking that at some point memory safety might be such a big deal that people just need drop in replacements.
- Valkey/ Redis port here https://github.com/ianm199/valdr (passes ~99% of single node test suite, real prod features like replication/ clustering/ HA early or not implemented)
- Further along port of Lua 5.1-5.5 https://github.com/ianm199/lua-rs-port/tree/main
- I have a less developed nginx version that would be the north star
- These projects are very alpha at the moment
If anyone is interested in getting involved in this or has done similar experiments I'd love to collaborate! There is so much variation in how you can run th
Read the rest
ese large scale agent fleets I don't think anyone has a perfect system yet.
I'd love to see where you end up on this! Happy to hop on a call or something too and get your impression.
This is how I was running the benchmarks https://github.com/ianm199/valdr#benchmark-commands . I hope that is helpful.
Redislab team is definitely legit! Valkey and then projects like this stand on the shoulder of giants
In Show HN: Valdr - Valkey/Redis in safe Rust, passes >99% of Valkey test suiteInspiration for this project is the changing landscape around memory safety + the ability to build quickly against benchmarks and test suites
Overview:
- valdr is a single node Redis/ Valkey server, drop in for RESP2/RESP3
- ~12 unsafe blocks, all at FFI/syscall boundaries, data path is zero-unsafe. Out of these some can be removed by changing the Lua dependency to a rust version
- Supports all the core features, didn't implement clustering, high availability, or the C ABI for now. Roadmap here https://valdr.dev/roadmap.html
Performance:
- Faster than upstream on core commands, especially with high pipeling (GET 1.3X, Set 1.4X, LRANGE up to ~1.6x)
- The win mainly comes from Rust's borrow checker, the rest is scattered. Some if it is because we just implement less features than
- Reproduction steps here https://github.com/ianm199/valdr#
Read the rest
benchmark-commands
Why I built it:
- The landscape of OSS security is changing greatly, I was thinking that if memory safety becomes an even larger issue it is good to have drop in memory safer alternatives
- The bun rewrite kicked off a lot of discussion in this area, I was curious if you could take the great parts of that with closer to creating a port that is closer idiomatic/ safe Rust
- The Rust community has built some great primatives like rustls and tokio, and now is a great time to build on top of those. This project doesn't use tokio but likely will when I implement thread pooling
How it was built:
- Heavily leveraged by orchestrated AI agents between Claude Code and Codex + API calls to other providers
- I developed several different porting harnesses in the process although none that are yet good enough to share and be useful
- Tuned performance using a suite of tools to track hotspots in the code, happy to share more details
Try it:
- docker run --rm -p 6379:6379 ghcr.io/ianm199/valdr:alpha then point any redis client at it
- This project is definitely in an alpha state - would love for anyone to throw some real workloads at it and let me know what you think!
Show HN: Valdr - Valkey/Redis in safe Rust, passes >99% of Valkey test suite
5 points · Open discussion