Hosting V4

V4 is Webscale’s fourth-generation hosting platform, combining battle-tested architectures and systems engineering patterns with improved security, performance, cost-management, and re-configurability — all accessible from the Webscale Control Plane.

Primary stacks

To accommodate a wide range of application needs, traffic patterns, and reliability requirements, the V4 platform is built around four distinct architectural stacks. Whether hosting Magento, Shopware, WordPress, or custom PHP and Node.js applications, these stacks provide a clear upgrade path as traffic and complexity grow.

Essentials

The Essentials stack provides a robust, streamlined foundation for applications that do not yet require horizontal scaling. It provisions a comprehensive, all-in-one environment on a single, highly optimized server.

Architecture: Single-server deployment.

How it Works: A single server accommodates the complete application stack, including the web tier, an NFS shared filesystem, cron execution, relational database (MySQL or MariaDB), caching (Valkey), message brokering (RabbitMQ), and search (OpenSearch).

Best For: Baseline workloads, staging environments, or applications with predictable, moderate traffic.

Standard

The Standard stack introduces dynamic capacity by decoupling the web delivery layer from the backend services.

Architecture: An autoscaling web tier supported by a single “core” server.

How it Works: The web server is moved into a horizontally scaling layer that automatically expands or contracts based on real-time request demand. The core server processes and manages common backend services (databases, caching, search, NFS, and cron).

Best For: Applications prone to traffic spikes or those experiencing rapid growth that require immediate, automated scaling at the web tier.

Pro

The Pro stack optimizes performance and reduces management overhead by offloading critical backend services to highly resilient, cloud-native managed services.

Architecture: Autoscaling web tier + cloud provider managed services + core server.

How it Works: Building on the Standard stack, Pro moves heavy-lifting services off the core server and into the cloud provider’s ecosystem. For example, MySQL is managed via AWS RDS, Valkey is transitioned to ElastiCache, and OpenSearch utilizes the AWS OpenSearch service. The core server remains strictly for shared files (NFS), cron execution, and message queueing.

Best For: Resource-intensive applications that benefit from the dedicated performance, separate backups, and reduced operational overhead of managed cloud services.

Pro HA

The Pro HA (High Availability) stack is the pinnacle of the V4 architecture, designed for mission-critical applications where uptime is the ultimate priority.

Architecture: Multi-zone deployment of the Pro stack with automatic failover.

How it Works: HA Pro takes the distributed architecture of the Pro stack and spans it across two isolated availability zones. By redundantly defining most components across these zones, the platform provides seamless, automatic failover in the event of a total zone failure.

Best For: Enterprise-grade workloads and revenue-critical applications that require strict Service Level Agreements (SLAs) and maximum fault tolerance.

Additional stacks

To provide further flexibility and adaptability, the primary stacks can be combined with additional infrastructure using add-on stacks. These stacks can be configured as standalone or seamlessly interconnected to other architectural components.

EKS stack

The EKS stack creates and manages an Amazon EKS cluster in your AWS account. The stack also builds the add-ons, a base node group, External Secrets Operator, Karpenter node autoscaling, and a network unless you bring subnets. Webscale deploys Helm charts to the cluster through the Control Plane. Explore this guide for network topologies, variables, outputs, cluster access, secrets, and autoscaling.

RDS stack

The RDS stack is an add-on AWS RDS instance or cluster deployed into an existing network. Explore this guide for details.

Web server stack

The Web server stack is a language-agnostic environment designed for hosting web-facing containerized applications. By decoupling routing from application runtimes, it allows developers to deploy custom container images while Webscale manages underlying auto-scaling, network topology, and security. The stack supports both standalone VPC deployments and add-on integrations into existing subnets, utilizing host-level Go Relay proxying to dynamically forward HTTP/HTTPS traffic to isolated containers. Explore this guide to learn about network topologies, cluster metadata configuration, custom port overrides, and traffic architecture.

Have questions not answered here? Contact Support to get more help.

Last modified on September 2, 2026