# Spain VPS in 2026: a Madrid server for Iberian audiences URL: https://cloudj.net/blog/best-vps-spain Published: 2026-11-11 ยท Updated: 2026-11-11 > A buyer checklist for a Spain VPS in Madrid: who it suits in Spain and Portugal, when to pick another region, how to size it and what to set up first. A Spain VPS earns its place when most of the people who use your site, shop or API are on the Iberian Peninsula. Cloudj runs cloud servers in Madrid, right in the middle of the peninsula, which puts the server close to users in Barcelona, Valencia, Seville, Bilbao and, across the border, Lisbon and Porto. This guide is a buyer checklist: who a Madrid server fits, who should look elsewhere, how to size it, and what to do in the first hour after you deploy. ## Who a Madrid server is for Choose by where your users are, not by where your company is registered. A Madrid server is a strong default for: - Spanish online shops on WooCommerce, PrestaShop or Magento whose buyers are mostly in Spain. - Portuguese projects. Madrid is the nearest Cloudj location to Portugal, so it is the natural pick for a Lisbon agency or a Porto store. - Tourism, booking and restaurant sites whose visitors browse from inside Spain, including the Balearic and Canary Islands. - Regional media, local directories and Spanish-language content sites that rank in Google.es. - Internal tools for teams based in Spain: an ERP, a Git server, a CI runner or a staging copy of production. If you run a store that sells into both Spain and Italy, the comparison in [our e-commerce guide for Spain and Italy](https://cloudj.net/blog/ecommerce-vps-spain-italy) covers how to split or combine the two markets. ## When Spain is not the right pick Being honest about this saves you a migration later. - **Latin America.** A Spanish-language site is not automatically a Spain project. If your readers are in Mexico, Colombia or Argentina, a server in the Americas is physically much closer to them. Look at the US locations, such as Miami or Dallas, on the [United States cloud server page](https://cloudj.net/cloud-servers/united-states). - **Audiences spread across Europe.** If Spain is only one of ten markets, a more central city may serve the whole continent better. The [Europe VPS guide](https://cloudj.net/blog/europe-vps-guide) compares all Cloudj locations in Europe. - **Asian audiences.** If your team is in Spain but your users are in Southeast Asia, put the server near the users. Read the [Singapore VPS guide](https://cloudj.net/blog/best-vps-singapore) instead; for Vietnamese users, the [Vietnam VPS guide](https://cloudj.net/blog/best-vps-vietnam) compares the nearest locations, since Cloudj has no servers in Vietnam. ## The Spain VPS buyer checklist Work through these eight points before you click deploy. 1. **Check your analytics by region.** Split traffic into mainland Spain, Portugal, the islands and everyone else. If more than half comes from the peninsula, Madrid is a good fit. 2. **Pick the CPU type.** Shared CPU (listed as "Availability") is fine for blogs, small shops and staging. General purpose suits most production sites. Dedicated cores make sense for steady CPU-heavy work such as search indexing, image processing or busy PHP workers. The trade-offs are covered in [shared vs dedicated CPU](https://cloudj.net/blog/shared-vs-dedicated-cpu-vps). 3. **Size it.** Plans in Madrid start at 1 vCPU, 1 GB RAM and 20 GB disk and go up to custom sizes of 104 vCPU and 512 GB RAM. There are 30 ready-made plans, or you can build your own mix of vCPU, RAM and disk. 4. **Choose billing.** Hourly billing draws from your account balance and suits tests and short projects. A prepaid term of 1, 3, 6 or 12 months, with optional auto-renew, suits a production shop. See [hourly vs monthly VPS](https://cloudj.net/blog/hourly-vs-monthly-vps) for the full comparison. 5. **Plan for traffic.** Monthly plans in Madrid include 5 TB of traffic. On hourly billing, traffic is charged per GB used. 6. **Pick the operating system.** Ubuntu, Debian, AlmaLinux, Rocky Linux, CentOS and Windows are offered; check the OS list for Madrid in the console. Windows includes a monthly licence fee that the console shows before you deploy. 7. **Prepare access.** Add an SSH key before deploying. A generated root password is also available on the server page, and there is a browser SSH console if you lock yourself out. 8. **Think about personal data.** Your shop collects names, addresses and order histories. Hosting in an EU country can make conversations with Spanish clients simpler, but GDPR compliance depends on how you handle the data, not only on the server's location. ## Sizing for typical Spanish workloads These are sensible starting points, not rules. Because you can resize CPU and RAM and grow the disk later, it is cheaper to start small and measure. | Workload | Starting point | Notes | |---|---|---| | Spanish-language blog or brochure site | 1 vCPU, 1 to 2 GB RAM, shared CPU | Add a page cache before adding CPU | | WooCommerce or PrestaShop store | 2 vCPU, 4 GB RAM, general purpose | Expect peaks around Black Friday and the January sales | | Booking engine for holiday rentals | 2 to 4 vCPU, 4 to 8 GB RAM | Database size grows with every season | | Agency hosting several client sites | 4 vCPU, 8 GB RAM, general purpose | Isolate clients with containers or separate users | | CI runner or build server | 4+ vCPU, dedicated cores | Hourly billing works well if it runs only during work hours | Spanish retail has a strong seasonal rhythm: summer tourism, back-to-school, Black Friday and the "rebajas" sales in January. Resize a few days before a known peak and scale back afterwards. ## The first hour on a Madrid server After the server is running, connect with SSH and do the basics. On Ubuntu or Debian: ```bash ssh root@YOUR_SERVER_IP apt update && apt upgrade -y timedatectl set-timezone Europe/Madrid locale-gen es_ES.UTF-8 ufw allow OpenSSH ufw allow 80,443/tcp ufw enable ``` One country-specific detail: mainland Portugal and the Canary Islands are one hour behind Madrid. If you serve both, keep the server and the database in UTC and convert times in the application, so order confirmations and booking slots show the right local hour. Then work through the [new VPS security checklist](https://cloudj.net/blog/secure-new-vps-checklist): a non-root user, key-only SSH, automatic security updates and a backup plan. ## FAQ ### Is a Madrid VPS a good choice for users in Portugal? Yes. Madrid is the nearest Cloudj location to Portugal, and for most Portuguese sites it is the first location to test. If your Portuguese audience also includes Brazil, consider a second server in the Americas. ### Can I run a Windows server in Madrid? Windows is offered alongside Linux, with password login and a monthly licence fee shown in the console before you deploy. Check the OS list for Madrid in the console, since it can differ by location. ### How is traffic billed? Monthly plans in Madrid include 5 TB of traffic. Hourly servers are charged per GB of traffic used. ### Can I upgrade the server later? Yes. You can resize CPU and RAM and grow the disk from the console, so you can start small and grow when your shop does. ### Does a stopped hourly server still cost money? Yes. An hourly server is charged for as long as it exists, running or stopped, because its disk and IP stay reserved. Delete it to stop charges. ## Deploy your Madrid server If your users are in Spain or Portugal, a Madrid server is the straightforward choice. Compare plans on the [Spain cloud server page](https://cloudj.net/cloud-servers/spain), see live prices on the [pricing page](https://cloudj.net/pricing), and deploy in the [Cloudj console](https://app.cloudj.net), which shows the exact price before you confirm.