cPanel hosting
WP Starter
For company WordPress sites and personal publications.
Tailored quoteA quote for your project
Get a quote
1Website in the same account- 3 coresCPU
- 3 GBRAM
WordPress hosting, with the right resources.
Resource options for WordPress projects, from company websites to content platforms. A hosting plan assessed alongside your theme, plugins and publishing workflow.
Resource options for WordPress
A plan that fits how your site works.
Each option is planned for one WordPress site. Plugins, page builders and actions by logged-in users affect resource needs.
Websites are managed in the same hosting account; CPU and RAM are account resources.
Compare all plansA balanced choice
WP Business
For content creation and regularly updated websites.
Tailored quoteA quote for your project
Get a quote
- 1Website in the same account
- 4 coresCPU
- 4 GBRAM
cPanel hosting
WP Pro
For projects with more plugins and dynamic processing.
Tailored quoteA quote for your project
Get a quote
- 1Website in the same account
- 6 coresCPU
- 6 GBRAM
cPanel hosting
WP Performance
For WordPress projects with growing resource needs.
Tailored quoteA quote for your project
Get a quote
- 1Website in the same account
- 8 coresCPU
- 8 GBRAM
Included in all plans
- Control panel
- cPanel
- Web server
- LiteSpeed
- Backups
- Weekly
- Storage
- Unmetered*
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.
Compare resources
Make more room as your workload grows.
A plan’s resources alone do not guarantee page speed or a number of concurrent visitors. Measure using real pages and user actions.
Scroll the table sideways to see other plans; feature names stay fixed.
| Plan featuresResources and included platform | WP StarterTailored quote quoted | WP BusinessTailored quote quoted | WP ProTailored quote quoted | WP PerformanceTailored quote quoted |
|---|---|---|---|---|
| Resources and capacity | ||||
| Website | 1 | 1 | 1 | 1 |
| CPU | 3 cores | 4 cores | 6 cores | 8 cores |
| RAM | 3 GB | 4 GB | 6 GB | 8 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 | cPanel | cPanel | cPanel | 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 | 1 | 1 | 1 | 1 |
| Choose your plan | Get a quote | Get a quote | Get a quote | Get a quote |
Inside the platform
For WordPress, working practices matter as much as resources.
One installation, different resource levels
Each WordPress plan is for one website. Options with 3, 4, 6 or 8 CPU cores and the same number of GB of RAM are assessed against the theme, page builder and peak-hour processing.
LiteSpeed and caching
Compatible tools such as LiteSpeed Cache can configure caching for public pages. Test cart, checkout, account and membership pages outside the general cache.
Media and inode usage
Each image size, plugin file and cache item can increase the file count. Removing unused sizes and old caches is a maintenance task regardless of the unmetered space description.
Database and background tasks
Post revisions, plugin tables and scheduled tasks affect resource usage. Review processing queues and failed tasks regularly, especially for stores.
Weekly backups and updates
The weekly copy is the baseline restore point. Take an additional backup of files and the database immediately before updating the core, PHP or a critical plugin; test forms and checkout workflows afterward.
cPanel and application access
The hosting panel and WordPress administrator account are different types of access. Give each user only the permissions their role requires; record who owns theme and plugin licenses in the project record.
Read resources correctly
Unmetered space is not unlimited processing power.
Assess storage and account counts together with CPU, RAM, how the application runs and backup needs.
- * Unmetered space and account counts
- Reference plans do not specify a fixed count or capacity quota for disk, inodes, email, MySQL and subdomains. These resources are not independent of CPU, RAM and service usage terms. High file counts, large mail archives and intensive processing are assessed together.
- Traffic and process limits
- No numerical monthly traffic quota is published in the reference table. I/O, concurrent processes, email sending rate and PHP process limits are different measures; specific requirements are added to the order scope.
- Weekly backups
- A weekly backup is a restore point from the last backup. Retention and available restore dates are determined per service. For projects with daily order or content changes, plan more frequent backups using additional file and database copies under your control.
What runs behind a WordPress page?
A visitor’s request becomes a page through the theme template, plugins, PHP processing and database queries. A cached article and a logged-in customer’s cart do not use the same amount of resources.
So do not choose a plan based only on monthly visitor counts. Measure real workflows such as search, admin screens, checkout, media uploads and scheduled tasks. Removing unnecessary plugins and reducing image sizes also lowers resource needs.
Share your WordPress needs
Have a rollback ready when updating.
Before launching a new theme, PHP version or payment plugin, keep copies of the files and database together. Try critical changes on a test copy; check that the test site is blocked from search engines.
Afterward, do more than open the homepage: repeat the steps visitors use, such as form delivery, login, search and payment notifications.
Migration steps and checksControlled WordPress migration
The same address, a more organized start.
Migration involves more than copying files. Forms, media, links and email delivery should be checked together.
See migration steps- Back up files, the database and current settings.
- Record the PHP version and theme and plugin licenses.
- Test forms, search and administrator login on the new copy.
- Verify permalinks, HTTPS and redirects.
- Monitor email and transaction logs after the DNS cutover.
Preparing to choose a plan
Which actions on your site use resources?
Measure real user actions before looking at product counts. The observations below are starting points; assess them alongside panel usage and application logs from the same period.
| Workflow | First measurement | Effect on selection |
|---|---|---|
| Content and company information | Logged-out page response, image size and cache status. | Assess page delivery first, then the account resources required. |
| WooCommerce cart and checkout | Dynamic processing time, peak-hour CPU/RAM and waits for external services. | Include uncached workload and order backups in the plan. |
| Product imports and task queues | Task duration, failed jobs and required custom services. | Verify standard hosting compatibility or the need for a separate server. |
Use the WooCommerce selection checklist for a store, and the hosting and VPS decision guide when custom services are needed.
For agencies and content teams
Move from a test copy to your live WordPress site in a controlled way.
Changing a theme and moving a store’s order data are different tasks. Define the scope of the change before launch; preserve data created on the live site while updating files.
1. Separate the test environment
Restrict the test copy with authentication and block indexing. Disable emails to real customers, live payment collection and tasks that send data to external systems in the test environment.
At the quote stage, specify how the additional installation affects account/site counts and whether you need an automated staging tool.
2. Choose the change to publish
Record theme files, plugin settings and database changes separately. Replacing the entire database of a site accepting orders with an old test copy can delete new orders; define final data synchronization and rollback steps in advance.
3. Verify the real workflow
After launch, try the mobile menu, forms, search, login and password reset. For a store, run an authorized test workflow for cart, shipping/tax calculation, payment notifications and order emails.
Record the change time and result to prepare a support ticket with concrete observations.
If you are starting for the first time, the WordPress installation guide helps establish the right order of checks; for slowness, use the WordPress performance guide. If you want tools such as WP-CLI, SSH, object caching or automatic updates, share your requirements before setup.
WordPress questions
What to know when deciding.
What is the difference between WordPress hosting and regular hosting?
WordPress plans offer resource options based on the CPU and memory needs of a WordPress installation. WordPress can also run on general web hosting. The right choice depends on your plugins, visitor actions and measured resource usage.
Are theme and plugin licenses included in the plan?
Paid themes, plugins, image licenses and custom development are separate from hosting resources. Check whether existing licenses can be transferred and who is responsible for renewals before you order.
Can I host my WooCommerce store?
WooCommerce needs vary with product count, variations, payment infrastructure and concurrent transactions. Cart and checkout pages, webhook notifications and scheduled tasks are tested to identify the right hosting or server solution.
Is WordPress hosting a managed WordPress service?
The plans on this page define the hosting resources for your WordPress site. Core, theme and plugin updates, troubleshooting, security monitoring and test environment management are separate maintenance tasks. If you need managed WordPress, tasks, permissions and the application owner are defined separately in the written quote.
Will migration affect my Google ranking?
When changing hosting, preserve the URL structure, use correct redirects and check HTTPS and indexing settings. The aim is a smooth technical transition; hosting does not guarantee search engine rankings.
Can I use a test site or WordPress Multisite?
Plans are offered for one website. Before ordering, specify any additional test installation and the domain, site and access structure of a Multisite network; account scope and plugin licenses are assessed accordingly. Automated staging, one-click cloning or Multisite support should not be assumed from the plan name alone.
How can I determine which plan will be sufficient?
Current CPU and RAM usage, media size, plugin lists and peak-hour processing are good starting points. If no measurements are available, an initial configuration is determined together using representative pages and user workflows.
FROM SELECTION TO SETUP
Guides for your next step.
Let’s assess your WordPress site together.
Share your current site, plugin list and growth plan. Let’s prepare a compatible starting configuration.