The core resources are shown in regular HTML so you can compare CPU, RAM, I/O, IOPS and process limits directly, without relying only on tooltips.
| Plan | NVMe | CPU | RAM | I/O | IOPS | EP | TP | Sites |
|---|---|---|---|---|---|---|---|---|
| Pulse | 20GB | 2 CPU | 6GB | 60MB/s | 1024 | 50 | 150 | 1 |
| Boost | 40GB | 4 CPU | 12GB | 60MB/s | 1024 | 60 | 160 | 1 |
| Turbo | 80GB | 6 CPU | 24GB | 100MB/s | 2048 | 80 | 180 | 1 |
| Ultra | 120GB | 8 CPU | 24GB | 100MB/s | 2048 | 100 | 200 | 1 |
These values match the technical limits already shown on the plans. EP and TP are kept as defined by the service resource limits.
The right hosting choice depends on the real workload of your website: traffic, CPU/RAM usage, database load, concurrent requests and traffic peaks.
Suitable when your website runs comfortably on shared hosting and does not regularly push the available resource limits.
View Web HostingFor one demanding website that needs more resources, NVMe I/O, higher limits and more predictable behavior as load increases.
View plansFor projects that need dedicated CPU/RAM, multiple websites and one-click Auto Scale for 48 hours during traffic peaks.
View Cloud NVMeSemi-dedicated isn’t “full cloud infrastructure” and it doesn’t pretend to be. But it’s exactly what many large sites need when they want stability, higher limits and a cleaner environment than shared—especially when breaking news, a campaign or a promotion suddenly brings thousands of visitors.
The goal is simple: hold up during peak hours, avoid breaking under spikes, and keep room for growth.
For an e-shop, portal or news site, “speed” is not a feeling. It’s a measurable outcome: fewer timeouts, better response time and a more consistent peak-traffic experience.


With semi-dedicated hosting, what matters is having practical solutions when something gets stressed: cache, DB, limits, plugins, spikes. That’s where a team that knows what to look for makes the difference.