I built Steadykey after fighting duplicate API calls and messy idempotency logic in our queue workers. It canonicalizes any JSON payload (order-insensitive, handles Maps/Sets/BigInts) and hashes it to a stable key, then lets you drop markers into Redis, Postgres, MySQL, MongoDB, SQLite, or an in-memory adapter. You can opt in to storing the canonical payload, refresh TTLs, or clear markers when a workflow finishes. I’d love feedback on the hashing semantics, adapter API, and any gaps in the docs/examples—especially if you’ve rolled your own idempotency layer before.
Show HN: Steadykey – Deterministic Idempotency Keys with Pluggable Stores | Heykuki News