Capacity and Add-Ons
Outcome
Section titled “Outcome”You will know how capacity questions relate to site count, storage, backup retention, and support coverage, and how to tell the difference between a plan limit and a technical failure.
When Capacity Becomes A Support Topic
Section titled “When Capacity Becomes A Support Topic”Capacity matters when a workflow stops because the workspace has reached a limit, or when a plugin surfaces a plan-related message that blocks the next action. The most common signals are:
- A new site cannot be added because the site count is at the plan ceiling
- A backup is skipped or pruned earlier than expected
- Storage usage shows a warning state in the workspace overview
- An import or upload fails because the resulting size would exceed the current allowance
These are not bugs. They are the workspace doing exactly what the plan tells it to do, and the right next step is to review the plan rather than to open a technical incident.
Plan Comparison
Section titled “Plan Comparison”The tabs below describe the typical shape of each TMXIO plan tier. Use them to find the plan that matches your team’s day-to-day workload.
- Site count: small portfolios, typically a single brand or a handful of related sites
- Storage: enough for a normal WordPress site with media, but not unlimited
- Backup retention: short rolling window, suitable for routine recovery
- Support SLA: standard business-hours response
Good fit for solo operators, agencies just starting on TMXIO, and projects that have not yet committed to TMXIO as their long-term home.
- Site count: larger portfolios with multiple active brands
- Storage: higher per-site allowance plus a larger workspace pool
- Backup retention: longer rolling window with more restore points
- Support SLA: priority business-hours response
Good fit for agencies running production work for clients and small in-house teams who need predictable recovery options.
- Site count: room for large portfolios with consistent activity
- Storage: the largest standard allowance, with add-on options for outliers
- Backup retention: the longest standard retention plus add-on options
- Support SLA: prioritized response with escalation paths for production issues
Good fit for larger agencies, multi-brand publishers, and teams who treat TMXIO as core infrastructure.
Add-Ons
Section titled “Add-Ons”Add-ons let you grow a single dimension of capacity without changing the plan tier. Use them when the rest of the plan still fits but one specific limit is in the way.
| Add-On | When to use it |
|---|---|
| Extra sites | You need a few more sites than the base plan allows, but not a full tier upgrade |
| Extra storage | Media or backups have grown beyond the standard allowance for the plan |
| Extended backup retention | You need a longer restore window than the plan default |
| Priority support | Production workloads need a faster response than the base SLA |
Which Question Are You Actually Asking
Section titled “Which Question Are You Actually Asking”You are blocked today and need the workflow to complete. Confirm the exact limit involved, then either remove an unused site or asset, or add the matching add-on so the action can proceed.
You are not blocked today, but you can see the trend. Review the plan tier against the next six to twelve months of expected work and move up a tier before the ceiling is reached. Planning ahead avoids mid-cycle proration surprises.
What To Do Next
Section titled “What To Do Next”Review the current plan and add-ons in workspace settings before treating a capacity limit as a technical failure. If the limit is genuinely the issue, the fix is an add-on or a plan change, not a support ticket about a broken feature.