Service type
Datastore service
Datastore service
Redis service
In-memory datastore service for caching, queues, sessions, and other low-latency workloads.
Use it as a reusable, versioned service inside custom or predefined stacks so teams can keep the runtime and operational model consistent.
Why teams use this service
Technical profile
Review versions, ports, source, and packaging.
Stacks that use it
See where this service fits in ready-made stacks.
Runtime wiring and defaults
See ports, links, storage, configs, and runtime behavior.
Valkey is the open-source replacement for Redis
See why Valkey is the better fit going forward.
Overview
Technical profile and packaging
This page shows how Redis is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.
Versions
8.6, 8.4, 8.2, 8.0
Source repository
Public Helm chart
Ports and protocols
6379/TCP
Labels
redis
Persistent volumes
Data
Stacks
Use it inside ready-made stacks or your own
These public stacks already include Redis as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.
Runtime wiring
Reuse connectivity, storage, and runtime defaults
This service can expose ports, connect to other services, attach persistent storage, and define runtime defaults that become reusable inside stacks rather than being rebuilt case by case.
Endpoints
6379/TCP
Volumes
Data
Replacement
Valkey is the open-source replacement for Redis
Valkey is the full open-source community-driven drop-in replacement for Redis. Use it when you want Redis-compatible behavior with the community-led project.