Hosting V4
To accommodate a wide range of application needs, traffic patterns, and reliability requirements, the V4 platform is built around four distinct architectural tiers. Whether hosting Magento, Shopware, WordPress, or custom PHP and Node.js applications, these tiers provide a clear upgrade path as traffic and complexity grow.
Essentials
The Essentials tier 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 tier 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 tier 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 tier, 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) tier 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 tier with automatic failover.
How it Works: HA Pro takes the distributed architecture of the Pro tier 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.
Last modified on July 5, 2026