People who run key-value stores ask the same small questions over and over. Which cluster node holds this key? Why did that command fail with CROSSSLOT? How much memory will two million keys take? Will this redis.conf even start? What happens to my keys when a sixth server joins? The answers usually come from a one-off script, a half-remembered blog post, or pasting real data into some website and hoping for the best.
KeyValueStore.com turns those jobs into tools. It publishes free, open-source tools for Redis and Valkey, DynamoDB, etcd and the ideas behind them. Every tool runs in your browser, and nothing you paste leaves the page.
The Pitch in Four Numbers
- 15 free tools, each built on one JavaScript file.
- 0 bytes sent anywhere. Each page’s security policy blocks it from contacting other sites, and the tools keep working offline once loaded.
- 0 dependencies to install.
- 15 Redis and Valkey versions built from source and tested against.
The Tools
A few of them show the range. The Cluster Rebalancing Planner works out how to spread the 16,384 slots when a new primary joins a Redis or Valkey cluster. The Memory Calculator estimates what your keys will cost in memory. The Config Checker reads redis.conf the way each version does and flags lines that would stop the server from starting. The ACL Builder writes Redis and Valkey ACL rules and drafts least-privilege users from MONITOR output.
For DynamoDB, the Expression Tester checks conditions, filters and updates against DynamoDB Local, which matters when there are 563 reserved words, “status” among them. For etcd, the Revision Viewer opens snapshots and shows the revisions of a Kubernetes object, handy when you hit the default 2 GiB quota. The Graph Key Builder shows the keys a graph uses in RocksDB, LMDB or etcd and what each hop costs. And the Consistent Hashing Playground compares modulo hashing, a hash ring, rendezvous hashing and jump hash. Add a sixth server to five, and modulo moves 83% of keys while jump hash moves 17%.
How It Works
Each tool’s logic is one JavaScript file with no dependencies. The same file powers the web page, a Node.js command line and the tests. Three of the tools, the Memory Calculator, Config Checker and ACL Builder, answer from recordings of real servers, one per patch release. The tools were checked against the real systems: Redis and Valkey built from source, DynamoDB Local, the etcd and Kubernetes code, the AWS SDK, the Python mmh3 package, the original jump hash code and values written by Python, PHP, Java and Ruby. The tests replay those recordings, and the results are on GitHub. Each tool’s folder has a README that explains the technology in plain words.
Who It’s For
- Engineers and operators running Redis, Valkey, DynamoDB or etcd.
- Anyone sizing a cache or planning a cluster change.
- Security-minded teams writing ACLs who don’t want production data on a third-party site.
- Kubernetes operators digging into etcd when something’s gone wrong.
- Students and engineers learning how consistent hashing actually behaves.
Limits
Most tools are tested against the current Redis and Valkey releases. A couple, the Snapshot Viewer and Traffic Analyzer, go back to Redis 2.8 because those formats changed over time. Where the version matters, the tool says so. The site is independent and isn’t affiliated with Redis, Valkey or AWS. And it isn’t a hosted data service: your data stays in your browser.
The Four-Question Screening
Every project featured here gets the same four questions, the way you’d screen a startup idea.
1. Where is the money in it?
The tools are free under Apache 2.0, with no paid tier. This is a classic utility site: its value is traffic from engineers searching for exactly these answers. The money paths are sponsorship from managed Redis, Valkey and DynamoDB providers who want to reach those engineers, a paid desktop or team bundle with saved configurations, and consulting for cluster sizing and migrations. A trusted, private tool set is a strong way to earn attention in a crowded infrastructure market.
2. What real problem does it solve?
Small, recurring operational questions that waste time and invite mistakes. A wrong memory estimate, a config that won’t start or an ACL that’s too open all cause real incidents. And pasting production data into random websites to answer them is its own risk.
3. The technology in plain words
Think of a toolbox for a particular kind of engine. Each tool does one fiddly job, like a gauge for one bolt size. You use them right on your own bench, so nothing about your engine leaves the garage, and each tool was calibrated against the real engine before it went in the box.
4. Moat and differentiation
There are scattered calculators and blog posts for each of these questions. KeyValueStore gathers them in one place, verifies them against the real systems version by version, and keeps everything private in the browser. The moat that can grow is breadth and accuracy across stores and versions, plus the search traffic that comes with being the place people land when they have these questions.
Why It Matters
Key-value stores sit under almost every modern app. Getting the small details right, memory, config, permissions, hashing, prevents a surprising number of outages. Free, private tools that get those details right are useful every day.
Follow the Project
Browse all the tools, read what a key-value store is, try the Consistent Hashing Playground, or get the code from the KeyValueStore tools repository on GitHub. KeyValueStore is listed with the other open-source projects on SoftDevStudio.com, and more featured projects are in the Projects section.