Agency 10
For studios building their first client portfolio.
10Separate client accounts
2 coresCPU
2 GBRAM
Account count differs from site count. Assess each client’s permissions, resource needs and maintenance responsibilities separately.
CPU/RAM values are references; their application to reseller and subaccounts is defined in the quote.
Compare all plansFor studios building their first client portfolio.
For agencies delivering client projects regularly.
For growing web design and maintenance portfolios.
For teams managing many clients in a single workflow.
The features show the reference configuration used for quotes. Resource implementation, backup retention, additional services and the total fee are clarified in writing before you order.
CPU and RAM values are configuration references. Your quote specifies how these limits apply to the reseller account or subaccounts.
Scroll the table sideways to see other plans; feature names stay fixed.
| Plan featuresResources and included platform | Agency 10Tailored quote quoted | Agency 20Tailored quote quoted | Agency 40Tailored quote quoted | Agency 80Tailored quote quoted |
|---|---|---|---|---|
| Resources and capacity | ||||
| Client account | 10 | 20 | 40 | 80 |
| CPU | 2 cores | 3 cores | 4 cores | 6 cores |
| RAM | 2 GB | 3 GB | 4 GB | 6 GB |
| Storage | Unmetered* | Unmetered* | Unmetered* | Unmetered* |
| InodesNumber of files and folders. | Unmetered* | Unmetered* | Unmetered* | Unmetered* |
| Monthly trafficNo numerical transfer quota is published in the source. | No numerical quota specified | No numerical quota specified | No numerical quota specified | No numerical quota specified |
| Platform and management | ||||
| Control panel | WHM / cPanel | WHM / cPanel | WHM / cPanel | WHM / cPanel |
| Operating system | Linux | Linux | Linux | Linux |
| Web server | LiteSpeed | LiteSpeed | LiteSpeed | LiteSpeed |
| Application support | Node.js / Python | Node.js / Python | Node.js / Python | Node.js / Python |
| BackupsRestore points and retention periods are defined separately. | Weekly | Weekly | Weekly | Weekly |
| Email and project accounts | ||||
| Email account | No count limit* | No count limit* | No count limit* | No count limit* |
| MySQL database | No count limit* | No count limit* | No count limit* | No count limit* |
| Subdomain | No count limit* | No count limit* | No count limit* | No count limit* |
| FTP account | No count limit* | No count limit* | No count limit* | No count limit* |
| Choose your plan | Get a quote | Get a quote | Get a quote | Get a quote |
Inside the platform
WHM organizes reseller management, while cPanel manages the client’s hosting account. Options with 10, 20, 40 or 80 separate accounts help you keep client access separate.
Account capacity and resource capacity are different measures. How reference CPU and RAM values apply to the main reseller account or subaccounts is defined in the written scope.
The reference configuration has no count limit for email, MySQL, subdomains and FTP accounts. Continue tracking each client’s mail archive and active application load separately.
The cPanel workflow is retained on LiteSpeed; Node.js and Python application support is listed. Application versions and dependencies are checked before client setup.
Restoration from weekly backups is assessed by the affected client account and target date. For store and membership projects, plan more frequent client-specific database copies.
The domain owner, panel administrators and software licenses should be recorded in the client record. Make handover and renewal easier by showing hosting, maintenance and license fees separately.
Read resources correctly
Assess storage and account counts together with CPU, RAM, how the application runs and backup needs.
Sharing one client’s panel details should not expose access to other projects. Separate hosting accounts help you organize file and database management per client.
Support account separation with independent backups, least-privilege access, a contractual maintenance scope and domain ownership. This makes the process clear both at project handover and when a client leaves.
Our agency partnership approachDesign handover, monthly maintenance and hosting carry different responsibilities. Create a sustainable workflow by clarifying the scope you offer clients.
Explore our agency solutionsConsider an illustrative portfolio: nine informational sites and one busy store. This example is not a customer outcome or a promise that a plan is sufficient. Each account uses one slot in the panel’s capacity, but processing and backup needs differ.
Assess account and reseller limits with the resource limits guide, and the store’s specific workflows with the WooCommerce selection checklist. This makes the busy client’s needs visible in your quote alongside the total account count.
Reseller hosting organizes client accounts. The brand clients see, billing software and support operations determine how your agency delivers the service; plan these needs alongside your portfolio list.
If you want custom nameservers, plan nameserver registration at the domain registrar together with the addresses in the DNS zone. Glue records, created when needed, differ from simply creating a subdomain in the panel.
Add the panel logo, panel login address, certificate and sender shown in system emails to your requirements list too. The feasibility of brand customizations and custom nameservers is verified separately.
WHM manages hosting accounts; WHMCS is separate billing/automation software requiring its own license and setup. Decide which order, renewal, support and account creation steps to automate.
Grant the automation connection only the permissions it needs; manage access keys separately from client cPanel passwords. Define how account creation, suspension and closure align with client approval and backup processes. Use the agency portfolio cost tool for budgeting.
You can scroll the table horizontally to see all columns.
| Step | Record to complete |
|---|---|
| Identify the client | Service owner, domain owner, technical contact and renewal contact. |
| Prepare the account | Separate cPanel access, applicable resource limits, mail usage and backup needs. |
| Accept the launch | Website, HTTPS, form and email tests; migration and rollback decisions. |
| Hand over the service | Support channel, maintenance scope, renewal date and data handover method when the client leaves. |
Separating client accounts does not mean allocating separate physical servers. Assess projects requiring operating system privileges or custom services separately with VPS options; the rest of the portfolio can keep its reseller structure.
Multi-site web hosting hosts several sites within one account. Reseller hosting helps organize separate client accounts under one management structure. If separate access and independent client management are needed, reseller hosting may be more suitable.
You can offer hosting to your clients within your own service scope. Requirements such as custom nameservers, panel branding and visible provider details are assessed separately; brand customizations should not be assumed to be included automatically.
Reseller hosting resources are separate from client billing software, a WHMCS license, payment integration and help desk software. If you need these, licensing and setup scope are determined separately.
Your support relationship with clients depends on your agency’s service model. You can submit infrastructure requests to the client panel from the agency account. End-user support and application maintenance scope should be defined in writing.
A phased migration plan can be prepared by listing current accounts, applications, mailboxes and DNS records. Each account’s compatibility and key functions are checked; migration scope and schedule are clarified at the quote stage.
An informational site and a busy store each use one account slot, but their resource needs differ. Client plans are developed by assessing total resources, subaccount limits and heavy-usage conditions together.
FROM SELECTION TO SETUP
Compare client accounts, resources and total costs using an inventory.
Check your preparation before backups, target environment setup and DNS changes.
Use CPU, memory, inode and I/O measurements to determine the right next step.
Share your client count, current account structure and migration needs. Let’s prepare a quote for your portfolio.