Application Types

OpenSRS Cloud Hosting is currently in closed beta and is available only to participating resellers. To sign up for Cloud Hosting, visit opensrs.com/hosting

Every Cloud Hosting site is created in a new, isolated cloud container environment set up from scratch using a predefined image. We call this predefined image an application. Applications are separate from plans:

• Applications define the software stack your site runs.
• Plans define the features, resources, and service limits available to that site.

Available Applications

During the closed beta, two applications are available: WordPress and PHP Stack.

What All Applications Include

Regardless of which application you choose, every site runs on a LAMP-based stack that includes:

• Operating system: Debian Linux
• Web server: Apache
• Database: MySQL on Amazon RDS
• PHP runtime: PHP-FPM

Environment & Access

All applications run in a managed, standardized environment. Currenly:

• PHP version is set during provisioning.
  It cannot be changed at this time, but this capability is planned for a future release.
  See: PHP Guide.
• PHP extensions are fixed.
  Each site includes a curated set of pre-installed extensions, and additional extensions cannot currently be added.
  See: PHP Extensions.
• Shell access is not available.
  SSH access is not currently supported. File management is handled through SFTP only.
  See: SFTP Guide.

WordPress Application

In addition to the LAMP stack, the WordPress application installs a full CMS layer, including WordPress core files and database configuration. Installation is completed using your chosen setup method.

PHP Stack Application

The PHP Stack application installs the LAMP stack without a CMS layer, giving you a clean environment to install and configure your own website. This is the recommended option if you are not using WordPress or prefer to manage your own application stack.

Hosting Infrastructure

Every site runs in its own isolated environment. Each site is deployed as a dedicated pod-container combination in Kubernetes on AWS, with no shared software or resources between sites.

A second pod-container configuration is also deployed to run phpMyAdmin independently from the main website container. This architecture provides several key benefits:

• Security: Each container runs in complete isolation — issues with one site cannot affect others.
• Isolation: Separating the website and phpMyAdmin containers means heavy traffic or activity in one won't slow down the other.
• Scalability: Containers can automatically scale to handle increases in traffic or data without disruption.
• Reliability: If a container fails, Kubernetes can instantly deploy a replacement, bringing the site back online within minutes.

This document contains confidential and proprietary information intended solely for the use of OpenSRS Cloud Hosting customers. Unauthorized distribution, reproduction, or disclosure of any part of this document is strictly prohibited.