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 relate to each other and what role each one plays: teams, subscriptions, plans, environments, and sites.
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 team is the top-level container for a paying account, where all resources live.
A subscription holds one or more plans and lives within a team.
Each plan is tied to a single environment.
Each environment can host one or more sites (excluding Starter 1 plan).
This creates a hierarchy that looks like this: Team → Subscription → Plan → Environment → Site
Each layer has its own role:
Entity | What It Represents |
Team | A paying account: one owner, with optional team members |
Subscription | Billing container: payment method, frequency |
Plan | Defines resources and site limits |
Environment | Server-level container (region, PHP version, etc.) |
Site | Individual and logically isolated WordPress instance |
Let’s take a closer look at each of these.
Teams
When a new customer creates an account and purchases a plan, a Team is created in the dashboard. Every subscription, plan, environment, and site associated with that account lives within the Team.
A few things worth knowing:
Every Team has exactly one owner, who is the account holder that completed the purchase
The owner can invite additional team members, each with their own access and permissions
Team members have a Rapyd Cloud user account but do not have a Team of their own unless they have also purchased a plan independently
Subscriptions
A subscription is normally first created when you sign up and complete checkout.
Holds your billing information, payment frequency (monthly, yearly, etc.), and payment method
Can contain one or more plans
Has a single billing cycle and payment source
Must contain at least one plan
If the final plan is removed, the subscription will also be cancelled
Discounts are applied at the subscription level, with a limit of one discount active at a time
Each subscription supports only one billing frequency, either monthly or yearly. If you need both frequencies under the same account, you will need two separate subscriptions
Multiple subscriptions are especially useful for agencies and freelancers who manage sites for clients and need to separate billing by client or payment method
You can view all subscriptions under the Billing section of your dashboard. Additional subscriptions can be added at any point from that section.
If you create an account during checkout but do not complete a purchase, a Team will be created without an active subscription. A plan must be purchased and a subscription created before any environment can be deployed.
Plans
A plan defines your hosting resources, including CPU, memory, storage, and how many sites you can run in the associated environment.
When you purchase a plan, it's added to a subscription
Each plan supports one environment
Each plan includes a set number of sites, with the option to add more up to a plan-specific maximum (except Starter 1, which supports a single site only)
For a full breakdown of what each plan level includes, see Technical Specifications of Rapyd Cloud Plans.
Think of your plan as the billing-level commitment to a particular set of infrastructure resources. Note that billing is based on your active plans, not on whether a site has been created inside them. Once a plan is purchased, it is billable regardless of whether a site has been deployed.
Environments
An environment is the actual server your WordPress sites run on. Each plan allows you to deploy one environment, which inherits the specs of that plan.
Environments define infrastructure-level settings such as:
Region
PHP version
Resource usage and scaling limits
Environments are also where key server-level services run, including LiteSpeed Web Server, MariaDB, KeyDB, and PHP workers. These power your sites behind the scenes and are configured at the environment level.
A few other things to know:
All sites within an environment share its server-level resources, including staging sites
Environments can be restarted, stopped, and deleted
Accessing an environment:
There are two primary ways to reach an environment's management area:
From the Sites page: Use the menu next to any site, then click Manage Environment to access full server-level settings, usage stats, and tools.
From the account icon: Click the account icon in the top-right corner of the dashboard, then select Environments to navigate directly to your environment list.
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.
Among other things, sites include:
Custom domain support, including primary domain assignment
Backups and staging controls
Cache management
phpMyAdmin access and a dedicated database
WordPress management tools for themes, plugins, and core updates
CDN integration
SSL management, file access (via file manager or SFTP), and site-level logs
Cron job management
Real-time usage and performance stats
Sites within the same environment share infrastructure but remain completely separate in configuration and content.
Conclusion
Understanding how teams, subscriptions, plans, environments, and sites relate to each other is the foundation for managing your hosting confidently. Each layer has a clear role, and together they give you the flexibility to grow without unnecessary complexity.
If you have questions about your account structure or need help navigating the dashboard, our support team is available 24/7.