Austria — Vienna
Germany — Berlin
Finland — Finland (exit)
Netherlands — Netherlands (exit)Infrastructure as code: getting started
With Infrastructure as Code (IaC), manage servers with code, not clicks. In this guide, you'll learn why manual configuration is risky and how to get started with Terraform.
Cloud VPS in WS
Why WS?
Our WS location sits in WS (Other locations) and is delivered from a carrier-grade datacentre with NVMe storage and a dedicated IPv4. Latency from Iran is roughly 150 ms and from central Europe roughly 120 ms, so it is the right pick whenever your visitors — or the services you talk to — are on that side of the map.
Approximate latency
150 ms
to Iran
120 ms
to Europe
These are rough figures based on common routes; your real latency depends on your ISP and transit path.
What is it good for?
- General web and application workloads
- Staging and development environments
- Off-site backups away from your main datacentre
Plans in WS
We have no ready plan in this location right now. Have a look at the other locations or contact us.
Frequently asked questions
How fast is the server delivered?
Provisioning starts automatically once your payment is confirmed and the server is usually ready within a few minutes. Username, password and IP appear in your panel.
Can I upgrade the plan later?
Yes. CPU, memory and disk upgrades are requested from the panel and the price difference is prorated over the remaining days of the period.
Do I choose the operating system?
Yes. Ubuntu, Debian, AlmaLinux, Rocky and a few ready-made app images (such as Docker) are selected at checkout, and you can rebuild with a different OS whenever you like.
Which location should I choose?
Put the server near your users, not near yourself. For Iranian visitors the Middle East and eastern Europe give the lowest latency; for European visitors Germany and the Netherlands; for American visitors the US. Each location page lists its approximate latency.
How is traffic counted?
Each plan includes its own monthly traffic allowance, shown in the table. Where it says “Fair use”, no hard number is published and only abnormal usage is limited.
Related pages
Related guides & articles
Autoscaling: horizontal vs vertical
Learn the differences between horizontal and vertical scaling, architectural prerequisites, costs, and common pitfalls with practical examples and real commands.
Server monitoring and effective alerting
With proper server monitoring, you'll be alerted before a crisis hits. In this guide, you'll learn what to monitor, how to set thresholds, and how to avoid alert fatigue.