CloudLinux resource isolation and selected disk, site and resource limits
Consider concurrency and processing needs alongside disk and website count. CloudLinux resource isolation does not remove package limits.
Hosting and infrastructure
Select resources that support product, cart and order workflows in your store.

The written scope defines actions and access within the selected product limits.
Consider concurrency and processing needs alongside disk and website count. CloudLinux resource isolation does not remove package limits.
Assess WP Toolkit Deluxe and LiteSpeed Cache against store sessions, carts and orders, treating dynamic areas separately.
Review AutoSSL, Imunify360 and weekly external backups. Discuss backup and recovery needs in relation to how frequently order data changes.
A conceptual example explaining the approach, not a customer project or an achieved result.
An example store lists product count, image sizes and expected simultaneous visitor activity.
Catalogue pages are distinguished from cart and checkout workflows when assessing resources and caching.
Agreed test scenarios are prepared before launch; actual orders and payment tests require separate authorisation.
An illustrative workflow, not a customer project.
Timing, authorised access and responsibilities are agreed with the scope.
Record existing usage, dependencies and resource requirements.
Planned outputRequirements and dependency list
Compare features and billing periods; consider migration and licences separately.
Planned outputSelection and access plan
Track current product availability and setup status in the customer panel.
Planned outputSetup status record
Check access and basic functions, then define administration responsibilities.
Planned outputAccess checks and administration plan
The product and written scope define final deliverables; not every item is included in every package.
Product descriptions or proposals define limits and support. Migration and restoration require an explicit scope.
No. Store design, product entry and payment-provider agreements are separate tasks. Hosting supplies the environment.
Sessions and order data need separate assessment. Suitable cache areas must be checked against the current installation.
Post-backup orders and external payment records matter. Lossless recovery is not assumed; coverage and restoration require planning.
Check billing, resources and fees on the product detail page. Additional requirements are not automatically included.
Store design, product entry and payment agreements are separate. Guaranteed sales and unlimited processing resources are not included.
Package prices exclude 20% VAT. Review the exact scope, billing period and any additional charges in the product details.
Hosting for one WooCommerce store with WP Toolkit Deluxe access.
Hosting for growing stores with up to three WooCommerce sites.
View all packages side by side. You can upgrade your package later while preserving your data.
| Store package | Stores | Disk | Monthly traffic | vCPU | RAM | Email accounts | Monthly | |
|---|---|---|---|---|---|---|---|---|
| Starter Store | 1 | 30 GB | 300 GB | 2 | 2 GB | 10 | 1.045 ₺ | Select |
| Growing StoreRecommended | 3 | 40 GB | 400 GB | 2 | 2 GB | 25 | 1.770 ₺ | Select |
| Marketplace | 5 | 60 GB | 600 GB | 3 | 3 GB | 50 | 2.915 ₺ | Select |
Prices exclude VAT.
You can upgrade your package while preserving your data. Starting small and moving up as your needs grow is a common approach.
After payment approval, your account is opened automatically. You access cPanel from the service page in your customer panel; credentials are not emailed for security reasons. There is no setup fee.
Yes. Open a migration request from the Migration section of your service page. Our team can transfer the site from your existing provider. You can also upload files and databases using cPanel tools.
A weekly account backup is stored outside the server in Cloudflare R2, so a server problem does not affect that copy.
Stores need more processor and memory resources for one website. Cart and checkout flows cannot use ordinary full-page caching. These packages allocate higher resources to a single store.
There is no artificial product count limit. Disk space and resource limits determine capacity; upgrade as your catalog grows.
Need help deciding? Let us choose a suitable package together.