Datastore service

Valkey service

Redis-compatible datastore service for caching, queues, sessions, and other in-memory workloads.

Use it as a reusable, versioned service inside custom or predefined stacks so teams can keep the runtime and operational model consistent.

All services

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.

Overview

Technical profile and packaging

This page shows how Valkey is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.

Service type

Datastore service

Versions

8.1, 7.2

Source repository

wodby/service-valkey

Public Helm chart

wodby/valkey

Ports and protocols

6379/TCP

Labels

valkey

Persistent volumes

Data

Stacks

Use it inside ready-made stacks or your own

These public stacks already include Valkey 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.

Drupal 10 Drupal 11 Laravel Matomo Next.js Node.js PHP Valkey WordPress

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