Managed Premium — OpenResty Platform for Business Applications

A Cloud VPS gives root access and full control. Your team owns OS hardening, stack configuration, monitoring, patching, and incident response. That model works when you have a dedicated sysadmin or DevOps engineer who wants to own every layer.

Managed Premium gives a correctly configured, production-grade platform operated by us. You manage the application. We manage everything underneath — server, OS, OpenResty, PHP-FPM, database, Redis, monitoring, backups, and security patching. The server does not appear in your team's support queue.

Enterprise Hosting provides reserved vCPU and RAM inside Docker isolated containers in a platform-managed environment with a control panel. Each account has its own filesystem and process namespace enforced at the kernel level.

Managed Premium is configured at the server layer — OpenResty with Lua, per-application PHP-FPM pools, database settings matched to the access pattern — operated directly without a panel abstraction. The right choice for development teams that deploy via Git or CI and want the infrastructure layer configured correctly underneath the application.

Managed Premium: we operate the platform, you operate the application. Managed Solutions: we operate both.

If your team deploys and maintains the application — updates, config changes, plugin management — Managed Premium is the right model. If you want us to handle application-layer operations for a specific product like Odoo, Keycloak, or Nextcloud, that is a Managed Solution. The underlying infrastructure is the same. Moving from one to the other is a scope change, not a migration.

Yes. SSH access to the application layer is included on all tiers. You can deploy code, run Composer, use Git, manage files, and run CLI tools. Root access to the operating system is not included — that layer is managed by us. If your workflow requires root access, Cloud VPS is the right product.

The platform supports any PHP application. Common setups we configure regularly: Laravel, Symfony, WordPress, WooCommerce, PrestaShop, Drupal, MODX. Node.js LTS is also available alongside PHP or standalone. If the application has specific runtime or extension requirements, include them in the initial request and we will confirm support before onboarding starts.

Yes. Deployment is your team's responsibility and your choice of tooling — GitHub Actions, GitLab CI, Deployer, Capistrano, or a simple git push to a bare repository on the server. We configure the application environment and provide SSH key access. The deployment pipeline stays under your control. If the pipeline needs specific server-side hooks or a post-deploy script, that is handled during onboarding.

Yes. Multiple applications run with separate PHP-FPM pools, virtual hosts, databases, and Redis namespaces. The practical consideration is whether separate workloads with different scaling patterns or security requirements should share a server. For applications at different stages of growth or with different risk profiles, separate environments are often cleaner. We assess this during onboarding and recommend based on the actual setup.

Infrastructure layer: CPU utilisation, RAM, disk usage, disk I/O, and network throughput. Application layer: PHP-FPM worker pool saturation and queue depth, database connection count, slow query rate, Redis memory pressure and eviction rate, application error rate via log analysis, and SSL certificate expiry. All alerts go to the operations team. On Pro and Elite, weekly health checks review trends in these metrics before they cause incidents. We do not monitor application business logic — checkout conversion rates, form submissions, or user activity are outside scope.

The monitoring system pages the operations team. The incident triage process starts: confirm which layer the issue sits on, isolate platform-layer causes, apply mitigation, communicate status. On Pro and Elite this is covered by the SLA response commitment. If the cause is in application code, a plugin update, or a third-party API, we document what the platform shows and hand off findings to the application team with context — not a closed ticket with no information.

Yes, on Pro and Elite tiers. A DPA template aligned with GDPR Article 28 is available on request. A written scope statement defining what Yhost manages and what the customer manages is available as a document suitable for internal IT review or vendor approval processes. Responses to vendor security questionnaires are prepared on request. If procurement needs to complete before work starts, send us the questionnaire and timeline in the initial conversation — we handle it before the contract, not after.

All Managed Premium infrastructure runs in Germany on Hetzner and UpCloud data centres. Data does not leave EU jurisdiction at the platform layer. Both providers hold ISO 27001 certification. Backup storage is also within EU. This is the default for all tiers — not a geo-lock premium option. For applications with specific country requirements within the EU, ask about alternative data centre locations during the initial conversation.

We review the current setup — stack, application, database size, traffic profile, and any specific configuration decisions that need to carry over. We produce a migration plan with a staging step: the application runs in the Managed Premium staging environment first, including database copy, functional testing, and performance baseline. DNS cutover happens only after staging validation is complete. For standard application stacks the migration takes one planned window. Highly customised environments may require additional professional services for specific components.

Yes. Managed Premium is the platform layer. If the team later decides to hand off operations for the application itself — Odoo upgrades, Keycloak major version migrations, Nextcloud configuration management — that is added as a Managed Solution scope on the same infrastructure. Nothing moves. The scope expands in place.