Skip to main content

Understanding the Structure of Your Rapyd Cloud Account

A clear breakdown of how plans, environments, subscriptions, and sites all connect.

Rapyd Team avatar
Written by Rapyd Team
Updated this week

When you use Rapyd Cloud, your hosting experience is built around a flexible and transparent structure. This guide explains how the core entities in your account—subscriptions, plans, environments, and sites—relate to each other and what role each one plays.

Whether you're managing one site or scaling across multiple projects, understanding this structure will help you make informed decisions about your resources, billing, and site management.


Overview of the Structure

Here’s a simplified view of how everything connects:

  • A subscription holds one or more plans.

  • Each plan is tied to a single environment.

  • Each environment can host one or more sites, depending on the plan type.

This creates a hierarchy that looks like this: Subscription → Plan → Environment → Site

Each layer has its own role:

Entity

What It Represents

Subscription

Billing container: payment method, frequency

Plan

Defines resources and site limits

Environment

Server-level container (region, PHP, etc.)

Site

Individual WordPress instance

Let’s take a closer look at each of these entities.

Subscriptions

A subscription is normally first created when you sign up and complete checkout.

  • Contains billing information, frequency (monthly, yearly, etc.), and payment method

  • Can contain one or more plans

  • Has a single billing cycle and payment source

You can view all subscriptions under the Billing section of your dashboard. Additional subscriptions can be added at any point from this section.

Plans

A plan defines your hosting resources—CPU, memory, storage, and how many sites you can run.

  • When you purchase a plan, it’s added to a subscription

  • Each plan supports one environment

  • Plans are visible in the Plans section of the dashboard

  • Each plan specifies whether it is for single-site or multi-site use

Think of your plan as the billing-level commitment to a particular amount of infrastructure.

Environments

An environment is the actual server your WordPress sites run on.

Each plan allows you to deploy one environment. That environment inherits the specs of the plan and defines infrastructure-level settings such as:

  • Region

  • PHP version

  • Resource usage and scaling limits

  • Logs, performance stats, and certain security controls

Environments are where key server-level services are managed, including:

  • LiteSpeed Web Server

  • MariaDB (database)

  • Redis

  • PHP workers

These services power your sites behind the scenes and are configured per environment.

Key facts about environments:

  • A single-site environment hosts one site

  • A multi-site environment allows you to add and manage multiple sites

  • All sites within an environment share its server-level resources

  • Environments can be restarted, stopped, and deleted

You can view or manage your environment in a few different ways:

  • From the Plans screen: Navigate to Plans in the dashboard, then click Manage Environment to access full server-level settings, usage stats, and tools.

  • From the Sites screen: Use the ••• menu next to a site, then click Manage Environment to jump directly to the environment that site belongs to.

  • From the environment name tooltip: On the Sites screen, hover over the environment name to view details like PHP version, plan type, and region. This is for quick reference only—not management.

Sites

A site is an individual WordPress installation created inside an environment. Each site is fully isolated at the application level and comes with its own dedicated tools and controls.

Sites include:

  • Custom domain support including primary domain assignment

  • Backups and staging controls

  • Cache management specific to the site

  • phpMyAdmin access and a dedicated database

  • WordPress management tools for themes, plugins, and core updates

  • CDN integration and controls

  • SSL management, file access (via file manager or SFTP), and site-level logs

  • Cron job management for scheduled tasks

  • Real-time usage and performance stats

In multi-site environments, you can create and manage multiple sites that share infrastructure but remain completely separate in configuration and content.

Conclusion

Rapyd Cloud is built for developers, teams, and businesses that demand power, clarity, and control. By understanding how subscriptions, plans, environments, and sites relate, you can make smarter decisions about how to organize your infrastructure, scale your projects, and manage costs over time.

Whether you're deploying a single high-traffic site or managing dozens of isolated environments, this layered structure gives you the flexibility to grow without complexity.

Every layer—from billing to server to WordPress instance—is clearly defined and designed to work together seamlessly.

If you're just getting started, this guide is your foundation. If you're already growing on Rapyd Cloud, it's your roadmap for scaling with confidence.

Did this answer your question?