Skip to content

feat(jawn): add official Valkey backend support with CI and docs - #5764

Open
rileydes-improving wants to merge 1 commit into
Helicone:mainfrom
rileydes-improving:feat/valkey-support
Open

feat(jawn): add official Valkey backend support with CI and docs#5764
rileydes-improving wants to merge 1 commit into
Helicone:mainfrom
rileydes-improving:feat/valkey-support

Conversation

@rileydes-improving

Copy link
Copy Markdown
  • Add integration test validating all Redis command patterns against Valkey
  • Add GitHub Actions workflow running Jawn tests against valkey:8-alpine
  • Add self-hosting documentation for Valkey as a supported backend
  • Zero application code changes; ioredis connects to Valkey transparently

Ticket

#5753

Component/Service

What part of Helicone does this affect?

  • Web (Frontend)
  • [ x ] Jawn (Backend)
  • Worker (Proxy)
  • Bifrost (Marketing)
  • AI Gateway
  • Packages
  • [ x ] Infrastructure/Docker
  • [ x ] Documentation

Type of Change

  • Bug fix
  • [ x ] New feature
  • Breaking change
  • [ x ] Documentation update
  • Performance improvement
  • Refactoring

Deployment Notes

  • [ x ] No special deployment steps required
  • Database migrations need to run
  • Environment variable changes required
  • Coordination with other teams needed

No application code is modified. Operators already on Valkey continue working as-is. Operators on Redis are completely unaffected. For new Valkey adopters, the only change is pointing REDIS_HOST at their Valkey endpoint.

Extra Notes

  • Jawn's existing CI already exercises the graceful-degradation (no-Redis) path implicitly. This PR adds coverage for the Valkey-present path.

Context

Helicone's Redis dependency in Jawn works with Valkey transparently (all commands predate the fork), but this compatibility is undocumented, untested in CI, and invisible to operators evaluating Helicone's stack. Two of three closest competitors (LangFuse, LangSmith) already officially support Valkey. This PR adds tests, CI, and documentation confirming what already works.

The five subsystems that touch Redis (KV cache, proxy rate limiter, HTTP API rate limiter, usage-limit cache, encrypted provider key/auth cache) all share a single ioredis client and issue only core Redis commands present since Redis 2.x, all fully supported in Valkey.

- Add integration test validating all Redis command patterns against Valkey
- Add GitHub Actions workflow running Jawn tests against valkey
- Add self-hosting documentation for Valkey as a supported backend
- Zero application code changes, ioredis connects to Valkey transparently

Signed-off-by: Riley Desserre <riley.desserre@improving.com>

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your trial has ended. Reactivate Greptile to resume code reviews.

@vercel

vercel Bot commented Aug 7, 2026

Copy link
Copy Markdown

@rileydes-improving is attempting to deploy a commit to the Helicone Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant