Pricing & Billing - Public Cloud [EN]
- 1 Q1. How much will my new VM cost after migration?
- 2 Q2. Why did the price change?
- 3 Q3. Can I keep my current price?
- 4 Q4. Are there any discounts for existing customers?
- 5 Q5. When does the new price take effect - right after migration or later?
- 6 Q6. What happens to my prepaid balance?
- 7 Q7. I have VMs with the 1 vCPU / 1 GB RAM flavor. What happens to these?
- 8 Q8. Will the billing cycle change?
- 9 Q9. What if I've paid for the next month on the old platform?
- 10 Q10. How do I figure out which plan to choose?
- 11 Q11. I’ve got a VDS with 1 vCPU / 1-2 GB RAM. What’s smaller than Cloud S?
You can find detailed pricing and billing information here: Public Cloud Pricing
Q1. How much will my new VM cost after migration?
First and foremost, the billing model itself is changing - you'll no longer be paying per individual virtual machine but for a resource pool instead.
When you choose a plan, you get a shared allocation of compute resources: CPU cores (vCPU), RAM, and storage (NVMe). You distribute this pool however you like - spin up any number of VMs with the configurations you need, allocate resources between them, and readjust at any time.
Example: The Cloud M plan (€60/mo) includes 8 vCPUs, 16 GB RAM, and 200 GB NVMe. From that pool, you can create one large VM (8 vCPU / 16 GB), eight smaller ones (1 vCPU / 2 GB each), or any other combination - and you can change it whenever you want.
Billing works on a fixed base + hourly overage model. Each plan has a strict cap: no matter the load, your bill will never exceed that ceiling.
Q2. Why did the price change?
New platform runs on more advanced cloud infrastructure and hardware, which means better performance and higher reliability.
The cost structure of running such a platform is different, so initial prices have changed accordingly. With that said, due to the performance improvements, you're getting an upgraded service - and in many cases you may be able to use fewer resources (vCPU/RAM) while maintaining the same speed, which can actually reduce your overall spend.
Q3. Can I keep my current price?
Keeping your current pricing is not possible: the old products are being retired and replaced with a fundamentally new infrastructure.
That said, the new plan is not simply the same service at a different price: you get guaranteed resources on modern hardware (AMD EPYC 5th Gen, DDR5, NVMe), predictable billing with a hard spending cap, and flexible infrastructure management. In many cases, the same workload requires fewer resources than before - so the final cost may end up comparable.
Q4. Are there any discounts for existing customers?
There are no dedicated "existing customer" discounts - the same terms apply to everyone.
If you previously had an individual volume-based discount, please reach out to our customer service team, and we'll review your situation individually.
However, the pricing model is designed in a way that the more resources your plan includes, the lower the effective cost per unit.
Q5. When does the new price take effect - right after migration or later?
The new pricing kicks in as soon as you fully transition to the new cloud platform and start using the new service.
Once migration is complete and the old service is deactivated (upon your confirmation), billing will switch entirely to the new plan.
Q6. What happens to my prepaid balance?
If you have other active services, your balance won't be transferred automatically by default. Upon request, we can move it to the new platform, where it will be applied toward charges under your new plan.
If you have no other active services, the balance transfer will occur automatically.
Q7. I have VMs with the 1 vCPU / 1 GB RAM flavor. What happens to these?
The minimum VM size on the new platform is 1 vCPU and 2 GB RAM*, so a 1 vCPU / 1 GB configuration won't be available.
This reflects the reality that modern applications generally require more resources. Slimer configurations frequently hit memory limits and cause performance and stability issues.
The entry-level plan is Cloud S (€30/month) with 4 vCPUs and 8 GB RAM included in the base. You can build four 1 vCPU / 2 GB RAM VMs with these resources, and it is scalable up to 16 vCPUs / 32 GB. For small projects this is typically more than enough - and you get a predictable flat monthly cost instead of an hourly meter.
*Cloud S plan, allowing for four 1 vCPU / 2 GB RAM VMs or other combinations within the tariff resources.
If you have a single VM on this plan, consider Cloud VPS service - see Q11 for details.
Q8. Will the billing cycle change?
Yes, billing becomes more flexible. It's built around a fixed base + hourly overage structure.
The fixed base is the monthly cost - your guaranteed resource pool based on the tariff. If your load spikes, you can manually add extra resources, which are billed hourly based on actual usage time. Once the peak subsides, you manually scale back down, and the overage charges stop.
Important: VM resources don't change automatically. Scaling up or down is always a deliberate action on your part (or through an automation tool you've configured, such as Kubernetes with Cluster Autoscaler).
Every plan has a strict cap (limit): regardless of load, your bill will never exceed it. You know the worst-case cost upfront, before you even start.
Previously, Websa billing was purely hourly. Now you pay a predictable monthly minimum, manually scale up during load spikes if needed, and never exceed a predefined maximum.
Q9. What if I've paid for the next month on the old platform?
The amount you've already paid will be credited toward your subscription on the new platform. You won't need to make any additional payments upfront to start using the new service.
Q10. How do I figure out which plan to choose?
If you're running a single VDS, the easiest approach is to assess your current server's resources: check how many vCPUs and how much RAM your VM has and pick a plan that covers those appetites.
Example: if your current VM has 4 vCPUs / 8 GB RAM, the Cloud S tariff (€30/month, 4 vCPUs / 8 GB RAM base) would be a direct equivalent with a notable potential.
If you have multiple VMs or you're not sure which plan fits best, open a ticket and we'll help you find the right option based on your setup.
If you have multiple VMs - add up their resources and choose a plan that covers the total.
We'll review your current usage and reach out via ticket with a ready-made recommendation.
Q11. I’ve got a VDS with 1 vCPU / 1-2 GB RAM. What’s smaller than Cloud S?
Our slimmest Public Cloud option is indeed Cloud S, but we can offer the Cloud Virtual Machines (A/VM) service as an alternative.
Cloud VPS is a single virtual server with a fixed configuration. You know exactly what you're getting in terms of vCPU, memory, and storage, and you pay a flat monthly fee for it.
Both Cloud VPS and Public Cloud run on the same cloud platform, deliver guaranteed resources, and use the same high-performance hardware (5th Gen AMD EPYC, DDR5, NVMe). The difference is in the access level: with Cloud VPS you get access to your virtual server, not to a full cloud infrastructure environment.
The A/VM 1-2 plan would suit your needs:
vCPU: 1
RAM: 2 GB
NVMe storage: 20 GB
Price: €6.99/month