One stack across environments
Use the same stack for development, staging, production, and customer-specific app instances instead of creating a different stack for each environment.
Deploy the ZooKeeper stack
This page shows how the ZooKeeper stack fits the available hosting models on Wodby. The stack definition stays the same while the underlying infrastructure changes.
That means the default services, third-party integrations, and revision model stay attached to the same stack whether you run a fast managed environment, a cluster in your own cloud account, or a leaner self-managed server setup.
Infrastructure choice stays flexible
Changing the hosting model does not force you to rebuild services, integrations, or the upgrade path attached to the stack.
Hosting models
Three ways to run this stack
Choose the infrastructure model that fits the environment while keeping the same stack, enabled services, and app upgrade path.
Wodby Cloud
Start without creating or operating a separate cloud account when you want the most managed way to run the stack.
Learn more
Managed Kubernetes
Keep the cluster in your own cloud account and use the same stack when networking, billing, or compliance need to stay under your control.
Learn more
K3S on your own servers
Run the same stack on a VM, dedicated server, or bare metal when you want a lighter self-managed setup.
Learn more
Match the hosting model to the environment
Keep lightweight development or preview environments cheaper and simpler, while production can move to the hosting model that matches scale, networking, or compliance needs.
Promote the same stack toward production
The same services, integrations, configs, and revision model can move from lower environments to production without redesigning the app around a new platform.
Change infrastructure without replatforming the app
Move from a managed starting point to your own cluster or servers when requirements change, while keeping the same stack definition and app behavior.