• Docs
  • Changelog
Sign in
Get started
    • Home
    • Your first deploy
    • Free instances
    • Platform features by plan
    • Use with coding agents
    • FAQ
    • Templates
      • Migrate from…
        • Heroku
        • Railway
    • Compute plans
    • SandboxesBeta
      • Service types
        • Which to use?
        • Static sites
        • Web services
        • Private services
        • Background workers
        • Cron jobs
        • Workflows
        • Multi-service architectures
      • Data storage
        • Render Postgres
        • Render Key Value (Redis®-compatible)
        • Persistent disks
    • How deploys work
    • Supported languages
    • Git providers (GitHub, etc.)
    • Build pipeline
    • Deploy hooks
    • Monorepo support
    • Troubleshooting deploys
      • Previewing changes
        • Single-service previews
        • Preview environments (multi-service)
      • Docker deploys
        • Overview
        • Deploy a registered image
        • Using secrets
      • Runtime
        • Native runtimes
        • Environment variables & secrets
        • Default environment variables
    • Intro to sandboxes
    • Limits
      • How to…
        • Create & configure sandboxes
        • Execute commands
        • Manage files
        • Manage snapshots
      • Use with…
        • Claude Managed Agents
        • Cursor Cloud Agents
        • OpenAI Agents API
      • SDK/CLI reference
        • TypeScript SDK
        • Python SDK
        • CLI commands
    • Intro to workflows
    • Tutorial
    • Limits & pricing
      • How to…
        • Define tasks
        • Define flowsNew
        • Trigger runs
        • Develop locally
      • SDK reference
        • TypeScript SDK
        • Python SDK
      • Example workflows
        • TypeScript examples
        • Python examples
    • Overview
    • Create & connect
    • Database credentials
    • Extensions
    • Version upgrades
    • Logical replication
    • Legacy instance types
      • Database recovery
        • Recovery & backups
        • High availability
      • Database performance
        • Read replicas
        • Connection pooling
        • Admin apps
        • Repacking tables
        • Troubleshooting performance
    • Regions
    • Inbound IP rules
    • Edge caching
    • WebSockets
    • TLS certificates
      • Custom domains
        • Overview
        • Cloudflare
        • Namecheap
        • Other DNS providers
      • Internal traffic
        • Private network
        • Private links
      • Outbound traffic
        • Default IP ranges
        • Dedicated IP addresses
        • Outbound bandwidth
        • Handling network changes
      • Static site config
        • Custom response headers
        • Redirects & rewrites
    • The Render Dashboard
    • SSH / Shell access
    • Projects & environments
      • Service actions
        • Scaling
        • Rollbacks
        • Maintenance mode
        • One-off jobs
      • Infrastructure as code
        • Blueprints overview
        • render.yaml reference
        • Terraform provider
    • In-dashboard metrics
    • Health checks
    • Uptime best practices
      • Logging
        • In-dashboard logs
        • Log streams (syslog/HTTPS)
      • OpenTelemetry (OTel) metrics
        • Provider setup
        • Metrics reference
      • Notifications
        • Webhooks
        • Email / Slack
    • MCP Server
      • Render CLI
        • Overview
        • Command reference
      • REST API
        • Overview
        • API reference
      • Third-party connections
        • OIDC support
        • Datadog
    • Workspaces, members, & roles
    • Login settings
    • Audit logs
      • Organizations
        • Overview
        • SAML SSO
    • DDoS protection
    • Platform maintenance
      • Compliance
        • Overview
        • HIPAA (US health data)
        • HIPAA best practices
        • Shared responsibility model
        • Pentest policy
    • Heroku vs Render
    • Vercel vs Render

FAQ: Valkey on Render

New Render Key Value instances run Valkey instead of Redis®.

Render has adopted Valkey in place of Redis®* for all newly created instances of Render Key Value.

Existing Redis instances continue operating as usual. See details below.

FAQ

What is Valkey?

Valkey is an open-source key-value store that began as a fork of Redis version 7.2.4. For most applications and frameworks that connect to a Redis instance, Valkey is a drop-in replacement.

Valkey and Redis are completely independent projects that might diverge further over time.

Why has Render adopted Valkey for new Key Value instances?

In 2024, the Redis project moved from the BSD 3-clause license to the Redis Source Available License. This change imposed restrictions on offering Redis as a managed service (and also led to the creation of the Valkey project).

Valkey immediately gained strong community backing, and it has established itself as the leading open-source Redis-compatible datastore. After comparing it against other available options, we believe Valkey provides the most comprehensive combination of capabilities, compatibility, and community support for Render customers.

How do I create a Valkey instance?

When you create a new Render Key Value instance, that instance automatically runs Valkey. The creation process is largely identical to the previous process for creating Redis instances.

In a render.yaml Blueprint file, the values keyvalue and redis are equivalent for a service's type field: when used to create a new service, both values provision a Render Key Value instance that runs Valkey.

What will happen to my existing Redis instances?

Existing Redis instances will continue operating as usual, with the following platform changes:

  • Redis instances will no longer receive version updates.

    They will remain on version 6.2.14 indefinitely.

  • You cannot create new Redis instances, with one exception:

    Preview environments can create Redis instances as needed to accurately replicate your existing instances.

Do I need to migrate my existing Redis instances to Valkey?

No, but you're welcome to. For the vast majority of Render users, Valkey is a drop-in replacement for Redis.

Are there any changes to pricing?

No. Render Key Value compute plans remain unchanged in both specs and pricing. The only difference is that new instances run Valkey instead of Redis.


*Redis is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd. Any use by Render Inc is for referential purposes only and does not indicate any sponsorship, endorsement or affiliation between Redis and Render Inc.
FAQ: Valkey on Render
  • FAQ
    • What is Valkey?
    • Why has Render adopted Valkey for new Key Value instances?
    • How do I create a Valkey instance?
    • What will happen to my existing Redis instances?
    • Do I need to migrate my existing Redis instances to Valkey?
    • Are there any changes to pricing?
All Systems Operational
© Render Inc. All rights reserved.