render-keyvalue

Provisions and configures Render Key Value instances for caching, sessions, and job queues.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/DingJun1028/esggo-kv --skill render-keyvalue-dingjun1028
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: render-keyvalue
Source: https://github.com/DingJun1028/esggo-kv/tree/main/.agents/skills/render-keyvalue
Command: npx skills add https://github.com/DingJun1028/esggo-kv --skill render-keyvalue-dingjun1028

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up a Redis-compatible store on Render involves several decisions that are easy to get wrong: choosing the right maxmemory policy, wiring connection strings into services, configuring the required ipAllowList in Blueprints, and understanding internal versus external URLs. This Skill guides you through provisioning and configuring Render Key Value (Valkey 8) instances correctly the first time. ## Core Features & Use Cases - Blueprint Configuration: Generate valid render.yaml Key Value services with the mandatory ipAllowList field and correct maxmemoryPolicy for your workload. - Connection Wiring: Wire REDIS_URL into web services and workers using fromService with type: keyvalue and the connectionString property. - Policy Selection: Choose between allkeys-lru for caches and noeviction for job queues so queued jobs are never silently evicted. - Use Case: You are deploying a Node.js API with a BullMQ background worker on Render. Use this Skill to create a Key Value instance with noeviction, wire REDIS_URL to both services via Blueprint, and connect with ioredis using the internal URL. ## Quick Start Ask the assistant to create a Render Blueprint with a Key Value instance named cache using the allkeys-lru policy and wire its connection string to your web service as REDIS_URL.

Frequently Asked Questions about render-keyvalue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a Redis instance to a Render Blueprint?▼

Add a service with `type: keyvalue` in your render.yaml, set a plan and region, choose a `maxmemoryPolicy`, and include the required `ipAllowList` field. Use `ipAllowList: []` for internal-only access, which is recommended for most applications.

Which maxmemory policy should I use for a job queue on Render?▼

Use `noeviction` for job queues so keys are never dropped when memory fills; writes return an error instead. Using `allkeys-lru` for queues silently evicts queued jobs, which causes lost work.

Does Render Key Value work with existing Redis client libraries?▼

Yes. New Render Key Value instances run Valkey 8, a drop-in Redis fork, so existing clients like ioredis, node-redis, redis-py, redis-rb, Sidekiq, and go-redis work without changes. Legacy instances created before February 2025 run Redis 6.

How do I connect a Render service to Key Value with REDIS_URL?▼

Wire it in your Blueprint using `fromService` with `type: keyvalue` and `property: connectionString` under the service's envVars. This injects the internal URL, which has lower latency and requires no authentication by default.

Why does my Render Key Value connection fail with an allowlist error?▼

The error means your IP is not in the instance's access control list for external connections. Add your IP in CIDR notation under the instance's Networking settings in the Dashboard. Internal connections from same-region Render services are unaffected.

What happens to Key Value data when upgrading from the free plan?▼

All data is lost when upgrading from a free instance because free instances have no disk persistence and are recreated with disk backing. Export critical data before upgrading, or start on a paid plan for production workloads.