One stack across environments
Use the same stack for development, staging, production, and customer-specific app environments instead of creating a different stack for each environment.
This page shows how the Matomo (buildable) 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 it runs on Wodby Cloud, in your own cloud account, or on your own server. Wodby maintains the cluster in all three cases.
Use the same stack for development, staging, production, and customer-specific app environments instead of creating a different stack for each environment.
Changing the hosting model does not force you to rebuild services, integrations, or the upgrade path attached to the stack.
Hosting models
Choose the infrastructure model that fits the environment while keeping the same stack, enabled services, and app upgrade path.
Wodby hosts the cluster, so you can run the stack without setting up a cloud account or server first.
Learn more
Keep the cluster in your own cloud account when networking, billing, or compliance need to stay there. Wodby creates it and keeps it up to date.
Learn more
Run the same stack on one VM, dedicated server, or bare metal server for budget hosting without Kubernetes scaling. You keep the server’s operating system updated.
Learn more
Keep lightweight development or preview environments cheaper and simpler, while production can move to the hosting model that matches scale, networking, or compliance needs.
The same services, integrations, configs, and revision model can move from lower environments to production without redesigning the app around a new platform.
Move from a managed starting point to your own cluster or servers when requirements change, while keeping the same stack definition and app behavior.