Cloud plans and limits
Choose a Cloud plan by the number of WordPress sites you need connected to your workspace. Enterprise is the 1,000-site Cloud plan.
Connected-site allowances
Section titled “Connected-site allowances”| Cloud plan | Connected sites | Artifact storage | Hosted Gateway | Settings sync |
|---|---|---|---|---|
| Free | 3 | 25 MB | No | No |
| Freelancer | 25 | 250 MB | Yes | Yes |
| Agency | 100 | 500 MB | Yes | Yes |
| Enterprise | 1,000 | 1 GB | Yes | Yes |
The allowance applies to connected sites in the Cloud workspace. It is separate from the installation allowance on your EMCP Tools Pro licence. Connecting a site beyond your Cloud allowance is refused; reconnecting an already-active site does not add another site to the count.
Use Account → Billing to review your subscription and Account → Sites to review connections. The cloud-status tool reports the connected account’s plan, effective limits, and usage. If your account shows a different allowance from the plan you purchased, contact support so the entitlement can be corrected.
For current purchase options, see Cloud pricing or your billing page. Prices and billing offers are not duplicated here.
All paid plans include the same features; connected-site, storage, and Cloud API request allowances differ. Recurring and lifetime purchases of the same tier receive the same allowances.
Storage and other allowances
Section titled “Storage and other allowances”Cloud storage is for supported Sandbox artifacts, such as blocks, widgets, and snippets. It is not a full WordPress filesystem or database backup service. Storage and artifact allowances are separate from connected-site capacity; check the limits reported for your account before a large import.
Marketplace availability and access to paid artifacts depend on the applicable Cloud entitlement. See features and services for what each service does.
Cloud does not activate the Pro plugin
Section titled “Cloud does not activate the Pro plugin”A paid Cloud plan provides Cloud services. Pro plugin activation happens separately through Freemius on each independent WordPress installation. Copying a licence key or pushing Cloud settings does not complete that activation.
The free plugin works with the hosted Gateway on an eligible Cloud plan. Pro-only tools require Pro to be activated on their target WordPress site. See installation and activation.
Site capacity and request rates
Section titled “Site capacity and request rates”A 1,000-site allowance does not mean 1,000 simultaneous requests or unlimited authentication traffic. Gateway concurrency, authentication rate limits, and each WordPress host affect throughput. Use paced operations and inspect per-site failures. See rate limits and recovery.
Cloud API request limits
Section titled “Cloud API request limits”Freelancer includes the standard paid-plan request allowance. Agency doubles that allowance for larger teams, while Enterprise supports larger fleets. The default allowances are:
| Cloud plan | Requests per minute | Requests per 10-second burst window |
|---|---|---|
| Free | 60 | 12 |
| Freelancer | 180 | 36 |
| Agency | 360 | 72 |
| Enterprise | 1,200 | 240 |
Monthly, annual, and lifetime purchases of the same tier have the same request allowance. Your billing page shows the configured allowance for your current plan.
The allowance is per workspace, not per site, user, or API client. All authenticated Cloud API requests in that workspace share it, including status checks, settings sync, artifact operations, and marketplace operations. Adding sites or connecting another client does not create another request budget.
Both limits apply together, using fixed server-time windows. For example, Freelancer can admit up to 36 requests in one 10-second window, provided its 180-request minute allowance has not been used. Enterprise’s 1,200 requests per minute does not permit sending all 1,200 at once. A shared service-wide limit can also apply during heavy demand.
These are admission limits, not a throughput or completion-time guarantee. OAuth login, registration and token refresh, Gateway tool execution, and the target WordPress host have separate limits. One Gateway operation can make multiple downstream requests; Cloud API requests are not a count of completed tool calls.
When a limit is reached
Section titled “When a limit is reached”The Cloud API returns HTTP 429 with error: "cloud_rate_limited" and a Retry-After header specifying how many seconds to wait. Pause requests from the workspace for that interval, then resume gradually with bounded retries and jitter. A request rejected by this limiter does not consume additional Cloud request allowance or execute its Cloud operation.
Spread fleet work over time with bounded concurrency. After a timeout or an uncertain write result, inspect the outcome before retrying; do not replay a whole batch simply because one request failed. See fleet rate limits and recovery.