Valkey stack for Redis-compatible caching and other in-memory data workloads.
Why teams use this stack
Start new instances with the right services already linked
Use a ready service baseline.
Deploy to managed Kubernetes, VMs, or dedicated servers
Keep one stack across hosting models.
Keep services current with managed stack auto-updates
Included services get managed updates through new revisions.
Reuse one stack across all environments
Create dev, staging, and preview copies with per-environment configuration.
Services
These are the services enabled by default when you create a new instance from the Valkey stack.
Stack services can be configured, added or removed for specific instances, and their versions can be changed as your workload evolves.
Explore the full stack service catalog for configs, settings, actions, cron, volumes, links, backups, and imports attached to each service in this stack.
Deploy
The stack stays the same while the hosting model changes. That lets you keep one stack across lighter environments, production clusters, and self-managed servers.
Start without running a cluster in your own account when you want the most managed option.
Keep the cluster in your own cloud account while using the same stack to deploy and operate the app.
Run the same stack on a VM, bare-metal, or dedicated server when you want a leaner self-managed setup.
Explore hosting options for this stack to compare Wodby Cloud, managed Kubernetes, and K3S in more detail.
Get started
Launch this stack with the enabled services, integrations, hosting options, and managed updates outlined on this page.
Stack control
Included service updates can mark the stack as outdated. Upgrading the stack releases a new revision, but existing instances stay on their current revision until you decide to move them or enable automatic updates.
Explore stack control to see how revisions, app-by-app upgrades, and auto-updates work.
Environments
Reuse the same Valkey stack for development, staging, production, customer-specific environments, or short-lived feature branches, with per-environment values and configuration overrides where needed instead of rebuilding the stack every time.
Create development and staging environments from the same stack
Teams can test against the same enabled services and integrations instead of maintaining a separate setup for non-production environments.
Spin up dedicated feature environments when teams need them
Short-lived environments can reuse the same stack instead of forcing teams to create a new stack for every branch or task.
Preview app instances on branch push are coming soon
Automatically create a new preview environment on branch push. Coming soon.
Explore app instances for reusable environments, preview apps, and branch-based workflows.
Get started
Reuse the same stack across environments without rebuilding the definition for every new instance.
FAQ
Valkey stack for Redis-compatible caching and other in-memory data workloads. Instances created from this stack inherit the services enabled by default, attached integrations, hosting options, and stack revision history.
You can reuse the same stack for multiple similar apps and for development, staging, production, and other environment types. The stack defines the shared services and defaults, you can set different values for env types such as dev and prod, and each app instance can still be configured individually.
When an included service gets an update, the stack can be marked as outdated. Upgrading releases a new stack revision, but existing instances stay on their current revision until you upgrade selected ones manually or enable automatic updates.
External providers stay attached to the stack definition so credentials, variables, and related services can be reused across app instances.
Yes. Development and production instances from the same stack can run on different hosting models, including Wodby Cloud, managed Kubernetes, and K3S on a VM or dedicated server, while keeping the same stack definition and upgrade path.