Start with the application outcome
Choose PaaS, DevOps, or hosting first, then narrow the infrastructure model around the level of ownership your team wants.
Solutions
Choose the Wodby path that matches what your team needs to ship
Use Wodby as a Kubernetes PaaS, a managed DevOps layer, or an application hosting platform. Then pick Wodby Cloud, your own managed Kubernetes provider, or K3S as the infrastructure model.
Featured solutions
Start from the buying intent, not the infrastructure checklist
These are the main entry points for teams evaluating Wodby: a Kubernetes application platform, managed DevOps workflows, or stack-aware hosting.
Platform
Kubernetes PaaS
Deploy applications on Kubernetes with managed stacks, environments, CI/CD, scaling, backups, and access control in one platform workflow.
Explore Kubernetes PaaS
Operations
DevOps as a Service
Reduce platform setup and maintenance work with a managed delivery model for clusters, releases, environments, and routine app operations.
Explore DevOps as a Service
Hosting
Managed application hosting
Host Drupal, WordPress, Laravel, Next.js, Node.js, PHP, and OpenClaw apps on Wodby Cloud, managed Kubernetes, or K3S.
Explore app hosting
Infrastructure paths
Pick the hosting model after the solution is clear
Wodby keeps the application workflow consistent while letting teams choose how much infrastructure ownership they want.
Hosted by Wodby
Wodby Cloud
Use Wodby-hosted persistent clusters when you do not want to bring your own cloud account, Kubernetes cluster, or server.
Explore Wodby Cloud
Your cloud account
Managed Kubernetes
Connect a managed Kubernetes provider when you want infrastructure ownership while keeping Wodby’s app delivery workflow.
Compare providers
Cost control
Affordable Kubernetes with K3S
Run a lean Kubernetes-compatible setup on servers or VMs when ownership and lower infrastructure cost matter more.
Read the K3S guide
Stack hosting
Open the hosting page for the application stack you run
Each stack page explains how that runtime or CMS fits Wodby Cloud, managed Kubernetes, and K3S.
Drupal hosting
Host Drupal on Wodby Cloud, managed Kubernetes, or K3S.
View hosting page
Laravel hosting
Host Laravel on Wodby Cloud, managed Kubernetes, or K3S.
View hosting page
Next.js hosting
Host Next.js on Wodby Cloud, managed Kubernetes, or K3S.
View hosting page
Node.js hosting
Host Node.js on Wodby Cloud, managed Kubernetes, or K3S.
View hosting page
OpenClaw hosting
Host OpenClaw on Wodby Cloud, managed Kubernetes, or K3S.
View hosting page
PHP hosting
Host PHP on Wodby Cloud, managed Kubernetes, or K3S.
View hosting page
WordPress hosting
Host WordPress on Wodby Cloud, managed Kubernetes, or K3S.
View hosting page
Keep production operations close
Use the same platform surface for environments, releases, backups, access control, scaling, and troubleshooting.
Match cost to control
Start with Wodby Cloud for the least infrastructure work, or use managed Kubernetes and K3S when ownership or economics matter more.
Evaluation stage
Compare the platform model before choosing a path
If you are evaluating lock-in, platform ownership, or alternatives to existing hosting and PaaS vendors, start with the open platform and comparison pages.
Open platform without vendor lock-in
Use standard Kubernetes foundations, public artifacts, and transparent stack components when portability matters.
Explore open platform
Compare Wodby with alternatives
See how Wodby compares with Heroku, Render, Fly.io, Northflank, OpenShift, Rancher, Pantheon, Acquia Cloud, and Platform.sh.
View comparisons