Persistent hosting, not throwaway demos
Run real application environments with Wodby-managed stacks, services, integrations, scaling, and releases.

Application hosting
Start with Wodby Cloud when you want Wodby to manage the cluster layer, or use your own managed Kubernetes or self-hosted Kubernetes infrastructure while keeping the same stack-based delivery workflow.
Hosting models
Wodby hosting is built around reusable stacks and app instances, so the deployment workflow stays consistent as infrastructure needs change.
Use Wodby-hosted persistent clusters when you want the lowest operational workload and do not want to prepare a cloud account or server.
Explore option
Connect a managed Kubernetes provider when you want infrastructure in your own account while still using Wodby for delivery workflows.
Explore option
Run a budget single-server Kubernetes setup with K3s when one server is enough and you do not need Kubernetes scaling.
Explore option
Stack hosting
These pages explain how each stack fits Wodby Cloud, managed Kubernetes, and self-hosted Kubernetes. They are here for teams comparing a specific application runtime or CMS.
Host Drupal with Wodby Cloud, managed Kubernetes, or self-hosted Kubernetes.
View hosting page
Host Laravel with Wodby Cloud, managed Kubernetes, or self-hosted Kubernetes.
View hosting page
Host Next.js with Wodby Cloud, managed Kubernetes, or self-hosted Kubernetes.
View hosting page
Host Node.js with Wodby Cloud, managed Kubernetes, or self-hosted Kubernetes.
View hosting page
Host OpenClaw with Wodby Cloud, managed Kubernetes, or self-hosted Kubernetes.
View hosting page
Host PHP with Wodby Cloud, managed Kubernetes, or self-hosted Kubernetes.
View hosting page
Host WordPress with Wodby Cloud, managed Kubernetes, or self-hosted Kubernetes.
View hosting page
Run real application environments with Wodby-managed stacks, services, integrations, scaling, and releases.
Keep SSL, backups, access control, CI/CD, logs, and app environments close to the hosting model.
Start with Wodby Cloud for less operational work, or use managed Kubernetes and self-hosted Kubernetes when ownership or cost profile matters more.
Recommended starting point
You can still move to your own Kubernetes provider or self-hosted Kubernetes later. The stack and application workflow stay aligned.