WordPress
WooCommerce
MagentoYour team operates
Your team owns monitoring, maintenance, backups and incidents on the selected capacity.
See infrastructure Managed hosting
Managed hosting for production applications.
Run WordPress, WooCommerce, Magento or a supported custom application on cloud or dedicated infrastructure, with the management responsibilities stated in writing.
Management boundary
Choose who operates each layer.
The application, platform and management scope are separate decisions. The written scope names what ZenoCloud owns and what stays with your team.
Your team uses tooling
Deployment and management tools automate tasks. Responsibility for the environment remains with your team.
Compare the modelsWe own the agreed scope
ZenoCloud owns only the monitoring, maintenance, backup and incident responsibilities listed in writing.
Define the managed scopeResponsibilitySelf-managedManaged where contracted
Monitoring and alert responseCustomerZenoCloud
OS patching and maintenanceCustomerZenoCloud
Backups and restore checksCustomerZenoCloud, with stated retention
Incident responseCustomerZenoCloud, P1 under 15 minutes where contracted
Application code and deploymentsCustomer or developerCustomer or developer
Common questions.
Can an existing application move without downtime?
The realistic downtime boundary depends on the application and data path. Migration follows the controlled sequence: assess, rehearse against the target, then cut over with rollback conditions agreed in advance.
Is this shared hosting?
The current ZenoCloud focus is cloud and dedicated application infrastructure rather than anonymous low-cost shared hosting.
Can the developer keep access?
Yes, with access, change authority and security responsibilities stated in the operating scope.