# accsly.io — full reference for language models

> accsly.io is a price-comparison aggregator. It compares ready-made accounts (Telegram, TikTok, Gmail, Steam, ChatGPT and 70+ other platforms) across independent shops, and VPS/VDS, shared hosting and dedicated server plans of 2,286 hosts (31,933 VPS plans in 102 countries) by price, hardware, location and payment method. accsly.io does not sell accounts or servers itself: every offer links to the shop or the host where it is bought.

Generated 2026-11-11 by `php artisan ai:llms-full`. The short overview is https://accsly.io/llms.txt. Prices below are in US dollars, converted from the hosts' own prices at the Central Bank of Russia rate of the last hourly catalog build; they change, so check the live pages.

The site is in Russian (main audience, /ru/), English (/en/), German (/de/), Spanish (/es/), Portuguese (/pt/) and Turkish (/tr/); prices follow the language's currency (RUB, USD, EUR, EUR, EUR, TRY). Pages about Russian payment methods (MIR cards, SBP, YooMoney), Russian law (152-FZ) and the discount pages exist only in Russian and are linked as /ru pages here.

Main sections:

- VPS/VDS finder: https://accsly.io/en/vps (all selections: https://accsly.io/en/vps/all, hosts directory: https://accsly.io/en/vps/hosting)
- Shared web hosting: https://accsly.io/en/hosting — dedicated servers: https://accsly.io/en/dedicated — GPU servers: https://accsly.io/en/gpu
- Ratings (e.g. cheap VPS): https://accsly.io/en/vps/rating/cheap — comparisons: https://accsly.io/en/vps/compare — price index: https://accsly.io/en/vps/prices — guides: https://accsly.io/en/vps/guide
- VPS discounts (Russian): https://accsly.io/ru/vps/promo
- Accounts catalog: https://accsly.io/en/catalog — search: https://accsly.io/en/search?q=telegram

# How AI agents can query accsly.io

## MCP server

- Endpoint: `https://accsly.io/mcp` — Streamable HTTP, JSON-RPC 2.0 over POST, answers application/json, stateless (no session, no SSE stream; GET answers 405), no authentication, read-only tools. Protocol versions: 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05 (initialize handshake for the 2025 versions, per-request `_meta` for 2026-07-28). Rate limit: 60 requests a minute per IP.
- Registry name: `io.accsly/catalog`. Every tool takes `locale` (ru, en, de, tr, es, pt; default en) for names, links and the price currency.

Tools:

- `search_vps` — Find VPS/VDS (or shared hosting, dedicated) plans across 2,000+ hosts by country, RAM/CPU/disk minimums, disk type, monthly budget, payment method, hourly billing and task presets. Returns 10 plans per page, cheapest first by default, each with specs, monthly price, payment methods, the host page and an order link. Prices are read on the hosts' own sites and refreshed hourly.
- `get_vps_host` — Everything the catalog knows about one VPS/hosting provider: legal entity and country, server countries, payment methods, terms (trial, money back, hourly billing, DDoS, IPv6, SLA, long-term discount), place in the accsly rating, VPS price range and cheapest plan per RAM size, the cheapest plans with order links, and links to its comparison, alternatives and page.
- `compare_hosts` — Like-for-like comparison of two VPS hosts from catalog data: cheapest plan with at least 1/2/4/8/16 GB RAM, plan counts, median price, countries, NVMe share, payment methods, trial, money back, hourly billing, DDoS, IPv6, SLA, rating place, and who wins on each.
- `host_promo` — Discount signals of a host: the promotion published on its site (Russian text), long-term prepayment discount computed from its own period prices, free trial and money-back days. Without a host: the hosts with the strongest discount signals. Promo codes are never invented: only those the host publishes.
- `vps_rating` — Top of the accsly.io VPS host rating: score 0-10 per host computed from catalog data (price per resource, entry price, trust, terms, tech, reach), with plans count and entry price. Category narrows it: cheap, russia, abroad (ru only), europe, usa, netherlands, germany, vpn (corporate VPN), windows, hourly, crypto (not on ru), game-server, or web-hosting for the shared hosting rating. Empty = overall.
- `search_accounts` — Search the catalog of ready-made accounts (Telegram, TikTok, Gmail, Steam, ChatGPT and 70+ platforms) compared across independent shops. Returns matching platforms with their categories (slugs and URLs) and the most bought in-stock offers with price, stock, shop, product page and buy link (list_offers sorts one platform or category by price).
- `list_offers` — Offers of one platform or category of the accounts catalog, across shops: price, items in stock, seller shop, product page and buy link. Pass a catalog URL (https://accsly.io/en/catalog/messengers/telegram/…), "platform/category" slugs or a platform slug.

Example (legacy handshake, then a call):

```
POST https://accsly.io/mcp
Content-Type: application/json
Accept: application/json, text/event-stream

{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"my-agent","version":"1.0"}}}

{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search_vps","arguments":{"country":["DE"],"ram_gb":2,"max_price":5,"locale":"en"}}}
```

## HTTP endpoints

- OpenAPI 3.1 description: https://accsly.io/openapi.json
- VPS search as JSON: `https://accsly.io/{locale}/vps?…&format=json` (also on every landing, /hosting and /dedicated pages): 10 plans a page (`page`, `pages`), the finder's filters as query parameters — `country` (ISO codes, comma-separated), `price` (monthly budget in the locale currency), `ram`, `cpu`, `ghz`, `disk`, `disk_type`, `pay`, `opt`, `virt`, `os`, `traffic=unlim`, `region`, `task`, `q`, `sort`, `one=1`.
- Accounts search as JSON: `https://accsly.io/api/search?q=telegram&locale=en`.
- Markdown versions: add `?format=md` to a VPS rating, comparison, host, alternatives, price index, guide or VPS landing page (also /ru/vps/promo pages). HTML pages announce it with `<link rel="alternate" type="text/markdown">`.
- Agent manifest: https://accsly.io/.well-known/ai-catalog.json

# Accounts catalog

Ready-made accounts and services of independent shops; prices and stock are live on the pages, the MCP tools `search_accounts` and `list_offers` query them.

- **Social Networks**: [Tumblr](https://accsly.io/en/catalog/social/tumblr) (26), [Bluesky](https://accsly.io/en/catalog/social/bluesky) (39), [Quora](https://accsly.io/en/catalog/social/quora2) (55), [Twitter (X)](https://accsly.io/en/catalog/social/twitter-x) (986), [TikTok](https://accsly.io/en/catalog/social/tiktok) (1,898), [LinkedIn](https://accsly.io/en/catalog/social/linkedin) (113), [Reddit](https://accsly.io/en/catalog/social/reddit) (265), [Pinterest](https://accsly.io/en/catalog/social/pinterest) (60), [Snapchat](https://accsly.io/en/catalog/social/snapchat) (62)
- **Messengers**: [Telegram](https://accsly.io/en/catalog/messengers/telegram) (4,900), [Discord](https://accsly.io/en/catalog/messengers/discord) (244), [WhatsApp](https://accsly.io/en/catalog/messengers/whatsapp) (152), [Skype](https://accsly.io/en/catalog/messengers/skype) (45), [Viber](https://accsly.io/en/catalog/messengers/viber) (1)
- **Email**: [Google](https://accsly.io/en/catalog/email/google) (1,182), [Tuta (Tutanota)](https://accsly.io/en/catalog/email/tuta) (20), [ProtonMail](https://accsly.io/en/catalog/email/protonmail) (58), [GMX](https://accsly.io/en/catalog/email/gmx) (237), [Mail.com](https://accsly.io/en/catalog/email/mail-com) (197), [AOL](https://accsly.io/en/catalog/email/aol) (51), [Onet.pl](https://accsly.io/en/catalog/email/onet-pl) (80), [Mail.tm](https://accsly.io/en/catalog/email/mail-tm) (93), [web.de](https://accsly.io/en/catalog/email/web-de) (7), [t-online.de](https://accsly.io/en/catalog/email/t-online-de) (10), [Gazeta.pl](https://accsly.io/en/catalog/email/gazeta-pl) (17), [Inbox.lv](https://accsly.io/en/catalog/email/inbox-lv) (10), [Microsoft / Outlook](https://accsly.io/en/catalog/email/microsoft-outlook) (679), [Yahoo](https://accsly.io/en/catalog/email/yahoo) (65), [Firstmail](https://accsly.io/en/catalog/email/firstmail) (139), [Other Emails](https://accsly.io/en/catalog/email/other-email) (216)
- **AI / Neural Networks**: [DeepSeek](https://accsly.io/en/catalog/ai/deepseek) (25), [Leonardo AI](https://accsly.io/en/catalog/ai/leonardo-ai) (16), [ChatGPT / OpenAI](https://accsly.io/en/catalog/ai/chatgpt-openai) (180)
- **Gaming**: [Steam](https://accsly.io/en/catalog/gaming/steam) (1,388), [PlayStation](https://accsly.io/en/catalog/gaming/playstation) (116), [World of Tanks](https://accsly.io/en/catalog/gaming/wot) (230), [Epic Games](https://accsly.io/en/catalog/gaming/epicgames) (23), [Supercell](https://accsly.io/en/catalog/gaming/supercell) (1), [Minecraft](https://accsly.io/en/catalog/gaming/minecraft) (5), [Origin](https://accsly.io/en/catalog/gaming/origin) (10), [Battle.NET](https://accsly.io/en/catalog/gaming/battlenet) (8), [GOG](https://accsly.io/en/catalog/gaming/gog) (52), [Roblox](https://accsly.io/en/catalog/gaming/roblox) (27), [Xbox](https://accsly.io/en/catalog/gaming/xbox) (64), [Nintendo](https://accsly.io/en/catalog/gaming/nintendo) (108), [Mobile games](https://accsly.io/en/catalog/gaming/mobile-games) (34)
- **Social Boosting**: [Boosting](https://accsly.io/en/catalog/boosting/nakrutka) (343)
- **Dating**: [Beboo](https://accsly.io/en/catalog/dating/beboo) (69), [Mamba.ru](https://accsly.io/en/catalog/dating/mambaru) (100), [Fotostrana](https://accsly.io/en/catalog/dating/fotostrana) (31), [Teamo](https://accsly.io/en/catalog/dating/teamo) (33), [RusDate](https://accsly.io/en/catalog/dating/rusdate) (2), [Tabor](https://accsly.io/en/catalog/dating/tabor) (60), [Topface](https://accsly.io/en/catalog/dating/topface) (28), [Badoo](https://accsly.io/en/catalog/dating/badoo) (13), [LovePlanet](https://accsly.io/en/catalog/dating/loveplanet) (71), [Twinby](https://accsly.io/en/catalog/dating/twinby) (5), [Премиум](https://accsly.io/en/catalog/dating/premium) (4), [Loloo](https://accsly.io/en/catalog/dating/loloo) (9), [Badanga](https://accsly.io/en/catalog/dating/badanga) (21), [Other Dating Sites](https://accsly.io/en/catalog/dating/other-dating-sites) (17)
- **Other**: [GitHub](https://accsly.io/en/catalog/other/github) (71), [Mega.nz](https://accsly.io/en/catalog/other/mega-nz) (33), [OLX](https://accsly.io/en/catalog/other/olx) (9), [Rutube](https://accsly.io/en/catalog/other/rutube) (3), [Duolingo](https://accsly.io/en/catalog/other/duolingo) (6), [Kick](https://accsly.io/en/catalog/other/kick) (18), [YouTube](https://accsly.io/en/catalog/other/youtube) (418), [Spotify](https://accsly.io/en/catalog/other/spotify) (347), [Netflix](https://accsly.io/en/catalog/other/netflix) (10), [Twitch](https://accsly.io/en/catalog/other/twitch) (113), [Other](https://accsly.io/en/catalog/other/other-service) (232), [Software](https://accsly.io/en/catalog/other/software) (877), [Online Cinema](https://accsly.io/en/catalog/other/cinema) (45), [Amazon](https://accsly.io/en/catalog/other/amazon) (13)

# Best cheap VPS hosting 2026

We scored 38 hosts and 202 plans read on their sites. Scores 0–10 come from a formula over catalog data; places are not sold.

> Source: https://accsly.io/en/vps/rating/cheap · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

| # | Host | Score | Resource price | Entry price | Reliability | Terms | Technology | Choice | Plans | From | Countries |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 1 | [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | 8.7 | 9.2 | 10.0 | 8.3 | 6.6 | 7.2 | 5.4 | 12 | 0.40 $ | 4 |
| 2 | [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | 8.2 | 10.0 | 9.5 | 8.1 | 2.5 | 3.8 | 5.5 | 13 | 0.70 $ | 4 |
| 3 | [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) | 7.7 | 9.7 | 9.2 | 6.8 | 3.3 | 5.5 | 2.0 | 3 | 0.71 $ | 1 |
| 4 | [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | 6.9 | 7.0 | 8.4 | 6.8 | 3.3 | 6.5 | 4.9 | 4 | 0.99 $ | 6 |
| 5 | [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) | 6.8 | 7.8 | 8.6 | 6.8 | 0.9 | 5.0 | 3.1 | 7 | 0.97 $ | 1 |
| 6 | [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | 6.7 | 4.9 | 9.7 | 5.7 | 4.1 | 5.7 | 9.6 | 30 | 0.64 $ | 13 |
| 7 | [EUGameHost](https://accsly.io/en/vps/hosting/eugamehost) | 6.7 | 4.3 | 8.9 | 8.6 | 5.0 | 9.0 | 2.0 | 3 | 0.86 $ | 1 |
| 8 | [TierHive](https://accsly.io/en/vps/hosting/tierhive) | 6.6 | 8.4 | 7.3 | 5.3 | 1.5 | 8.0 | 6.5 | 3 | 1.01 $ | 10 |
| 9 | [Hostablanca.com](https://accsly.io/en/vps/hosting/hostablanca) | 6.5 | 6.5 | 7.6 | 6.8 | 2.5 | 8.0 | 4.8 | 16 | 1.01 $ | 2 |
| 10 | [TNA Hosting](https://accsly.io/en/vps/hosting/tnahosting) | 6.5 | 8.9 | 5.7 | 6.8 | 3.3 | 5.4 | 2.7 | 5 | 1.33 $ | 1 |
| 11 | [myPrepaid-Server](https://accsly.io/en/vps/hosting/myprepaid-server) | 6.4 | 6.8 | 7.0 | 6.8 | 3.4 | 7.9 | 2.9 | 6 | 1.12 $ | 1 |
| 12 | [Hostodo](https://accsly.io/en/vps/hosting/hostodo) | 6.4 | 5.9 | 6.5 | 7.8 | 5.9 | 7.3 | 2.4 | 4 | 1.25 $ | 1 |
| 13 | [SecureDragon](https://accsly.io/en/vps/hosting/securedragon) | 6.0 | 8.1 | 2.4 | 10.0 | 5.9 | 3.0 | 2.0 | 3 | 2.08 $ | 1 |
| 14 | [Time4VPS](https://accsly.io/en/vps/hosting/time4vps) | 6.0 | 8.6 | 1.1 | 10.0 | 6.8 | 5.5 | 2.7 | 5 | 2.48 $ | 1 |
| 15 | [hostEONS.com](https://accsly.io/en/vps/hosting/hosteons) | 5.9 | 4.1 | 8.1 | 6.8 | 4.3 | 6.7 | 2.0 | 3 | 1.00 $ | 1 |
| 16 | [Host Media Ltd](https://accsly.io/en/vps/hosting/hostmedia) | 5.5 | 3.0 | 7.8 | 8.5 | 1.6 | 5.5 | 2.4 | 4 | 1.01 $ | 1 |
| 17 | [host.com.pk](https://accsly.io/en/vps/hosting/host-com) | 5.2 | 5.7 | 4.1 | 8.3 | 4.1 | 2.0 | 2.9 | 6 | 1.80 $ | 1 |
| 18 | [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | 5.2 | 9.5 | 0.8 | 7.4 | 1.6 | 8.0 | 2.0 | 3 | 2.59 $ | 1 |
| 19 | [Firstbyte](https://accsly.io/en/vps/hosting/firstbyte) | 5.1 | 4.6 | 4.6 | 7.6 | 2.6 | 4.5 | 7.2 | 5 | 1.56 $ | 12 |
| 20 | [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | 5.1 | 7.3 | 1.9 | 6.9 | 4.1 | 8.0 | 2.4 | 4 | 2.29 $ | 1 |
| 21 | [OrangeVPS](https://accsly.io/en/vps/hosting/orangevps) | 4.9 | 5.1 | 3.0 | 7.2 | 4.3 | 8.0 | 3.9 | 4 | 1.96 $ | 4 |
| 22 | [Poyraz Hosting](https://accsly.io/en/vps/hosting/poyrazhosting-com) | 4.9 | 6.2 | 1.4 | 10.0 | 4.1 | 3.0 | 2.0 | 3 | 2.37 $ | 1 |
| 23 | [LandVPS](https://accsly.io/en/vps/hosting/landvps) | 4.8 | 1.9 | 6.8 | 6.8 | 4.1 | 4.8 | 4.4 | 4 | 1.14 $ | 5 |
| 24 | [WebHosting24](https://accsly.io/en/vps/hosting/webhosting24) | 4.8 | 3.2 | 5.1 | 6.8 | 4.3 | 6.5 | 2.9 | 4 | 1.39 $ | 2 |
| 25 | [Pyro Inc.](https://accsly.io/en/vps/hosting/pyro) | 4.8 | 5.4 | 2.7 | 8.3 | 1.6 | 8.0 | 2.5 | 3 | 2.00 $ | 2 |

## How the score works

- **Resource price** (30 %): median price of a «resource unit» (1 GB RAM ≈ ½ core ≈ 50 GB disk) — the cheaper compared with the other rated providers, the higher the score
- **Entry price** (30 %): the provider's cheapest plan in this selection
- **Reliability** (20 %): known legal entity, years on the market, SLA of 99.9% or more, published address or registration number
- **Terms** (10 %): trial period, money-back, hourly billing and convenient payment methods
- **Technology** (5 %): share of NVMe plans, IPv6, DDoS protection, API and instant setup
- **Choice** (5 %): how many countries and plans the provider has

## Other ratings

- [Best VPS hosting in Russia](https://accsly.io/en/vps/rating/russia)
- [Best VPS hosting in Europe](https://accsly.io/en/vps/rating/europe)
- [Best VPS hosting in the USA](https://accsly.io/en/vps/rating/usa)
- [Best VPS hosting in the Netherlands](https://accsly.io/en/vps/rating/netherlands)
- [Best VPS hosting in Germany](https://accsly.io/en/vps/rating/germany)
- [Best VPS for a corporate VPN](https://accsly.io/en/vps/rating/vpn)
- [Best Windows VPS hosting](https://accsly.io/en/vps/rating/windows)
- [Best cloud VPS with hourly billing](https://accsly.io/en/vps/rating/hourly)
- [Best VPS hosting that accepts crypto](https://accsly.io/en/vps/rating/crypto)
- [Best VPS for game servers](https://accsly.io/en/vps/rating/game-server)
- [Best dedicated server hosts](https://accsly.io/en/vps/rating/dedicated)

# VPS prices 2026

Medians over 31,630 plans of 2,286 hosts, prices read on their sites. Median plan: 43.22 $ a month; 1 GB of RAM: 5.25 $.

> Source: https://accsly.io/en/vps/prices · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Price by RAM

| RAM | Plans | Median | NVMe | SSD | NVMe premium |
| --- | --- | --- | --- | --- | --- |
| 1 GB | 2125 | 8.00 $ | 6.36 $ | 9.86 $ | -36 % |
| 2 GB | 3728 | 13.40 $ | 9.99 $ | 16.78 $ | -40 % |
| 4 GB | 4548 | 22.39 $ | 17.81 $ | 29.66 $ | -40 % |
| 8 GB | 4665 | 42.76 $ | 32.80 $ | 50.99 $ | -36 % |
| 16 GB | 3689 | 77.00 $ | 58.01 $ | 93.71 $ | -38 % |
| 32 GB | 2468 | 134 $ | 101 $ | 185 $ | -46 % |

## Price by country

| Country | Plans | Hosts | Median | Per GB RAM | Cheapest 2 GB+ |
| --- | --- | --- | --- | --- | --- |
| USA | 9143 | 667 | 49.06 $ | 5.16 $ | 0.49 $ (VDS6.Net) |
| Germany | 6096 | 478 | 48.12 $ | 5.15 $ | 0.80 $ (Çelen Hosting Information Tech.) |
| Netherlands | 5796 | 433 | 55.97 $ | 6.06 $ | 0.49 $ (VDS6.Net) |
| United Kingdom | 4848 | 338 | 76.23 $ | 6.48 $ | 1.71 $ (TierHive) |
| Singapore | 3622 | 229 | 89.00 $ | 7.00 $ | 1.71 $ (TierHive) |
| France | 2836 | 176 | 83.16 $ | 6.70 $ | 0.80 $ (Çelen Hosting Information Tech.) |
| India | 2798 | 132 | 104 $ | 6.75 $ | 2.65 $ (Web Eye Soft) |
| Canada | 2743 | 167 | 96.00 $ | 7.47 $ | 1.71 $ (TierHive) |
| Australia | 2571 | 127 | 133 $ | 8.17 $ | 1.71 $ (TierHive) |
| Japan | 2378 | 111 | 129 $ | 8.00 $ | 1.71 $ (TierHive) |
| Poland | 2149 | 124 | 95.00 $ | 6.57 $ | 0.49 $ (VDS6.Net) |
| Sweden | 1996 | 79 | 160 $ | 8.13 $ | 2.23 $ (Aeza) |
| Spain | 1983 | 97 | 125 $ | 8.17 $ | 2.13 $ (Hostablanca.com) |
| Russia | 1876 | 194 | 24.14 $ | 4.10 $ | 1.20 $ (RocketCloud) |
| Italy | 1640 | 69 | 151 $ | 7.51 $ | 0.49 $ (VDS6.Net) |
| Hong Kong | 1607 | 92 | 120 $ | 7.56 $ | 1.99 $ (HostVDS) |
| Brazil | 1375 | 55 | 202 $ | 8.28 $ | 4.52 $ (ISBrasil) |
| Switzerland | 1359 | 69 | 184 $ | 7.85 $ | 3.02 $ (Infomaniak) |
| South Korea | 1348 | 27 | 320 $ | 9.40 $ | 5.00 $ (PhotonVPS) |
| South Africa | 1337 | 44 | 200 $ | 8.34 $ | 3.05 $ (Sive Host) |
| Ireland | 1183 | 28 | 368 $ | 8.29 $ | 2.99 $ (Rabisu.com) |
| Finland | 1177 | 117 | 39.72 $ | 4.31 $ | 1.19 $ (Çelen Hosting Information Tech.) |
| Israel | 1174 | 32 | 277 $ | 9.19 $ | 5.03 $ (Cloudys) |
| Indonesia | 1124 | 46 | 165 $ | 6.71 $ | 3.86 $ (Kenceng Solusindo.co.id) |
| Norway | 980 | 25 | 330 $ | 7.80 $ | 4.00 $ (Hosthatch) |

## Other figures

- Plans on NVMe: 42 %
- NVMe premium (median over 1–8 GB): -38 %
- Plans of hosts taking a foreign card or PayPal: 74 %, median 44.77 $

## History

| Month | Median | Per GB | Plans |
| --- | --- | --- | --- |
| 2026-10 | 39.14 $ | 4.97 $ | 28081 |

# Hosting for a company website and domain mail

A company website rarely gets heavy traffic, but it comes with staff mail on the domain, lead forms with personal data and an accounts department that needs invoices. Shared hosting covers all of this in one plan, provided you check the mail limits in advance, set up SPF, DKIM and DMARC and choose a host that works with companies. Below is what to look at and what it costs.

> Source: https://accsly.io/en/vps/guide/hosting-for-company-website-and-mail · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

For a small company, shared hosting is convenient because the site, mailboxes, certificates and backups live in one panel while the host looks after the server. To avoid looking for a new plan six months later, look not only at the space for the site but also at mail, data storage and the paperwork for accounting. The general comparison of hosting and your own server is in the article [Shared hosting or VPS for a website](https://accsly.io/en/vps/guide/hosting-or-vps-for-website).

## Mail on shared hosting: what is limited

Mail on a domain such as info@your-company.com is included in many hosting plans, but with limits written in the small print.

- **Number of mailboxes.** According to the accsly.io catalog as of November 2026, of 6,650 hosting plans on monthly billing, the number of mailboxes is stated for 803. Of these, 451 plans offer unlimited mailboxes, 112 offer one to five, and 13 offer no mail at all. Count your employees and shared addresses (info@, sales@, support@) and add some headroom.
- **Mailbox size.** Mail usually shares disk space with the site. Over a few years, mailboxes with attachments grow to gigabytes, and when the space runs out, both incoming mail and uploads to the site stop working. Check whether there is a separate quota per mailbox and what happens when it is exceeded.
- **Sending limit.** The host limits how many emails a domain or account can send per hour. In cPanel, according to its [documentation](https://docs.cpanel.net/knowledge-base/email/how-to-set-email-send-limits/), emails over the limit are not rejected right away but are queued and sent later. If, however, a domain has too high a share of undelivered emails, sending is temporarily blocked. Ask support for the actual figures for your plan.
- **Mailings.** Newsletters and marketing mailings to the customer base are not sent from shared hosting: the emails will hit the limit, and spam complaints will damage the reputation of the shared server. There are separate mailing services for that, while work mail stays on the hosting.

If there is a lot of mail or you need shared calendars and large mailboxes, mail can be kept with a separate mail service and the site on shared hosting. In that case, the domain's MX records point to the mail service and the A records to the hosting.

## SPF, DKIM and DMARC

Without these three DNS records, emails from your domain end up in spam more often, and fraudsters can send emails in your name.

- **[SPF](https://www.rfc-editor.org/rfc/rfc7208)** is the list of servers allowed to send mail on behalf of the domain. If emails go out from the hosting, the CRM and a mailing service, all of them must be in a single SPF record.
- **[DKIM](https://www.rfc-editor.org/rfc/rfc6376)** is a digital signature of the email. The hosting panel generates the key, and you publish the public part in DNS.
- **[DMARC](https://www.rfc-editor.org/rfc/rfc7489)** is a rule for what to do with emails that fail the checks, plus an address for reports. Start with the p=none policy, read the reports and tighten it later.

Large mail services require this directly. Under the [Gmail sender guidelines](https://support.google.com/a/answer/81126), all senders need SPF or DKIM, senders of more than 5,000 emails a day need all three records, and the share of emails marked as spam must stay below 0.3%. On shared hosting it is usually enough to enable DKIM in the panel and add two or three DNS records. A detailed walkthrough of the records with examples is in the article [Mail server on a VPS: SPF, DKIM, DMARC](https://accsly.io/en/vps/guide/mail-server-on-vps-spf-dkim-dmarc), and DNS records in general in the article [Domains and DNS for a server owner](https://accsly.io/en/vps/guide/domains-and-dns).

## Backups of the site and mail

Backups are listed for 865 of the 6,650 hosting plans; for the rest the host does not describe them. Ask support whether backups include mailboxes, not just site files and databases, how long copies are kept and whether you can restore a single mailbox or a single email. For a company, mail matters most: it holds contracts and correspondence with clients. Keep one more copy outside the hosting: an export of the mailboxes over IMAP or an archive from the panel in the company's cloud storage. Backup storage schemes are covered in the article [VPS backups: strategies and tools](https://accsly.io/en/vps/guide/vps-backups).

## Personal data and the GDPR

A lead form, a callback request, an appointment booking: all of these collect personal data such as a name, phone number and email address. If leads are sent by email, they are also stored in the mailbox on the hosting. If your customers include people in the EU, the EU General Data Protection Regulation (GDPR) applies, including to a company outside the EU that offers goods or services to them. The host that stores this data on your behalf is a processor, and Article 28 requires a data processing agreement (DPA) with it; hosts usually include one in their terms or sign it on request. The GDPR does not require data to be kept in the EU, but a transfer outside the European Economic Area needs a lawful basis such as an adequacy decision or standard contractual clauses, so in practice data of people in the EU is easiest to keep on a server in the EU: [hosting in Europe](https://accsly.io/en/hosting/europe). What else to check in the host's terms is covered in the article [GDPR and choosing a host](https://accsly.io/en/vps/guide/gdpr-and-hosting). If the site collects data of Russian citizens, Russia's law No. 152-FZ also requires it to be recorded and stored in databases located in Russia; see the article [152-FZ and hosting: where to store the data](https://accsly.io/en/vps/guide/152-fz-and-hosting).

## Paying by invoice and accounting documents

A company needs to pay from its business bank account and receive documents for its accounts: a contract, an invoice and, where VAT applies, a VAT invoice. Of the 1,652 shared hosting providers in the catalog, 725 state that they accept payment by invoice. Before ordering, check:

- whether the contract is concluded with a company or a sole trader, and whether the terms can be accepted on behalf of the company;
- which documents are issued and how: in the customer account, electronically or by post;
- whether VAT is included in the price and which of the host's legal entities issues the invoice;
- what happens if payment is late: after how many days the site and mail are suspended.

If the host is registered in a different country from your company, the documents and payment procedure will differ; what this affects is covered in the article [Hosting provider jurisdiction: what it affects](https://accsly.io/en/vps/guide/hoster-jurisdiction). Servers from hosts that invoice companies are collected in the selection [VPS paid by invoice](https://accsly.io/en/vps/pay-by-invoice).

## Access for employees and contractors

A company website outlives several contractors and employees, so keeping access in order matters more than on a personal site. The contract with the host, the domain and the hosting account must be in the company's name, not a web studio's or a former employee's. Otherwise, when you part ways, you will have to recover access through support, and the site and mail will be under someone else's control all that time.

- The password to the main account and to the domain registrar's panel is known to a small circle of people, and the login is protected with two-factor authentication if the host supports it.
- Developers get separate FTP or SSH users with access to the site folder, not the main password.
- Mailboxes of employees who leave are not deleted right away: forwarding to a manager is set up and an archive is kept.
- The contact address for notifications from the host and the registrar is a shared company address, not one person's personal mailbox: reminders about renewing the domain and the plan go there.

If the company has several sites, such as the main one and sites for brands or branches, a multi-site plan in one account is more convenient: one payment, one set of documents and shared backups.

## What hosting for a company costs

According to the accsly.io catalog as of November 2026, hosting plans on monthly billing with at least 10 mailboxes cost $10 a month in the middle of the market (676 plans), and a quarter of them cost less than $5.20. The catalog keeps prices in roubles; the dollar figures are converted at the Central Bank of Russia rate of 7 November 2026 and rounded. Plans for five or more sites, if the company has separate sites for brands or branches, also cost $10 in the middle of the market. The domain is paid for separately.

If there are many employees, the whole company depends on mail, or the site runs its own software, look at a VPS with your own mail server: [VPS for a mail server](https://accsly.io/en/vps/for-mail-server). For most companies of up to a few dozen people, shared hosting is enough. All plans are collected in the section [website hosting](https://accsly.io/en/hosting), and plans with the ISPmanager panel, where mail, domains and SSL are set up in one interface, in the selection [hosting with ISPmanager](https://accsly.io/en/hosting/ispmanager).

## FAQ

### Can company mail be kept on ordinary shared hosting?

Yes, if the plan provides enough mailboxes and space and the domain has SPF, DKIM and DMARC set up. Bulk mailings to customers go through a separate mailing service, while work mail stays on the hosting.

### How many emails can be sent from shared hosting?

It depends on the host: usually there is a limit on emails per hour per domain or account. In cPanel, emails over the limit are queued, and if the share of undelivered emails is high, sending is temporarily blocked. Ask support for the exact figure.

### Why do I need SPF, DKIM and DMARC?

SPF states which servers send mail for the domain, DKIM signs emails, and DMARC sets what to do with emails that fail the checks. Without them, mail ends up in spam more often, and Gmail requires SPF or DKIM from all senders.

### Where should a company website with customer data be hosted?

If the site collects data of people in the EU, the GDPR does not require an EU server, but it does require a data processing agreement with the host and a lawful basis for transfers outside the EEA, so a server in the EU is the simplest choice. Data of Russian citizens must be recorded and stored in databases in Russia under 152-FZ.

### Can a company pay for hosting by invoice?

Yes. According to the accsly.io catalog as of November 2026, 725 of 1,652 shared hosting providers state that they accept payment by invoice. Check which documents they issue and whether VAT is included.

### How much does hosting with mail for a company cost?

The median price of a plan with at least 10 mailboxes is about $10 a month on monthly billing. The domain is paid for separately.

_Updated: 2026-11-07_

# Hosting for a landing page or business card site

A landing page or a business card site does not need a powerful server or a VPS: the simplest shared hosting plan for a few dollars a month is enough. What matters more is that the plan includes free SSL, the domain stays yours and the page opens quickly on a phone. Below is how to choose a plan, what to check in it and what it costs.

> Source: https://accsly.io/en/vps/guide/hosting-for-landing-page · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A landing page is a single page built around one specific offer; a business card site is a few pages about a company or a specialist: services, prices, contacts. Such sites get little traffic and often have no database at all, so almost any hosting can handle the load. The usual mistakes are different: a plan without SSL, a domain registered in the contractor's name, a year paid in advance at a price that later goes up, and a slow page because of heavy images. If you are torn between hosting and your own server, first read the article [Shared hosting or VPS for a website](https://accsly.io/en/vps/guide/hosting-or-vps-for-website): for a landing page the answer is almost always hosting.

## A static site or a CMS

How the site is built determines what the plan needs.

- **A static site** is a set of HTML, CSS, JavaScript and image files. That is what a hand-coded landing page looks like, as does one built with a static site generator or exported from a website builder. It needs neither PHP nor a database, and the page is served fastest of all. Any plan will do, even one without databases.
- **A CMS site** runs on WordPress, Joomla, MODX or another system where texts are edited in an admin panel. It needs PHP and a MySQL or MariaDB database. For WordPress, PHP 8.3 or newer, MySQL 8.0 or MariaDB 10.11 or newer and HTTPS are [recommended](https://wordpress.org/about/requirements/); check the versions in the plan description or with support.

If the texts change once every few months, a static landing page is simpler and more reliable: there is nothing to update and nothing to hack. A CMS is convenient when the pages are edited by an employee without coding skills or the site has a blog and news. In that case, see the selection [hosting for WordPress](https://accsly.io/en/hosting/wordpress).

## The cheapest sensible plan

According to the accsly.io catalog as of November 2026, there are 301 hosting plans in stock on monthly billing for up to 100 roubles (about $1.20) a month from 215 hosts, and 536 plans for up to 150 roubles (about $1.85). The cheapest costs about 40 cents a month. The median plan for one site costs $3.95. A cheap plan suits a landing page if it has:

- **Free SSL.** Of the 536 plans up to about $1.85, only 42 explicitly list a free certificate, and 6 do not have one. For the rest the condition is not stated, so ask support before paying. The median price of cheap plans with SSL listed is $1.40 a month.
- **At least 1 GB of disk space.** A landing page with images needs a few hundred megabytes, but space is also needed for logs and backups. The median disk size of plans up to about $1.85 is 3 GB.
- **Monthly billing.** 23% of hosting plans in the catalog are sold only for a year in advance. That pays off if the site will definitely live for a year, but for a two-month ad campaign a monthly plan is better.
- **The renewal price.** Often the low price applies only to the first term. Look for the renewal price in the plan description or the contract.
- **A trial period.** Some hosts let you try hosting for free, see the selection [hosting with a free trial](https://accsly.io/en/hosting/free-trial) and the article [Free trials and money-back guarantees](https://accsly.io/en/vps/guide/trial-and-money-back).

Selections by price: [hosting under 100 roubles (about $1.20) a month](https://accsly.io/en/hosting/under-100) and [cheap hosting under 150 roubles (about $1.85)](https://accsly.io/en/hosting/cheap). If more sites may come later, look at multi-site plans right away: moving sites between accounts later takes longer than choosing some headroom now.

## Free SSL

Without HTTPS, the browser marks the page as not secure, and lead forms send the visitor's phone number and name in plain text. Free certificates are issued by Let's Encrypt: according to its [FAQ](https://letsencrypt.org/docs/faq/), a certificate is valid for 90 days and should be renewed every 60 days. On shared hosting the panel does this automatically; your job is to enable the certificate for the domain and check that the site opens over https:// and redirects there from http://. A landing page does not need a paid certificate: the encryption is the same. More in the article [SSL certificates: free and paid](https://accsly.io/en/vps/guide/ssl-certificates).

## The domain

A domain is bought separately from hosting, from a registrar or through the host itself. The main rule: the domain's registrant must be you or your company, not the contractor who built the site. Otherwise, when you change contractors you can lose the address together with the ads and business cards it is printed on. For the site to open, the domain's DNS points to the hosting server's address (A and AAAA records) or to the host's name servers. If you change hosts later, these records can be updated in a few minutes, but the changes take effect gradually, over the TTL period. How the records work and how to move without downtime is explained in the article [Domains and DNS for a server owner](https://accsly.io/en/vps/guide/domains-and-dns).

## Loading speed

A landing page is most often opened on a phone from an ad link, and a slow page loses visitors before the first screen appears. Google measures speed with [Core Web Vitals](https://web.dev/articles/vitals): the main element of the page should appear within 2.5 seconds (LCP), the response to an interaction should come within 200 ms (INP), and layout shift should not exceed 0.1 (CLS) for 75% of visits. What affects these numbers:

- **Images and fonts.** Most of the time usually goes on heavy images. Compress them and use WebP or AVIF: this gains more than changing hosts.
- **Server location.** Choose a server in or near your audience's region, for example [hosting in Europe](https://accsly.io/en/hosting/europe) or [hosting in the USA](https://accsly.io/en/hosting/usa). For visitors from different countries a CDN helps, see the article [CDN: when a website needs one](https://accsly.io/en/vps/guide/cdn-for-website).
- **Disk and cache.** For a static landing page the disk type hardly matters. For a CMS, plans on NVMe are faster: there are 181 of them among plans up to about $1.85, see the selection [NVMe hosting](https://accsly.io/en/hosting/nvme). Enable page caching if the CMS supports it.

## Lead forms and mail

The key part of a landing page is the lead form, and it is the part that most often breaks without anyone noticing. The form script sends an email through the hosting mail function, and if the domain has no SPF and DKIM records, leads go to spam or do not arrive at all. What to check:

- the form email is sent from an address on your domain, and the domain's DNS has SPF and DKIM; the records are covered in the article [Hosting for a company website and domain mail](https://accsly.io/en/vps/guide/hosting-for-company-website-and-mail);
- leads are duplicated somewhere they will not get lost: a CRM, a spreadsheet or the manager's messenger;
- a test lead is sent after launch and after every change to the landing page.

A name and phone number in a form are personal data. If your visitors include people in the EU, the GDPR applies, and the host that stores the form data acts as a processor, so check whether it offers a data processing agreement (DPA); more in the article [GDPR and choosing a host](https://accsly.io/en/vps/guide/gdpr-and-hosting). If visitors are Russian citizens, Russia's law No. 152-FZ requires their data to be recorded in databases located in Russia, and the site must have a data processing policy and a consent to processing; see the article [152-FZ and hosting: where to store the data](https://accsly.io/en/vps/guide/152-fz-and-hosting).

## When a simple plan is no longer enough

Even with active advertising, a landing page usually fits into an inexpensive plan if the page is static or cached. Signs that it is time for a higher plan: the site returns 503 or 508 errors during ad hours, a blog and a catalog have been added to the landing page, and one account already hosts several sites. You will need your own server only if the landing page works together with software that shared hosting does not allow you to run, see the article [When to move from shared hosting to a VPS](https://accsly.io/en/vps/guide/hosting-to-vps-when).

## A short checklist before paying

- Whether the site is static or on a CMS, and whether it needs PHP and a database.
- Free SSL is listed in the plan or confirmed by support.
- The domain is registered to you, and you have access to its control panel.
- The monthly price and the renewal price are clear, and the billing term matches the site's lifetime.
- The server is close to your audience.
- There are backups, or you keep the site's source files yourself.

All shared hosting plans are collected in the section [website hosting](https://accsly.io/en/hosting).

## FAQ

### What hosting does a landing page need?

The simplest single-site shared hosting plan with free SSL and at least 1 GB of space. A static landing page needs neither PHP nor a database; for a landing page on a CMS, check the PHP and MySQL versions.

### How much does hosting for a business card site cost?

According to the accsly.io catalog as of November 2026, the median plan for one site costs about $3.95 a month. There are 301 plans on monthly billing for up to 100 roubles (about $1.20) a month, and the cheapest costs about 40 cents.

### Does a landing page need a VPS?

No. A landing page with ordinary traffic runs on shared hosting, while a VPS adds costs and administration work. You need your own server only if the landing page is connected to software that shared hosting does not allow.

### Can I host a site made in a website builder?

Yes, if the builder lets you export the site as HTML, CSS and image files. Such a static site is uploaded to the domain folder on any hosting plan.

### Do I need to pay for SSL for a business card site?

No. A free Let's Encrypt certificate encrypts the connection the same way as a paid one, and the hosting panel renews it automatically. Just check that free SSL is included in the plan.

### What should I do if the domain is registered to the contractor?

Ask for the domain to be transferred to you or your company through the registrar while relations with the contractor are good. The domain registrant controls the site's address, and without access to the domain you cannot change hosts.

_Updated: 2026-11-07_

# How to choose hosting for an online shop

A small shop on WooCommerce, OpenCart or 1C-Bitrix runs fine on a good shared hosting plan. Its requirements are stricter than those of a business card site, though: recent PHP and database versions, HTTPS on every page, headroom in the limits for sales and backups from which orders can be restored quickly. Below is what to check in a plan, what it costs and when it is time to move to a VPS.

> Source: https://accsly.io/en/vps/guide/hosting-for-online-store · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A shop differs from an ordinary website in that every minute of downtime costs money and the database changes all the time: orders, stock levels, customers. So hosting for a shop is chosen on four points: whether the environment suits the CMS, how HTTPS and payments are set up, whether the account can handle a rush of buyers and whether there is a fresh copy of the database. The general comparison of hosting and a VPS is in the article [Shared hosting or VPS for a website](https://accsly.io/en/vps/guide/hosting-or-vps-for-website); this one is only about shops.

## Requirements of popular CMS

Start with the official requirements of your platform and compare them with the plan description:

| CMS | PHP | Database | Other |
| --- | --- | --- | --- |
| WooCommerce | 8.3 or newer | MySQL 8.0+ or MariaDB 10.6+ | PHP memory of 256 MB or more, HTTPS |
| OpenCart | 8.0 or newer | MySQL or MariaDB (MySQLi or PDO) | cURL, GD, mbstring, ZipArchive, zlib and OpenSSL extensions |
| 1C-Bitrix: Site Management | 8.2 | MySQL 8.0 or newer | Apache 2.0+ or Nginx |

Sources: [WooCommerce recommendations](https://woocommerce.com/document/server-requirements/), [OpenCart documentation](https://docs.opencart.com/getting-started/system-requirements.md) and [1C-Bitrix system requirements](https://www.1c-bitrix.ru/products/cms/requirements.php). 1C-Bitrix is a CMS common in Russia and the CIS, and its developer states plainly that any hosting meeting these requirements will do. WooCommerce still allows the old PHP 7.4 and MySQL 5.6, but warns that their support has ended and they are not secure.

Plan descriptions rarely state PHP versions. According to the accsly.io catalog as of November 2026, of the 1,469 plans suitable for a shop, PHP versions are named for 127, and PHP 8.3 or newer for only 39. So before paying, ask support about the PHP and database versions, the PHP memory limit (memory_limit) and whether you can switch the version yourself in the panel.

Besides the versions, a shop needs:

- **Cron jobs.** They run stock imports, product feeds to marketplaces, abandoned cart emails and cache cleanup.
- **Two or more databases.** The second one is for a staging copy of the shop, where updates are tested before going live.
- **Headroom in disk space and inodes.** Product photos, thumbnails and cache quickly add up to tens of thousands of files. The limit on the number of files can be stricter than the disk space limit; more on this in the article [How to read hosting plans: the hidden limits](https://accsly.io/en/vps/guide/hidden-limits-in-hosting-plans).
- **Mail on the domain.** Order emails are sent in the shop's name, and without SPF and DKIM records they end up in spam.

## SSL and payment pages

A shop works only over HTTPS: logging in to the customer account, the cart and forms with a phone number and address all depend on it. A free Let's Encrypt certificate suits a shop just as well as a paid one, and the hosting panel takes care of issuing and renewing it. In the catalog, free SSL is listed for 488 plans suitable for a shop and explicitly absent from 11; for the rest it is not stated, so check before paying. How certificate types differ and when a paid one is worth it is covered in the article [SSL certificates: free and paid](https://accsly.io/en/vps/guide/ssl-certificates).

It is best not to accept card details on your own hosting at all. Set up payments so that the buyer enters the card on the payment provider's page or in its widget, and the shop receives only the payment status. Then card numbers never pass through your server, and the requirements of the [PCI DSS](https://www.pcisecuritystandards.org/) standard for your hosting are kept to a minimum. If the card entry form is on your own site, ordinary shared hosting is no longer enough, and such a setup has to be agreed with the payment provider.

## Traffic peaks: sales and mailings

On shared hosting every account has limits, and a shop hits them on its best days: a sale, a mailing to the customer base, an ad campaign. For example, in CloudLinux, which many hosts run, an account is allowed [by default](https://docs.cloudlinux.com/cloudlinuxos/limits/) 20 simultaneous PHP entry processes and 1 GB of process memory. When there are more buyers, the site responds with error 508, and some orders are lost.

What helps:

- find out from the host the real process, memory and CPU limits on the chosen plan and the next one up;
- enable caching of catalog pages and serve images through a CDN, see the article [CDN: when a website needs one](https://accsly.io/en/vps/guide/cdn-for-website);
- load-test the shop on a staging copy before a big promotion, as described in the article [Load testing a website before launch](https://accsly.io/en/vps/guide/load-testing-before-launch);
- choose a plan without a traffic cap so that a spike in visits does not turn into an extra charge: [hosting with unlimited traffic](https://accsly.io/en/hosting/unlimited-traffic).

## Backups

For a shop, what matters is not just having a copy but how fresh it is. A week-old copy means a week of lost orders. Backups are listed for 395 plans suitable for a shop; for the rest the host does not describe them. Check three things: how often files and the database are copied, how many days copies are kept and whether you can restore them yourself from the panel.

Even with good backups at the host, keep your own: a daily database dump and a weekly archive of files somewhere else, in cloud storage or on another server. Once a quarter, test a restore on a staging copy. Storage schemes are covered in more detail in the article [VPS backups: strategies and tools](https://accsly.io/en/vps/guide/vps-backups).

## Shop security on shared hosting

The host is responsible for the server, but the shop owner is responsible for the CMS itself. Shops are most often hacked through outdated modules and themes, not through the server. What to do from day one:

- **Update the CMS, modules and themes** as soon as security fixes are released. Test the update on a staging copy in the second database first, then roll it out to the live site.
- **Remove what you do not use.** Unused modules, old themes and copies of the site in folders like /old or /backup remain reachable from the internet and become an entry point.
- **Protect the admin login.** A separate account for each employee, two-factor authentication if the CMS supports it, and a strong password for the hosting panel.
- **Separate access.** Give a contractor a separate FTP or SSH user with access only to the site folder, not the password to the whole panel. Remove the access once the work is done.

Ask the host whether the server scans files for malware and protects against password brute-forcing. If the host finds malicious code, it may take the site offline temporarily, so a clean backup is needed for that case too.

## What hosting for a shop costs

Prices are per the accsly.io catalog as of November 2026, plans in stock on monthly billing, per month. The catalog keeps prices in roubles; the dollar figures are converted at the Central Bank of Russia rate of 7 November 2026 and rounded. A plan suitable for a shop here means hosting with at least two databases and 10 GB of disk.

| Option | Price, all locations |
| --- | --- |
| Hosting for a shop, a quarter of plans cost less than | $5 |
| Hosting for a shop, median | $8.95 (1,469 plans) |
| Hosting for 1 site, median | $3.95 (977) |
| VPS 2 vCPU, 4 GB, median | $21.25 (2,440) |
| VPS 4 vCPU, 8 GB, median | $40.15 (2,335) |

The cheapest single-site plan usually does not suit a shop: it has one database and little space. Plans that include both free SSL and backups cost $10 a month in the middle of the market (369 plans). About a quarter of hosting plans are sold only with payment for a year in advance, so compare the price per month. A selection of plans: [hosting for an online shop](https://accsly.io/en/hosting/online-store), and if you need a fast database, [NVMe hosting](https://accsly.io/en/hosting/nvme).

## When a shop needs a VPS

Shared hosting stops being enough when the shop has tasks that do not fit into a shared account:

- error 508 or 503 appears on ordinary days, not only during sales;
- the catalog has tens of thousands of products with filters, and category pages take several seconds to open;
- imports from the accounting or inventory system take hours and are cut off by the script time limit;
- you need Redis, a search engine, queues or your own web server configuration.

Such a shop usually does well on a VPS with 2–4 vCPU and 4–8 GB of memory: [VPS for an online shop](https://accsly.io/en/vps/for-online-store). How to tell that a move is justified is described in the article [When to move from shared hosting to a VPS](https://accsly.io/en/vps/guide/hosting-to-vps-when), and the move itself without downtime in the article [How to move a website from shared hosting to a VPS](https://accsly.io/en/vps/guide/move-site-hosting-to-vps).

## FAQ

### Is shared hosting suitable for an online shop?

Yes, for a small shop on WooCommerce, OpenCart or 1C-Bitrix. The plan should provide the required PHP and database versions, at least two databases, free SSL and backups, and its account limits should hold up on peak days.

### How much does hosting for an online shop cost?

According to the accsly.io catalog as of November 2026, the median price of a plan with at least two databases and 10 GB of disk is about $8.95 a month. Plans with free SSL and backups cost about $10 a month in the middle of the market.

### Which PHP version does WooCommerce need?

WooCommerce recommends PHP 8.3 or newer, MySQL 8.0 or MariaDB 10.6 or newer, a memory limit of 256 MB or more and HTTPS. The old PHP 7.4 and MySQL 5.6 still work but no longer receive security fixes.

### Does a shop need a paid SSL certificate?

No. A free Let's Encrypt certificate encrypts the connection just as reliably, and the hosting renews it automatically. A paid certificate with organisation validation is needed only if a partner or the company's internal rules require it.

### Can I accept card payments on shared hosting?

Yes, if the card is entered on the payment provider's page or in its widget and the shop receives only the payment status. Storing and processing card numbers on shared hosting is not a good idea.

### When does an online shop need a VPS instead of hosting?

When errors 508 and 503 appear on ordinary days, the catalog is large and pages are slow, imports do not fit within the limits, or you need Redis, search and queues. A VPS with 2–4 vCPU and 4–8 GB of memory is usually enough.

_Updated: 2026-11-07_

# A database on a VPS: PostgreSQL or MySQL

A database is almost never limited by the processor; memory and disk are what hold it back. If the working set fits in the cache, queries are fast even on an inexpensive server; if it does not, disk speed decides everything. Here is how to choose between PostgreSQL and MySQL, how much memory to give the database, which disk to pick and how to avoid losing data.

> Source: https://accsly.io/en/vps/guide/databases-on-vps-postgresql-mysql · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

For most websites and applications the choice of database has already been made for you: WordPress, 1C-Bitrix and most PHP engines are built for MySQL, while many Django, Rails and Go projects use PostgreSQL by default. If you are free to choose, either database will handle a typical load, and the difference comes down to what you find easier to maintain and what your stack supports.

## PostgreSQL or MySQL

- **MySQL and MariaDB** are the standard for PHP-based CMSs and online shops. Every control panel and every shared hosting plan supports them, there are more ready-made guides for them, and moving a site from shared hosting to a VPS usually comes down to a dump and an import.
- **PostgreSQL** is the choice for applications with complex queries, reports and strict data integrity. It has richer data types (JSONB, arrays, ranges) and supports extensions such as PostGIS for geodata and pgvector for vector search.

If the project is new and the engine does not dictate the database, pick the one your team knows: on a server with 4–8 GB of memory, the speed difference between them is smaller than the difference between a well-tuned and a poorly tuned database. Switching databases on a live project is expensive, so this decision is made once.

## How much memory to give the database

Both databases keep frequently used data in their own cache, and its size is the most important setting after installation. The default is small, 128 MB in both, so without tuning a database on a server with 8 GB of memory barely uses it.

- **PostgreSQL**: according to the [documentation](https://www.postgresql.org/docs/current/runtime-config-resource.html), on a dedicated database server with 1 GB of memory or more, a reasonable starting value for `shared_buffers` is 25% of memory. Allocating more than 40% is unlikely to help, because PostgreSQL also relies on the operating system's file cache.
- **MySQL (InnoDB)**: according to the [MySQL 8.4 documentation](https://dev.mysql.com/doc/refman/8.4/en/innodb-buffer-pool.html), on dedicated servers up to 80% of physical memory is often given to the buffer pool, `innodb_buffer_pool_size`.

The key word in both cases is "dedicated". If the same VPS also runs a web server, PHP-FPM, Redis and queues, less is left for the database: on a 4 GB server that also hosts the site, it makes sense to give the MySQL buffer pool 1–1.5 GB rather than 3. The rest is needed by the application processes and as headroom; otherwise the server starts swapping and the database becomes slower than it would be with a small cache.

The yardstick for server size is the volume of "hot" data: the tables and indexes that are accessed all the time. If they fit entirely in the cache, most reads never reach the disk. According to the accsly.io catalog as of November 2026, the median price of a VPS with 4 GB of memory is about $22 a month, with 8 GB about $41, with 16 GB about $74 and with 32 GB about $134. The catalog keeps prices in roubles; dollar figures are converted at the catalog rate of 7 November 2026. Choosing memory and cores is covered in more detail in the article [How much RAM and how many cores a website needs](https://accsly.io/en/vps/guide/ram-and-cpu-for-website), and plans with 16 GB of memory or more are listed on the page [VPS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram).

## Disk and IOPS

When the data does not fit in memory, and on every write, the database accesses the disk with small random operations. What matters here is not the capacity or the sequential speed from the plan description but the number of input/output operations per second (IOPS) and latency. This is exactly where NVMe beats SATA SSD, and a hard drive is not suitable for a production database at all: it delivers hundreds of operations per second where an SSD delivers tens of thousands.

According to the accsly.io catalog as of November 2026, NVMe is listed in 41% of 29,603 VPS plans, and its share is higher among larger plans: 38% of plans with 2 GB of memory and 45% of plans with 32 GB. Disk types are compared in the article [NVMe or SSD: does it matter for a website](https://accsly.io/en/vps/guide/nvme-or-ssd), and plans are collected in [NVMe VPS](https://accsly.io/en/vps/nvme).

The figures in a VPS plan description are an upper limit: the disk is shared with neighbours on the physical server, and many hosts cap IOPS per virtual machine. Measure the real speed after purchase, while you can still return the server, with the [fio](https://fio.readthedocs.io/en/latest/fio_doc.html) utility, using a random read and write test with 4–16 KB blocks. How to do this during a trial period is explained in the article [How to test VPS ping and speed before you pay](https://accsly.io/en/vps/guide/check-vps-speed-before-buying).

## Backups and replicas

A disk snapshot at the host is a convenient but not the most reliable copy of a database: a snapshot taken during a write may need crash recovery, and it is usually stored at the same host. For a database, make your own copies with the database's tools:

- **A logical dump** with `pg_dump` for PostgreSQL or `mysqldump` for MySQL. For InnoDB tables, take the dump with the `--single-transaction` option; then, as the [mysqldump documentation](https://dev.mysql.com/doc/refman/8.4/en/mysqldump.html) states, it is consistent without locking tables. This suits databases of up to tens of gigabytes; restoring a large database from a dump can take hours.
- **Point-in-time recovery**: a full copy of the database files plus a continuous archive of the change log. In PostgreSQL this is [WAL archiving](https://www.postgresql.org/docs/current/continuous-archiving.html), in MySQL the binary log. This lets you roll back to the minute before an erroneous `DELETE` rather than to last night.

Keep the copies outside the database server, in object storage or on a separate VPS in another data centre, and test them regularly by restoring. General backup rules are covered in the article [VPS backups: strategies and tools](https://accsly.io/en/vps/guide/vps-backups), and storage options for copies in the article [File storage on a VPS: disks and object storage](https://accsly.io/en/vps/guide/file-storage-on-vps).

A replica is a second copy of the database on another server that receives changes almost immediately: [streaming replication](https://www.postgresql.org/docs/current/warm-standby.html) in PostgreSQL, [replication](https://dev.mysql.com/doc/refman/8.4/en/replication.html) in MySQL. It lets you switch over quickly if the primary server fails and take load off it by sending reports to the replica. But it does not replace a backup: an accidentally dropped table disappears from the replica a fraction of a second later.

## A managed database or your own on a VPS

Cloud providers offer managed databases: you get an address to connect to, and the provider takes care of installation, updates, backups and replicas. In [Amazon RDS](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithAutomatedBackups.html), for example, automated backups are kept for up to 35 days with point-in-time recovery.

- **A managed database** pays off when nobody on the team is ready to take responsibility for the database, when you need fault tolerance with automatic failover, or when downtime costs more than the markup. The downsides: the same memory and disk cost noticeably more than on a VPS, some settings and extensions are unavailable, and moving to another provider is harder.
- **Your own database on a VPS** is cheaper and gives you full control over the version, settings and extensions. In return, updates, backups, disk space monitoring and restore testing are your job. The difference between the two approaches is covered in the article [Cloud server or VPS](https://accsly.io/en/vps/guide/cloud-or-vps).

A common compromise for a small project is a database on the same VPS as the site, with a daily dump and a log archive sent to separate storage. When the database grows to several gigabytes of hot data or starts getting in the way of the application, it is moved to a separate server with NVMe, and the database port is closed to the internet, leaving access only from the application's addresses. Plans for such a server are collected on the pages [VPS for PostgreSQL](https://accsly.io/en/vps/for-postgresql), [VPS for MySQL](https://accsly.io/en/vps/for-mysql) and [VPS for databases](https://accsly.io/en/vps/for-database). Add disk space and query latency to [monitoring](https://accsly.io/en/vps/guide/server-monitoring-uptime-alerts) right away: a full disk is the most common reason a database stops.

## FAQ

### Which is faster on a VPS, PostgreSQL or MySQL?

Under a typical website load, the difference between them is smaller than between a tuned and an untuned database. Cache size, disk and indexes matter more. Choose the database your engine supports and your team knows.

### How much memory should I give shared_buffers in PostgreSQL?

The PostgreSQL documentation advises starting with 25% of memory on a server dedicated to the database and not going above 40%. If the site runs on the same server, lower the share so the application has enough memory.

### What should innodb_buffer_pool_size be set to?

On a server used only for MySQL, up to 80% of memory is often given to the buffer pool, as the MySQL 8.4 documentation states. On a server shared with the site, give it noticeably less, for example 1–1.5 GB out of 4 GB.

### Is an HDD suitable for a database?

Not for a production database: a hard drive performs hundreds of random operations per second, while SSD and NVMe perform tens of thousands. An HDD is fine for storing dumps and archives.

### Does a replica replace a backup?

No. A replica repeats every change, including an accidental deletion of data. It is there for fast failover if the server goes down; only backups with history protect you from mistakes.

### When is a managed database better than a VPS?

When nobody can take responsibility for updates, backups and fault tolerance, or when downtime costs more than the provider's markup. If your team can maintain the database itself, a VPS will be cheaper and give you full control over the settings.

_Updated: 2026-11-07_

# File storage on a VPS: disks and object storage

A project's files, such as user uploads, product photos, videos, documents and archives, grow faster than the database and the code. You can keep them on the server's disk, on a separate volume or in object storage, and the choice determines the price per terabyte, the speed and what happens to the files when you change servers. Here are the options and prices according to the accsly.io catalog.

> Source: https://accsly.io/en/vps/guide/file-storage-on-vps · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

While a site is small, its files sit in a folder next to the code, and that is fine. Problems start as it grows: the disk runs out, a plan with a bigger disk drags along cores and memory you do not need, a full server backup takes hours, and a move means copying hundreds of gigabytes together with the site. That is why it pays to keep files separate from the system from the very start and to know where you can move them.

## The local VPS disk: NVMe, SSD and HDD

The disk included in the plan is the fastest and simplest place for files. Its drawback is that its size is tied to the plan: to get more space, you have to take a plan with resources you do not need.

- **NVMe and SSD** are needed for the system, the database and files that are read all the time: thumbnails, static assets and cache. According to the accsly.io catalog as of November 2026, a VPS plan with an NVMe disk of about 1 TB costs a median of about $200 a month, and with SSD about $206: such disks come bundled with large amounts of memory and many cores. The catalog keeps prices in roubles; dollar figures are converted at the catalog rate of 7 November 2026. Disk types are compared in the article [NVMe or SSD: does it matter for a website](https://accsly.io/en/vps/guide/nvme-or-ssd).
- **HDD** is cheap capacity for archives, backups, videos and rarely opened documents. Plans with hard drives are rare: 830 of the 29,603 VPS plans in the catalog, under 3%, from 172 hosts. On the other hand, a plan with an HDD of about 1 TB costs a median of $13.5 a month, and among plans with 500 GB or more the median price per terabyte is $11 a month, with the cheapest tenth at $4 or less. Collections: [Storage VPS with a large disk](https://accsly.io/en/vps/storage) and [VPS with HDD](https://accsly.io/en/vps/hdd).

If you need more than ten terabytes, a dedicated server with several disks is better value: the catalog has 800 configurations with 4 TB or more of HDD from 47 hosts, with a median price per terabyte of $35 a month, but that price includes a whole physical server with its processor and memory. These servers are collected on the page [Dedicated servers for data storage](https://accsly.io/en/dedicated/storage). Their disks are combined into RAID so that the failure of one does not mean data loss, but RAID protects against a broken disk; it is not a backup.

## Attachable volumes

Many cloud hosts sell additional disks called volumes (block storage), which attach to a VPS as one more disk and are billed per gigabyte separately from the plan. This is convenient when you need space but not cores and memory: you enlarge the volume without changing the server, and when you move to a new VPS you detach it from the old one and attach it to the new one in the same data centre.

What to check before buying:

- the speed and IOPS limit of the volume, which for network disks are often lower than for a local NVMe;
- whether the volume can be attached to a server in another data centre (usually not, a volume lives in a single zone);
- whether volume snapshots are included in the price and where they are stored;
- how the volume is mounted at boot: in `/etc/fstab` it is specified by UUID with the `nofail` option, which, as described in the [fstab manual](https://man7.org/linux/man-pages/man5/fstab.5.html), keeps the boot from stopping if the device is not found.

## S3 object storage

Object storage works differently from a disk: files (objects) live in containers (buckets) and are uploaded and read over HTTP through an API. The [Amazon S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html) interface has become the standard, and many hosts and clouds offer S3-compatible storage that works with the same libraries and programs; [rclone](https://rclone.org/s3/), for example, supports dozens of such providers.

- **Pros:** capacity is unlimited and you pay for what you use, files are not tied to a server and survive its deletion, and they can be served to visitors directly or through a CDN without loading the VPS. The storage keeps several copies by itself: for Amazon S3 storage classes, according to the [AWS description](https://aws.amazon.com/s3/storage-classes/), the designed durability is 99.999999999% over a year. S3-compatible storage from other providers has its own durability figures; check them in their documentation.
- **Cons:** you cannot open a file and append to it as on a disk, and the application has to be able to work with the API (WordPress, Laravel and Nextcloud have plugins and drivers for this). Besides gigabytes, you pay for requests and outbound traffic, as the [S3 pricing](https://aws.amazon.com/s3/pricing/) shows, and for a site that serves a lot of files the traffic can cost more than the storage itself.

The accsly.io catalog has no object storage prices, so compare providers on three lines of their price list: gigabytes per month, requests and outbound traffic. To serve images and videos to visitors, storage is usually placed behind a CDN; see the article [CDN: when a website needs one](https://accsly.io/en/vps/guide/cdn-for-website).

## What goes where

- the system, code and database go on the server's local NVMe or SSD; databases are covered in the article [A database on a VPS: PostgreSQL or MySQL](https://accsly.io/en/vps/guide/databases-on-vps-postgresql-mysql);
- user uploads and media that grow without limit go to object storage or a separate volume;
- archives, backups and videos that are rarely opened go to an HDD server or a cold storage class of object storage;
- a shared folder for the team goes on a VPS with Nextcloud and a large disk; plans are on the page [VPS for Nextcloud](https://accsly.io/en/vps/for-nextcloud).

Even if everything sits on one disk for now, keep uploads in a separate directory and put its path in the application settings, not in the code. Then moving the files to a volume or to storage comes down to copying them and changing one setting. Add free disk space to [monitoring](https://accsly.io/en/vps/guide/server-monitoring-uptime-alerts) with an alert at 80%: a full disk stops both the database and log writing, and not every host lets you upgrade the plan or attach a volume in five minutes.

## Backing up files

Wherever the files are, their copy must be somewhere else. The classic 3-2-1 rule, cited for example by the [US agency CISA](https://www.cisa.gov/sites/default/files/publications/data_backup_options.pdf), means three copies of the data, on two different media, with one off site. For a VPS, this means that a copy on the same server, or at the same host in the same data centre, is not a backup in case of an account suspension or a fire.

Hosts often offer their own backups, but read the terms carefully: in the accsly.io catalog, 1,644 of 2,248 VPS hosts describe backups, and quite often copies are made only for shared hosting, cost extra or work on a "best effort" basis. Your own copies are more reliable:

- programs such as [restic](https://restic.readthedocs.io/) make encrypted, deduplicated copies, where each subsequent copy transfers only the changes, and can write straight to S3-compatible storage;
- in object storage, turn on [versioning](https://docs.aws.amazon.com/AmazonS3/latest/userguide/Versioning.html), so an overwritten or deleted object can be recovered from an older version;
- once a month, restore a copy to a test server; that is the only way to know it works.

Schedules, storage and testing of copies are covered in more detail in the article [VPS backups: strategies and tools](https://accsly.io/en/vps/guide/vps-backups), and plans with a large, cheap disk for copies are on the page [VPS for backups](https://accsly.io/en/vps/for-backups).

## FAQ

### How much does a terabyte cost on a VPS?

It depends on the disk. According to the accsly.io catalog as of November 2026, among HDD plans with 500 GB or more the median price per terabyte is about $11 a month, while a plan with about 1 TB of NVMe costs a median of about $200, because such a disk comes with plenty of memory and processor power.

### Which is better for a website's files, the VPS disk or S3?

For a small site, the server's disk is enough. When uploads grow without limit or files are served to a large number of visitors, they are moved to S3-compatible storage: capacity is unlimited, and you can change servers without moving the files.

### How does an attachable volume differ from the plan's disk?

A volume is billed separately per gigabyte, and it can be enlarged without changing the plan or reattached to another server in the same data centre. It is often slower than a local NVMe, so databases are kept on the plan's disk.

### Is an HDD suitable for storing files?

For archives, backups and videos that are read sequentially and infrequently, yes: it is the cheapest terabyte. For a database and thousands of small files that are opened all the time, an HDD is too slow.

### Does RAID replace a backup?

No. RAID protects against the failure of one disk, but a file deleted by mistake or encrypted disappears from every disk in the array at once. You need a separate copy somewhere else.

### What do you pay for in object storage besides gigabytes?

Read and write requests and outbound traffic are usually billed separately. If files are downloaded a lot, the traffic can cost more than the storage, which is why files are served through a CDN.

_Updated: 2026-11-07_

# How to leave a host without losing anything

People leave hosts for all sorts of reasons: prices went up, the server got slow, support stopped answering, or you need a different country. During a move you can lose data, emails, your domain and the money for months already paid. Here is an order of steps in which the old and new servers run side by side for a while, so that switching off the old one breaks nothing.

> Source: https://accsly.io/en/vps/guide/moving-away-from-a-hoster · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

The main rule of any move is not to switch off the old setup until the new one has been checked. So the plan goes like this: first an inventory and copies, then the new server and testing, then the DNS switch, and only after a quiet period cancelling the old service and transferring the domain.

## Inventory: what you have at the host

A host usually holds more of your things than it seems. Before the move, make a list:

- websites and applications, their files, databases and cron jobs;
- mailboxes, forwarding rules and autoresponders, if your mail is with the same host;
- the DNS zone: every record, including TXT records for verifying services, SPF, DKIM and subdomain records;
- domains registered through the host and their renewal dates;
- SSL certificates, if they are paid and were issued through the host;
- additional IP addresses, backups, storage and add-on services that renew automatically.

Export the DNS zone in full, from the panel or by hand into a spreadsheet. A lost TXT record that verified your domain with a mail or payment service tends to surface a week later, when something stops working.

## Exporting data and backups

Make a fresh full copy with your own tools rather than relying on the host's backups: once the account is closed, they will no longer be available. Copy files with `rsync` or as an archive, databases as a dump (`mysqldump`, `pg_dump`) and mail over IMAP. Keep the copy outside both the old and the new server, for example in object storage; the options are covered in the article [File storage on a VPS: disks and object storage](https://accsly.io/en/vps/guide/file-storage-on-vps), and checking copies in the article [VPS backups: strategies and tools](https://accsly.io/en/vps/guide/vps-backups).

If you might lose access to the panel, for example because the host is shutting down or the account has been suspended for non-payment, export the data first, before any negotiations. Test the copy by restoring it on the new server: an archive that will not open is usually discovered only after the old server has been switched off.

## Running both servers in parallel

Rent the new server in advance, deploy the site on it from the copy and test it at a temporary address or through the `hosts` file on your own computer. Meanwhile the old server keeps running. Allow at least a week for the parallel period: during that time SSL certificates get issued, and forgotten cron jobs and integrations show up.

Paying for two servers costs less if you can first take the new one for a short term. According to the accsly.io catalog as of November 2026, 173 hosts explicitly state hourly billing, and 818 of 2,248 VPS hosts, or 36%, offer a money-back guarantee, most often for 30 days. Collections: [VPS with hourly billing](https://accsly.io/en/vps/hourly-billing) and [VPS with a money-back guarantee](https://accsly.io/en/vps/moneyback). The step-by-step process of moving a site is described in the article [How to move a website from shared hosting to a VPS](https://accsly.io/en/vps/guide/move-site-hosting-to-vps).

## Lowering the TTL and switching DNS

Every DNS record has a TTL, the time in seconds for which ISP resolvers may cache its value, as defined back in [RFC 1035](https://www.rfc-editor.org/rfc/rfc1035). If the TTL is a day, some visitors will keep reaching the old server for a whole day after the IP address changes.

- One or two periods of the old TTL before the move, lower the TTL of the A, AAAA and MX records to 300 seconds. If the TTL was 86,400 seconds, do this at least two days ahead.
- Right before the switch, synchronise the data once more: files uploaded by users and new orders in the database. Shops turn on maintenance mode for this time.
- Change the addresses in the records. Thanks to the short TTL, most visitors will reach the new server within a few minutes.
- After a few quiet days, set the TTL back to an hour or a day.

If the DNS zone is served by the old host's name servers, first move it to your registrar or to a separate DNS service with the same records, and only then change the domain's name servers. How records and name servers work is explained in the article [Domains and DNS for a server owner](https://accsly.io/en/vps/guide/domains-and-dns).

## Transferring the domain to another registrar

You can keep the domain at its current registrar and change only the DNS; that is the simplest path. A transfer makes sense if the registrar is the very host you are leaving. For gTLD domains (.com, .net, .org and others), the rules are set by the [ICANN Transfer Policy](https://www.icann.org/en/contracted-parties/accredited-registrars/resources/domain-name-transfers/policy):

- at the owner's request, the registrar must provide the transfer code (AuthInfo, also called the EPP code) and remove the transfer prohibition (ClientTransferProhibited, which panels call the registrar lock) within 5 calendar days;
- a transfer may be denied within the first 60 days after the domain was registered or after a previous transfer, and after a change of registrant the registrar applies a 60-day lock, which the owner can opt out of in advance;
- the code is entered at the new registrar, and you pay for a one-year renewal; unless the old registrar objects, the registry completes the transfer within 5 days.

Country-code domains (.de, .uk, .ru and others) follow the rules of their own registry, and the procedure for changing registrar differs from the ICANN one; for .ru, for example, the rules are published on the [registry's documents page](https://cctld.ru/domains/docs/). Do not transfer the domain in the same days as the server, and do not start a transfer a few days before the registration expires: if something goes wrong, the domain must not end up expired.

## Moving mail

Mail is the most fragile part of a move. Create the mailboxes at the new mail provider or on your own server, then copy the messages from the old mailboxes over IMAP, for example with [imapsync](https://imapsync.lamiral.info/), which transfers folders and, when run again, fetches only what is new. Then change the MX, SPF and DKIM records to the new provider's values, and a day later run the synchronisation again to pick up messages that arrived at the old server while DNS was updating. If you are setting up mail on your own VPS, the requirements are described in the article [Mail server on a VPS: SPF, DKIM, DMARC](https://accsly.io/en/vps/guide/mail-server-on-vps-spf-dkim-dmarc).

## Cancelling the service and getting a refund

Cancel the old service only when traffic and mail have stopped arriving at the old server and the copy has been checked. Before that, turn off auto-renewal and remove the saved card so you are not charged for the next period, and ask for written confirmation that the account is closed.

Whether you can get back the unused part of your payment depends on the host's terms: some hosts refund the unused months, sometimes minus the discount for a long term, while others refund only during the guarantee period. Beyond the terms, your rights depend on the law of the host's country and on the consumer protection rules where you live; consumers in the EU, for example, should check what the contract and the law of their country provide, and business customers usually rely on the contract alone. Guarantees are covered in more detail in the article [Free trials and money-back guarantees](https://accsly.io/en/vps/guide/trial-and-money-back), and contracts with a host abroad in the article [Hosting provider jurisdiction: what it affects](https://accsly.io/en/vps/guide/hoster-jurisdiction).

## FAQ

### How many days before the move should I lower the TTL?

At least one period of the current TTL before, preferably two. If the TTL was a day, lower it to 300 seconds at least two days before changing the address.

### Is the registrar required to give me the domain transfer code?

For .com, .net, .org and other gTLD domains, yes: under ICANN rules, the registrar must provide the code and remove the transfer prohibition within 5 calendar days of the owner's request. A transfer may be denied within the first 60 days after registration or a previous transfer.

### Do I need to transfer the domain along with the hosting?

No. You can keep the domain at its current registrar and change only the DNS records. A transfer makes sense if the registrar was the same host you are leaving.

### How do I avoid losing emails when changing mail servers?

Copy the mailboxes over IMAP before changing the MX records, switch the records and repeat the synchronisation a day later to pick up messages that arrived at the old server. Keep the old mailboxes for a few more days.

### Will the host refund the months I have already paid for?

It depends on the terms: some hosts refund the remaining balance, others return money only during the guarantee period. Your statutory rights depend on the law of the host's country and on consumer protection rules where you live, so check the contract and, as a private customer, your local consumer rules.

### How long should I keep the old server after the move?

At least a week after switching DNS: during that time forgotten jobs, integrations and emails will show up. Cancel the service once requests to the old server have stopped and the data copy has been verified by restoring it.

_Updated: 2026-11-07_

# CI/CD on your own VPS

A dedicated build server pays off when hosted CI minutes run out, builds are slow or jobs need access to internal resources. But a runner executes any code in the repository, so a mistake in its setup exposes the production server and every secret. Here is how GitLab and GitHub runners work, what resources they need, how to deploy over SSH and where to keep the keys.

> Source: https://accsly.io/en/vps/guide/ci-cd-on-vps · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

CI/CD means building, testing and releasing code automatically after every change. The pipeline is described in the repository (`.gitlab-ci.yml` or files in `.github/workflows/`) and executed by a runner, a program that picks up jobs from GitLab or GitHub and runs them. You can use the service's runners or install one on your own VPS.

## Self-hosted runners: GitLab and GitHub

**GitLab Runner** is installed from the official repository ([installation guide](https://docs.gitlab.com/runner/install/)) and registered with a project or group using a token from the CI/CD settings. The main choice at registration is the executor. `shell` runs commands directly on the server's system, while `docker` runs each job in a fresh container. According to the [GitLab documentation](https://docs.gitlab.com/runner/executors/), the shell executor gives no clean environment per build, and jobs can see the whole file system, including the runner token and other projects' caches. The docker executor suits most projects.

**A self-hosted GitHub Actions runner** is added in the repository or organisation settings ([GitHub documentation](https://docs.github.com/en/actions/concepts/runners/self-hosted-runners)). Using it is free; you pay only for the server. The runner connects to GitHub itself over HTTPS on port 443, so you do not need to open any inbound ports. If a runner has not been updated for 30 days, GitHub stops sending it jobs ([self-hosted runners reference](https://docs.github.com/en/actions/reference/runners/self-hosted-runners)).

An important limitation for open-source projects. GitHub states that self-hosted runners should [almost never be used with public repositories](https://docs.github.com/en/actions/reference/security/secure-use): anyone can open a pull request and run their own code on your server. Keep hosted runners for public code and connect your own server to private repositories.

## Why builds and production need separate servers

- **Load.** A frontend build or a compilation occupies every core for minutes. If the runner lives on the site's server, the site responds more slowly while it runs.
- **Security.** A runner executes code from any branch, including a branch pushed by a contractor. According to the [GitLab documentation](https://docs.gitlab.com/runner/security/), the shell executor carries a high risk for the server and the network, and a container in privileged mode gives the job full root on the host. If a site with a customer database runs on the same server, every job can reach that database.
- **Disk space.** Docker images, dependency caches and artifacts take tens of gigabytes. When the disk fills up, not only the build stops but the site as well.

A setup for a small team: one VPS for the runner, another for the production site and, if needed, a third for a staging environment (see the article [VPS for developers: staging environments](https://accsly.io/en/vps/guide/vps-for-developers-staging)). The runner delivers only the finished build to the production server.

## How many resources a build needs

GitHub's hosted runners are a good yardstick. According to its [reference](https://docs.github.com/en/actions/reference/runners/github-hosted-runners), the standard Linux runner for private repositories has 2 cores, 8 GB of memory and a 14 GB SSD, and the one for public repositories has 4 cores and 16 GB. If your builds fit within these resources, a VPS of the same size will do no worse, and with a fast disk and a persistent cache it is usually faster.

- **Cores.** A build with parallel compilation and tests uses every core. If builds run one after another, 4 cores shorten the queue noticeably compared with two.
- **Memory.** A frontend build, Java or Go compilation and tests with a database in a container need 4–8 GB per job. The number of simultaneous jobs is set by the `concurrent` parameter in GitLab Runner's `config.toml` ([parameter reference](https://docs.gitlab.com/runner/configuration/advanced-configuration/)); multiply the memory of one job by that number.
- **Disk.** Installing dependencies means thousands of small files, which is faster on NVMe. Take at least 50 GB and clean the Docker cache on a schedule with `docker builder prune` and `docker image prune`. Why the disk matters is explained in the article [NVMe or SSD: does it matter for a website](https://accsly.io/en/vps/guide/nvme-or-ssd).
- **Virtualization.** The docker executor needs KVM: on OpenVZ, Docker works with limitations or not at all ([KVM or OpenVZ: which to choose](https://accsly.io/en/vps/guide/kvm-or-openvz)).

According to the accsly.io catalog as of November 2026, a VPS plan with 2 cores and 4 GB of memory costs a median of about $21 a month, and a quarter of such plans are cheaper than $12.5. With 4 cores and 8 GB the median is $40, with a quarter below $22. With 8 cores and 16 GB it is $80. The catalog keeps prices in roubles; dollar figures are converted at the catalog rate of 7 November 2026. Suitable plans are collected in [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci) and, if you also host GitLab itself, [VPS for GitLab](https://accsly.io/en/vps/for-gitlab).

## A build server billed by the hour

A runner is needed only while builds are running, usually a few hours of a working day. According to the accsly.io catalog as of November 2026, 173 of 2,248 hosts with VPS plans offer hourly billing, 298 offer an API for creating and deleting servers, and 96 offer both. A plan with 4 cores and 8 GB at hosts with hourly billing costs a median of $51 a month, about $0.07 an hour. A server that runs 3 hours on each of 22 working days costs about $4.6 instead of the monthly price.

To make this work without manual steps, the server is created through the API before a build and deleted afterwards. GitLab Runner can autoscale this way with cloud plugins, and GitHub [recommends](https://docs.github.com/en/actions/reference/runners/self-hosted-runners) ephemeral runners that take one job and are then removed. A bonus for security: the next job sees no traces of the previous one. When hourly billing beats monthly is explained in the article [Hourly billing: when it pays off](https://accsly.io/en/vps/guide/hourly-billing-when-worth-it); plans are collected in [VPS with hourly billing](https://accsly.io/en/vps/hourly-billing) and [VPS with an API](https://accsly.io/en/vps/api).

## Deploying over SSH with a restricted key

The simplest way to deliver a build to the production server is SSH: `rsync` the files or run a command that fetches the new version and restarts the service. To keep the CI key from becoming a key to the whole server:

1. **A separate user.** Create a `deploy` user without sudo and with rights only to the site's directory. If a service needs restarting, allow that one specific command in sudoers.
2. **A separate key.** Generate a key pair for CI only and do not use it anywhere else.
3. **Restrictions in authorized_keys.** Put `restrict` before the key, which disables port forwarding and the terminal, and `from="runner address"` so the key works only from the build server. The `command="…"` option lets the key run only one deploy script ([man authorized_keys](https://manpages.debian.org/bookworm/openssh-server/authorized_keys.5.en.html)).
4. **Server verification.** Store the production server's host key fingerprint in a CI variable and write it to `known_hosts` before connecting. Never turn verification off with `StrictHostKeyChecking=no`: the runner would then connect to any server that pretends to be yours.

To keep the site running during a deployment, start the new version next to the old one and switch traffic once it passes a health check; the previous version stays in place for a rollback. How to set this up on a single server is covered in [Updating a server without downtime](https://accsly.io/en/vps/guide/zero-downtime-updates).

Basic protection of the production server itself, with key-only login, a firewall and fail2ban, is described in the article [First 10 steps after buying a VPS: security](https://accsly.io/en/vps/guide/vps-security-first-steps). Login records for the deploy key help you find out what happened if something goes wrong; where to find them is covered in the article [Server logs and login auditing](https://accsly.io/en/vps/guide/server-logs-and-access-audit).

## Where to keep secrets

- **Not in the repository.** Database passwords, API tokens and deploy keys are stored in CI variables. In GitLab a variable can be protected, so it is available only to pipelines on protected branches and tags, and masked, so its value is replaced with `[MASKED]` in the job log. A masked value must be a single line without spaces and at least 8 characters long ([GitLab documentation](https://docs.gitlab.com/ci/variables/)).
- **One value per secret.** GitHub warns that a secret stored as JSON or YAML is harder to redact from logs; store each value separately and never print secrets to the build log.
- **Different secrets for staging and production.** The production deploy key should be available only to a protected branch, not to any developer's branch.
- **Short-lived tokens instead of permanent ones.** For cloud services GitHub recommends OpenID Connect: the job receives a token for the duration of the build, and you do not have to store a permanent key.
- **Rotation.** Change keys when someone with access to the CI settings leaves the team and after any leak of a build log.

The `.env` file with the production settings is created on the server once, with permissions 600, and the deployment never overwrites it. Then even a full copy of the repository contains no passwords to the production database.

## FAQ

### How much does a self-hosted GitHub Actions runner cost?

GitHub does not charge for self-hosted runners; you pay only for the server. According to the accsly.io catalog as of November 2026, a VPS with 2 cores and 4 GB of memory costs a median of about $21 a month, and one with 4 cores and 8 GB about $40.

### Can the runner go on the same server as the website?

Technically yes, but it is a bad idea: builds take cores away from the site and fill the disk, and a job with malicious code gets access to the database and secrets. Keep the runner on a separate VPS.

### Which GitLab Runner executor should I choose?

For most projects, docker: every job gets a clean container. The shell executor runs commands directly on the system, and jobs can see the runner token and other projects' files. Enable privileged mode only on an isolated server.

### How many resources does a build server need?

A good yardstick is GitHub's hosted runner for private repositories: 2 cores and 8 GB of memory. For several simultaneous jobs, multiply the memory by their number, take at least 50 GB of NVMe disk and clean the Docker cache.

### How do I deploy from CI over SSH safely?

Use a separate user without sudo, a separate CI-only key with the restrict and from= options in authorized_keys, and verify the server's host key through known_hosts. Keep the key in a protected CI variable.

### Does hourly billing pay off for a build server?

Yes, if the server is created through the API before builds and deleted afterwards. A server with 4 cores and 8 GB that runs 3 hours each working day costs about $4.6 a month instead of $51 for round-the-clock use.

_Updated: 2026-11-07_

# Server logs and login auditing

Logs answer three questions: what broke, who logged in to the server and what they did there. You only get an answer if logging is enabled, the logs are kept long enough and they are not stored only on the server that may have been compromised. Here is where to find logs on Linux, which commands show logins, how to set up rotation and what to do in advance so that there is something to investigate after an incident.

> Source: https://accsly.io/en/vps/guide/server-logs-and-access-audit · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

On a Linux system with systemd, two services write logs. **journald**, part of systemd, collects messages from all services, the kernel and logins into a binary journal. **rsyslog**, if installed, sorts the same messages into text files under `/var/log`. The web server, the database and Docker keep their own logs. You need to know where everything is before an incident, not during one.

## Where the logs are

- **journald.** Read it with `journalctl`. The journal is kept on disk if the `/var/log/journal` directory exists; otherwise it is kept only in memory and lost on reboot ([journald.conf](https://www.freedesktop.org/software/systemd/man/latest/journald.conf.html), the `Storage=auto` setting). Check this on a new server with `ls /var/log/journal`. If the directory is missing, create it and restart the service: `systemctl restart systemd-journald`.
- **System files.** On Ubuntu, logins and sudo are written to `/var/log/auth.log` and general messages to `/var/log/syslog`. On AlmaLinux and Rocky Linux these are `/var/log/secure` and `/var/log/messages`. Debian 12 and later do not install rsyslog by default, so everything is only in journald.
- **The web server.** nginx writes to `/var/log/nginx/access.log` and `error.log`; Apache writes to `/var/log/apache2/` on Debian and Ubuntu or `/var/log/httpd/` on AlmaLinux. The access log records every request: address, time, path, response code, size and browser. The set of fields is defined by the [log_format](https://nginx.org/en/docs/http/ngx_http_log_module.html) directive. If the site sits behind a CDN, configure the server to pass on the visitor's real address, or the log will contain only CDN addresses (more in the article [CDN: when a website needs one](https://accsly.io/en/vps/guide/cdn-for-website)).
- **Applications and Docker.** Databases write to their own directories under `/var/log`, and containers write to Docker's files, which you read with `docker logs`.

A few [journalctl](https://www.freedesktop.org/software/systemd/man/latest/journalctl.html) commands cover most cases: `journalctl -u nginx --since "1 hour ago"` shows one service's messages for the last hour; `journalctl -p err -b` shows errors since the last boot; `journalctl -f` follows new messages; `journalctl --disk-usage` shows how much space the journal takes.

## Who logged in to the server

Every SSH login leaves a record with the user name, the address and the authentication method, key or password. To see successful logins:

- in journald: `journalctl -u ssh --since today | grep Accepted` (on AlmaLinux the service is called `sshd`);
- in a file: `grep Accepted /var/log/auth.log` or `/var/log/secure`;
- as a summary: `last` shows logins and reboots, `lastb` shows failed attempts.

Debian 13 no longer ships `last`, `lastb` and `lastlog`: their old file formats cannot store dates after 2038. The wtmpdb and lastlog2 packages replace them ([Debian 13 release notes](https://www.debian.org/releases/trixie/release-notes/issues.en.html)). The `Accepted` entries in the journal remain in every version.

What to look for. Logins from unfamiliar addresses and at unusual times. Password logins when you have configured key-only access: that means the setting did not take effect. Commands run with sudo: `auth.log` and journald record who ran what. New keys in `~/.ssh/authorized_keys` and new users in `/etc/passwd`: intruders add them to get back in later. If you need a detailed audit of file changes and commands, Linux has the `auditd` audit subsystem, but its rules need separate configuration and disk space.

## fail2ban: what it offers beyond SSH

fail2ban reads logs and temporarily blocks addresses that fail to log in again and again. Installing it and protecting SSH is covered in the article [First 10 steps after buying a VPS: security](https://accsly.io/en/vps/guide/vps-security-first-steps). By default an address is blocked for 10 minutes after 5 failures within 10 minutes ([jail.conf](https://github.com/fail2ban/fail2ban/blob/master/config/jail.conf)). What is worth adding:

- **Long bans for repeat offenders.** The `recidive` jail reads fail2ban's own log and blocks for a week any address that was banned several times within a day. The `bantime.increment = true` setting doubles the ban with each new one.
- **Web server jails.** The ready-made `nginx-http-auth`, `nginx-limit-req` and `nginx-botsearch` jails react to wrong passwords on protected pages, exceeded request rate limits and scanning for non-existent URLs.
- **Your own addresses as exceptions.** The `ignoreip` setting with your office's static address keeps you from locking yourself out.

fail2ban does not protect against distributed attacks from thousands of addresses and does not replace key-based login. Its main value for auditing is a shorter log: what remains are meaningful events rather than tens of thousands of identical password-guessing attempts. `fail2ban-client status sshd` lists the blocked addresses.

## Rotation and disk space

Logs grow all the time, and inexpensive VPS plans have small disks. According to the accsly.io catalog as of November 2026, the median disk on VPS plans with 1 GB of memory is 20 GB, and 9% of VPS plans have a disk of 20 GB or less. The access log of a busy site or a container writing an error in a loop fills such a disk within days, after which the database and the site itself stop working.

- **journald** by default takes no more than 10% of the file system and no more than 4 GB. Set your own limit with `SystemMaxUse=` in `/etc/systemd/journald.conf` and a retention period with `MaxRetentionSec=`, which is off by default. To free space once: `journalctl --vacuum-size=500M` or `--vacuum-time=30d`.
- **Text files** are rotated by [logrotate](https://manpages.debian.org/bookworm/logrotate/logrotate.8.en.html) according to the rules in `/etc/logrotate.d/`. On Ubuntu 24.04, system logs are rotated weekly and 4 old files are kept, which is about a month. The nginx logs from the AlmaLinux 9 package are rotated daily with 10 old files kept. The `rotate`, `daily` or `weekly`, `compress` and `maxsize` options change the retention, compression and size-based rotation. The `copytruncate` mode suits programs that cannot reopen their log file, but according to the documentation it may lose lines. To test a rule without changing anything: `logrotate -d /etc/logrotate.d/nginx`.
- **Docker** by default writes container logs with no size limit ([json-file driver](https://docs.docker.com/engine/logging/drivers/json-file/)). Set `max-size` and `max-file` in `/etc/docker/daemon.json` and recreate the containers: the settings apply only to new ones. More in the article [Docker on a VPS: getting started](https://accsly.io/en/vps/guide/docker-on-vps).

To find what filled the disk, `df -h` shows the full partition and `du -xh /var/log | sort -h | tail` the largest directories. Do not delete a log file that a service keeps open: the space will not be freed until the service restarts. Empty it with `truncate -s 0` instead. It is better to get a warning before the disk fills up; that is covered in the article [Server monitoring: uptime, load, alerts](https://accsly.io/en/vps/guide/server-monitoring-uptime-alerts).

## Keeping logs for incident review

If a server is compromised, the first thing an intruder with root access does is edit or delete the logs. That is why a copy that leaves the server immediately is worth more than any retention settings on the server itself.

1. **Ship logs to another server.** rsyslog can forward messages over the network, and journald has the systemd-journal-upload service for this. The receiving end can be a separate inexpensive VPS with a larger disk or a log collection system such as Loki, Graylog or OpenSearch; suitable plans are collected in [VPS for Elasticsearch](https://accsly.io/en/vps/for-elasticsearch).
2. **Decide how long to keep them.** Most incident reviews need 30–90 days of logs, because a break-in is often discovered well after the day it happened. A week or two on the server itself is enough; the rest belongs on the collection server or in an archive.
3. **Synchronise the clock.** Without accurate time you cannot match events across servers. Run `timedatectl`: the "System clock synchronized" line should say yes.
4. **Do not log more than you need.** Passwords, tokens and full card numbers must never end up in a log. Under the GDPR, IP addresses and user logins are personal data, so the retention period should be stated in your records of processing and your privacy policy; more in the article [GDPR and choosing a host](https://accsly.io/en/vps/guide/gdpr-and-hosting).
5. **In an incident, preserve first, then fix.** Copy the logs and take a disk snapshot at the host before reinstalling the system. How snapshots and backups work is explained in the article [VPS backups: strategies and tools](https://accsly.io/en/vps/guide/vps-backups).

If you need logs not only for investigations but also for alerts, such as a spike in 500 errors or a root login, they are collected together with metrics on a separate monitoring server. Plans for this are collected in [VPS for monitoring](https://accsly.io/en/vps/for-monitoring).

## FAQ

### Where can I see who logged in to the server over SSH?

Run journalctl -u ssh (on AlmaLinux -u sshd) and filter for the word Accepted, or look in /var/log/auth.log, which is /var/log/secure on AlmaLinux. The last command shows a summary of logins; on Debian 13 use wtmpdb.

### Why is there no /var/log/auth.log on Debian 12?

Debian 12 and later do not install rsyslog by default, so all messages, including logins, are kept only in journald. Read them with journalctl, or install rsyslog if you need text files.

### How much space can logs take?

By default journald takes up to 10% of the file system, but no more than 4 GB. Web server and Docker logs without rotation are limited only by the size of the disk, so they need logrotate rules and the max-size and max-file settings.

### Can I simply delete a large log file?

If a service keeps the file open, the space is freed only after the service restarts. It is safer to empty the file with truncate -s 0 and set up rotation so it does not happen again.

### How long should logs be kept?

For incident review, 30–90 days is usually enough, with a week or two on the server itself. Under the GDPR, logs with IP addresses and logins contain personal data, so the retention period should be fixed in your records of processing and privacy policy.

### Does fail2ban protect against break-ins?

It blocks addresses that repeatedly fail to log in and cuts the log down to meaningful events. It does not protect against distributed attacks or a login with a stolen key, so you still need key-only login and updates.

_Updated: 2026-11-07_

# VPS for developers: staging environments

A staging environment exists so that you find the bug before your customers do. It should match the production server in software and configuration, but it can have half the resources and live for just a few days. Here is how to keep staging cheap, how to run several versions on one server and how to make sure a copy of the site does not end up in search results or send emails to real customers.

> Source: https://accsly.io/en/vps/guide/vps-for-developers-staging · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

Development usually involves three environments. On a local machine the developer writes code. In staging, the built version is tested in conditions close to production: the client reviews a new feature, a tester runs through the scenarios, database migrations are checked. The production server serves real users. Some teams add temporary environments for each branch: they are used to demonstrate a single task and deleted after the merge.

## What staging must share with production

- **Software versions.** The same operating system and the same versions of PHP, Node.js, Python, the database and the web server. Bugs that appear only on a different version are the most common surprise at release time.
- **Configuration.** Web server configuration, caching, upload limits, time zone and environment variables, except passwords and keys.
- **Deployment method.** Staging is updated by the same script or pipeline as production. That way you test the deployment itself, not just the code. How to set up such a pipeline is described in the article [CI/CD on your own VPS](https://accsly.io/en/vps/guide/ci-cd-on-vps).

What can differ. Resources: staging with one or two users needs 1–2 cores and 2–4 GB of memory, even if production needs 8 cores. Data volume: an anonymised sample instead of the full database. Load testing on a scaled-down environment is pointless: for that you need a server with the same configuration as production. How to run such a test is covered in [Load testing a website before launch](https://accsly.io/en/vps/guide/load-testing-before-launch).

## Short-lived environments: hourly billing and snapshots

An environment for demonstrating a task or testing an update is needed for a few days. There is no need to pay for a whole month: with hourly billing you are charged while the server exists, and charges stop once it is deleted. According to the accsly.io catalog as of November 2026, 173 of 2,248 hosts with VPS plans offer hourly billing. At these hosts a plan with 1 core and 2 GB of memory costs a median of about $11 a month, roughly $0.015 an hour, so a week of staging costs about $2.6. An environment with 2 cores and 4 GB costs $24 a month, about $0.033 an hour, and three days cost about $2.3. The catalog keeps prices in roubles; dollar figures are converted at the catalog rate of 7 November 2026. The break-even calculation and the pitfalls are covered in the article [Hourly billing: when it pays off](https://accsly.io/en/vps/guide/hourly-billing-when-worth-it), and plans are collected in [VPS with hourly billing](https://accsly.io/en/vps/hourly-billing).

A disk snapshot speeds up creating an environment. Configure a server once, take a snapshot and create new environments from it in minutes. Before deleting an environment you will need again, take a snapshot and then delete the server: storing a snapshot is usually cheaper than a running server, but it is not free. A snapshot at the same host does not replace a backup; the difference is explained in the article [VPS backups: strategies and tools](https://accsly.io/en/vps/guide/vps-backups).

If the host is new to you, a staging environment is a convenient way to test it before moving the production site. According to the accsly.io catalog as of November 2026, 247 hosts offer a free trial; the terms and limitations of such trials are covered in the article [Free trials and money-back guarantees](https://accsly.io/en/vps/guide/trial-and-money-back).

## Several environments on one server with Docker Compose

If you need staging all the time, it is cheaper to keep one larger server and run several versions on it in containers. Docker Compose reads `compose.yaml` and `compose.override.yaml` by default, and with the `-f` flag merges several files in order ([Docker documentation](https://docs.docker.com/compose/how-tos/multiple-compose-files/merge/)). The shared part is described once, while `compose.staging.yaml` holds what differs in staging: other ports, lower memory limits, test variables.

Each environment runs under its own project name: `docker compose -p feature-123 -f compose.yaml -f compose.staging.yaml up -d`. Projects with different names have their own containers, networks and volumes, so the environments do not interfere with each other. From the outside, a single web server or reverse proxy routes traffic to them by subdomain: `feature-123.stage.example.com`. How to prepare a server for Docker and keep images from filling the disk is explained in the article [Docker on a VPS: getting started](https://accsly.io/en/vps/guide/docker-on-vps).

How many resources to take: allow 1–2 GB of memory and 5–10 GB of disk for each environment with a database. A server with 2 cores and 4 GB holds two or three small environments. According to the accsly.io catalog as of November 2026, such a plan costs a median of about $21 a month, with a quarter of plans cheaper than $12.5. A plan with 1 core and 2 GB for a single environment costs $11, with a quarter below $7. Collections: [VPS for a staging environment](https://accsly.io/en/vps/for-testing) and [VPS for Docker](https://accsly.io/en/vps/for-docker).

## Keeping staging out of search engines

A copy of the site in search results means duplicate pages competing with the production site and a leak of whatever has not been published yet. The options, from least to most reliable:

- **robots.txt does not protect you.** Google states plainly that a robots.txt disallow is [not a mechanism for keeping a page out of search](https://developers.google.com/search/docs/crawling-indexing/robots/intro): a URL that others link to can appear in results even if the crawler never visited it.
- **noindex.** The `<meta name="robots" content="noindex">` tag or the `X-Robots-Tag: noindex` header prohibits indexing; the header is easier to add for the whole environment in the web server configuration. Both Google and Bing support it. The crawler has to see this directive, so you must not block the environment in robots.txt at the same time ([Google documentation](https://developers.google.com/search/docs/crawling-indexing/block-indexing)).
- **A password is the most reliable option.** Basic authentication in nginx takes two directives, `auth_basic` and `auth_basic_user_file`, and the password file is created with the `htpasswd` utility ([nginx documentation](https://nginx.org/en/docs/http/ngx_http_auth_basic_module.html)). The `satisfy any` directive lets office addresses in without a password and asks everyone else for one. A crawler will not see a single page.

The environment's name is not a secret. Let's Encrypt [submits every certificate it issues](https://letsencrypt.org/docs/ct-logs/) to public Certificate Transparency logs, which reveal every subdomain a certificate was issued for. A certificate for `*.stage.example.com` hides the names of individual environments but does not replace password protection. How to issue such certificates and set up subdomains is explained in the articles [SSL certificates: free and paid](https://accsly.io/en/vps/guide/ssl-certificates) and [Domains and DNS for a server owner](https://accsly.io/en/vps/guide/domains-and-dns).

## Data and side effects

- **Do not copy the production database as is.** It holds customers' personal data, and staging is less well protected than production. Anonymise names, phone numbers, email addresses and payment details, or build a test data set. Under the GDPR, a copy of customer data on a staging server is still personal data processing with the same obligations; see the article [GDPR and choosing a host](https://accsly.io/en/vps/guide/gdpr-and-hosting).
- **Turn off email and SMS sending.** Staging with a copy of the database can send notifications to real customers. Route outgoing mail to a catch-all test mailbox or disable it.
- **Payments in test mode only.** Payment providers have test keys and test cards; staging has no need for live keys.
- **Check scheduled jobs.** Exports to marketplaces, CRM synchronisation and calls to external APIs from cron on staging should go to test environments or be switched off.
- **Separate keys and passwords.** Contractors and testers get access to staging; no key from staging should open the production server.

## Forgotten environments

A forgotten staging server costs money every month and over time becomes the most vulnerable point: nobody installs updates on it, its passwords are old and a copy of the database stays open to contractors who left long ago. A few rules help prevent this:

- every environment has an owner and a deletion date, recorded in its name or in a label in the host's control panel;
- temporary branch environments are deleted after the merge by the same pipeline that created them;
- a permanent staging server is updated together with production and locked down the same way: key-only login, a firewall, security updates ([First 10 steps after buying a VPS: security](https://accsly.io/en/vps/guide/vps-security-first-steps));
- once a month, compare the list of servers in the host's control panel with the list of environments you actually need and delete the rest.

## FAQ

### How does staging differ from production?

Production serves real users; staging is its copy for testing a new version before release. Staging runs the same software versions and configuration, but with fewer resources and anonymised data.

### How much does a VPS for staging cost?

According to the accsly.io catalog as of November 2026, a plan with 1 core and 2 GB of memory costs a median of about $11 a month, and one with 2 cores and 4 GB about $21. With hourly billing, a week of a small staging environment costs about $2.6.

### Is blocking staging in robots.txt enough?

No. Google states that robots.txt does not remove pages from search: a URL can appear in results through links. The most reliable option is a password with basic authentication; without one, use the X-Robots-Tag: noindex header.

### Can I run several staging environments on one VPS?

Yes, with Docker Compose and different project names: each gets its own containers, networks and volumes. Allow 1–2 GB of memory and 5–10 GB of disk for each environment with a database.

### Can I copy the production database to staging?

Only after anonymising it: staging is less well protected than production, and the database holds customers' personal data. Also turn off email and SMS sending on staging so customers do not receive test notifications.

### Why take a snapshot of a staging server?

A new environment is created from a snapshot in minutes, and the server can be deleted between test rounds so you do not pay for it. Storing a snapshot also costs money, but usually less than a running server.

_Updated: 2026-11-07_

# Linux distributions for a server: Ubuntu, Debian, AlmaLinux

For a server, the choice is most often between three free distributions: Ubuntu, Debian and AlmaLinux. All three are stable and suitable for a website or a bot; they differ in how long they are supported, in their packages and in which panels and programs officially run on them. According to the accsly.io catalog as of November 2026, all three images are offered by 631 of the 1,241 hosts whose template list is known.

> Source: https://accsly.io/en/vps/guide/linux-distros-for-server · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A distribution is chosen for several years at once: upgrading to the next version is possible, but switching to another family essentially means moving to a new server. So the choice comes down not to taste but to three questions: how many years the version will receive security updates, whether the programs and panel you need run on it, and how comfortable you are working with it.

## Support periods

A server without security updates must not stay exposed to the internet, so the end-of-support date is the deadline by which the server has to be upgraded or rebuilt.

- **Ubuntu LTS.** Long-term support releases come out every two years in April. According to [Canonical's schedule](https://ubuntu.com/about/release-cycle), each one gets 5 years of standard security updates, 10 years with an Ubuntu Pro subscription and up to 15 with the Legacy add-on. Standard support for Ubuntu 22.04 ends in May 2027, for 24.04 in May 2029 and for 26.04 in May 2031. Interim releases (such as 25.10) are supported for only 9 months and are not installed on servers.
- **Debian.** A new stable release comes out roughly every two years. For three years it is supported by the Debian security team, and for two more by the [Debian LTS project](https://wiki.debian.org/LTS). Debian 11 stopped receiving updates on 31 August 2026. Debian 12 moved to LTS in June 2026 and is supported until 30 June 2028. Debian 13 was released on 9 August 2025, with [full support until 9 August 2028 and LTS until 30 June 2030](https://www.debian.org/releases/trixie/).
- **AlmaLinux.** A free distribution that is binary-compatible with Red Hat Enterprise Linux, with a 10-year cycle for each major version. According to [the project](https://wiki.almalinux.org/release-notes/), AlmaLinux 8 receives security fixes until 31 May 2029, AlmaLinux 9 until 31 May 2032 and AlmaLinux 10 until 31 May 2035. Rocky Linux is another free RHEL-compatible distribution.

A separate word on CentOS. CentOS Linux 8 stopped receiving updates on 31 December 2021, and [CentOS Linux 7 on 30 June 2024](https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-and-centos-linux-7/). CentOS Stream is not a long-term support replacement but the platform where future RHEL versions are prepared. Hosts keep the CentOS template for legacy projects; a new server should not be built on it, and existing ones are migrated to AlmaLinux or Rocky Linux.

## Upgrading to the next version

When the support period is coming to an end, a server has two options: upgrade in place, or install a new system alongside and move the site to it. Each distribution has its own rules for in-place upgrades.

- **Ubuntu** is upgraded with the `do-release-upgrade` command. According to the [Ubuntu Server documentation](https://documentation.ubuntu.com/server/how-to/software/upgrade-your-release/), an upgrade from one LTS to the next is only offered after the first point release: 24.04 will upgrade to 26.04 once 26.04.1 is out. Third-party repositories and PPAs are disabled during the upgrade, and they are the most common source of problems.
- **Debian** can only be upgraded from the previous version: you move to 13 from 12, and from 11 via 12. The [Debian 13 upgrade guide](https://www.debian.org/releases/trixie/release-notes/upgrading.en.html) recommends a full backup and running the upgrade inside `screen` or `tmux`, so that a dropped SSH connection does not interrupt it halfway.
- **AlmaLinux** has no built-in upgrade path between major versions. That is handled by the separate [ELevate project](https://wiki.almalinux.org/elevate/), which upgrades systems from 8 to 9 and from 9 to 10, and also migrates CentOS 7 to AlmaLinux. On a server with a panel, it is simpler to install the new version alongside and move the sites.

The practical conclusion: when buying a server, take the newest LTS version that your panel and programs support, so that more years pass before the next move.

## Packages and day-to-day work

Ubuntu and Debian belong to the same family: `.deb` packages, the `apt` package manager, the same configuration paths, and almost every guide on the internet works for both. Debian is more conservative: in a stable release, program versions are frozen for the whole support period and only fixes are added. Ubuntu is based on Debian but follows its own schedule and more often ships newer versions. For example, the system Python is [3.12](https://packages.ubuntu.com/noble/python3) in Ubuntu 24.04, [3.11](https://packages.debian.org/bookworm/python3) in Debian 12 and [3.13](https://packages.debian.org/trixie/python3) in Debian 13.

AlmaLinux uses `.rpm` packages and the `dnf` manager; the default firewall is firewalld, and SELinux is enabled by default and needs configuring if the site's files live in non-standard paths. Many programs are missing from the main repositories and are installed from the EPEL repository. On the other hand, RHEL instructions apply almost unchanged, and some commercial server software targets RHEL-compatible systems specifically.

## Control panels

If the server will run a panel, choose the distribution from the panel's list of supported systems, including the version number: panels do not support new releases right away.

- **cPanel** [runs on AlmaLinux, CloudLinux, Rocky Linux and Ubuntu](https://docs.cpanel.net/installation-guide/system-requirements/); Debian is not on the list.
- **ISPmanager** [supports AlmaLinux 8–10, Debian 12–13, Ubuntu 22.04–26.04, Rocky Linux 8 and CloudLinux](https://www.ispmanager.com/docs/ispmanager/system-requirements). An important caveat from the same documentation: upgrading a server with the panel installed to the next major OS version is not supported, so choose a version with plenty of support time left.
- **FASTPANEL**, according to its [installation guide](https://kb.fastpanel.direct/quick_start/how-to-install-fastpanel/), installs on Debian up to 12, Ubuntu up to 24.04, AlmaLinux 8 and Rocky Linux 8; Debian 13 and Ubuntu 26.04 are not on the list yet.

A detailed comparison of panels is in the article [Server control panels: ISPmanager, FASTPANEL, aaPanel](https://accsly.io/en/vps/guide/server-control-panels).

## Which images hosts offer

According to the accsly.io catalog as of November 2026, the list of OS templates is known for 1,241 of 2,247 VPS hosts. Of these, Ubuntu is offered by 1,030, Debian by 976, CentOS or CentOS Stream by 795, AlmaLinux by 705 and Rocky Linux by 422. Almost everyone offers Ubuntu and Debian, while RHEL-compatible systems are noticeably rarer, so if you specifically need AlmaLinux, it is easier to start with the selection [VPS with AlmaLinux](https://accsly.io/en/vps/almalinux). Plans with other systems are on the pages [VPS with Ubuntu](https://accsly.io/en/vps/ubuntu), [VPS with Debian](https://accsly.io/en/vps/debian) and [VPS with Rocky Linux](https://accsly.io/en/vps/rocky-linux).

Check the version too: templates sometimes still include releases that are out of support, and new ones appear with a delay. If the version you need is missing, some hosts let you install the system from your own ISO image; according to the catalog, 287 hosts have such plans, collected in the selection [VPS with a custom ISO](https://accsly.io/en/vps/custom-iso).

## What to choose for your task

- **A website.** Without a panel, Ubuntu LTS or Debian: they have the most guides for nginx, PHP and databases. With a panel, whatever it supports; for cPanel that means AlmaLinux or Ubuntu.
- **A bot or script.** Ubuntu LTS: recent Python and Node.js versions in the packages and the largest number of ready-made guides. More on servers for bots in the article [VPS for a Telegram bot: what the bot needs and how to pick a plan](https://accsly.io/en/vps/guide/vps-for-telegram-bot).
- **1C.** The 1C:Enterprise server officially [supports Debian 10–12, Ubuntu 20.04–24.04, Red Hat Enterprise Linux and Oracle Linux 8–9](https://v8.1c.ru/tekhnologii/systemnye-trebovaniya-1s-predpriyatiya-8/operatsionnye-sistemy/), as well as the Russian distributions Astra Linux, Alt and RED OS. AlmaLinux is not on this list, and neither are Debian 13 and Ubuntu 26.04 yet. For 1C, choose a system from the list, such as Ubuntu 24.04 or Debian 12. If your databases run on Windows, see the article [Windows VPS for 1C](https://accsly.io/en/vps/guide/windows-vps-for-1c).
- **Docker.** [Official Docker Engine packages](https://docs.docker.com/engine/install/) are released for Ubuntu, Debian, RHEL, CentOS and Fedora; for Ubuntu, 22.04, 24.04 and 26.04 are supported. Ubuntu LTS and Debian are the simplest choice. Keep in mind that Docker opens container ports with its own rules, and ufw restrictions do not apply to them; details are in the article [Docker on a VPS: getting started](https://accsly.io/en/vps/guide/docker-on-vps).

If in doubt, take the latest Ubuntu LTS or Debian stable that your panel or program supports. After installing the system, go through the [first steps to secure the server](https://accsly.io/en/vps/guide/vps-security-first-steps) and decide in advance how you will install updates; that is the subject of the article [Updating a server without downtime](https://accsly.io/en/vps/guide/zero-downtime-updates).

## FAQ

### Which is better for a server: Ubuntu or Debian?

Both are suitable. Debian is more conservative and does not change program versions within a release, while Ubuntu LTS more often ships newer versions and is supported for 5 years without a subscription. Choose whichever your panel or program supports.

### Can I still install CentOS?

Not on a new server: CentOS Linux 7 stopped receiving updates on 30 June 2024, and CentOS Stream prepares future RHEL versions and is not designed for long-term support. Use AlmaLinux or Rocky Linux instead.

### How long is Ubuntu 24.04 supported?

Standard security updates are released until May 2029. An Ubuntu Pro subscription extends support to 10 years from release, and the Legacy add-on to 15.

### How does AlmaLinux differ from Rocky Linux?

For a server owner, hardly at all: both are free and compatible with Red Hat Enterprise Linux, and they differ in the team and organisation behind the project. AlmaLinux is more common among hosts.

### Which Linux does a 1C server need?

One from the official 1C list: Ubuntu 20.04–24.04, Debian 10–12, RHEL or Oracle Linux 8–9, or one of the Russian distributions on the list (Astra Linux, Alt, RED OS). AlmaLinux, Debian 13 and Ubuntu 26.04 are not listed yet.

### Can I switch the distribution on a running server?

You cannot switch from Debian to Ubuntu or from Ubuntu to AlmaLinux in place: the system is reinstalled and the data restored from a backup. Upgrading to the next version of the same distribution is possible, but not supported with the ISPmanager panel.

_Updated: 2026-11-07_

# Load testing a website before launch

A load test answers two questions: how many visitors a site can handle on the chosen server and what breaks first. It is run on your own server and only there: the load generator is a separate machine, the host has been notified and external services are replaced with stubs. Here are the numbers to watch, the tools that produce them and how to use them to choose a plan.

> Source: https://accsly.io/en/vps/guide/load-testing-before-launch · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A site that opens quickly for its developer can stop responding when a hundred people arrive at once: it runs out of PHP processes, database connections or memory. Finding this out on the day of an advertising campaign costs far more than finding it out a week earlier. A load test reproduces a stream of visitors on your server and shows where the limit is and how much headroom you have left.

## What to measure

The result of a test is not a single number but a set of metrics that are read together:

- **RPS (requests per second)** is how many requests the server handles. On its own, RPS says little: a server can answer a thousand requests per second while every response takes five seconds.
- **Response time percentiles.** p95 means that 95% of requests completed within that time, p99 means 99%. An average hides slow responses: if 90 requests took 100 ms and 10 took 3 seconds, the average of about 400 ms looks decent, even though every tenth visitor waits three seconds.
- **Error rate** covers 5xx responses, dropped connections and timeouts. Under load, errors usually appear before response times grow noticeably.
- **Server resources**: CPU load, free memory and swap, disk wait (iowait) and the number of database connections. These are collected on the server itself during the test; otherwise you cannot tell what the site ran into.

Set the goal in advance and in the same units, for example: "at 50 requests per second, p95 for the home page and the catalog is under 500 ms and errors stay below 1%". Without a goal, a test turns into a pile of charts that cannot support any decision.

## Types of tests

- **Smoke test**: a few virtual users for about a minute. It confirms that the scenario is written correctly and gives a baseline response time without load.
- **Load test**: the expected peak traffic for 15–30 minutes. It shows whether the server copes with the planned load.
- **Stress test**: the load is raised in steps until errors or response times climb. It reveals the limit and how the site behaves beyond it: whether it returns an error quickly or hangs.
- **Soak test**: moderate load for several hours. It finds memory leaks, logs and disks filling up, and connections piling up.

The scenario should resemble real visitors: a mix of pages (home, catalog, product page, search), pauses between actions, and some users who are logged in or have items in the cart. A test that requests the same cached page a thousand times per second measures the cache, not the site.

## Tools

All four programs below are free and run from the command line. The first two suit scenarios with several pages; the last two are for a quick check of a single URL.

- **k6**: scenarios are written in JavaScript, and results are printed straight away with percentiles. You can set thresholds in the scenario: according to the [k6 documentation](https://grafana.com/docs/k6/latest/using-k6/thresholds/), conditions such as `http_req_failed: ['rate<0.01']` and `http_req_duration: ['p(95)<200']` are checked at the end of the test, and if one fails, k6 exits with a non-zero code. That makes k6 easy to add to CI: a build that slows the site down will not pass.
- **Apache JMeter**: scenarios are assembled in a graphical interface, with forms, authentication, response parsing and data from CSV files. The test itself [should be run in command-line mode](https://jmeter.apache.org/usermanual/best-practices.html) with `jmeter -n -t test.jmx -l test.jtl`, because the GUI mode consumes the generator's resources and skews the results.
- **wrk** is a [multithreaded generator](https://github.com/wg/wrk) that can put heavy load on a single URL from one machine. For example, `wrk -t4 -c100 -d60s --latency https://example.com/` runs 4 threads with 100 connections for one minute and reports the latency distribution. More complex scenarios are written in Lua.
- **ab (ApacheBench)** is the simplest option and is often already installed together with Apache. Its [documentation](https://httpd.apache.org/docs/2.4/programs/ab.html) states plainly that ab does not fully implement HTTP/1.x and that under high load it may measure its own speed rather than the server's. Keep-alive is off by default and is enabled with the `-k` flag. It is fine for a quick check but not for deciding on a plan.

## How to test without disturbing anyone

A load test creates the same stream of requests as a rush of visitors, so it may only be run on a server you control and in line with the rules of the platform it runs on.

- **Only your own server and your own domain.** Putting load on other people's sites and APIs without the owner's written consent is unacceptable, even "just for a minute". If your site calls a payment gateway, a delivery service or an external API, replace them with stubs or with those services' test environments for the duration of the test.
- **Notify your host.** The provider's DDoS protection may mistake the test for an attack and block the generator's address, and some hosts' rules require such tests to be agreed in advance. For example, the [AWS policy](https://aws.amazon.com/ec2/testing/) allows stress tests of your own prepared endpoints but prohibits DDoS simulations. A short message to support with the date, time, addresses and expected volume settles the matter. How hosts organise their protection is explained in the article [DDoS protection: what hosting providers actually give you](https://accsly.io/en/vps/guide/ddos-protection-at-hosters).
- **Not on shared hosting.** On a shared server, the test will slow down your neighbours, and the result will depend on them. Test on a VPS or a dedicated server where the resources are reserved for you.
- **Run the generator on a separate machine.** If it runs on the same server, it takes CPU away from the site. A VPS with hourly billing works well as a generator: you create it for the test and delete it afterwards. According to the accsly.io catalog as of November 2026, hourly billing is explicitly stated by 173 of 2,247 VPS hosts, and the plans are collected on the page [VPS with hourly billing](https://accsly.io/en/vps/hourly-billing).
- **Keep traffic in mind.** An hour of testing can push hundreds of gigabytes. If the plan has a traffic cap or the link is shared with neighbours, the excess is billed or the speed is reduced; more on this in the article [Bandwidth and traffic: what 1 Gbps and unlimited really mean](https://accsly.io/en/vps/guide/server-bandwidth-and-traffic).
- **CDN and protection in front of the site.** If the domain is connected to a CDN, a test through it measures the CDN and may hit its limits. Test the origin server directly by its address, and agree any load through the CDN with the CDN provider.

## How to read the results and choose a plan

As the load increases step by step, RPS first grows along with it while response time barely changes. Then comes the saturation point: RPS stops growing, p95 rises sharply and errors appear. Your working load should stay well below this point, because you need headroom for spikes, background jobs and audience growth. A handy rule of thumb is for the expected peak to take no more than half of the limit you found.

Next, look at what the server ran into at the saturation point:

- CPU at 100%: you need more cores, or a higher clock speed if the bottleneck is a single thread; plans with clock speeds from 4 GHz are collected on the page [VPS with a high CPU clock speed](https://accsly.io/en/vps/high-frequency);
- memory ran out and the server started swapping: you need more memory or fewer PHP-FPM processes and workers; sizing guidelines are in the article [How much RAM and how many cores a website needs](https://accsly.io/en/vps/guide/ram-and-cpu-for-website);
- high iowait: the disk cannot keep up, usually because of the database; NVMe and indexes help, and the comparison is in the article [NVMe or SSD: does it matter for a website](https://accsly.io/en/vps/guide/nvme-or-ssd);
- resources are free but errors occur: you have hit a configuration limit, such as the database connection limit, the number of web server workers or open files.

Before buying, it is worth repeating the test on the exact plan you intend to take: CPUs and disks differ between hosts more than the numbers in the description suggest. The easiest way is with hourly billing or during a trial period, as described in the article [How to test VPS ping and speed before you pay](https://accsly.io/en/vps/guide/check-vps-speed-before-buying). After launch, the same metrics (response time, errors, resource usage) move into [monitoring](https://accsly.io/en/vps/guide/server-monitoring-uptime-alerts), so that growing load becomes visible before the site starts returning errors.

## FAQ

### How many visitors can a VPS with 2 GB of RAM handle?

It cannot be calculated in advance: it all depends on the CMS, caching and how heavy the pages are. A site with full-page caching can serve hundreds of requests per second on such a server, while a dynamic online shop without caching may hit its limit at a few dozen. Only a test of your own site gives the answer.

### Can I load test someone else's website?

No. You may only test your own server or a site whose owner has given written permission for the test. External services that your site calls are replaced with stubs for the duration of the test.

### Do I need to tell my host about a load test?

Yes. DDoS protection may mistake the test for an attack and block the generator's address, and some hosts' rules require approval. A message to support with the time, addresses and expected traffic volume is enough.

### Why look at p95 rather than the average response time?

The average hides slow requests. p95 shows the time within which 95% of requests completed, that is, what every twentieth visitor sees in the worst case.

### Why is k6 better than ab?

k6 runs scenarios with several pages, reports percentiles and checks thresholds, so it can be built into CI. ab is only suitable for a quick check of a single URL and under high load may end up measuring itself.

### How long should a load test last?

A smoke test takes about a minute, the main test 15–30 minutes at the expected peak load, and a soak test several hours. A short test will not reveal memory leaks or logs filling up the disk.

_Updated: 2026-11-07_

# Updating a server without downtime

A server must not be left without updates, yet every update risks taking the site down. The risk is managed with a process: small security fixes are installed automatically, major changes follow a plan with a snapshot, testing and a ready rollback, and reboots are grouped into a maintenance window. Here is how to set this up on a single VPS.

> Source: https://accsly.io/en/vps/guide/zero-downtime-updates · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

Server updates come in two kinds, and they need to be handled differently. Security fixes are released often, change little and almost never break anything, so it is best to install them automatically on the same day. Planned upgrades, such as a new version of the operating system, PHP, the database or the panel, change how programs behave, so they are prepared and tested. Downtime is most often caused not by an update as such but by a major change being installed as if it were a minor one.

## Automatic security updates

On Ubuntu Server, the `unattended-upgrades` package is [installed and enabled by default](https://ubuntu.com/server/docs/how-to/software/automatic-updates/): once a day it installs security updates only, and the other origins in `/etc/apt/apt.conf.d/50unattended-upgrades` are commented out. The frequency is set in `20auto-upgrades`, and the log is written to `/var/log/unattended-upgrades/`. Debian uses the same package, but a minimal installation may not include it; how to enable it is described on the [Debian Wiki page](https://wiki.debian.org/UnattendedUpgrades).

On AlmaLinux and other RHEL-compatible systems, the same job is done by [dnf-automatic](https://dnf.readthedocs.io/en/latest/automatic.html). By default it does not install updates: in `/etc/dnf/automatic.conf` you set `upgrade_type = security` and `apply_updates = yes`, and then enable the `dnf-automatic.timer` timer.

Neither tool reboots the server by default. That is the right behaviour: a server should not restart at peak time. But the reboot must not be forgotten either, because an updated kernel and libraries only take effect after a restart. On Ubuntu and Debian, the file `/run/reboot-required` signals that a reboot is needed; on AlmaLinux, the command `dnf needs-restarting -r` does. It is worth adding this check to your [server monitoring](https://accsly.io/en/vps/guide/server-monitoring-uptime-alerts) and doing the reboot itself in a maintenance window.

## A snapshot before a planned upgrade

Before any major change, take a disk snapshot in the host's control panel. If the upgrade goes wrong, it returns the server to its original state within minutes. According to the accsly.io catalog as of November 2026, backup terms are described by 1,644 of 2,247 VPS hosts, and 318 of them explicitly mention snapshots. If your host does not offer snapshots, you need a full backup before the upgrade, one that you have already verified by restoring it.

Two caveats. A snapshot is usually stored in the same place as the server's disk and does not replace a backup: if the storage fails, both are lost. In addition, a snapshot of a running database may be inconsistent, so before taking it you dump the database or briefly stop writes. How to build a complete backup setup is explained in the article [VPS backups: strategies and tools](https://accsly.io/en/vps/guide/vps-backups), and plans with space for backups are on the page [VPS for backups](https://accsly.io/en/vps/for-backups).

## Blue-green and rolling updates on a single VPS

Zero-downtime techniques come from large systems with several servers behind a load balancer: blue-green keeps two complete copies and switches traffic from one to the other, while a rolling update takes servers out of service one at a time. On a single VPS, the same ideas apply to the application, though not to the operating system itself.

- **Release directories.** Each version of the site is deployed to its own directory, such as `releases/2026-11-07`, and the web server points to a `current` symlink. The new version is prepared alongside (dependencies, build, cache), and then the link is switched with a single command. Rolling back means pointing the link at the previous directory.
- **Two application instances.** The new version is started on another port or in another container, checked, and then nginx is switched over to it. Reloading the nginx configuration does not drop connections: according to the [nginx documentation](https://nginx.org/en/docs/control.html), the master process first checks the configuration and keeps running with the old one if there is an error, while the old worker processes finish serving their clients. Still, run `nginx -t` beforehand. How to run applications in containers is described in the article [Docker on a VPS: getting started](https://accsly.io/en/vps/guide/docker-on-vps).
- **Backward-compatible database migrations.** While both versions are running, the database has to work for both. So schema changes are split into steps: first add the new columns and tables, deploy the code that uses them, and remove the old ones only in the next release.

Upgrading the operating system itself to a new major version cannot be done without downtime on a single server. It is more reliable to set up a second VPS with the new system, move the site to it, test it and switch DNS, having lowered the records' TTL in advance; how to do this is explained in the article [Domains and DNS for a server owner](https://accsly.io/en/vps/guide/domains-and-dns). For the duration of the move, it is convenient to take the second server with [hourly billing](https://accsly.io/en/vps/hourly-billing). How to choose a system version so that such moves happen less often is covered in the article [Linux distributions for a server: Ubuntu, Debian, AlmaLinux](https://accsly.io/en/vps/guide/linux-distros-for-server).

## Kernel updates without a reboot

Kernel live patching fixes critical vulnerabilities in the running kernel without rebooting the server. On Ubuntu, this is [Livepatch](https://ubuntu.com/security/livepatch), part of the Ubuntu Pro subscription, which is free for personal use on up to five machines. RHEL-compatible systems have their own mechanisms, including commercial services.

The technology has its limits. Only functions that the kernel can trace can be patched, a restriction described in the [Linux kernel documentation](https://docs.kernel.org/livepatch/livepatch.html), so some fixes only arrive with a new kernel. Canonical states plainly that Livepatch does not replace scheduled reboots; it only lets you postpone them to a maintenance window. And most importantly for a VPS: only KVM virtualization gives you your own kernel. On OpenVZ and LXC the kernel is shared and the host updates it; more on this in the article [KVM or OpenVZ: which to choose](https://accsly.io/en/vps/guide/kvm-or-openvz).

## Maintenance window and rollback

A maintenance window is a time chosen in advance when traffic is lowest, usually night-time in your main audience's time zone, when reboots and planned changes are allowed. The time is taken from the site's analytics, not picked at random. If customers or employees use the site, they are warned in advance. The window is not only for you: the host also carries out maintenance, and how hosts announce it is covered in the article [SLA and uptime: what hosts promise](https://accsly.io/en/vps/guide/sla-and-uptime).

The rollback plan is drawn up before the work starts, not after something has broken:

- define the failure signs in advance (errors in the logs, rising response times, a failed check of key pages) and a deadline after which you roll back instead of trying to fix things further;
- for code, switch the symlink or nginx back to the previous release;
- for packages, AlmaLinux has [`dnf history undo`](https://dnf.readthedocs.io/en/latest/command_ref.html), which reverts the last transaction; Ubuntu and Debian have no built-in package rollback, so there you rely on the snapshot;
- a snapshot restores the entire disk, and everything written after it (orders, messages, sign-ups) will be lost. That is why the site is put into maintenance or read-only mode for the duration of a risky upgrade.

After the update, check the key pages and error logs and compare response times with the usual figures. If you ran [load testing](https://accsly.io/en/vps/guide/load-testing-before-launch) before launch, the same scenario will quickly show after a major update whether the site has become slower.

## FAQ

### Is it safe to enable automatic updates on a server?

For security updates, yes: they change little and close vulnerabilities on the day they are released. Automatically installing everything, including new program versions, is not a good idea, and reboots are best done manually in a maintenance window.

### Do I need to reboot the server after updates?

After updating the kernel and core libraries, yes; otherwise the old versions keep running. On Ubuntu and Debian, the file /run/reboot-required signals this; on AlmaLinux, the command dnf needs-restarting -r does.

### Does a VPS snapshot replace a backup?

No. A snapshot is usually kept on the same storage as the server's disk and is meant for a quick rollback after a failed update. A backup should be stored separately, ideally with another provider.

### Can the kernel be updated without a reboot?

Partly: live patching fixes critical vulnerabilities in the running kernel; on Ubuntu this is Livepatch. It only works on KVM, does not fix everything and does not replace scheduled reboots.

### How do I update a website on a single VPS without downtime?

Deploy each version to its own directory and switch a symlink, or start the new version alongside the old one and switch nginx over to it. Make database migrations compatible with both versions.

### How do I move to a new Ubuntu or Debian version without downtime?

On a single server, you cannot: an OS upgrade requires a reboot and may take a while. To avoid downtime, move to a second server with the new system and switch DNS.

_Updated: 2026-11-07_

# CDN: when a website needs one

A CDN stores copies of a site's files on servers around the world and delivers them to each visitor from the nearest one. This speeds up loading of images, scripts and video and takes load off your server, but it does not make a slow CMS faster and does not replace choosing the right country for your server. Here is when a CDN is really needed and when a single VPS in the right place is enough.

> Source: https://accsly.io/en/vps/guide/cdn-for-website · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A CDN (content delivery network) is a layer between the visitor and your server. The domain's DNS record points not to the server but to the CDN. The visitor connects to the nearest node of the network, the node serves whatever it has in its cache and fetches everything else from your server, which in this setup is called the origin.

## What a CDN does

- **Serves static files close to the visitor.** Images, CSS, JavaScript, fonts and video load from a node in the same or a neighbouring country rather than from another continent.
- **Shortens connection setup.** The encrypted connection is established with the nearest node. Even in TLS 1.3 the handshake takes a separate round trip ([RFC 8446](https://www.rfc-editor.org/rfc/rfc8446)), and with a 150 ms ping to a server on another continent, the connection alone takes about a third of a second.
- **Offloads the server and the network link.** If the cache serves 90% of requests, the server gets a tenth of the traffic. This lets you get by with a smaller plan and stay within the traffic limit discussed in the article [Bandwidth and traffic: what 1 Gbps and unlimited really mean](https://accsly.io/en/vps/guide/server-bandwidth-and-traffic).
- **Absorbs part of the attacks.** There is a separate section on this below.

## What a CDN does not do

- **It does not speed up what is not cached.** The cart, the user account area, search, the API and pages for logged-in users are requested from the origin every time. If a page takes two seconds to build because of a slow database, it will take the same two seconds with a CDN. What helps here is a more powerful server or optimization; see the article [How much RAM and how many cores a website needs](https://accsly.io/en/vps/guide/ram-and-cpu-for-website).
- **It does not protect a server whose address is known.** An attack aimed directly at the origin's IP bypasses the CDN.
- **It does not replace backups.** The cache holds only some of the files and only for a while; you cannot restore a site from it.
- **It adds a dependency.** A CDN outage or a mistake in its settings takes the site down just like a server failure.

## When a server closer to your visitors is enough

If your visitors are in one country or one region, the simplest way to speed up the site is to put the server there too. Every 100 km in a straight line adds about a millisecond to the ping, and a server in the audience's country usually responds within 5–30 ms. Such a site will get only slightly faster with a CDN and is simpler to set up without one. How to choose a location and check the ping before paying is described in the articles [How to choose a country for your server](https://accsly.io/en/vps/guide/choose-server-country) and [How to test VPS ping and speed before you pay](https://accsly.io/en/vps/guide/check-vps-speed-before-buying).

A CDN is needed when the audience is spread across continents, when the site has many heavy files (a catalogue with photos, video, downloads) or when traffic comes in peaks: a sale, a newsletter, a press mention. An alternative for an audience in two or three regions is a server in each. According to the accsly.io catalog as of November 2026, VPS plans are available in 96 countries, 400 hosts have servers in five or more countries and 155 in ten or more, so several locations can be rented from a single host. But several servers have to be kept in sync, whereas a CDN caches files from one.

## Caching rules

A CDN decides what to store and for how long based on the response headers from your server, first of all `Cache-Control` ([RFC 9111](https://www.rfc-editor.org/rfc/rfc9111)):

- `max-age` is how many seconds the response may be stored, and `s-maxage` is the same but only for CDNs and proxies;
- `private` means the response is for one user, so only the browser may store it, not the CDN;
- `no-store` means do not store it anywhere.

A working scheme for most sites: files with a version in the name (`app.3f2a.css`) are served with a one-year `max-age` and the `immutable` flag ([RFC 8246](https://www.rfc-editor.org/rfc/rfc8246)), and the name changes when the file changes. HTML is cached for minutes or not at all. Pages with a session, a cart or personal data are marked `private` or `no-store`.

CDNs also have their own defaults. For example, Cloudflare [does not cache HTML and JSON](https://developers.cloudflare.com/cache/concepts/default-cache-behavior/), nor responses with a `Set-Cookie` header or `Cache-Control: private`. If you enable caching of all pages with a rule that overrides these headers, the CDN may serve one visitor a page generated for another, complete with that person's name and orders. Enable such a rule only for URLs that definitely contain no personal data.

You can check whether a response came from the cache with `curl -I https://example.com/app.css`: the `Age` header shows how many seconds the response has been stored, and the CDN reports the cache status in its own header, whose name you will find in its documentation.

## CDN and DDoS protection

Large CDNs have network capacity and node counts orders of magnitude greater than a single data centre, so volumetric attacks are spread across the network and do not reach your server. Application-layer attacks are filtered by the CDN with rules: request rate limiting, browser checks, blocking by country or address. This complements the host's protection rather than replacing it: according to the accsly.io catalog as of November 2026, 1,123 of 2,243 hosts with VPS plans state that they offer DDoS protection, and it is usually network-layer filtering. What actually lies behind such a line in a plan is explained in the article [DDoS protection: what hosting providers actually give you](https://accsly.io/en/vps/guide/ddos-protection-at-hosters); plans that include it are collected in [VPS with DDoS protection](https://accsly.io/en/vps/ddos-protection).

Protection through a CDN only works as long as the origin's address is unknown. On the server, allow incoming connections to ports 80 and 443 only from the CDN's address ranges, which every provider publishes. Do not keep mail and other services on the same IP as the site: MX records and email headers reveal the address. After connecting a CDN, change the server's IP if the old one was already in public DNS records, since their history is kept in open databases.

## What it costs

The price of a CDN is made up of transferred traffic, the number of requests and additional features. There are three models:

- **A free plan** with limits on volume or features. It is often entirely enough for a small site. For example, Amazon CloudFront's free plan includes [one million requests and 100 GB a month](https://aws.amazon.com/cloudfront/pricing/).
- **Pay per gigabyte** with prices by region. Bunny.net, for example, charges [from $0.01 per gigabyte in Europe and North America and 3–6 times more in other regions](https://bunny.net/pricing/cdn/). In this model, video and large downloads become the main expense.
- **A fixed monthly fee** for a bundle of traffic and requests, with no extra charge for overage within the plan.

Application protection (WAF), image optimization, log storage and dedicated addresses are paid for separately. Before connecting a CDN, compare its price with the cost of traffic at your host: if the server already includes several terabytes a month and the audience is nearby, you do not need a CDN to save on traffic.

## How to connect a CDN without breaking the site

1. **Choose the setup.** You can hand the CDN the domain's entire zone by changing the DNS servers at the registrar, or route only a subdomain for static files through the CDN with a CNAME record, for example `static.example.com`. The second option is easier to undo. How these records work is explained in the article [Domains and DNS for a server owner](https://accsly.io/en/vps/guide/domains-and-dns).
2. **Set up encryption to the origin.** The connection between the CDN and the server must also use HTTPS with certificate verification. A mode in which the CDN connects to the server over HTTP leaves traffic unencrypted on that leg. Certificates are covered in the article [SSL certificates: free and paid](https://accsly.io/en/vps/guide/ssl-certificates).
3. **Pass the visitor's real IP to the server.** Otherwise logs, rate limits and fail2ban will see only the CDN's addresses. The CDN passes the address in a header, and the web server has to be configured to trust it only from the CDN's addresses.
4. **Check the nodes for your audience.** Look at the CDN's node map and measure latency from the regions where your visitors are, especially from the countries where most of your audience is. A CDN without nodes near your audience can turn out slower than direct access to the server.

## FAQ

### Does a small website need a CDN?

If the visitors are in one country and the server is there too, usually not: the speed gain will be small. A CDN is useful when the audience is spread across continents, when there are many images and videos or when there are traffic peaks.

### Does a CDN speed up dynamic pages?

Hardly at all: the cart, the user account area and the API are requested from your server every time. A CDN only shortens connection setup, while page build time depends on the server and the CMS.

### Does a CDN protect against DDoS attacks?

Yes, if the server's address is hidden: the CDN spreads volumetric attacks across its network and filters requests to the application. If the server's IP is known, the attack will go straight to it, so the server should accept web traffic only from the CDN's addresses.

### How much does a CDN cost?

A free plan is often enough for small sites. With pay-per-traffic pricing, the price in Europe and North America starts at about one cent per gigabyte and is several times higher in other regions. WAF and image optimization cost extra.

### Which is better: a CDN or a server closer to visitors?

If the audience is in one region, a server in that region is simpler and cheaper. If visitors are all over the world or the site serves many heavy files, you need a CDN, and the server is placed where most of the audience is.

### Why does the site show an old version after connecting a CDN?

The CDN serves the cached copy until it expires. Purge the cache in the CDN panel or use files with a version in the name, and set a short max-age for HTML.

_Updated: 2026-11-06_

# Domains and DNS for a server owner

You can switch servers in an evening, but a domain stays with a project for years. Through DNS, the domain points to your server, your mail and third-party services, and a single wrong record can take the site offline or send your emails to spam. Here are the records a VPS owner will need, how caching works, where to keep the zone and how to move to a new server without visitors noticing.

> Source: https://accsly.io/en/vps/guide/domains-and-dns · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A domain has three independent parts, and it helps to tell them apart. The registrar sells and renews the domain itself. The DNS servers listed at the registrar in the NS records host the zone, the list of the domain's records. The host provides the server with the IP address those records point to. All three roles can be played by one company or by three different ones, and that determines what you will have to change when you move.

## The main DNS records

- **A** is the server's IPv4 address for a name ([RFC 1035](https://www.rfc-editor.org/rfc/rfc1035)). A website usually needs two: one for `example.com` and one for `www.example.com`.
- **AAAA** is the same for IPv6 ([RFC 3596](https://www.rfc-editor.org/rfc/rfc3596)). Add it only if the server really responds over IPv6: browsers try this address first, and broken IPv6 causes delays for some visitors. More on this in the article [IPv4 and IPv6 on a server](https://accsly.io/en/vps/guide/ipv4-and-ipv6-on-server).
- **CNAME** is an alias: one name points to another name, for example `www` to `example.com` or a subdomain to a CDN address. Under [RFC 2181](https://www.rfc-editor.org/rfc/rfc2181#section-10.1), a name with a CNAME cannot have any other records, so a CNAME is not placed on the bare domain: it already has NS and SOA records. Some DNS providers work around this with their own ALIAS or ANAME types, but that is an extension of a particular service, not a standard.
- **MX** lists the servers that receive the domain's mail, with a priority: the lower number is the primary. An MX record must point to a name with an A or AAAA record, not to an IP address and not to a CNAME.
- **TXT** holds arbitrary text. It is used for SPF, DKIM and DMARC for mail and for domain verification codes for search engines and other services. How to write the mail records is explained in the article [Mail server on a VPS: SPF, DKIM, DMARC](https://accsly.io/en/vps/guide/mail-server-on-vps-spf-dkim-dmarc).
- **CAA** specifies which certificate authorities may issue certificates for the domain ([RFC 8659](https://www.rfc-editor.org/rfc/rfc8659)). The record is optional, but if it exists, an authority not named in it will refuse to issue. Certificates are covered in the article [SSL certificates: free and paid](https://accsly.io/en/vps/guide/ssl-certificates).

A typical zone for a site on a VPS with mail at a third-party service looks like this: A and AAAA records for the domain and `www`, the mail service's MX, TXT with SPF and DMARC, CNAME or TXT for DKIM and a few TXT records with service verifications.

## TTL: why changes do not show up immediately

TTL is the time in seconds for which the DNS servers of internet providers and visitors' devices remember an answer ([RFC 2181, section 8](https://www.rfc-editor.org/rfc/rfc2181#section-8)). Until it expires, they do not query the zone again, so a new record reaches everyone no sooner than the TTL of the old one. That is where the common saying "DNS takes up to 72 hours to update" comes from: in reality, everything depends on the TTL you set yourself.

- 3,600 seconds (an hour) is a sensible value for normal operation;
- 300 seconds is for the period of a move or setup, when you may need to change the address quickly;
- a day or more is for records that do not change for years, such as MX.

The absence of a record is cached too. If you query a subdomain before you have created it, the negative answer is remembered for the period set in the zone's SOA record ([RFC 2308](https://www.rfc-editor.org/rfc/rfc2308)), often an hour. So create the record first and only then check it.

NS records at the registrar are a special case. Their TTL is set not by the domain owner but by the top-level zone. A query to the zone servers on 6 November 2026 showed that NS records for .com domains are cached for 172,800 seconds, that is two days, and for .ru domains for 345,600 seconds, four days. Changing a domain's DNS servers therefore always takes longer than changing an A record.

## PTR: the reverse record for mail

Ordinary records translate a name into an address, while PTR translates an address into a name: `203.0.113.10` → `mail.example.com`. It does not live in your domain's zone but in the address zone `in-addr.arpa` or `ip6.arpa`, which is managed by the owner of the IP address, that is, the host. You set it in the host's control panel or through support.

A website does not need PTR, but mail does: Google [requires senders](https://support.google.com/a/answer/81126) to have a PTR record for the server's IP address and for the name in it to point back to the same address. Before buying a VPS for mail, check whether the host lets you change PTR and whether outgoing port 25 is open; such servers are collected in [VPS for a mail server](https://accsly.io/en/vps/for-mail-server).

## Where to keep the zone: registrar, host or a separate DNS service

- **At the registrar.** Free and independent of the host: when you change servers, you change one A record. The downsides are a limited choice of record types, no API or a restricted one, and response speed that depends on the registrar's infrastructure.
- **At the host.** Convenient when everything is in one panel, and some hosts fill in the zone for you. But if you move to another host, you will have to move the zone as well, and if the account is suspended or there is a dispute, DNS becomes unavailable along with the server, and with it your mail and all subdomains.
- **A separate DNS service.** Servers in different countries with anycast, fast responses, an API for automation and for issuing wildcard certificates, and a change history. Many offer free basic plans. It suits projects with several servers or those that use a CDN.

The rule for every option: the registrar account and the domain must belong to the project owner, not to a contractor or the host. According to the accsly.io catalog as of November 2026, a free domain is mentioned in 494 shared hosting plans from 153 of 1,655 hosts, usually with annual payment. Before accepting such an offer, find out in whose name the domain is registered and how much it costs to renew in the second year. Hosting plans are collected in the section [Website hosting](https://accsly.io/en/hosting).

Protect the domain itself as you would money: two-factor login at the registrar, auto-renewal with a valid card and an up-to-date owner email. Under the current [ICANN rules](https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en), a domain in generic zones such as .com cannot be transferred to another registrar for 60 days after registration or a transfer, so it is better to choose the registrar right away.

## How to move a site without downtime

1. **A day or two in advance**, lower the TTL of the A and AAAA records to 300 seconds and wait for the old TTL to expire.
2. **Prepare the new server** and test the site on it before changing DNS: `curl --resolve example.com:443:203.0.113.10 https://example.com/` or an entry in the `hosts` file on your computer.
3. **Change the A and AAAA records** to the new address. Within a few minutes most visitors will be on the new server.
4. **Do not switch off the old server** for at least a day: devices with the cached address will still connect to it. If the site accepts data, make the old copy read-only for the duration of the move so that orders and comments do not end up split between two databases.
5. **Restore the TTL** to its normal value once everything works.

The full procedure for moving files, the database and mail is described in the article [How to move a website from shared hosting to a VPS](https://accsly.io/en/vps/guide/move-site-hosting-to-vps).

If you are changing the domain's DNS servers along with the server, do it as a separate step. First copy all the records to the new zone and compare the answers from the old and new servers: `dig @new-ns example.com MX`, and so on for each record type. Only then change the NS records at the registrar, and keep the old zone working for at least the delegation TTL: two days for .com and four for .ru. If DNSSEC is enabled for the domain, remove the DS record at the registrar before changing NS or migrate the keys following the scheme in [RFC 6781](https://www.rfc-editor.org/rfc/rfc6781#section-4.3.5): otherwise DNSSEC-validating resolvers will stop resolving the domain.

## How to check

The command `dig example.com A +short` shows the current answer, while `dig example.com A +trace` shows the path from the root servers to yours and helps you find which server is returning the old record. `dig -x 203.0.113.10` checks PTR. To see the TTL remaining in a particular resolver's cache, query it directly without `+short`. If the site is behind a CDN, the A record will point to the CDN rather than to your server; how this works is explained in the article [CDN: when a website needs one](https://accsly.io/en/vps/guide/cdn-for-website).

## FAQ

### How long does DNS take to update after a record change?

As long as the TTL of the old record: with a TTL of 300 seconds, about five minutes; with a TTL of a day, up to a day. Changing a domain's DNS servers at the registrar takes longer: NS records are cached for two days for .com and for four days for .ru.

### What is the difference between an A record and a CNAME?

An A record points a name to an IP address, while a CNAME points it to another name, whose address is then taken from that name's records. A CNAME cannot be placed on the bare domain; only A and AAAA can.

### Where is it better to keep DNS: at the registrar or at the host?

If you have one server and rarely change it, the registrar's DNS is enough, and it does not depend on the host. A zone at the host is convenient, but you will have to move it if you leave. A separate DNS service is needed when there are several servers, a CDN or a need for automation via an API.

### Who sets up the PTR record?

The owner of the IP address, that is, the host: in the server control panel or on request to support. You cannot create a PTR record in your own domain's zone.

### How do I move a site to another server without downtime?

A day in advance, lower the TTL to 300 seconds, test the site on the new server via the hosts file, change the A and AAAA records and keep the old server running for at least another day.

### Do I need an AAAA record if the server has IPv6?

Yes, if the site on the server actually responds over IPv6 on ports 80 and 443. If IPv6 is assigned but the web server does not listen on it, it is better not to add the AAAA record: some visitors will get delays and errors.

_Updated: 2026-11-06_

# SSL certificates: free and paid

A free certificate encrypts the connection just as reliably as a paid one: browsers make no distinction between them in terms of security. The difference lies in what the certificate authority checks, how long the certificate lasts and who is responsible for renewing it. According to the accsly.io catalog as of November 2026, free SSL is explicitly listed in 1,449 shared hosting plans from 178 hosts. Here is when that is enough and when a certificate is worth paying for.

> Source: https://accsly.io/en/vps/guide/ssl-certificates · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

The word "SSL" is a leftover from an old protocol: today the connection is protected by TLS, and the certificate confirms that the encryption key belongs to the owner of the domain. Without a certificate, the browser marks the site as not secure, login and payment forms show warnings, and search engines treat HTTPS as a baseline requirement for normal rankings. Below are the types of certificates, how paid ones differ from free ones and how to keep a certificate from expiring on your own server.

## DV, OV and EV: what exactly is checked

Certificates are classified by how the owner is validated. Encryption is the same for all three types; the only thing that changes is what the certificate authority has confirmed before issuing it.

- **DV (domain validation)** only checks that you control the domain, using a file on the site or a DNS record. It is issued automatically within minutes. All free certificates are DV.
- **OV (organization validation)** also checks the company: registration documents, address and phone number. The organization's name is written into the certificate. Issuance takes from one to several days.
- **EV (extended validation)** is the strictest company check. Browsers used to display it as a green bar with the company name, but Safari dropped this in 2018, and in 2019, starting with version 77, Chrome [moved EV information into the Page Info panel](https://chromium.googlesource.com/chromium/src/+/HEAD/docs/security/ev-to-page-info.md): research showed that users did not pay attention to it.

The takeaway for a typical website, blog or online shop: DV is enough. A paid OV or EV certificate is needed when a counterparty, a bank, tender conditions or an internal security policy require it, not for the sake of a badge in the browser.

## Free certificates: Let's Encrypt and ZeroSSL

Free certificate authorities issue certificates over the ACME protocol ([RFC 8555](https://www.rfc-editor.org/rfc/rfc8555)): a program on the server validates the domain, obtains the certificate and renews it on its own. The best-known of these authorities is Let's Encrypt; another example is ZeroSSL, which also [issues free 90-day certificates via ACME](https://zerossl.com/documentation/acme/), including wildcards.

A short lifetime is the main difference of free certificates, and it is getting even shorter. Let's Encrypt currently issues 90-day certificates and has [announced a move to 45 days](https://letsencrypt.org/2025/12/02/from-90-to-45/): from 13 May 2026 this lifetime is available as an option, from 10 February 2027 the default will be 64 days, and from 16 February 2028 it will be 45. There are also rate limits: [no more than 50 certificates per registered domain and 5 identical ones within 7 days](https://letsencrypt.org/docs/rate-limits/). That is plenty for an ordinary site, and while you are debugging your setup it is better to use the authority's staging environment so you do not hit the limit.

Paid certificates are no longer annual either. Under [CA/Browser Forum ballot SC-081v3](https://cabforum.org/2025/04/11/ballot-sc081v3-introduce-schedule-of-reducing-validity-and-data-reuse-periods/), the maximum lifetime of any public certificate is 200 days from 15 March 2026, 100 days from 15 March 2027 and 47 days from 15 March 2029. A "one-year certificate" now means a subscription during which the certificate has to be reissued. So automation is needed whatever you choose, and the argument that "a paid certificate is installed once a year and forgotten" no longer holds.

## When a paid certificate makes sense

- you need the organization's name in the certificate, that is, OV or EV at the request of a partner, payment provider or regulator;
- a server or device does not support ACME and the certificate has to be installed manually, in which case a paid authority provides support and reissue reminders;
- the company needs a single supplier with a contract, invoices and the paperwork its accountant requires.

The warranty payouts advertised in descriptions of paid certificates cover a mistake made by the certificate authority itself during issuance, not a hacked website. Choosing a certificate by the size of that warranty is not worth it.

## Wildcards and certificates for several names

A wildcard certificate for `*.example.com` covers all subdomains at one level: `shop.example.com`, `api.example.com`. It does not cover `example.com` itself or second-level subdomains such as `a.b.example.com`; those are added to the certificate as separate names.

Let's Encrypt issues wildcards [only with DNS validation (DNS-01)](https://letsencrypt.org/docs/challenge-types/): the program on the server has to create a TXT record in the domain's zone. For automatic renewal it needs an API key from the DNS provider, and that key, stored on the server, grants the right to change every record of the domain. If there are only a few subdomains and they are known in advance, it is simpler to issue one certificate listing all the names using ordinary HTTP validation. How DNS records work is explained in the article [Domains and DNS for a server owner](https://accsly.io/en/vps/guide/domains-and-dns).

## What hosting plans include

On shared hosting, certificates are usually handled by the control panel: cPanel, ISPmanager and others obtain a free certificate for the domain and renew it themselves. According to the accsly.io catalog as of November 2026, free SSL is listed in 1,449 plans from 178 hosts, while only 47 plans from three hosts explicitly come without it. In total the catalog has 8,998 shared hosting plans from 1,655 hosts, and for most of them the plan page simply does not mention this condition, which does not mean there is no certificate. Before buying, check whether the free certificate covers all the domains and subdomains of the plan. Plans are collected in the sections [Website hosting](https://accsly.io/en/hosting) and [Hosting for WordPress](https://accsly.io/en/hosting/wordpress).

On a VPS, nobody installs a certificate by default: that is the server owner's job. The exception is servers with a panel: ISPmanager, FASTPANEL, aaPanel and similar panels issue Let's Encrypt certificates from their interface, and they are compared in the article [Server control panels: ISPmanager, FASTPANEL, aaPanel](https://accsly.io/en/vps/guide/server-control-panels). Paid certificates that hosts sell as an add-on are issued by the same certificate authorities, so it is worth comparing the price with what the authority itself charges.

## A certificate on a VPS: certbot and renewal

On a server without a panel, the easiest way to get a certificate is the certbot program. For nginx it takes one command: `certbot --nginx -d example.com -d www.example.com`. Certbot validates the domain over HTTP, adds the certificate to the configuration and enables the redirect to HTTPS. The files are stored in `/etc/letsencrypt/live/example.com/`.

Renewal is set up during installation: according to the [certbot documentation](https://eff-certbot.readthedocs.io/en/stable/using.html), the `certbot renew` job runs twice a day, and the certificate is reissued when less than a third of its lifetime remains. You can check that renewal will succeed with `certbot renew --dry-run` and see the timer with `systemctl list-timers | grep certbot`. If the certificate is used not only by the web server but also, for example, by a mail server, add `--deploy-hook` with a command that reloads that service: otherwise it will keep serving the old file.

There will be no more email reminders: Let's Encrypt [stopped sending expiration emails on 4 June 2025](https://letsencrypt.org/2025/01/22/ending-expiration-emails/). So it is best to add certificate expiry to your monitoring; how to set it up is described in the article [Server monitoring: uptime, load, alerts](https://accsly.io/en/vps/guide/server-monitoring-uptime-alerts).

## Common mistakes

- **Port 80 is closed.** HTTP-01 validation only uses port 80, so the firewall must allow it even if the site runs on HTTPS only. Firewall setup is covered in the article [First 10 steps after buying a VPS: security](https://accsly.io/en/vps/guide/vps-security-first-steps).
- **The domain points to another server.** During a move, validation goes to the old address. Get the certificate after the DNS records have been changed or use DNS validation, as described in the article [How to move a website from shared hosting to a VPS](https://accsly.io/en/vps/guide/move-site-hosting-to-vps).
- **www or a subdomain was forgotten.** A certificate is valid only for the names listed in it, and the browser shows an error on `www.example.com` if only `example.com` was issued.
- **Incomplete chain.** The web server configuration should use `fullchain.pem`, not `cert.pem`: without the intermediate certificate, some devices will not open the site.
- **Mixed content.** The page is opened over HTTPS, but images and scripts load over `http://`, so the browser blocks them or removes the security indicator.
- **HSTS without testing.** The HSTS header ([RFC 6797](https://www.rfc-editor.org/rfc/rfc6797)) forbids the browser from opening the site over HTTP. If you enable it with a long lifetime and `includeSubDomains` before every subdomain has a certificate, those subdomains will be unreachable for visitors for that whole period.
- **A CAA record.** A CAA DNS record ([RFC 8659](https://www.rfc-editor.org/rfc/rfc8659)) lists the authorities allowed to issue certificates for the domain. If it names only one authority, any other will refuse to issue.

## FAQ

### Is a free SSL certificate worse than a paid one?

Not in terms of connection security: the encryption is the same. Free certificates only confirm control of the domain and last 90 days, so they are renewed automatically. Paid OV and EV certificates also confirm the company.

### Does an online shop need a paid certificate?

Usually not: a DV certificate and properly configured HTTPS are enough to accept payments. A paid OV or EV certificate is needed if a payment provider, bank or partner explicitly requires it.

### Does a wildcard certificate cover the main domain?

No. A certificate for *.example.com is valid for subdomains at one level, while example.com and second-level subdomains are added to it as separate names.

### How often should a Let's Encrypt certificate be renewed?

Never manually: certbot checks the certificate twice a day and reissues it when less than a third of its lifetime remains. From 2027 the lifetime will drop to 64 days and from 2028 to 45, so automation is a must.

### Is SSL included in a hosting plan?

Most often, yes. According to the accsly.io catalog as of November 2026, free SSL is listed in 1,449 shared hosting plans from 178 hosts. On a VPS, the server owner installs the certificate themselves or through a control panel.

### Why is the certificate not being issued?

Most often port 80 is closed, the domain still points to the old server, the issuance limit has been reached or a CAA record does not allow this certificate authority. Certbot writes the detailed reason to /var/log/letsencrypt/letsencrypt.log.

_Updated: 2026-11-06_

# 152-FZ and hosting: where to store the data

If a website or service collects personal data of Russian citizens, that data must be recorded and stored in databases located in Russia: this is Part 5 of Article 18 of Federal Law No. 152-FZ. For choosing a VPS, this means the data centre's country matters, not the host's, and copies abroad fall under separate rules. Here is what the law requires, what duties fall on the server owner, how it applies to companies outside Russia and which setups are used in practice.

> Source: https://accsly.io/en/vps/guide/152-fz-and-hosting · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

Federal Law No. 152-FZ "On Personal Data" is Russia's general data protection law. It concerns almost any project with an order form, sign-up, CRM or mailing list whose users include Russian citizens, and it is not limited to Russian companies. Under [Article 3 of the law](https://www.consultant.ru/document/cons_doc_LAW_61801/4f41fe599ce341751e4e34dc50a4b676674c1416/), personal data is any information relating to an identified or identifiable person: a name and phone number, an email address, a delivery address, an order history. Whoever decides why and how it is processed is the operator, the Russian counterpart of a controller. For a company's website that is the company itself, not the host or the developer. Below is what the law requires of where data is hosted. This is an overview of the rules, not legal advice: check your specific processing with a lawyer.

## What Part 5 of Article 18 requires

Since 1 July 2025, [Part 5 of Article 18](https://www.consultant.ru/document/cons_doc_LAW_61801/cbf4e15b7c330f9372e876cdf2bc928bad7950ef/) is worded as a direct prohibition: when personal data is collected, including over the internet, recording, systematisation, accumulation, storage, updating and retrieval of data of Russian citizens using databases located outside Russia are not allowed. The exceptions are narrow and listed in [Article 6](https://www.consultant.ru/document/cons_doc_LAW_61801/315f051396c88f1e4f827ba3f2ae313d999a1873/): processing for the purposes of an international treaty or a law, for the administration of justice, for the exercise of powers of state bodies and for the professional activity of journalists and the media. User consent is not on this list, so a "I agree to my data being stored abroad" checkbox does not lift the requirement.

In practice the law is read like this: the first record of a Russian citizen's data must go into a database physically located in Russia, and that database remains the primary one. If the data is later copied abroad, that is a cross-border transfer with its own rules, covered below.

## What this means for choosing a VPS

What matters is the country of the data centre where the server with the database stands. The country where the host is registered is irrelevant for this requirement: a British company with a data centre in Moscow is fine, a Russian company with a server in the Netherlands is not. How else the company's country differs from the server's country is covered in the article [Hosting provider jurisdiction](https://accsly.io/en/vps/guide/hoster-jurisdiction).

According to the accsly.io catalog as of November 2026, 218 of the 1,934 VPS hosts with a known location, or 11%, have servers in Russia. 78 of them operate only in Russia, while the other 140 also offer locations abroad. So at one host a Moscow plan and a Frankfurt plan can sit side by side: check the country of the specific plan, not the brand. Russian servers are most often in Moscow (149 hosts), followed by Saint Petersburg (33), Novosibirsk (23) and Kazan (11). Plans are collected in the selections [VPS in Russia](https://accsly.io/en/vps/russia) and [VPS for 152-FZ](https://accsly.io/ru/vps/for-152-fz).

Besides the main server, check everything else where data is also written:

- **the host's backups**: in which data centre and country they are kept;
- **managed databases and storage**: their location may differ from the VPS location;
- **external services**: CRM, mailing services, forms, support chats and analytics systems that store visitor data themselves;
- **logs**: if a proxy abroad sits in front of the site and logs request bodies with form contents, the data ends up there too.

## The operator's duties

A server in Russia is only one requirement among several. The operator must also:

- **Notify Roskomnadzor**, the Russian data protection authority, before processing begins, under [Article 22](https://www.consultant.ru/document/cons_doc_LAW_61801/d996966e22e1320c9de1ab82d9f6be12c3d9d765/). There are few exceptions to this duty. Among other things, the notification states where the database with data of Russian citizens is located, so find out the data centre's address from the host in advance. The notification is filed through the [Roskomnadzor personal data portal](https://pd.rkn.gov.ru/).
- **Take security measures** under [Article 18.1](https://www.consultant.ru/document/cons_doc_LAW_61801/eeeebe22bf738fd65bb66b95cc278911ae2525ee/) and [Article 19](https://www.consultant.ru/document/cons_doc_LAW_61801/ca9e5658710519f09ab2fdb8196fcb3eb024a051/): a processing policy, a responsible person, an assessment of threats and of the required protection level, access control, an inventory of media, backups. On an ordinary unmanaged VPS, almost all of this is done by the customer, not the host: updates, a firewall, keys instead of passwords, login logs. Where to start is described in the article [First 10 steps after buying a VPS: security](https://accsly.io/en/vps/guide/vps-security-first-steps).
- **Put a processing instruction in place** if another party carries out the processing. Under Part 3 of Article 6, it lists the operations on the data, the purposes and the security requirements, much like a data processing agreement. The law does not say directly whether a host that only rents out a server and has no access to its contents processes the data. With managed services, such as administration, databases or backups with access to files, an instruction is definitely needed. Many Russian hosts sign one on request.

## Cross-border transfer

Transferring data abroad is allowed, but under the rules of [Article 12](https://www.consultant.ru/document/cons_doc_LAW_61801/e4ebbe1780de623c7cf32a59ca82a7bb523a25dd/). Before the transfer begins, the operator sends Roskomnadzor a separate notification, having first obtained from the foreign recipient information on its security measures, the conditions for ending the processing and its contact details. Roskomnadzor reviews the notification within ten working days. Data may be transferred to countries on the list of those providing adequate protection immediately after the notification; to other countries only once this period has passed, if the transfer has not been prohibited or restricted.

A cross-border transfer is not only moving the database. A backup copy on a foreign server, exporting orders to a foreign CRM, sending mailings through a foreign service: all of these are transfers of data abroad. Each such chain must be stated in the notification.

## If your company is outside Russia

The localisation requirement follows the data of Russian citizens, not the operator's country, so it can also concern a company in the EU, the UK or elsewhere that collects such data from Russian users. Your own law applies on top of it. In the EU this is the GDPR, and in the UK the [UK GDPR](https://www.legislation.gov.uk/eur/2016/679/contents): neither requires the server to be in a particular country, but both require a data processing agreement with the host and a lawful basis for transfers outside their territory. How these rules apply to renting a server is covered in the article [GDPR and choosing a host](https://accsly.io/en/vps/guide/gdpr-and-hosting).

## Typical setups

- **Everything in Russia.** The site, database, backups and mail run on servers in Russian data centres. The simplest setup with the least paperwork. For copies, take a second server from another Russian host, so that one incident does not destroy both the data and the copy; more in the article [VPS backups](https://accsly.io/en/vps/guide/vps-backups).
- **Database in Russia, front end abroad.** Static pages and images are served from a foreign server or a content delivery network closer to the audience, while forms, the shopping cart and the account area send data directly to the server in Russia. The setup works but needs discipline: no form may store or log data on the foreign part.
- **Primary database in Russia, replica abroad.** Suitable for projects with an audience in several countries. The primary record goes to Russia and a replica goes abroad after the cross-border transfer notification.
- **A foreign project with Russian users.** If the service collects data of Russian citizens, the localisation requirement applies to it as well; one option is a separate server in Russia for those users. For data of EU residents, the European rules are added on top.

Employees' data in accounting and HR systems is personal data too. If a Russian company pays for the server, the documents it receives when paying by invoice are covered on the page [VPS paid by invoice](https://accsly.io/en/vps/pay-by-invoice).

## What to ask the host

- the data centre address for the chosen plan, which is needed for the Roskomnadzor notification;
- where the host keeps its own backups and whether you can choose their location;
- whether the host signs a processing instruction or a confidentiality agreement;
- whether the host holds FSTEC licences (issued by Russia's technical security regulator) and offers a certified secure segment, if your protection level requires certified tools;
- which closing documents it issues to companies.

## FAQ

### Do personal data of Russian citizens have to be stored on a server in Russia?

Yes, if you collect them: under Part 5 of Article 18 of Federal Law No. 152-FZ, recording, storing and retrieving data of Russian citizens in databases outside Russia during collection is not allowed. The exceptions are narrow, and user consent is not one of them.

### Does 152-FZ apply to a company outside Russia?

The localisation requirement is tied to the data of Russian citizens, not to the company's country, so a foreign service that collects such data falls under it too. Its own law, such as the GDPR or UK GDPR, applies in addition.

### Is a foreign host with a data centre in Russia suitable?

For the localisation requirement, what matters is the country where the database is, not the company's country. A server in a Russian data centre run by a foreign host meets the requirement, but check where its backups are kept.

### Can backups be stored abroad?

Yes, if the primary database is in Russia, but a copy abroad is a cross-border transfer. Before it starts, Roskomnadzor must be notified separately under Article 12 of the law. Keeping copies on a second server in Russia is simpler.

### Does the Roskomnadzor notification have to include the data centre address?

Yes, the processing notification states where the database with data of Russian citizens is located. Get the address from the host before filing the notification.

### Can the site be abroad and the database in Russia?

This setup is possible if forms send data straight to the Russian server and the foreign part neither stores it nor writes it to logs. If the data stays on the foreign server, that is already recording into a database outside Russia.

_Updated: 2026-11-06_

# GDPR and choosing a host

The EU General Data Protection Regulation (GDPR) does not require data to be kept in the EU, but it does require a data processing agreement with the host and a lawful mechanism for any transfer of data out of the EU. According to the accsly.io catalog as of November 2026, 61% of VPS hosts have servers in the EU, but almost half of them are registered outside the European Economic Area. Here is why that matters and what to check in the terms.

> Source: https://accsly.io/en/vps/guide/gdpr-and-hosting · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

The GDPR is [Regulation (EU) 2016/679](https://eur-lex.europa.eu/eli/reg/2016/679/oj), which applies in all countries of the European Union and the European Economic Area. For choosing a server, three topics in it matter: who is responsible for what, what agreement you need with the host and where data may be transferred. Below is how these rules apply to renting a VPS or a dedicated server. This article explains general rules and is not a substitute for advice from a lawyer.

## When the GDPR applies to your project

Under Article 3, the regulation applies to a company with an establishment in the EU, and to a company from any other country if it offers goods or services to people in the EU or monitors their behaviour, for example through analytics and advertising tags. So a shop outside the EU that delivers to Germany, or a service with a Spanish interface and prices in euros, can also fall under the regulation. In that case, a company without an establishment in the EU usually has to appoint a representative in the Union under Article 27.

Personal data is understood broadly in the GDPR: a name, an email address, a postal address, an order number, an IP address, a device identifier. If your server holds any of this about people in the EU, the rules below apply to you.

## Controller and processor

The regulation divides the parties into two roles (Article 4).

- **The controller** decides why and how data is processed. For a website or service, that is its owner.
- **The processor** processes data on behalf of the controller. A host whose servers hold your customers' data is a typical processor: this is also how cloud and hosting services are described in the [European Data Protection Board Guidelines 07/2020](https://www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-072020-concepts-controller-and-processor-gdpr_en).

The same company can have different roles: for the data on your server the host is a processor, while for your own data, such as your name, payment details and correspondence with support, it is a controller. The role determines the duties. You are responsible for the lawfulness of processing and for security inside the server, and the host for what is written in the agreement and for the security of its infrastructure.

## The data processing agreement (DPA)

Article 28 requires the relationship between controller and processor to be set out in a contract or another legal act. Hosts call it a Data Processing Agreement or Data Processing Addendum (DPA), and it is usually part of the terms or signed on request. Under the regulation, it must state that the processor:

- processes data only on the customer's documented instructions, including with regard to transfers outside the EU;
- commits its staff to confidentiality and takes security measures under Article 32;
- engages sub-processors only with the customer's authorisation and gives notice of changes so that the customer can object;
- helps the customer respond to requests from individuals and report breaches;
- deletes or returns the data when the services end;
- makes available the information needed to demonstrate compliance and allows audits.

If a host does not offer a DPA and is not prepared to sign one, that is a serious drawback for a project with data of people in the EU, even if the server is in Frankfurt.

## Data inside and outside the EU

The regulation allows data to be transferred outside the EEA, but only on the terms of Chapter V. There are two main mechanisms.

- **An adequacy decision** (Article 45). The European Commission has recognised the level of protection in a number of countries as adequate, and transfers there require no additional documents. According to the [Commission's list](https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en) as of November 2026, these include the UK, Switzerland, Japan, the Republic of Korea, Canada for commercial organisations and, since January 2026, Brazil. For the US, the decision covers only companies participating in the EU-US Data Privacy Framework. Russia is not on the list.
- **Standard contractual clauses** (Article 46). If a country is not recognised as adequate, the parties sign the model clauses adopted by [Commission Decision 2021/914](https://eur-lex.europa.eu/eli/dec_impl/2021/914/oj) and assess whether the law of the recipient's country allows them to be complied with. Where necessary, they add technical measures, above all encryption with keys that remain in the EU.

A transfer is not only moving the database. According to [EDPB Recommendations 01/2020](https://www.edpb.europa.eu/our-work-tools/our-documents/recommendations/recommendations-012020-measures-supplement-transfer_en), remote access to data from a third country is also a transfer, for example when the host's support team works from outside the EU. Backup copies on a server in another country and foreign mailing and analytics services also need to be taken into account.

If your users include Russian citizens, Russian law adds its own requirement to store their data in Russia; how the two sets of rules are combined is described in the article [152-FZ and hosting](https://accsly.io/en/vps/guide/152-fz-and-hosting).

## An EU data centre vs an EU company

A server in the European Union does not yet mean that the data is subject only to European law. If the host or its parent company is registered in another country, they are subject to its laws too. The most discussed example is the US CLOUD Act, under which a US company hands over data to US authorities wherever the server stands. Its relationship with the GDPR was analysed by the [EDPB and the European Data Protection Supervisor](https://www.edpb.europa.eu/documents/edpb-correspondence/edpb-edps-joint-response-to-the-libe-committee-on-the-impact-of-the_en).

According to the accsly.io catalog as of November 2026, 1,184 of the 1,934 VPS hosts with a known location, or 61%, have servers in the EU. Most often these are in Germany (597 hosts), the Netherlands (536), France (273), Poland (184) and Finland (164). Among those whose country of registration is known, 470 of 874, or 54%, are registered in the EEA, and the other 404 outside it, most often in the US (79), the UK (69) and Russia (53). The reverse is also true: of the 551 hosts registered in the EU, 131 also rent out servers outside the EEA, so with a European company it is still worth checking the country of the specific plan. More on the difference between the company's country and the server's country is in the article [Hosting provider jurisdiction](https://accsly.io/en/vps/guide/hoster-jurisdiction).

Plans with servers in the European Union are collected in the selection [VPS in Europe](https://accsly.io/en/vps/europe) and on the country pages: [Germany](https://accsly.io/en/vps/germany), [the Netherlands](https://accsly.io/en/vps/netherlands), [Finland](https://accsly.io/en/vps/finland).

## What to check in the host's terms

- whether there is a DPA and whether it meets Article 28: customer instructions, confidentiality, security measures, sub-processors, data deletion, audits;
- the list of sub-processors and how new ones are announced;
- the country and city of the data centre for the plan, and where the host keeps its own backups;
- where support works from and whether it has access to the contents of servers;
- the transfer mechanism if data or access leaves the EEA: an adequacy decision or standard contractual clauses;
- how quickly the host notifies the customer of a data incident;
- the data centre's security certifications, such as ISO/IEC 27001, if your customers need them.

## Your duties on a VPS

On an unmanaged server, security measures inside the system, such as updates, key-based access, a firewall and encryption of disks and backups, are up to you: where to start is described in the article [First 10 steps after buying a VPS: security](https://accsly.io/en/vps/guide/vps-security-first-steps), and backups in the article [VPS backups](https://accsly.io/en/vps/guide/vps-backups). Under Article 33, the controller reports a serious breach to the supervisory authority within 72 hours, and the processor must notify the controller without undue delay. Fines for infringing the regulation can reach 20 million euros or 4% of the company's worldwide annual turnover, whichever is higher.

## FAQ

### Does the GDPR require data to be stored only in the EU?

No. Data may be transferred outside the EEA: to countries with a Commission adequacy decision, or on the basis of standard contractual clauses and other Chapter V mechanisms. Without such a basis, the transfer is unlawful.

### Is a host a controller or a processor?

For customer data on your server, the host is usually a processor, and the controller is the owner of the website or service. For your own account and payment data, the host acts as a controller.

### Do I need a DPA with a VPS host?

Yes, if the server stores personal data of people in the EU: Article 28 of the GDPR requires a contract between controller and processor. Hosts usually offer a DPA as part of their terms or sign one on request.

### Is a server in Germany enough to comply with the GDPR?

No. The location does not replace a data processing agreement, security measures and a lawful basis for processing. Besides, if the host or its support is outside the EEA, access to the data from there may also count as a transfer.

### Can data of Europeans be stored on a server outside the EU, for example in Russia?

Only on the basis of a Chapter V mechanism. Russia has no adequacy decision, so a transfer there is possible only with other mechanisms, such as standard contractual clauses and a risk assessment. In practice, data of people in the EU is easier to keep on a server in the EU.

### Does the GDPR apply to a company outside the EU?

Yes, if it offers goods or services to people in the EU or monitors their behaviour, for example through analytics. In that case, a company without an establishment in the EU usually appoints a representative in the Union.

_Updated: 2026-11-06_

# Hosting provider jurisdiction: what it affects

Every server has two countries: the one where the data centre stands and the one where the company renting it out is registered. According to the accsly.io catalog as of November 2026, these are different countries for 15% of VPS hosts. The first determines latency and the rules on where data is stored; the second determines the law of the contract, the court for disputes, the documents your accountant receives and whose authorities can request your data. Here is what each of them changes.

> Source: https://accsly.io/en/vps/guide/hoster-jurisdiction · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A host's jurisdiction is the law of the country that governs the hosting company and its contract with the customer. It is easy to confuse with the place where the server stands: a Dutch brand may rent out machines in Germany, a British company in Moscow and a Russian one in Kazakhstan. Below is how to find out where a host is registered, what that affects and what to check in the terms before paying. This article explains general rules and is not a substitute for advice from a lawyer.

## Two countries: the company and the data centre

In the accsly.io catalog, the country of a plan is always the place where the server stands. The company's country has to be looked up separately: in the contract or terms of service, on the legal information page, in the site footer or on the invoice. Hosts do not always state it. According to the accsly.io catalog as of November 2026, 1,935 of 2,242 VPS hosts (86%) name their legal entity, the country of registration can be established for 1,565 (70%), and 1,029 (46%) publish a company registration number or VAT number.

Where both countries are known, 208 of 1,397 hosts, or 15%, are registered in a country that is not among the countries of their servers. It is even more common for one company to have servers in several countries: that is the case for 975 hosts, half of those whose locations are known. The most common countries of registration are the US (139), the UK (136), Russia (124), Germany (75) and India (63).

The practical rule is simple. The data centre's country determines latency to your users and where the data physically sits; that is covered in the article [How to choose a country for your server](https://accsly.io/en/vps/guide/choose-server-country). The company's country determines everything legal: the contract, the court, taxes and obligations towards the state. A host is subject to the laws of both countries: the one where it is registered and the one where its equipment operates.

## Which law governs the contract

The governing law is usually stated in the terms in a single line: "this agreement is governed by the laws of…" and "disputes shall be resolved by the courts of…". For a company or a sole trader this choice is normally binding: by accepting the terms you agree to argue under the law and in the courts of the host's country. Suing abroad over a VPS that costs a modest monthly fee is almost never worth it, so for a business a clear complaints procedure matters more than the formal choice of law: where to write, how quickly they reply and how refunds are made.

Private customers have more protection. In the EU, under [Article 6 of the Rome I Regulation](https://eur-lex.europa.eu/eli/reg/2008/593/oj), a choice of foreign law does not deprive a consumer of the protection of the mandatory rules of the country where they live, provided the seller does business in that country or directs its activities there, for example with a site in the local language and prices in the local currency. Russia has a similar rule in [Article 1212 of the Civil Code](https://www.consultant.ru/document/cons_doc_LAW_34154/8b277bec1196471c8fd02da726b36d2116a708f4/); in the catalog, 161 hosts list roubles among their currencies. How this works for refunds is covered in the article [Free trials and money-back guarantees](https://accsly.io/en/vps/guide/trial-and-money-back). In other countries, it all depends on local law and the host's terms.

## Data requests from authorities

Every host complies with lawful requests from the authorities of its own country, and often of the country where the server stands as well. This is a normal part of the business, and what matters is not whether such obligations exist but what they are and how the host communicates them.

- **Russia.** Under [Article 10.2-1 of the Russian law on information](https://www.consultant.ru/document/cons_doc_LAW_61798/b99fcec60c7460838ae71cdd49a1bac4332fcb12/), hosting providers operating in Russia are entered in the Roskomnadzor register, identify their customers in the manner set by the government and cooperate with the bodies that carry out operational investigations. That is why a Russian host asks you to confirm your identity or company details at sign-up.
- **European Union.** Since 18 August 2026, the [e-evidence Regulation 2023/1543](https://eur-lex.europa.eu/eli/reg/2023/1543/oj) applies: a court or prosecutor in one EU country can request data directly from a provider offering services in the EU, including when the provider is registered in another member state.
- **United States.** Under the CLOUD Act, a US company must hand over data at the request of US authorities even if the server is located outside the country. How this relates to European rules was analysed by the [European Data Protection Board and the European Data Protection Supervisor](https://www.edpb.europa.eu/documents/edpb-correspondence/edpb-edps-joint-response-to-the-libe-committee-on-the-impact-of-the_en).

The conclusion for your choice: data on a server is subject to at least two legal systems, and the more countries in the chain of company, data centre and support team, the more rules apply to it. If you store other people's personal data, take this into account in your own documents: see the articles [152-FZ and hosting](https://accsly.io/en/vps/guide/152-fz-and-hosting) and [GDPR and choosing a host](https://accsly.io/en/vps/guide/gdpr-and-hosting). In the host's terms, it is worth finding the section on how it handles requests from authorities and whether it notifies the customer where the law allows.

## Payments and restrictions

The company's country also shapes the payment side. A host works with the banks and payment systems of its country and follows its sanctions and currency rules. In practice this means that hosts have different rules on which countries they accept customers from and which cards and payment methods are available. 271 hosts in the catalog state explicitly that they accept customers from Russia. If the terms say nothing about your country, ask support before paying, not after.

Restrictions change along with laws and payment system rules, so for an important project keep a backup with another host in another jurisdiction: that way a change of rules at one company will not stop your work. How to set up copies is described in the article [VPS backups](https://accsly.io/en/vps/guide/vps-backups). And give your real details at sign-up: if they do not match, the host is entitled to block the account under its terms.

## Invoices, VAT and documents

For a company or a sole trader, the host's jurisdiction decides which documents the accounts department will receive.

- **Within the EU**, hosting is an electronically supplied service, and under the [VAT Directive](https://eur-lex.europa.eu/eli/dir/2006/112/oj) it is taxed where the customer is. A company with a VAT number usually receives an invoice from a European host without VAT under the reverse-charge mechanism and accounts for the tax itself, while a private customer pays the VAT of their own country.
- **A host outside your country** issues an invoice under its own rules. Many countries have their own regime for digital services bought from abroad, so check whether the price includes VAT or sales tax or whether you have to account for it yourself. Plans from hosts that invoice companies are collected in [VPS paid by invoice](https://accsly.io/en/vps/pay-by-invoice).
- **A Russian host** invoices in roubles and issues Russian closing documents. Under [Article 174.2 of the Russian Tax Code](https://www.consultant.ru/document/cons_doc_LAW_28165/ae4f89299a9012dee14fc5628d79101eb39263f8/), hosting is an electronic service: when a Russian company buys it from a foreign host, the buyer calculates and pays the VAT as a tax agent, and when a private person buys it, the foreign company registered with the Russian tax authority pays the tax.

Because of tax and currency, prices that look the same at two hosts can differ by a fifth or more. How to compare them with this in mind is explained in the article [How to compare VPS prices](https://accsly.io/en/vps/guide/compare-vps-prices-per-resource), and plans you can pay for with an international card are collected in [VPS paid by international card](https://accsly.io/en/vps/pay-with-foreign-card).

## What to check before paying

- the full company name, country and registration number, in the terms or on the legal information page, not only in the site footer;
- the country and city of the data centre for the chosen plan, and where the host keeps its own backups;
- the governing law and the court for disputes, the complaints procedure and response times;
- the terms for refunds and account closure, including closure at the host's initiative;
- which documents you will receive and whether VAT is included;
- whether customers from your country are accepted and which payment methods are available;
- whether there is a section on requests from authorities and a data processing agreement, if you handle personal data.

If a host does not name its legal entity at all, that is not always a sign of poor service, but it does mean that in a dispute it is unclear whom to turn to. For a server running a business project, weigh this condition as seriously as price and latency.

## FAQ

### What is a hosting provider's jurisdiction?

It is the country where the hosting company is registered and the law that governs its contract with the customer. It may differ from the country of the data centre: according to the accsly.io catalog as of November 2026, this is the case for 15% of VPS hosts for which both countries are known.

### How do I find out where a host is registered?

Look at the terms of service or contract, the legal information page, the site footer and the invoice: they give the name of the legal entity, its country and registration number. If none of them do, ask support in writing.

### What matters more for a website: the company's country or the server's country?

The server's country matters for speed and for where personal data is stored. The company's country matters for the contract, disputes, taxes and documents. You need to consider both.

### Do consumer protection laws of my country apply if the host is foreign?

They may. In the EU, the Rome I Regulation keeps the mandatory consumer protection of your country of residence if the seller directs its business there, for example in your language and currency; Russia has a similar rule in Article 1212 of its Civil Code. This does not apply to companies.

### Who pays VAT when buying hosting from a company in another country?

Within the EU, a business with a VAT number usually accounts for it itself under the reverse charge, while a private customer pays the VAT of their own country through the host. Elsewhere it depends on local rules for digital services, so check whether the price includes tax.

### Can authorities of another country request data from my server?

Yes: a host complies with lawful requests from the country where it is registered and usually from the country where the server stands. If the server holds customers' personal data, take this into account when choosing a host and in your own data protection documents.

_Updated: 2026-11-06_

# How to compare VPS prices: the price of a resource unit

A plan's price tells you how much you will pay, but not how much you get for that money. According to the accsly.io catalog as of November 2026, a gigabyte of memory on a 1 GB plan costs a median $8.00 a month, while on a 4 GB plan it costs $5.00. Here is how to work out the price per vCPU, per gigabyte of memory and of disk, and what to bring to a common basis before you compare two offers.

> Source: https://accsly.io/en/vps/guide/compare-vps-prices-per-resource · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

Two plans at $18 a month can differ twofold in memory, and a $15 plan can end up costing more than a $21 one once you add VAT, a separate IP address and a setup fee. For a fair comparison, divide the price by what you are actually buying and bring the terms to the same form. Below is how to do it and which figures to check yourself against.

## Why the plan price tells you little

A plan is a bundle: processor, memory, disk, bandwidth and an address. The host sells it at one price, and every line-up has its own proportion of resources. Let us look at a typical "ladder" of plans: the median prices for four common configurations according to the accsly.io catalog as of November 2026. These are VPS plans in stock with monthly billing. The catalog keeps prices in roubles; the dollar figures are converted at the Central Bank of Russia rate of 5 November 2026, and whether VAT is included depends on the host.

| Configuration | Monthly price, median | Per 1 GB of memory | Per 1 vCPU | Per 1 GB of disk |
| --- | --- | --- | --- | --- |
| 1 vCPU, 1 GB, 20 GB | $8.00 (1,553 plans) | $8.00 | $8.00 | $0.37 |
| 2 vCPU, 4 GB, 60 GB | $20.78 (2,354) | $5.20 | $10.40 | $0.35 |
| 4 vCPU, 8 GB, 120 GB | $40.00 (2,247) | $5.00 | $10.01 | $0.33 |
| 8 vCPU, 16 GB, 240 GB | $78.65 (1,304) | $4.92 | $9.84 | $0.33 |

The disk size in the first column is the median for that pair of cores and memory. A gigabyte of memory on the smallest plan costs one and a half times as much as on the 4 GB plan, and beyond that the price per gigabyte barely changes. With the processor it is the other way round: the smallest plan is the cheapest per vCPU, because each core comes with only a gigabyte of memory. The conclusion is simple: "cheaper" only makes sense in relation to the resource your workload needs.

Individual hosts show the same picture. Of the 2,010 hosts that have at least three monthly-billed plans in the catalog, 686 have a cheapest plan that is the most expensive in their line-up per gigabyte of memory, and at 1,154 it costs more than the line-up's average price per gigabyte.

## How to calculate the unit price

The formula is always the same: the monthly price after all the adjustments described below, divided by the amount of the resource. Divide by the resource that will limit you first:

- **Memory** for CMS-based sites, databases, Java and Node.js applications and containers. It is most often memory that decides whether a plan is enough; how to estimate it is explained in the article [How much memory and CPU a website needs](https://accsly.io/en/vps/guide/ram-and-cpu-for-website).
- **vCPU** for builds, transcoding, calculations and other jobs that keep the processor busy for a long time.
- **Disk** for backups, file storage and logs. Here the price per gigabyte is compared separately for NVMe, SSD and HDD.

Dividing the whole price by a single resource overstates its cost, since the price also covers everything else. To see what the price is made of, we broke the catalog plans' prices down into components with median regression, for plans with up to 16 vCPU, 64 GB of memory and 1 TB of disk. The result is roughly $2.55 per vCPU, $1.47 per gigabyte of memory, $0.08 per gigabyte of disk and about $3 a month for the server itself: the address, a slot in the control panel, support and billing. This fixed part is what makes small plans expensive per unit. The estimate is rough but useful as a benchmark: by it, a plan with 2 vCPU, 4 GB and 60 GB is worth about $19, and an offer well above that should be checked for hidden advantages, or skipped.

## Not all units are equal

A unit price is only comparable between identical units. Before you divide, check three things.

- **What kind of vCPU.** A shared core and a dedicated core cost differently and behave differently under sustained load; the difference in clock speed and processor generation is also large. Compare the price of a vCPU within one class, and read about what hides behind the word "core" in the article [How to read a host's plans: hidden limits](https://accsly.io/en/vps/guide/hidden-limits-in-hosting-plans).
- **What kind of disk.** According to the accsly.io catalog as of November 2026, the median price per gigabyte is $0.30 for NVMe plans, $0.38 for SSD and $0.11 for HDD. NVMe is on average no more expensive than SSD, because many hosts have already moved their main line-ups to it; the speed difference is covered in the article [NVMe or SSD](https://accsly.io/en/vps/guide/nvme-or-ssd). HDD is three times cheaper, but it suits archives, not databases.
- **What kind of port.** A 100 Mbit/s port and a 1 Gbit/s port with the same cores and memory are different plans. If the server delivers files, also work out the price per terabyte of traffic.

## What to bring to a common basis

Even with identical resources, the prices on plan cards are often calculated differently. Before comparing, convert each one into the same figure: what you will pay per month for the chosen term, including tax and mandatory extras.

- **Billing term.** Many hosts show the monthly price for annual or three-year billing. According to the accsly.io catalog as of November 2026, 4,897 VPS plans have a separate price for a longer term, and at the median it is 17% below the monthly one. Compare prices for the same term, and remember that a long term is paid upfront.
- **VAT and sales tax.** Some hosts quote prices with tax, others without it, so look for "incl. VAT" or "excl. VAT" next to the price. In the EU, VAT on electronically supplied services to private customers is charged at the rate of the customer's country, while a business with a valid VAT number is usually invoiced without VAT and accounts for it itself under the [reverse charge procedure](https://europa.eu/youreurope/business/taxation/vat/cross-border-vat/index_en.htm). Russian hosts quote prices with or without Russian VAT, which has been 22% since 1 January 2026 ([Federal Tax Service of Russia](https://www.nalog.gov.ru/rn26/news/smi/16596761/)), and some on the simplified tax system charge no VAT at all; ask what applies to a customer abroad. Elsewhere, local VAT, GST or sales tax may be added at checkout.
- **IPv4.** One address is usually included in the plan, but not always: the catalog has 236 VPS plans at 28 hosts that come with no IPv4 at all. An extra address costs a median $2.20 a month, which is a noticeable surcharge on a cheap plan. More on this in the article [IPv4 and IPv6 on a server](https://accsly.io/en/vps/guide/ipv4-and-ipv6-on-server).
- **Setup fee.** It is rare for a VPS: 502 plans, or 2% of the catalog, with a median one-off fee of $8.82, about a quarter of the monthly price. Divide it by the number of months you intend to pay for.
- **Traffic.** Traffic terms are known for 19,830 plans, and 11,236 of them have a quota, a median of 5 TB a month. If your server will exceed it, add the overage charges to the price; what happens after the quota is covered in the article [Server bandwidth and traffic](https://accsly.io/en/vps/guide/server-bandwidth-and-traffic).
- **Currency.** 93% of the VPS plans in the catalog are priced in a currency other than the rouble, most often US dollars and euros; the rest are mostly Russian hosts that charge in roubles. If you pay in dollars for a plan priced in euros or roubles, its cost moves with the exchange rate: a €20 plan cost $22.47 at the Central Bank of Russia cross rate of 5 November 2026, and a 5% move in the euro shifts that by about $1.10 a month. Your bank or payment provider may also charge a currency conversion fee, so calculate at the rate you actually pay, fees included.

## A worked example

Take two offers with identical resources, 2 vCPU, 4 GB of memory and 60 GB of disk, and figures close to the catalog medians. Plan A costs $20.78 a month including VAT, billed monthly, with IPv4 and setup included. Plan B is advertised as "$17.25 a month": that is the price with annual billing and without VAT, an IPv4 address costs $2.20 a month, and setup is a one-off $5.20.

| Item | Plan A | Plan B |
| --- | --- | --- |
| Server for 12 months | $249.36 | $207.00 |
| IPv4 for 12 months | included | $26.40 |
| Setup | included | $5.20 |
| VAT 22% | included | $52.49 |
| Total for the year | $249.36 | $291.09 |
| Per month | $20.78 | $24.26 |

The plan that looked 17% cheaper on its card is actually 17% more expensive. And if the project closes after three months or the server does not suit you, plan A will have cost you $62.34, while for plan B you will have paid the whole annual sum, unless the host refunds the unused term. That is why the billing term is compared not only by price but also by risk; refunds and trial periods are covered in the article [Trial periods and money-back guarantees](https://accsly.io/en/vps/guide/trial-and-money-back).

## How to compare, step by step

1. Identify the resource that will limit your workload first, and the minimum amounts of the others.
2. Shortlist plans with suitable resources of the same class: the same type of cores and disk and the same port speed.
3. Bring the prices to one billing term, one tax treatment and one currency.
4. Add the mandatory extras: IPv4, the setup fee spread over the term, traffic above the quota, licences.
5. Divide the total by the amount of the main resource and compare the unit prices.
6. For the best two or three, check what a number cannot express: disk and network speed on a test server, support and refund terms.

Plans with the memory you need are easier to find in the catalog's selections: [cheap VPS with 2 GB](https://accsly.io/en/vps/cheap-2-gb), [cheap VPS with 4 GB](https://accsly.io/en/vps/cheap-4-gb) and [cheap NVMe VPS](https://accsly.io/en/vps/cheap-nvme); all low-cost plans are collected on the [cheap VPS](https://accsly.io/en/vps/cheap) page. How to choose a configuration from scratch is described in the article [How to choose a VPS](https://accsly.io/en/vps/guide/how-to-choose-vps).

## FAQ

### How do I calculate the price of a VPS per gigabyte of memory?

Divide the plan's monthly price by the amount of memory in gigabytes, after bringing the price to one billing term and adding VAT and mandatory extras. According to the accsly.io catalog as of November 2026, the median ranges from $8.00 per gigabyte on 1 GB plans to $4.92 on plans with 8 vCPU and 16 GB.

### Why are small VPS plans more expensive per resource?

Every plan's price contains a fixed part: the IP address, a slot in the control panel, support and billing. In the accsly.io catalog it comes to about $3 a month, which is more than a third of an $8 plan but only a few percent of a $73 plan.

### How much does a vCPU cost on a VPS on average?

If you break the prices of the accsly.io catalog plans down into components, as of November 2026 it comes to about $2.55 a month per vCPU, $1.47 per gigabyte of memory and $0.08 per gigabyte of disk. Dedicated and high-frequency cores cost more than shared ones.

### Is VAT included in a VPS price?

It depends on the host: some show prices with tax, others without it. In the EU, private customers pay VAT at their own country's rate on such services, while businesses with a VAT number are usually invoiced without VAT under the reverse charge. Russian hosts quote prices with or without Russian VAT of 22%. Check the note in the price list or the contract.

### Is it worth paying for a VPS a year in advance?

According to the accsly.io catalog as of November 2026, a longer billing term is a median 17% cheaper than monthly billing. It pays off if you are sure of the host and of the project's lifetime: not every host refunds the unused months if you cancel early.

### Is NVMe more expensive than SSD on a VPS?

Not on average: according to the accsly.io catalog as of November 2026, a gigabyte of disk on NVMe plans costs a median $0.30 a month and on SSD plans $0.38. Only HDD is cheaper, about $0.11 per gigabyte, but it suits archives rather than databases.

_Updated: 2026-11-05_

# SLA and uptime: what hosts promise

An SLA of 99.9% allows a host 43 minutes of downtime a month, 99.99% about four. But a percentage in an advert is not yet a commitment: the commitment is the document that says what counts as downtime, what is excluded and how much you get back. Most often that is a discount on the next invoice, not money. Here is how to read such documents and how to check availability yourself.

> Source: https://accsly.io/en/vps/guide/sla-and-uptime · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

An SLA (Service Level Agreement) is the part of the contract in which a host promises a certain level of availability and describes what happens if it fails to deliver. Uptime is the share of time the service was working. Below is how to turn percentages into minutes, what hosts actually promise, what exactly an SLA compensates and why you will not get compensation without your own monitoring.

## What the percentages mean in minutes

The difference between 99.9% and 99.99% looks like rounding, but in minutes it is tenfold. For a 30-day month and a year, not counting planned maintenance:

| Availability | Allowed downtime per month | Per year |
| --- | --- | --- |
| 99% | 7 h 12 min | 87 h 36 min |
| 99.5% | 3 h 36 min | 43 h 48 min |
| 99.9% | 43 min 12 s | 8 h 46 min |
| 99.95% | 21 min 36 s | 4 h 23 min |
| 99.99% | 4 min 19 s | 52 min 34 s |
| 99.999% | 26 s | 5 min 15 s |

A single three-hour outage in a 30-day month brings availability down to 99.58%. Rebooting a host to update its kernel takes several minutes, so 99.99% for a single physical server is an almost impossible promise: it becomes realistic when machines run on several hosts and are moved between them without stopping. Mind the length of the month too: in a 31-day month, 99.9% already means 44 minutes 38 seconds.

## What hosts promise

According to the accsly.io catalog as of November 2026, 1,479 of 2,242 VPS hosts state their availability, and 1,409 of them give a specific percentage. Taking the highest figure each host names, the picture is as follows:

- 99.9%: 720 hosts, or 51%;
- above 99.9% but below 99.99% (usually 99.95% or 99.98%): 161, or 11%;
- from 99.99% to 99.999%: 327, or 23%;
- 100%: 86, or 6%;
- below 99.9%: 115, or 8%.

At 150 hosts the description contains two or more different figures: one on the home page and another on the plan page or in the terms, sometimes a different one for the network and for the servers. Only 62 hosts mention compensation in the terms recorded in the catalog. That does not mean the others have none, but it does mean you will not find it on the visible pages of their site: you need the document itself.

## What an SLA actually pays

An SLA almost never covers your losses; it returns part of the fee for the service, and most often not as money but as a discount. This is easy to see in the documents of large cloud platforms that publish their SLAs in full.

- [The SLA of one international cloud platform](https://cloud.google.com/compute/sla) promises 99.9% for a single virtual machine and, if this is breached, gives a credit of 10% of the monthly bill for that machine when availability was between 95% and 99.9%, 25% between 90% and 95%, and 100% below 90%. The credit goes towards future payments and cannot exceed the monthly bill for the service.
- [The SLA of the largest international platform](https://aws.amazon.com/compute/sla/) promises only 99.5% for a single machine, and 99.99% for machines deployed across several availability zones. The credits are 10%, 30% and 100% on similar steps, and they are not paid out as money.
- [A large Russian cloud's agreement](https://yandex.ru/legal/cloud_sla) states plainly that compensation is a discount that reduces the cost of services, not a cash payment, and that it cannot exceed the cost of the service for the billing period.

Let us work through an example. A VPS at $21 a month was down for three hours, so availability was 99.58%. Under the first scheme you are entitled to 10%, that is a $2.10 discount on next month. Under the second, with a 99.5% threshold, you get nothing: three hours fit within the promise. If an online shop lost orders during those three hours, the SLA will not cover them. So an SLA is a lever on the host and a signal of how confident it is in its infrastructure, not business insurance.

## Exclusions and claim deadlines

The key part of an SLA is not the percentage but the list of what does not count as downtime. Typical items appear in almost every document:

- **Planned maintenance.** In the Russian cloud's agreement from the example above, maintenance announced three days in advance is not counted as an interruption, and downtime caused by preventive and emergency work of up to 8 hours per billing period is not compensated.
- **Customer actions.** A misconfigured firewall, a full disk or a crashed application is not the host's downtime.
- **External causes.** Force majeure, orders from government authorities and often DDoS attacks. What changes during an attack is covered in the article [DDoS protection at hosts](https://accsly.io/en/vps/guide/ddos-protection-at-hosters).
- **Rule violations and unpaid bills.** If the server was suspended for breaking the terms of use or the invoice is overdue, there will be no compensation.
- **What exactly is measured.** Some SLAs measure the availability of the data centre network, others that of the host, others that of your machine. Under the international cloud's document, downtime means losing external connectivity or access to the disk, and only periods of one minute or longer count.

Compensation is almost never applied automatically: you have to claim it. The deadline is limited: 30 calendar days from the incident in the Russian cloud's agreement, 60 days at one international platform, and the end of the second billing cycle at the other. The claim must include the date and time of each incident, and the international documents explicitly require logs that show the downtime. Miss the deadline and you lose the right to compensation.

## Uptime without an SLA document

"99.99% uptime" on the home page and an SLA are different things. The figure in an advert promises nothing unless there is a section of the contract or a separate document behind it. Before buying, find that document and check:

- over what period availability is measured: a month, a quarter or a year;
- what counts as downtime and from what minimum duration;
- which work and events are excluded and how planned maintenance is announced;
- how much is compensated at each availability step and whether there is a cap;
- in what form: money, account credit or extra days;
- how and by when to file a claim and what evidence is needed.

If there is no such document, ask support in writing. An answer like "everything is stable here" without a reference to the terms means there is no availability commitment. That does not necessarily make it a bad host, but comparing it by percentage is pointless. A promise of 100% is also worth a question: what will the host give back when that percentage is inevitably missed?

## How to check availability yourself

The host measures availability with its own data, and the customer's data often settles a dispute. You need an external check that does not run on the same server, and preferably not at the same host: an HTTP or ping probe once a minute, a log with the exact start and end time of every failure, and an alert to a messenger or email. How to set this up for free is described in the article [Server monitoring: uptime, load, alerts](https://accsly.io/en/vps/guide/server-monitoring-uptime-alerts), and plans for a monitoring server are collected in the selection [VPS for monitoring](https://accsly.io/en/vps/for-monitoring).

If an outage happens, save the log and file the claim straight away rather than at the end of the month: state the start and end time, the server's address and what exactly was unavailable. A month with several short outages is also worth adding up, as the total may cross the SLA threshold.

## If availability really matters

No SLA makes a single server more reliable: it only distributes responsibility. If an hour of downtime costs more than the monthly fee for the server, build failure into the architecture:

- keep a backup on another server and test restoring it, see the article [VPS backups](https://accsly.io/en/vps/guide/vps-backups);
- for an important service, run a second server in another location or at another host and switch traffic via DNS or a load balancer;
- on a physical machine, put the disks in RAID and find out how quickly hardware is replaced; the differences from a VPS are covered in the article [Dedicated server or VPS](https://accsly.io/en/vps/guide/dedicated-or-vps).

Two 99.9% servers at different hosts, with independent failures, together give more than one server promised at 99.99%, and they usually cost less than one server with real guarantees at that level.

## FAQ

### How much downtime does a 99.9% SLA allow?

43 minutes 12 seconds in a 30-day month and about 8 hours 46 minutes a year. For 99.95% it is 21 minutes 36 seconds a month, and for 99.99% 4 minutes 19 seconds.

### What does a host pay if it breaches the SLA?

Usually a share of the monthly fee for the affected service, for example 10%, 25% or 100% depending on the actual availability. Most often it is a discount on the next invoice rather than money, and the amount does not exceed the monthly fee.

### Does an SLA compensate business losses from downtime?

No. An SLA returns part of the fee for the service; lost revenue and lost data are not covered. Backups and a second server protect you from losses, not an agreement.

### What uptime do VPS hosts promise?

According to the accsly.io catalog as of November 2026, 51% of the hosts that give a percentage promise 99.9%; 29% promise 99.99% or more, and 6% claim 100%. Only a handful mention compensation on the visible pages of their site.

### How do I get compensation under an SLA?

Write to the host within the deadline set in the agreement, usually 30 to 60 days, with the date and time of each outage and the log from your external monitoring. Compensation is rarely applied automatically: without a claim you usually get nothing.

### Does planned maintenance count as downtime?

As a rule, no, if the host announced it in advance in the way the SLA describes. Some agreements also do not compensate emergency work up to a certain total duration, for example up to 8 hours per billing period.

_Updated: 2026-11-05_

# Free trials and money-back guarantees

There are two ways to test a server before paying for a month or a year: a free trial or a money-back guarantee. According to the accsly.io catalog as of November 2026, 11% of VPS hosts offer a trial and 36% a money-back guarantee. But at many of them the terms apply only to shared hosting, only to the first order or only to card payments. Here is what to check so that the guarantee actually works.

> Source: https://accsly.io/en/vps/guide/trial-and-money-back · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A server is hard to judge from its description: disk speed, latency to your users, network stability and the quality of support only show up in use. That is why the terms for trying a server sometimes matter more than a difference in price. Below is how a trial differs from a refund, how many hosts offer each option, which restrictions appear in the terms and how to use the trial days to find out whether the server suits you.

## Trial, refund and hourly billing

- **A free trial** gives you a server for a few days without payment. Sometimes the trial is paid but costs a token amount, and sometimes instead of a server you get credit on your balance to spend within the period.
- **A money-back guarantee** means you pay upfront, and if you cancel within the stated period, the host refunds the payment in full or minus a part of it.
- **Hourly billing** is not a guarantee, but it works in a similar way: you can delete the server after a day and pay only for that day. When this pays off is covered in the article [Hourly VPS billing: when it pays off](https://accsly.io/en/vps/guide/hourly-billing-when-worth-it).

A trial is safer for the buyer: no money changes hands, so there is nothing to dispute. A refund requires action and trust that the host will keep its promise, but it lets you test exactly the plan you are buying rather than a cut-down trial version.

## How many hosts offer trials and refunds

According to the accsly.io catalog as of November 2026, of 2,242 VPS hosts, 248, or 11%, state a trial period and 813, or 36%, a money-back guarantee. 81 hosts offer both, and 980, or 44%, offer at least one of them.

|  | Free trial | Money-back guarantee |
| --- | --- | --- |
| Hosts offering it | 248 | 813 |
| Most common period | 7 days (65 hosts) and 30 days (62) | 30 days (467) |
| Other common periods | 14 days (41), 3 days (27) | 7 days (104), 14 days (80), 15 days (43) |
| Median period | 14 days | 30 days |

These figures are an upper bound for VPS. Many hosts sell both shared hosting and virtual servers, and their terms often apply only to hosting. Of the 244 trials described in the catalog, only 66 explicitly name VPS or servers, 77 apply to hosting, and the rest do not specify the product. Refunds are similar: at roughly a hundred of the 813 hosts, the guarantee as described covers only hosting or explicitly excludes VPS. So look not at the "30-day guarantee" badge on the home page but at the refund terms for the specific service.

## Typical trial conditions

A free server is an easy target for abuse, so hosts protect their trials with conditions. The trial descriptions in the catalog include:

- **Trial on request.** The server is not issued automatically but through a ticket or chat, sometimes only to companies and sole traders or for large orders.
- **Identity confirmation.** Linking a bank card or a phone number, less often an ID document check. Some hosts, on the contrary, state "no card required".
- **A cut-down server.** Fewer resources than the paid plan, limited traffic, port 25 closed for mail.
- **A paid trial with auto-renewal.** A few days for a token sum, after which the monthly plan is charged to your card automatically. If the server does not suit you, cancel the subscription before the trial ends.
- **Data deletion.** When the trial ends, the server is deleted along with its contents, and it cannot always be moved to a paid plan. Do not keep anything on a trial server that is not stored elsewhere.

## Typical refund conditions

Refund terms are described in the catalog for 794 of the 813 hosts with a guarantee. The notes are short, so the figures below are minimums: this many hosts mention the condition explicitly.

- **First order or new customers only**: at least 48. A repeat order, a renewal or a second server is usually not refunded.
- **VPS and dedicated servers excluded**: at least 34 hosts explicitly exclude VPS, another 66 give the guarantee only for hosting, and at least 53 exclude dedicated servers. There are also exclusions for custom configurations and hourly-billed servers.
- **Extras are not refunded.** Domains are mentioned by 90 hosts, licences by 25 and setup fees by 17. If you bought a Windows or control panel licence with the server, you will get back less than you paid.
- **Depends on the payment method**: at least 51. Payments in cryptocurrency and via some payment systems are refunded only to the account balance with the host or not at all; money goes back to a card only if you paid by card.
- **Fees are withheld**: at least 18 deduct the payment gateway fee or a fixed charge from the refund.
- **Usage limits**: at a few hosts the refund does not apply if a noticeable share of the traffic or resources has been used.
- **Breach of the rules.** If the server was suspended for violating the terms of use, almost no host will give a refund.

Also check how the period is counted: from payment, from registration or from the moment the server is delivered, in calendar days or in hours. "72 hours" and "3 days" at different hosts are counted from different events.

## Refunds for the unused term

A money-back guarantee is a voluntary promise by the host, but consumers may also have rights under the law. In the EU, a consumer who buys a service online has, under the Consumer Rights Directive 2011/83/EU, a [right to withdraw from a distance contract within 14 days](https://europa.eu/youreurope/citizens/consumers/shopping/returns/index_en.htm) without giving a reason. If you asked for the server to be activated during those 14 days, which is the usual case with hosting, you can still withdraw but pay a proportionate amount for the time it was provided. These rules protect private customers, not businesses, and outside the EU what you are entitled to depends on local law and on the host's own terms. Russian hosts usually refund the unused part of a prepayment under Russian consumer law, sometimes minus the discount for the long term. In the catalog, at least 70 hosts explicitly mention a pro-rata refund for the unused term.

## ID checks

Trials and refunds are often tied to identity verification: the host wants to make sure that a free server goes to a real person and that money is returned to whoever paid. In the catalog, an ID check at sign-up is noted for 41 VPS hosts and no check for 71; for the rest the condition is not stated. If you are not prepared to send documents, clarify this before paying: if you refuse a check after payment, the refund may take longer.

## What to check before paying

1. Find the refund or trial terms in the contract or terms of service, not just on the home page.
2. Make sure they cover VPS and the location you have chosen, not only shared hosting.
3. Check when the period starts and whether the guarantee applies to your payment method.
4. See what is not refunded: setup, licences, domains, fees, the discount for a long term.
5. For a paid trial, turn off auto-renewal if you are not sure you will buy.
6. Save the correspondence and the terms as of the purchase date: the rules may change.

## How to use the trial days

The period is short, so plan your tests in advance. In the first hours, measure ping to your users, disk speed and download speed; how to do this is described in the article [How to check VPS ping and speed](https://accsly.io/en/vps/guide/check-vps-speed-before-buying). Then deploy your real workload on the server and set up external monitoring to see its stability over several days. Ask support one technical question and time the answer. If the server does not suit you, request the refund a few days before the period ends, not on the last day.

Hosts with a free trial are collected in the selection [VPS with a free trial](https://accsly.io/en/vps/free-trial), those with a money-back guarantee in [VPS with a money-back guarantee](https://accsly.io/en/vps/moneyback), and those with hourly billing in [VPS with hourly billing](https://accsly.io/en/vps/hourly-billing). How to compare the prices of the plans you find is explained in the article [How to compare VPS prices](https://accsly.io/en/vps/guide/compare-vps-prices-per-resource).

## FAQ

### How does a free trial differ from a money-back guarantee?

A free trial is a server for a few days without payment. With a money-back guarantee you pay upfront and get your money back if you cancel within the period. A trial is safer, while a refund lets you test exactly the plan you are buying.

### How many VPS hosts offer a free trial?

According to the accsly.io catalog as of November 2026, 248 of 2,242 VPS hosts, or 11%, state a trial period, most often 7 or 30 days. But some of these trials apply only to shared hosting, not to servers.

### How long is a money-back guarantee usually?

Most often 30 days: that is the case at 467 of the 813 VPS hosts with a guarantee in the accsly.io catalog. Periods of 7, 14 and 15 days also occur, and some hosts give only 24 to 72 hours.

### Will I get a refund for a VPS paid in cryptocurrency?

Often only to your account balance with the host, or not at all: refunds depend on the payment method, and many hosts return money to a card only if you paid by card. Check this in the terms before paying.

### Can I get a refund for the unused months of a VPS?

Only if the host's terms or the law provide for it. In the EU, a consumer can withdraw from an online service contract within 14 days, paying a proportionate amount if the server was activated at their request; after that, refunds depend on the host's terms. Outside the EU it depends on local law and the host; Russian hosts usually refund the unused prepayment to private customers under Russian consumer law.

### What is usually not refunded under a guarantee?

Setup fees, licences, domains, payment system fees and repeat orders. Some hosts exclude VPS and dedicated servers from the guarantee entirely, keeping it only for shared hosting.

_Updated: 2026-11-05_

# Cloud server or VPS

A cloud server and a VPS are usually the same KVM virtual machine. The difference lies in what surrounds it: a cloud sells resources by the hour through an API and offers network disks, snapshots and ready-made services, while a classic VPS is a fixed monthly plan with a local disk and a traffic allowance. Here is which of this you actually need and what it costs.

> Source: https://accsly.io/en/vps/guide/cloud-or-vps · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

Hosts put the word "cloud" on all kinds of plans, so the name alone says little. It is more useful to look at how the server is billed, where its disk lives and what you can do without contacting support. Below is how a cloud platform differs from a classic VPS, what equal configurations cost according to the accsly.io catalog and where the extra costs of a cloud hide.

## What a cloud server is

A cloud server (an instance) is a virtual machine that you create, change and delete yourself, in a panel or through an API. Inside it is the same full virtualization as a good VPS; what differs is everything around it:

- **Paying for time.** Resources are billed by the hour, and on some platforms by the second: for example, at one of the largest international platforms Linux machines are [billed per second](https://aws.amazon.com/ec2/pricing/on-demand/) with a one-minute minimum. Delete the machine and the charges stop.
- **API and automation.** Machines, disks, networks and addresses are created with API requests or from Terraform. This matters when servers are spun up for a job and disappear after it: builds, tests, data processing.
- **Resizing.** Processor and memory change with a reboot, and a disk grows without reinstalling.
- **Snapshots and images.** A disk snapshot takes minutes, and from it you can bring up a copy of the server or roll back after a failed update.
- **Ready-made services.** Object storage, managed databases, load balancers, private networks between machines.

A classic VPS is a plan with fixed resources and a monthly price. The disk is usually local, NVMe or SSD inside the same server, traffic comes as an allowance or unmetered, and management goes through the host's panel. Many hosts have added hourly billing, snapshots and an API to their VPS plans, so the line between the two models is blurred. How VPS and VDS are organised is covered in the article [VPS or VDS](https://accsly.io/en/vps/guide/vps-vs-vds).

## Network disk and local disk

The main technical difference of a cloud is where the disk is stored. In a cloud it is usually a volume in distributed storage. For example, [Ceph RBD](https://docs.ceph.com/en/latest/rbd/) block devices, according to the project documentation, take up space as data is written, spread data across many storage nodes and support snapshots and replication. Hence the cloud's advantages: the disk survives the failure of a physical server, the machine can be restarted on another host, and a snapshot does not require a shutdown.

The price of this is latency. Every write travels over the network to several nodes, so the same database query runs slower on a network disk than on local NVMe. For a site or an API this is usually unnoticeable; for a busy database it is noticeable. Some platforms offer fast local disks, but without restarting on another host. How to test a disk before paying is explained in the article [How to check VPS ping and speed](https://accsly.io/en/vps/guide/check-vps-speed-before-buying), and the difference between NVMe and SSD in [NVMe or SSD](https://accsly.io/en/vps/guide/nvme-or-ssd).

## Object storage and managed databases

Object storage holds not a disk but files, called objects, in containers called buckets, and you work with it over HTTP. The most common interface is S3: according to the [S3 documentation](https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html), an object is a file with its metadata, a bucket is a container for objects, and access goes through a REST API. S3-compatible storage is offered by many cloud platforms and by some VPS hosts. It is a convenient place for backups, images and user uploads, so the server's disk does not keep growing. A backup scheme is described in the article [VPS backups](https://accsly.io/en/vps/guide/vps-backups).

A managed database is PostgreSQL, MySQL or Redis whose updates, replicas and backups are handled by the platform. You pay more than for the same database on your own VPS, but you do not administer it. If you install the database yourself, see the selections [VPS for a database](https://accsly.io/en/vps/for-database) and [VPS for PostgreSQL](https://accsly.io/en/vps/for-postgresql).

## What an equal configuration costs

The accsly.io catalog has no separate "cloud" label, so we compared two groups of hosts as of November 2026. Cloud-type: 94 hosts that have both hourly billing and an API. Classic: 152 hosts that have no hourly billing. We took VPS plans in stock with monthly billing. The catalog keeps prices in roubles; the dollar figures are converted at the Central Bank of Russia rate of 4 November 2026 and rounded. Prices are per month; whether VAT is included depends on the host.

| Configuration | Median plan: cloud-type | Median plan: classic | Cheapest plan per host, median: cloud-type / classic |
| --- | --- | --- | --- |
| 2 vCPU, 4 GB | $29 (185 plans) | $19 (175) | $15.50 / $15 |
| 4 vCPU, 8 GB | $63 (192) | $38 (167) | $36 / $33 |
| 8 vCPU, 16 GB | $170 (135) | $68 (110) | $75 / $62 |

If you compare the hosts' cheapest offers, the difference is small, from 2 to 22%. But a typical cloud-type plan costs one and a half to two and a half times more: these hosts' line-ups have more expensive variants of the same configuration, and those are what pull the median up. So compare specific plans, not the word "cloud". Classic VPS plans have another saving too: according to the catalog, for 23% of monthly-billed plans a month comes out cheaper if you pay six months or a year in advance. When hourly billing beats monthly billing is covered in the article [Hourly billing: when it pays off](https://accsly.io/en/vps/guide/hourly-billing-when-worth-it).

## Outbound traffic

With a classic VPS, traffic is usually included in the price. According to the accsly.io catalog for November 2026, of the 20 379 VPS plans that state their traffic terms, 8 762 have unmetered traffic, and the rest have a median allowance of 5 TB a month. Cloud-type hosts in the catalog follow a similar model: a median allowance of 6 TB, with unmetered traffic on about a third of plans.

Large cloud platforms work differently: only a small share of outbound traffic is free, and every gigabyte beyond it is paid for. Both at [the largest international platform](https://aws.amazon.com/ec2/pricing/on-demand/) and at [a large cloud platform in Russia](https://yandex.cloud/en/docs/vpc/pricing), the first 100 GB of outbound traffic a month are free. The Russian platform also does not charge for inbound traffic or for exchange between its services over internal addresses. For a site with moderate traffic this is not much, but for serving files, video or backups to external storage, the traffic bill can exceed the price of the machine itself. How to estimate your volume is explained in the article [Bandwidth and traffic: what 1 Gbit/s and unmetered mean](https://accsly.io/en/vps/guide/server-bandwidth-and-traffic).

## What else a cloud charges for

- **A public IP address.** Clouds often bill it separately. In the documentation of the same Russian platform, the address of a running machine costs about $0.0032 an hour including VAT, around $2.40 for 730 hours, while a reserved but unused address costs about $0.0074 an hour.
- **Disks and snapshots.** They are billed by size and time, separately from the machine. Under [the same platform's rules](https://yandex.cloud/en/docs/compute/pricing), the time a machine is stopped is not billed, but disks are charged whether the machine is running or not, and together with snapshots they keep being charged even after the machine is deleted. What is charged for a stopped server is covered in more detail in the article on [hourly billing](https://accsly.io/en/vps/guide/hourly-billing-when-worth-it).
- **Services around the machine.** A load balancer, NAT, a managed database, object storage, each with its own price list.

So the cost of a cloud is counted across all the lines, not by the machine price in the calculator. With a classic VPS the total is usually just the plan price, plus extra addresses and backups if they are billed separately; that is the subject of the article [How to read a host's plans](https://accsly.io/en/vps/guide/hidden-limits-in-hosting-plans).

## Which to choose when

**A cloud server** fits if:

- you need servers for hours or days, for tests, builds or one-off calculations: selections [VPS with hourly billing](https://accsly.io/en/vps/hourly-billing) and [VPS for CI](https://accsly.io/en/vps/for-ci);
- your infrastructure is described in code and created through an API or Terraform: the selection [VPS with an API](https://accsly.io/en/vps/api);
- the load changes and you need to add machines quickly, for example for Kubernetes: [VPS for Kubernetes](https://accsly.io/en/vps/for-kubernetes);
- the disk must survive a host failure, and you need snapshots without a shutdown.

**A classic VPS** fits if:

- the server runs all year with a steady load: a site, a bot, a database, mail;
- you need a predictable bill and plenty of traffic: the selection [VPS with unmetered traffic](https://accsly.io/en/vps/unlimited-traffic);
- the database is sensitive to latency and benefits from local NVMe: [VPS on NVMe](https://accsly.io/en/vps/nvme);
- the budget matters more than automation: for the same money a classic plan usually gives more resources.

A common compromise is a classic VPS for the permanent workload plus object storage for backups and files. And if a virtual machine is not enough, compare it with a physical one in the article [Dedicated server or VPS](https://accsly.io/en/vps/guide/dedicated-or-vps).

## FAQ

### How does a cloud server differ from a VPS?

Technically it is usually the same kind of virtual machine. A cloud is billed by the hour, managed through an API, keeps the disk in distributed storage and offers snapshots and ready-made services. A classic VPS is a fixed monthly plan with a local disk.

### Which is cheaper, a cloud or a VPS?

According to the accsly.io catalog for November 2026, the cheapest plans are almost equal, but a typical plan from a cloud-type host costs one and a half to two and a half times more. For a server that runs all month, a classic VPS is usually the better deal.

### Do you pay for traffic in a cloud?

At large cloud platforms only part of the outbound traffic is free, often the first 100 GB a month, and every gigabyte after that is paid for. Inbound traffic is usually free. With a classic VPS, traffic is more often included in the plan as an allowance or unmetered.

### What is a network disk in a cloud?

It is a volume in distributed storage such as Ceph: the data sits on several nodes, so the disk survives a server failure and supports snapshots. Its latency is higher than that of local NVMe.

### What is S3 object storage for?

For keeping files separately from the server: backups, images, user uploads. Access goes through an HTTP API, and the space is not limited by the size of the machine's disk.

### Are you charged for a stopped cloud server?

Usually not for the processor and memory, but yes for disks, snapshots and reserved IP addresses. To stop the charges completely, delete the server together with its disks, snapshots and unused addresses.

_Updated: 2026-11-04_

# Dedicated server or VPS

A VPS is a slice of a physical server, a dedicated server is the whole machine. With 4 cores and 8–16 GB of memory a VPS costs almost half as much, with 4 cores and 32 GB the prices are equal, and with 64 GB on 8 cores or 128 GB on 16 cores a dedicated server in the catalog is a third cheaper than a virtual one. Here is what else changes besides the price: neighbours, guarantees, delivery time, hardware failures and remote management.

> Source: https://accsly.io/en/vps/guide/dedicated-or-vps · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

The choice between a VPS and a dedicated server usually starts with the price, but other things decide it: whether you share the processor with neighbours, who is responsible for a failed disk, how long you wait for the server and whether you can reach the console when the system does not boot. Below is what exactly you rent in each case, a price comparison at equal resources and the signs that it is time to take a physical machine.

## What you rent in each case

**A VPS** is a virtual machine on the host's server. Dozens of such machines run on one physical server, and the hypervisor divides the processor, memory, disks and network card between them. You get root access, your own system and an IP address, but the hardware is shared. How it works is explained in the article [What is a VPS](https://accsly.io/en/vps/guide/what-is-vps), and the difference between the names VPS and VDS in [VPS or VDS](https://accsly.io/en/vps/guide/vps-vs-vds).

**A dedicated server** is a physical machine in a data centre rack that only you rent. The whole processor, all the memory and all the disks are yours, and there is no virtualization layer between the system and the hardware unless you install one yourself. The host is responsible for power, network, cooling and replacing faulty parts.

The figures in the plans mean different things too. A VPS lists vCPUs, virtual processors that the hypervisor maps onto the threads of a physical processor. A dedicated server usually lists the processor model and the number of physical cores and threads. "8 vCPU" and "8 cores" are not the same thing: on a processor with two-way SMT, eight physical cores give sixteen threads.

## Neighbours and steal time

The main difference of a VPS is its neighbours. If the host sells more vCPUs than the physical processor has threads, and the neighbours load the system at the same time, your machine waits its turn. Linux shows this wait as steal: according to the [kernel documentation](https://man7.org/linux/man-pages/man5/proc_stat.5.html), it is time spent in other operating systems when running in a virtualized environment. You can see it in the `st` column of `top` and `vmstat`.

- Steal near zero means the processor is fully available to you.
- A few per cent at peak hours happens even at good hosts on shared cores.
- A constant tens of per cent means you pay for cores you do not fully get.

The disk and the network are shared as well: a neighbour's heavy writes can raise the latency of your database, and the server's port is shared by every machine on it. A dedicated server has no steal at all, and disk and network speed depend only on the hardware and your own load. How to test a VPS before paying is described in the article [How to check VPS ping and speed](https://accsly.io/en/vps/guide/check-vps-speed-before-buying).

## Memory and disk guarantees

On a VPS with full virtualization (KVM), memory is usually pinned to the machine, but on containers and "burst" plans part of the memory is promised only while the host has free resources. A VPS disk is a file or a volume on a shared array: the size is guaranteed, the speed is not. The differences between virtualization types are covered in the article [KVM or OpenVZ](https://accsly.io/en/vps/guide/kvm-or-openvz).

On a dedicated server, memory and disks are physical modules installed in the machine. The flip side is that their number and type are fixed by the configuration. Adding memory or a disk means a request to the host, and often a shutdown and an engineer working at the rack. On a VPS the same step is a plan change and a reboot.

Pay attention to the disk type: according to the accsly.io catalog for November 2026, about a third of dedicated server plans come with HDDs. That is fine for an archive or backups, but not for a database. NVMe-only plans are collected in [dedicated servers with NVMe](https://accsly.io/en/dedicated/nvme).

## Setup, delivery time and hardware failures

A VPS is created from a template in minutes: according to the accsly.io catalog for November 2026, 955 of 2 210 VPS hosts state instant delivery. For a dedicated server the time depends on whether the machine is in stock: a configuration built to order has to be assembled and tested. Look for the delivery time in the plan description or ask support before paying.

A setup fee is rare for a VPS: according to the accsly.io catalog for November 2026, 500 of 27 thousand plans with monthly billing have one. For dedicated servers, 22 of the 120 hosts with monthly-billed plans charge it. The catalog keeps prices in roubles; dollar figures in this article are converted at the Central Bank of Russia rate of 4 November 2026 and rounded. Taking the cheapest plan of each such host, the median setup fee is about $52, paid once on top of the first month.

Virtual and physical servers survive hardware failure differently. If a VPS host breaks down, the provider restarts the machines on another server, and with network storage this can happen automatically. On a dedicated server an engineer replaces a broken disk or power supply, and the replacement time is written in the SLA, if it is written anywhere at all. That is why physical machines almost always get disks in RAID pairs and a backup kept off the server; how to set that up is explained in the article [VPS backups](https://accsly.io/en/vps/guide/vps-backups).

## ECC and remote console

Two things exist only on a dedicated server, and both are worth checking in the configuration description.

- **ECC memory.** Server memory stores check bits and corrects single-bit errors on the fly. Through the [EDAC](https://docs.kernel.org/driver-api/edac.html) subsystem Linux counts corrected (CE) and uncorrectable (UE) errors, so a growing counter tells you to replace a module before it fails. Servers on desktop processors do not always support ECC, so check the memory line in the configuration: for a database or storage, memory without ECC risks silent data corruption.
- **Remote management (IPMI, KVM over IP).** A separate controller on the board, the BMC, works independently of the system. Through it you can switch the power on and off, open the server's screen in a browser, mount an installation image and read the sensors. The feature set is well described in the [feature list of the open OpenBMC firmware](https://github.com/openbmc/docs/blob/master/features.md): remote KVM, a console over SSH, IPMI and Redfish, power control. Without such access, a server that did not boot after a kernel update can be fixed only by the host's support.

The VPS equivalent is the VNC console in the host's panel and reinstallation from an image. It is usually enough, and on a VPS you do not see hardware memory errors at all: they are the host's responsibility.

## What equal resources cost

For the comparison we took plans with the same number of cores and the same memory, in stock and with monthly billing, from the accsly.io catalog for November 2026. For each host we took the cheapest plan in that configuration, and the table shows the median across hosts. Prices are per month in US dollars, converted from roubles as described above; whether VAT is included depends on the host. Setup fees are not included in the table.

| Cores and memory | VPS, median | Dedicated server, median |
| --- | --- | --- |
| 4 cores, 8 GB | $34 (1 267 hosts) | $79 (23 hosts) |
| 4 cores, 16 GB | $47 (420) | $84 (44) |
| 4 cores, 32 GB | $99 (81) | $99 (52) |
| 8 cores, 32 GB | $96 (470) | $133 (28) |
| 8 cores, 64 GB | $215 (89) | $146 (39) |
| 16 cores, 64 GB | $193 (251) | $221 (37) |
| 16 cores, 128 GB | $402 (61) | $271 (38) |

The picture: with 4 cores and 8–16 GB of memory a VPS costs almost half as much, with 8 and 16 cores and 32 and 64 GB a VPS is 13–28% cheaper, with 4 cores and 32 GB the prices are equal, and at 8 GB per core on 8 and 16 cores (64 and 128 GB) a dedicated server is a third cheaper. Keep in mind that a VPS "core" is a vCPU, while a dedicated server core is a physical core, usually with two threads, so at equal figures the physical machine has more processor. The cheapest dedicated server at a mid-market host costs about $94 a month; a selection of inexpensive machines is in [cheap dedicated servers](https://accsly.io/en/dedicated/cheap).

## When a dedicated server pays off

- **You need a lot of memory.** With 64 GB on 8 cores and 128 GB on 16 cores, a dedicated server in the catalog is cheaper than a VPS of the same configuration, and the choice is wider: selections [with 128 GB](https://accsly.io/en/dedicated/128-gb-ram) and [with 256 GB of memory](https://accsly.io/en/dedicated/256-gb-ram).
- **The processor is busy all the time.** Builds, video encoding, calculations, game servers for many players: on shared cores such a load runs into steal, and a VPS with dedicated cores costs noticeably more than a regular one.
- **The database is sensitive to disk latency.** Direct NVMe with no virtualization layer and no neighbours gives steady latency.
- **Your own virtualization.** If you carve out machines for your team or clients yourself, you need a server where you can install your own hypervisor: [dedicated server for virtualization](https://accsly.io/en/dedicated/for-virtualization).
- **Licensing or audit requirements.** A licence counted per physical processor, or a ban on a shared hypervisor.

## When a VPS is enough

- A site, a bot, a small API or a database of tens of gigabytes: up to 4 cores and 16 GB a VPS is noticeably cheaper.
- The load changes: a VPS can be scaled up by changing the plan, while nobody refunds the unused capacity of a dedicated server.
- You need the server today and maybe not for long: a VPS is delivered at once, without a setup fee, and many hosts offer hourly billing.
- Nobody is available to look after hardware: on a VPS the host takes care of disk failures, RAID and part replacement.

If neighbours hold you back but a physical machine is still too much, a middle option is a VPS on fast processors with dedicated cores: selections [high-frequency VPS](https://accsly.io/en/vps/high-frequency) and [VPS with 32 GB of memory](https://accsly.io/en/vps/32-gb-ram). How many resources a site needs is worked out in the article [How much memory and CPU a website needs](https://accsly.io/en/vps/guide/ram-and-cpu-for-website). All physical machines in the catalog are in the [dedicated servers](https://accsly.io/en/dedicated) section.

## FAQ

### How does a dedicated server differ from a VPS?

A VPS is a virtual machine on a shared server: you share the processor, disks and network with neighbours. A dedicated server is a whole physical machine that is yours alone, with no hypervisor and no neighbours, but hardware is replaced by the host's engineer.

### Which is cheaper, a VPS or a dedicated server?

According to the accsly.io catalog for November 2026, with 4 cores and 8–16 GB of memory a VPS costs almost half as much. With 4 cores and 32 GB the prices are equal, and with 64 GB on 8 cores or 128 GB on 16 cores a dedicated server is about a third cheaper than a VPS of the same configuration.

### What is steal time on a VPS?

It is the time your virtual machine waited for the processor while the hypervisor gave it to other machines. You can see it in the st column of top and vmstat. A constant tens of per cent means the host is overloaded.

### Is there a setup fee for a dedicated server?

At some hosts, yes: according to the accsly.io catalog for November 2026, 22 of 120 dedicated server hosts with monthly billing charge it, with a median of about $52 paid once. For a VPS such a fee is rare.

### Why do you need ECC memory?

ECC memory corrects single-bit errors and reports them to the system. Without it, a failing module can silently corrupt data in a database or in files, so ECC matters for storage and databases.

### What are IPMI and KVM over IP?

Remote management of a physical server through a separate controller on the board: power, screen and keyboard in a browser, mounting an installation image. It works even if the system has not booted.

_Updated: 2026-11-04_

# Shared hosting or VPS for a website

Shared hosting is a ready place for a site where the host looks after the server. A VPS is your own server where you set everything up. For a landing page or an ordinary WordPress site, hosting is enough and costs several times less. You need a VPS when the account limits are too tight for the site or when it needs software that hosting does not allow. Below is what each option includes, what it costs and a table to help you choose.

> Source: https://accsly.io/en/vps/guide/hosting-or-vps-for-website · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

Hosting and VPS are often compared by price alone, but they are different services. With hosting you buy a ready environment for a site together with its administration. With a VPS you buy resources and freedom, and administration becomes your job. This article is a reference for choosing from scratch. If your site already lives on shared hosting and you are thinking of moving, read the article [When to move from shared hosting to a VPS](https://accsly.io/en/vps/guide/hosting-to-vps-when): it covers the signs that make a move worthwhile.

## What shared hosting gives you

On shared hosting your site lives on a common server together with other customers' sites. You get a folder for files, databases and a control panel, while the host configures and updates the system, the web server and PHP. What a plan usually includes:

- **A control panel**: cPanel, ISPmanager or the host's own panel, with sites, databases, mailboxes, cron jobs and one-click CMS installation.
- **Mail on your domain**: mailboxes like info@your-domain without a separate server.
- **An SSL certificate**: a free one is issued and renewed automatically.
- **Backups**: the host copies files and databases on its own schedule.
- **Security and updates**: the host is responsible for the system, the web server and protecting the server.

Not every plan has all of this. According to the accsly.io catalog for November 2026, free SSL is listed for 1 106 hosting plans and explicitly absent from 47. Backups are listed for 914 plans, mail for 991, and 14 plans offer no mail at all. For the remaining plans the host's site does not state these terms, so check them before paying.

## Hosting limits: CPU, processes, inodes

To keep one site from disturbing its neighbours, shared hosting limits every account. CloudLinux is often used for this, and its [documentation](https://docs.cloudlinux.com/cloudlinuxos/limits/) shows well what limits exist:

- **SPEED** is the share of the processor as a percentage of one core. The default is 100%, that is, one core for the whole account.
- **PMEM** is the physical memory of the account's processes, 1 GB by default. When it is exceeded, processes are killed and the site returns 500 or 503 errors.
- **EP** is the number of simultaneous entry processes: requests to PHP scripts, SSH sessions and cron jobs. The default is 20. When the limit is reached, the site answers with error 508 Resource Limit Is Reached.
- **NPROC** is the total number of processes and threads, 100 by default.
- **IO** is the disk read and write speed, 1024 KB/s by default; when it is exceeded, processes are not killed but slowed down.
- **Inodes** are the number of files and folders in the account. A site with a large cache or thousands of images hits this limit before it runs out of disk space.

These are the defaults; the real values are set by the host for each plan. Look for them in the plan description or ask support; how to read such terms is explained in the article [How to read a host's plans](https://accsly.io/en/vps/guide/hidden-limits-in-hosting-plans). One more restriction of shared hosting is that you cannot install your own software: a permanently running Node.js or Python process, Redis, a search engine, your own database version.

## What a VPS gives you

A VPS is a virtual machine with root access where the whole system is yours. What that gives you:

- **Any stack.** The PHP version you need, Node.js, Python, Redis, queues, search, Docker: anything that runs on Linux or Windows.
- **Your own limits.** All the cores, memory and disk of the plan go to your sites, and you decide how to divide them.
- **Background processes.** Queue workers, WebSockets, scheduled jobs of any length.
- **Isolation.** Other people's sites do not share a web server or PHP with you.

The flip side: everything the host does on shared hosting, on a VPS you do yourself or through a hired administrator. System updates, firewall, certificates, off-server backups, monitoring, dealing with failures. A control panel makes the work easier but does not take the responsibility away; free and paid panels are compared in the article [Server control panels](https://accsly.io/en/vps/guide/server-control-panels). Mail on your own server needs PTR, SPF, DKIM and DMARC set up separately, see [Mail server on a VPS](https://accsly.io/en/vps/guide/mail-server-on-vps-spf-dkim-dmarc). Where to start with security is described in the article [The first 10 steps after buying a VPS](https://accsly.io/en/vps/guide/vps-security-first-steps).

## What it costs

The prices below come from the accsly.io catalog for November 2026, plans in stock. They are median plan prices per month on monthly billing. The catalog keeps prices in roubles; the dollar figures are converted at the Central Bank of Russia rate of 4 November 2026 and rounded. Whether VAT is included depends on the host. Setup fees are rare for such plans: for hosting, 89 of 6 435 monthly-billed plans have one. The domain is paid for separately.

| Option | Median price, all locations |
| --- | --- |
| Hosting for 1 site | $3.80 (956 plans) |
| Hosting for 10 sites | $7.95 (414) |
| Hosting with unlimited sites | $13 (367) |
| VPS 1 vCPU, 1 GB | $8 (1 547) |
| VPS 2 vCPU, 2 GB | $16.70 (1 514) |
| VPS 2 vCPU, 4 GB | $21.30 (2 406) |

Keep one feature of shared hosting in mind: 26% of hosting plans in the catalog are sold only with payment for at least three months, and 23% only for a year in advance, so compare the price per month, not the amount due.

What this means for typical sites:

- **A landing page or a business card site.** The simplest hosting plan for 1 site is enough, which is a few dollars a month. A VPS for such a site means overpaying and extra work. Selections: [cheap hosting](https://accsly.io/en/hosting/cheap) and [hosting under 100 roubles (about $1.20) a month](https://accsly.io/en/hosting/under-100).
- **A WordPress site or blog.** [WordPress recommends](https://wordpress.org/about/requirements/) PHP 8.3 or newer, MySQL 8.0 or MariaDB 10.11 or newer and HTTPS support, so check the PHP and database versions in the plan description. Shared hosting works as long as the site fits within the account limits: [hosting for WordPress](https://accsly.io/en/hosting/wordpress). If you need Redis, your own page cache at the web server level or several busy sites, take a VPS with 2 vCPU and 2–4 GB: [VPS for WordPress](https://accsly.io/en/vps/for-wordpress).
- **An online shop.** A small shop on WooCommerce or another CMS runs on a good hosting plan: [hosting for an online shop](https://accsly.io/en/hosting/online-store). A catalog of thousands of products with filters, scheduled imports of product feeds and search more often need a VPS with 2–4 vCPU and 4 GB: [VPS for an online shop](https://accsly.io/en/vps/for-online-store). How many resources a specific load needs is worked out in the article [How much memory and CPU a website needs](https://accsly.io/en/vps/guide/ram-and-cpu-for-website).

Add to the VPS price what shared hosting already includes: a panel licence if you choose a paid one, off-server backups, a mail service for the domain and the administrator's time.

## Decision table

| Situation | What to choose |
| --- | --- |
| Landing page, business card site, blog, CMS site without custom software | Shared hosting |
| No time or wish to administer a server | Shared hosting or a VPS managed by the host |
| You need mail on the domain without separate setup | Shared hosting or a separate mail service |
| Many sites of one owner, all on PHP | Hosting for 10 sites or more; a VPS if the sites are busy |
| You need Node.js, Python, Redis, queues, WebSockets | VPS |
| The site regularly hits CPU, process or inode limits | A higher hosting plan or a VPS |
| You need your own web server configuration, access to logs, isolation | VPS |
| A shop with a large catalog, imports and search | VPS with 2–4 vCPU and 4 GB |

If in doubt, start with shared hosting: you can move to a VPS without downtime when the time comes, and the steps are covered in the article [How to move a site from shared hosting to a VPS](https://accsly.io/en/vps/guide/move-site-hosting-to-vps). All hosting plans are collected in the [website hosting](https://accsly.io/en/hosting) section, and virtual servers for sites in the selection [VPS for a website](https://accsly.io/en/vps/for-website).

## FAQ

### Which is better for a website, shared hosting or a VPS?

For a landing page, a blog or an ordinary CMS site, shared hosting is better: it is cheaper, and the host looks after the server. You need a VPS when the account limits are too tight for the site, or when it needs its own software or background processes.

### How much do hosting and a VPS for a website cost?

According to the accsly.io catalog for November 2026, the median price of hosting for 1 site is about $3.80 a month. A VPS with 2 vCPU and 2 GB costs about $16.70 a month in the middle of the market, on monthly billing.

### What is error 508 on shared hosting?

It is the Resource Limit Is Reached response: the account has used up its limit of simultaneous processes. The site opens again once the current requests finish; if the error keeps coming back, you need a higher plan or a VPS.

### What are inodes on shared hosting?

A limit on the number of files and folders in the account. A site with a large cache, thousands of images or old backups can hit it while there is still free disk space.

### Do I need to administer a VPS for a website?

Yes. System updates, firewall, certificates, backups and monitoring on a VPS are your job. If nobody can take care of this, choose shared hosting or a VPS managed by the host.

### Is shared hosting suitable for WordPress?

Yes, if the plan provides the versions WordPress recommends: PHP 8.3 or newer, MySQL 8.0 or MariaDB 10.11, and HTTPS. You will need a VPS for a busy site, Redis or a large WooCommerce shop.

_Updated: 2026-11-04_

# DDoS protection: what hosting providers actually give you

Every second host now lists "DDoS protection" in its plans. Behind that line there may be multi-terabit filtering, or only the right to take your address offline when an attack bothers the neighbours. Here is what protection is made of, how L3/L4 differs from L7, and how to tell from the contract what you are buying.

> Source: https://accsly.io/en/vps/guide/ddos-protection-at-hosters · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A DDoS attack is a flood of requests from many machines meant to overload a server or its link so that real visitors cannot reach it. Protection against it is built on the host's network or at an external filtering provider: suspicious traffic is separated from normal traffic and dropped before it reaches the server. The server itself cannot cope with a large attack: once the link to it is full, no settings inside the system will help.

## Attack layers: L3/L4 and L7

Attacks are classified by network-model layer, and each class is handled differently.

- **Volumetric attacks (L3/L4)** fill the link: so much traffic heads for the server that its port or the data centre's upstream links are saturated. Their size is measured in gigabits and terabits per second.
- **Protocol attacks (L3/L4)** exhaust not the link but the resources that track connections: firewall state tables, the queue of new TCP connections. They are measured in packets per second (pps, Mpps). Some of them are also handled on the server itself, for example with SYN cookies (RFC 4987).
- **Application attacks (L7)** look like ordinary HTTP requests to a site or API: search, cart and login pages. The link stays almost idle while the web server or database goes down. They are measured in requests per second (rps) and are told apart from visitors by behaviour, not volume.

L3/L4 network filtering is what hosts usually switch on for every customer. L7 protection is harder: the filter has to understand your site, see the contents of HTTPS requests and tell a visitor from a bot. That is why it is more often sold separately, connected through a proxy holding your certificate, or left to the site side: a CDN, a WAF, request rate limits in the web server.

## "Protection enabled" versus real filtering

According to the accsly catalog as of 3 November 2026, 1,117 of the 2,236 hosts with VPS plans claim DDoS protection, exactly half. Details could be found for 219 hosts in the catalog, and the picture is mixed:

- 35 hosts state the filtering capacity in Gbps or Tbps;
- 24 state the protection layer (L3/L4 or L7);
- 8 mention L7, and for half of them it is paid or enabled on request;
- in roughly a quarter of the cases protection is a separate paid option, and in roughly another quarter it is explicitly included in the price.

The rest keep it short: "yes", "claimed", "built-in network protection". That is not necessarily bad, but such a phrase does not tell you what will happen during an attack. Three different things hide behind the same words:

1. **Always-on filtering.** All traffic always passes through the filter. An attack is cut off at once, but the filter sometimes catches normal traffic too, for example game protocols over UDP.
2. **On-demand filtering.** The system watches traffic and turns scrubbing on when the flow crosses a threshold. Seconds or minutes pass between the start of an attack and the filter kicking in, and the server may be unreachable during that time.
3. **Blackhole only.** There is no real scrubbing: during an attack the host's network simply stops passing traffic to your address. That protects the neighbours and the host, but not you.

## Threshold and blackhole

Every protection has a limit: a volume or packet rate beyond which the host stops filtering. The rules usually say something like "for attacks above N Gbps the address may be temporarily taken offline". This is done with a blackhole: the operator tells neighbouring networks to drop traffic to your address. BGP has a standard BLACKHOLE community for this (RFC 7999), and where possible exactly one address is taken offline, a /32 for IPv4 or a /128 for IPv6, so that neighbours are not affected.

For the server owner this means a simple thing: the attack reaches its goal, just on the network rather than on your server. The address is unreachable for everyone until the blackhole is lifted, and the duration differs between hosts, so look for it in the rules too. If the project cannot survive such downtime, the filtering threshold must be well above the attacks you realistically expect, and the site should have additional L7 protection in front of it.

One more detail is the port. On a plan with a 100 Mbps port even a small attack fills it completely, and the host's filter has to cut it off before it reaches your port. How to read port speed and shared links is covered in [Bandwidth and traffic: what 1 Gbps and unlimited really mean](https://accsly.io/en/vps/guide/server-bandwidth-and-traffic).

## What to ask the host and check in the contract

- **Layers.** Only L3/L4, or L7 as well? If L7, how is it connected: through a proxy, by changing DNS, with or without your certificate.
- **Capacity.** How many Gbps and how many million packets per second the filter handles per address, not for the whole network.
- **Mode.** Is filtering always on or triggered by a threshold, and how long does it take to kick in.
- **Beyond the threshold.** Is the address taken offline, for how long, can it be brought back sooner, and what does an upgrade to higher protection cost.
- **Where the filter sits.** In the data centre itself or at an external provider; does protection cover all the host's locations — sometimes it exists in only one city.
- **Price and terms.** Is protection included in the plan or a separately paid option, and is there a charge per mitigated attack.
- **Liability.** Does attack time count towards the availability SLA. Often it does not: the rules exclude attacks from the guarantee.

Get the answers in writing, in a support ticket: if the host's website says little, these are your terms. General tips on reading a plan are in [How to read hosting plans: the hidden limits](https://accsly.io/en/vps/guide/hidden-limits-in-hosting-plans).

## What to do yourself

Even with good protection from the host, part of the work stays on your side:

- close everything except the ports you need with a firewall and enable SYN cookies — most Linux distributions already have them on; the basic setup is described in [First 10 steps after buying a VPS: security](https://accsly.io/en/vps/guide/vps-security-first-steps);
- for a site, rate-limit requests to heavy pages (search, login, cart) right in the web server and put a CDN with L7 protection in front of the site;
- if the site is behind a CDN or proxy, do not publish the server's direct address in DNS or in emails, otherwise traffic will go around the filter;
- watch availability from outside to learn about an attack before visitors do — see [Server monitoring: uptime, load, alerts](https://accsly.io/en/vps/guide/server-monitoring-uptime-alerts);
- keep a fresh backup and a moving plan: if the host cannot cope, the project can be brought up elsewhere.

Plans where protection is included in the price are collected in [VPS with DDoS protection](https://accsly.io/en/vps/ddos-protection). Game servers need protection more often than others, usually L3/L4 for UDP: see [VPS for a game server](https://accsly.io/en/vps/for-game-server) and [dedicated servers for games](https://accsly.io/en/dedicated/for-game-server).

## FAQ

### How does L3/L4 protection differ from L7?

L3/L4 filters network traffic by volume and packets, protecting the link and connections. L7 inspects HTTP requests to the site and tells visitors from bots. Hosts usually include the first for everyone; the second is more often sold separately or set up through a CDN.

### What does "DDoS protection included" in a plan mean?

Only that the host has some kind of filtering. It may be always-on scrubbing of terabits, a filter triggered by a threshold, or just taking the address offline during an attack. Ask about the layer, the capacity per address and what happens beyond the threshold.

### What is a blackhole during a DDoS attack?

The host stops passing all traffic to the attacked address, usually exactly one IP. That protects the rest of the network, but your server is unreachable for everyone in the meantime.

### How long does a blackhole last?

There is no single rule: some hosts lift it after a fixed time, others when the attack ends. Look for the duration and the option to lift it sooner in the rules, or ask support before you pay.

### Does a small website need DDoS protection?

The host's basic network filtering plus a CDN in front of the site is usually enough. Separate paid protection is worth it when downtime costs money: an online store, a game server, a service with paying customers.

### Does attack time count towards the uptime SLA?

Often not: many hosts' rules exclude DDoS attacks from the availability guarantee. If this matters to you, look for that clause in the SLA specifically.

_Updated: 2026-11-03_

# Mail server on a VPS: SPF, DKIM, DMARC

Installing Postfix or a ready-made bundle like Mailcow on a VPS takes an hour. Getting your mail into the inbox rather than spam is harder: mailbox providers look at the port, the server's address, its reputation and three DNS records. Here is what to check with the host before buying and how to set up SPF, DKIM and DMARC.

> Source: https://accsly.io/en/vps/guide/mail-server-on-vps-spf-dkim-dmarc · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A mail server does two different jobs: it receives mail for your domain and sends your mail to other servers. Receiving almost always works right away if DNS has an MX record. Sending is harder: the receiving side decides whether to trust your server and checks the network, the address and the signatures to do so. If even one link is not set up, messages are rejected or land in spam without any notice.

## Port 25 at hosting providers

Servers pass mail to each other over port 25. Ports 587 and 465 are for programs that hand a message to their own server; a message reaches someone else's MX server only via port 25. So the main condition for your own mail is an open **outbound** port 25.

Many hosts close it by default: new servers are often used to try sending spam, and the complaints and bad reputation fall on the host's addresses. According to the accsly catalog as of 3 November 2026, the port 25 terms could be established for 117 hosts: for 39% it is closed, for 37% it is opened on request, and for 24% it is open from the start. Large cloud platforms often close it for good, with no way to open it.

If the port is opened on request, the host usually wants to know the domain, what the mail is for, and sometimes that the server has been paid for more than a day. Say it plainly: "corporate mail for the domain, about N messages a day, no bulk mailings". To check the port on a server you already have: `nc -vz -w 5 gmail-smtp-in.l.google.com 25` — if there is no connection, the port is closed on the host's side. Plans from hosts where the port is open or opened on request are in [VPS for a mail server](https://accsly.io/en/vps/for-mail-server).

## PTR and the server name

Google requires every sender's server address to have a reverse DNS record (PTR) that matches the forward one. The scheme: the server has a name, for example `mail.example.com`; that name's A record points to the server's address, the address's PTR points back to `mail.example.com`, and the server introduces itself with the same name in the HELO command. The PTR is set by the host, in the panel or through support. If mail also goes out over IPv6, the IPv6 address needs a PTR too. Details are in [IPv4 and IPv6 on a server](https://accsly.io/en/vps/guide/ipv4-and-ipv6-on-server). On a NAT VPS without its own address you cannot set your own PTR, and such a server is not suitable for mail.

## IP address reputation

A VPS address could have belonged to anyone before you. If spam was sent from it, it may be on public lists of known spam sources (DNSBL), and some mailbox providers will reject your mail from day one. Before launch, check the address in public reputation lookup services; if it is listed, ask the host for another one or file a removal request — most lists have such a form.

A new clean address has a different problem: it has no history, and the big providers treat it with caution. Start with a small volume of mail to real recipients and increase it gradually. Google requires keeping the share of messages that recipients mark as spam below 0.3%; you can watch it in the free Google Postmaster Tools. Bulk mailings are better sent through a separate service, or at least from a separate address and subdomain, so that their reputation does not affect your working mail.

## SPF: who may send on behalf of the domain

SPF (RFC 7208) is a TXT record at the domain root listing the servers allowed to send mail on its behalf. The receiving server checks it against the envelope sender address (MAIL FROM) and the HELO name.

```
example.com.  TXT  "v=spf1 mx ip4:203.0.113.10 -all"
```

- `mx` and `ip4:` are your servers; if mail also goes out through an external service, add its `include:`.
- `-all` means everyone else is not allowed to send (fail), `~all` means "probably not" (softfail), handy while you are setting things up.
- A domain must have exactly one SPF record. Mechanisms that need DNS lookups (`include`, `a`, `mx`, `exists`, `redirect`) may be used no more than 10 times including nested ones; beyond that the check returns an error (permerror) and SPF does not work at all.

## DKIM: signing messages

DKIM (RFC 6376) is a digital signature over a message's headers and body. The server signs every message with a private key, and the public key is published in DNS under `selector._domainkey.example.com`. The recipient verifies the signature and confirms that the message was sent by the domain in the signature and was not altered on the way.

```
mail2026._domainkey.example.com.  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkq..."
```

The RSA key length must be at least 1024 bits, as RFC 8301 and Gmail require; 2048 is recommended. Keys are generated by OpenDKIM, rspamd or the panel of a mail bundle, which will also give you the ready record. The selector is there for key rotation: publish the new key under a new selector, switch signing over, and delete the old record a few days later, once the messages already sent have been checked.

## DMARC: policy and reports

DMARC (RFC 7489) ties SPF and DKIM to the From address the recipient sees. A message passes DMARC if SPF or DKIM passed and its domain matches the domain in From (by default a match of the organisational domain is enough). The record is published under the name `_dmarc`:

```
_dmarc.example.com.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@example.com"
```

- `p=none` means monitor only, `p=quarantine` sends messages that fail DMARC to spam, `p=reject` rejects them.
- `rua` is the address for daily aggregate reports: they show who sends mail on behalf of the domain and from which addresses.

Start with `p=none`, read the reports for 2–4 weeks, make sure all your legitimate mail sources pass, then move to quarantine and then to reject.

## What Gmail and Outlook require

Since 1 February 2024 Gmail has required every sender to have SPF or DKIM, a correct PTR record, delivery over TLS and a spam complaint rate below 0.3%. Those who send more than 5,000 messages a day to Gmail addresses need SPF and DKIM together, a DMARC record (`p=none` is enough) with the From domain matching the SPF or DKIM domain, and one-click unsubscribe in marketing mail. Since 5 May 2025 Outlook.com has applied similar rules to senders of 5,000+ messages a day: SPF and DKIM must pass, DMARC must be at least `p=none` with a domain match; messages without this go to the Junk folder or are rejected.

For a small server the conclusion is simple: set up all three records at once, even if you send little. To check the result, send a message to your own Gmail mailbox and open "Show original": it shows the SPF, DKIM and DMARC results.

## When you do not need your own mail server

Your own server makes sense if you need control over mailboxes and data, or many addresses on several domains. If the site only needs to send notifications and port 25 is closed, it is simpler to send through an external mail service on port 587: SPF, DKIM and DMARC are still set up for your domain. A server with full mail and spam filtering needs 2 GB of memory; plan disk space with room for mailboxes and [backups](https://accsly.io/en/vps/guide/vps-backups). When a site and its mail should move from shared hosting to a VPS is covered in [When to move from shared hosting to a VPS](https://accsly.io/en/vps/guide/hosting-to-vps-when).

## FAQ

### Why does my VPS not send mail?

Most often the host has closed outbound port 25. In the accsly catalog it is closed at 39% of hosts with known terms and opened on request at another 37%. Check the port and write to support.

### Can I send mail over port 587 instead of 25?

Only to your own or an external mail service that then delivers the message. Other mail servers accept mail from servers on port 25.

### What are SPF, DKIM and DMARC in plain words?

SPF is the list of servers allowed to send mail on behalf of the domain. DKIM is a signature proving that the domain sent the message and it was not altered. DMARC is the policy: what to do with messages that fail these checks and where to send reports.

### Do I need DMARC if I send little mail?

Yes. Gmail strictly requires DMARC from senders of more than 5,000 messages a day, but for a small server a p=none record costs nothing, and the reports show who sends mail on behalf of the domain.

### How long should a DKIM key be?

At least 1024 bits; 2048 is recommended. If the DNS panel does not accept a long TXT record as one string, split it into several quoted strings within a single record.

### Why does mail from my own server go to spam?

Usually a PTR record, SPF, DKIM or DMARC is missing, or the address has a poor reputation: it is on lists of known spam sources or brand new. Check the message headers in Gmail and the address in reputation lookup services.

_Updated: 2026-11-03_

# Server monitoring: uptime, load, alerts

Without monitoring you learn that the server is down from your visitors, and that the disk is running out when the database stops writing. A few checks from outside and a dozen metrics from inside are enough to see a problem before users do. Here is what to measure, where to run checks and how to do it for free.

> Source: https://accsly.io/en/vps/guide/server-monitoring-uptime-alerts · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

Monitoring answers two questions. The first is whether the service works for the user right now: does the site open, does the API respond, does SSH let you in. The second is why it works badly or will soon stop: space is running out, load is growing, neighbours on the host are taking the CPU. External checks answer the first, metrics from the server itself answer the second. You need both: one without the other either misses an outage or does not explain it.

## External and internal checks

An **external check** reaches the server from the internet the way a user does: it requests a page, connects to a port, checks a DNS answer. It sees what cannot be seen from inside the server: a broken route at the host, a dead uplink, a DNS error, an expired certificate. An important rule: external monitoring must not live on the same server and ideally not at the same host. If the data centre's network goes down, whoever was supposed to report it goes down together with the site. A good check looks not only at a 200 response code but also at a word or phrase on the page; that way it also catches the case where the web server is alive but serves an error page instead of the site.

**Internal monitoring** is an agent on the server that collects system metrics every 10–60 seconds and sends them to the monitoring server. It shows the cause: the graph reveals that the disk filled up overnight or that memory goes into swap more every hour.

The third kind of check is easy to forget: **checks from the server** (push, heartbeat). A scheduled job — a backup, an export, a report — sends a signal to monitoring by itself after finishing successfully. If the signal does not arrive on time, an alert goes out. This is how you find out about backups that quietly stopped being made weeks ago. How to set up the backups themselves is covered in [VPS backups: strategies and tools](https://accsly.io/en/vps/guide/vps-backups).

## What to measure

- **Availability and response time** — from outside, over HTTP(S), a port or ping, every 1–5 minutes from several locations.
- **CPU load** — utilisation in percent and load average. On Linux, load average counts not only processes waiting for the CPU but also those waiting for disk or network (state D). So a high load with low CPU utilisation usually means a slow disk, not a shortage of cores. Compare load with the number of cores: 4 on a four-core server is full load, on an eight-core one it is half.
- **Steal time** — the share of time when the virtual CPU is ready to run but the hypervisor has given the physical core to another machine. This is a VPS-specific metric, shown in `top` as `st`. Steady steal above 5–10% is a sign of an overloaded host, worth raising with support or changing the plan over.
- **Memory** — available memory (available, not free: Linux uses free memory for cache and hands it back on demand) and swap usage. Growing swap and OOM killer messages in the log signal that memory is short. How to size it is covered in [How much RAM and how many cores a website needs](https://accsly.io/en/vps/guide/ram-and-cpu-for-website).
- **Disk** — free space and free inodes on every partition, I/O latency and queue. Space most often runs out because of logs, backups and Docker images.
- **Network** — inbound and outbound traffic, errors and packet loss. On a plan with a quota it helps to see how much has already been used this month.
- **Services** — whether the web server, database, queues and containers are running; the number of 5xx errors in the web server log.
- **Expiry dates** — the TLS certificate and the domain registration: alert 14–30 days ahead.

## Alerts without false alarms

Monitoring that wakes you at night over trifles gets switched off within a month. A few rules help avoid that:

- **Alert only on what needs action.** You can graph everything, but write only about unavailability, a filling disk, service errors, a missed backup.
- **Trigger delay.** An external check should fail 2–3 times in a row or from several locations at once; load should stay above the threshold for 5–15 minutes, not for a single sample.
- **Two levels.** A warning (disk 80% full) goes to the work chat, an emergency (95% or site down) goes where you will see it at once: a push notification, a messenger, SMS.
- **Forecast instead of threshold.** For disks, the rule "space runs out within 24 hours at the current growth rate" is more useful than a fixed percentage: it fires on a fast-growing log and stays quiet on slow growth.
- **Recovery message.** Without it you cannot tell whether the problem is still there or already gone.

## Free tools

- **Uptime Kuma** — the simplest start: external HTTP(S), port, ping and DNS checks, keyword checks on a page, push checks for scheduled jobs, a status page and dozens of notification channels. Installs in Docker with one command, MIT licence. Keep it on a separate small server, not on the one it checks.
- **Prometheus + node_exporter + Grafana** — the standard stack for metrics: node_exporter exposes system metrics, Prometheus collects and stores them, Alertmanager sends alerts by rules, Grafana draws the graphs. Flexible, but setup will take an evening or two.
- **Zabbix** — a classic monitoring system with agents, templates for common services and alerts out of the box. Since version 7.0 it is distributed under the AGPLv3 licence. Convenient when there are many servers and you want a single interface.
- **Netdata** — an agent that, right after installation, shows hundreds of metrics at per-second resolution with alerts already configured. Good for working out what is happening on a server right now.

For one to three servers a practical setup is Uptime Kuma on a separate VPS for external and push checks, plus Netdata or node_exporter on each server for metrics. A monitoring server needs 1–2 GB of memory, but it is better placed at another host or at least in another location. Plans for this job are in [VPS for monitoring](https://accsly.io/en/vps/for-monitoring); if you run everything in containers, see [Docker on a VPS: getting started](https://accsly.io/en/vps/guide/docker-on-vps).

## Monitoring and the host's SLA

Your own availability data is the only way to check the host's promise. According to the accsly catalog as of 3 November 2026, 1,617 hosts state an availability guarantee; for 53% of them it is 99.9%, for 17% it is 99.99%. In minutes for a 30-day month it looks like this:

| Uptime | Allowed downtime per month |
| --- | --- |
| 99% | 7 h 12 min |
| 99.5% | 3 h 36 min |
| 99.9% | 43 min |
| 99.95% | 22 min |
| 99.99% | 4 min 19 s |

SLA compensation is usually granted only at the customer's request and only for downtime you can show; an external check log with exact times will do. Also note what the host counts as availability: often it is the network and the host node, not your site, and scheduled maintenance does not count as downtime. What else to read in the terms before buying is covered in [How to read hosting plans: the hidden limits](https://accsly.io/en/vps/guide/hidden-limits-in-hosting-plans).

## FAQ

### What should I monitor on a VPS first?

Availability from outside, free disk space, available memory, CPU load and steal time, plus whether key services are running and backups are being made. That is enough to catch most problems before users do.

### Can monitoring run on the same server?

Metrics, yes — the agent has to be on the server. External checks, no: if the server or the host's network goes down, monitoring goes down with them. Put it on a separate VPS, preferably at another host.

### What is steal time on a VPS?

The share of time when the virtual CPU is ready to run but the physical core is busy with another machine on the same host. It shows in top as st. A steady 5–10% or more is a sign of an overloaded host.

### Why is load average high while the CPU is almost idle?

On Linux, load average also counts processes waiting for disk or network. High load with low CPU utilisation usually means a slow or overloaded disk.

### Which free tool should I pick for one server?

Uptime Kuma on a separate small server for external checks, and Netdata or node_exporter on the main server for metrics. Prometheus with Grafana, or Zabbix, make sense once there are several servers.

### How much downtime does a 99.9% SLA allow?

About 43 minutes per 30-day month; 99.99% allows about 4 minutes. Compensation is usually granted on request, so it helps to keep your own availability log with exact times.

_Updated: 2026-11-03_

# How to read hosting plans: the hidden limits

A plan card shows cores, memory, disk and a monthly price. Yet two plans with identical numbers can cost different amounts a year later and behave differently under load. The difference lies in terms printed in small type, in the acceptable use policy, or only in the contract. Below are eight places worth checking before you pay.

> Source: https://accsly.io/en/vps/guide/hidden-limits-in-hosting-plans · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

Hosts rarely lie outright: everything covered here is usually written down somewhere. The advertised figure is simply calculated for the most favourable scenario — paying three years upfront, ignoring setup, and assuming a load most customers never reach. The buyer's job is to recalculate the plan for their own scenario. In order: the CPU, "unlimited", traffic, one-off fees, renewal, minimum term and the IP address.

## CPU: not all cores are equal

"2 vCPU" on a plan card almost never means two physical cores reserved for you. On a VPS, a virtual core is a share of the host's processor, which dozens of customers split between them. The usual arrangement has no hard cap: the core is yours as long as the neighbours do not load the host at the same moment. But some plans spell out a ceiling in their rules — for example, sustained load no higher than a certain percentage, or a clock-speed cap on "budget" lines. Look for these rules under the words "fair use", "CPU limit", "sustained load" and "burst".

If the server will run under constant load — building code, transcoding video, number crunching — look for plans with dedicated cores (dedicated vCPU) or take a physical server. For a website, a bot or a control panel an ordinary shared core is enough: they use the CPU in short bursts. How to check real performance on the first day is covered in [How to test VPS ping and speed before you pay](https://accsly.io/en/vps/guide/check-vps-speed-before-buying), and how many cores a site actually needs in [How much RAM and how many cores a website needs](https://accsly.io/en/vps/guide/ram-and-cpu-for-website).

## "Unlimited" and fair use

The word "unlimited" on a plan almost always refers to the volume of traffic, not the speed. Traffic is not counted in gigabytes, but the connection is capped by the port speed — 100 Mbps, 1 Gbps or more. A 100 Mbps port can physically move no more than 32 TB in a month, so "unlimited" on such a port is a ceiling of about 32 TB, just expressed differently.

The second limit is the fair use rule (fair use, AUP). In it the host reserves the right to cut the speed or ask you to move to another plan if the server saturates the link for a long time. Such rules often contain no specific figures. Before buying for file or video distribution, read this section in full and, if in doubt, ask support in writing: "what average monthly throughput do you consider normal on this plan?" More on what port speed and unlimited mean in [Bandwidth and traffic: what 1 Gbps and unlimited really mean](https://accsly.io/en/vps/guide/server-bandwidth-and-traffic).

In the accsly catalog as of 2 November 2026, unlimited traffic is listed for 43% of VPS plans whose traffic terms are known, and for 54% of dedicated servers. Collections: [VPS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic) and [dedicated servers with unlimited traffic](https://accsly.io/en/dedicated/unlimited-traffic).

## What happens after the traffic quota

If a plan says "5 TB of traffic", what matters is not only the number but what happens when it runs out. There are three variants:

- **The speed is reduced** until the end of the month, to the value stated in the terms. The server keeps working, only slowly; for a website this is usually unnoticeable, for file distribution it is noticeable.
- **Each additional terabyte is billed separately** at the price-list rate. That is fair, but the bill for a month with a traffic spike can come as a surprise.
- **The server is cut off** until the next month or until you buy an extra package. The worst option for a production project.

Also check how traffic is counted: outbound only or inbound too, and whether traffic inside the data centre — to backup storage, for example — counts towards the quota. The median quota for VPS plans with metered traffic in the catalog is 5 TB a month; for dedicated servers it is 15 TB. For a website that is a lot; for video distribution it is little.

## Setup fee

A one-off setup fee is rare on a VPS but common on dedicated servers: the host assembles and installs a machine for you. In the accsly catalog a setup fee is listed for 2% of VPS plans (median about $10) and for 10% of dedicated servers (median about $169). On a dedicated server you take for two or three months, that amount noticeably changes the total price. Hosts often waive the setup fee for annual payment or on promotional configurations — it is worth asking.

## First-term price and renewal price

The most common surprise is the bill for the second year. Adverts show the monthly price when paying 12, 24 or 36 months ahead, and sometimes a promotional price for new customers only. 6,406 VPS plans in the catalog have a separate price for long-term payment, and at the median it is 20% lower than the monthly rate. The discount is real, but you pay for the whole term at once.

The second case is a promotional first-term price. Of the 1,224 hosts whose promotion terms are in the catalog, 275 give a discount on the first month, the first year or to new customers only. After that, renewal follows the regular price list, and the gap with the advertised price can be large. How to check:

- find the phrase "renewal price" or "regular price" in the price list or terms;
- work out the two-year total: first term plus renewal, not the advertised price multiplied by 24;
- check whether you can renew at the same price by paying for a new long term in advance.

## Minimum term and prepayment

Monthly billing does not always mean "you can cancel after a month". Some plans state a minimum contract term in their conditions — a quarter, six months or a year — and some lines can only be ordered with prepayment. In the accsly catalog, prepayment for several months is mandatory for 791 VPS plans from 176 hosts, most often for 12 months. Separately, check the cancellation notice period: on dedicated servers "30 days before the end of the period" is not unusual.

Related terms are refunds and hourly billing. If you are unsure about a host, pick a plan with a money-back guarantee ([VPS with a money-back guarantee](https://accsly.io/en/vps/moneyback)) or with hourly billing, where the server can be deleted at any moment; see [Hourly billing: when it pays off](https://accsly.io/en/vps/guide/hourly-billing-when-worth-it). Keep in mind that refunds often do not cover setup, licences and dedicated servers — that is also written in the terms.

## Your own IPv4 or NAT

The cheapest plans sometimes come without a public IPv4 address of their own. There are two variants. A NAT VPS shares one external address among several customers, and you get a small range of ports; the standard ports 80 and 443 are not yours, and you cannot run a website on such a server without an intermediary. An IPv6-only server has IPv6 addresses only, and visitors without IPv6 will not reach it. In the accsly catalog, 349 VPS plans from 31 hosts come without IPv4.

An extra IPv4 address is almost always paid. Across 140 hosts that state the price unambiguously, the median is about $2.2 a month per address (180 ₽ at the 2 November 2026 rate), and half of the prices fall between about $1.9 and $3.4. Why that is and when IPv6 is enough is explained in [IPv4 and IPv6 on a server](https://accsly.io/en/vps/guide/ipv4-and-ipv6-on-server).

## A short checklist before you pay

- CPU: shared or dedicated cores, and whether the rules limit sustained load.
- Traffic: the quota, what happens after it, whether inbound counts; for unlimited plans, the port speed and the fair use rule.
- One-off fees: setup, a control panel or Windows licence, an extra IP.
- Price: what renewal costs and the two-year total.
- Term: minimum contract term, prepayment, cancellation notice period, refund conditions.
- Address: your own IPv4 or NAT, whether IPv6 is available, whether reverse DNS (PTR) can be set.

For the overall selection scheme — from virtualisation to disk — see [How to choose a VPS: the 7 specs that matter](https://accsly.io/en/vps/guide/how-to-choose-vps).

## FAQ

### What does fair use mean in a hosting plan?

It is an acceptable use rule: the host may cut the speed or offer another plan if the server saturates the link or the CPU for a long time. Specific figures are often missing, so under heavy load it is worth confirming them with support in writing.

### Is unlimited traffic really without limits?

The volume is not counted, but the speed is capped by the port. In a month a 100 Mbps port can move no more than 32 TB, a 1 Gbps port about 324 TB. On top of that, a fair use rule may restrict constant saturation of the link.

### What happens when the plan traffic runs out?

It depends on the host: the speed is reduced until the end of the month, each additional terabyte is billed, or the server is cut off until you buy a package. This is written in the plan terms and should be checked before you pay.

### Why is VPS renewal more expensive than the first payment?

The advertised price often applies only to the first term or only when paying for a year or more. Renewal follows the regular price list. Calculate the two-year total rather than the advertised price multiplied by 24 months.

### What is a NAT VPS?

A server without its own public IPv4: several customers share one external address, and you get a range of ports. That is enough for a bot or tests, but not for a website on ports 80 and 443 or a mail server.

### How much does an extra IPv4 address cost?

According to the accsly catalog as of 2 November 2026, the median across 140 hosts with an unambiguous price is about $2.2 a month per address, and half of the prices range from about $1.9 to $3.4.

_Updated: 2026-11-02_

# IPv4 and IPv6 on a server

A typical VPS has one public IPv4 address and, if the host supports it, an IPv6 subnet. An extra IPv4 address almost always costs money, and the cheapest plans sometimes come without their own IPv4 at all. Here is where the shortage comes from, what you can do with IPv6 alone and which address settings a mail server needs.

> Source: https://accsly.io/en/vps/guide/ipv4-and-ipv6-on-server · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

An IP address is a server's number on the internet. In IPv4 it is 32 bits long, giving about 4.3 billion addresses in total, and some of them are reserved for special-purpose and private networks. In IPv6 the address is 128 bits long, and there are so many addresses that a host can give every server an entire subnet. The two protocols run in parallel: a dual-stack server is reachable both by those who have IPv6 and by those who have only IPv4.

## Why IPv4 ran out and costs money

Free IPv4 addresses were handed out by five regional registries, each in its own part of the world. Their common pool at IANA ran out on 3 February 2011: on that day the last addresses were split equally between the registries. North America's ARIN exhausted its pool on 24 September 2015. Europe's RIPE NCC handed out its last free addresses on 25 November 2019. Since then a new organisation can join the RIPE NCC waiting list and receive just 256 addresses (a /24) when addresses returned by others come back into the pool.

So a host that needs new addresses buys or leases them from other organisations and either passes the cost into the plan price or charges for an extra address separately. According to the accsly catalog as of 2 November 2026, across 140 hosts that state the price of an extra IPv4 unambiguously, the median is about $2.2 a month per address (180 ₽ at the 2 November 2026 rate), and half of the prices range from about $1.9 to $3.4. A free extra address is a rarity.

Hence a practical tip: if the server needs several addresses — separate sites with their own certificates have not required this for a long time, but it can be needed for mail or for separating services — factor them into the plan price from the start.

## NAT VPS and servers without IPv4

To sell servers more cheaply, some hosts do not give each one its own IPv4. There are two variants.

- **NAT VPS**: one external IPv4 for several servers, each with its own small range of ports. The host forwards an incoming connection on a port from your range to your server. That is enough for SSH, a bot that calls APIs itself, or tests. You cannot run a website on ports 80 and 443 without an intermediary, and the PTR and the address reputation are shared with the neighbours.
- **IPv6-only**: the server has IPv6 addresses only. Incoming connections are possible only from those who have IPv6; outgoing ones only to resources reachable over IPv6.

In the accsly catalog, 349 VPS plans from 31 hosts come without their own IPv4. Buy such a plan only if you understand what the server will do and where connections to it will come from.

## IPv6 and the /64 subnet

In IPv6 the address is split in half: the first 64 bits are the network number, the last 64 bits the number of the device within it. This is a requirement of the IPv6 architecture (RFC 4291, discussed in RFC 7421), so the minimum subnet for a single network segment is a /64, and it is not customary to divide it further. In its recommendations for operators (document RIPE-690), RIPE NCC advises giving a customer a /48 or /56, and no less than a /64 per segment.

For a server this means: a /64 holds more than 18 quintillion addresses, and you can put as many IPv6 addresses on one VPS as you need, free of charge. In practice hosts assign them differently — a whole /64, a larger subnet or individual addresses from a shared network — so check the terms if you need many addresses. IPv6 support is confirmed by 703 hosts in the catalog; plans are in the collection [VPS with IPv6](https://accsly.io/en/vps/ipv6).

Three commands check that IPv6 works on the server:

```
ip -6 addr show scope global
ping -6 -c 3 2001:4860:4860::8888
curl -6 -sI https://www.google.com | head -1
```

The first shows the assigned addresses, the second that the server reaches the outside network over IPv6, the third that DNS and HTTPS work. Do not forget the firewall: IPv4 rules do not automatically apply to IPv6. ufw applies them to both protocols, while with hand-written iptables rules you need a separate ip6tables set. The other hardening steps are in [First 10 steps after buying a VPS: security](https://accsly.io/en/vps/guide/vps-security-first-steps).

## When IPv6 alone is enough

An IPv6-only server fits when ordinary visitors do not connect to it directly:

- internal services — a database, a queue, backup storage — that your own IPv6-enabled servers connect to;
- a website behind a CDN or reverse proxy: visitors arrive at the CDN's IPv4 address, and the CDN fetches pages from your server over IPv6 — if the CDN provider supports it;
- test environments and code builds, if all the repositories you need are reachable over IPv6;
- SSH administration, if you yourself have IPv6 at home or in the office.

It is not enough if visitors connect to the server directly — a website without a CDN, a game server, mail — or if the server itself calls services that have no IPv6: some APIs, package mirrors and websites still work over IPv4 only. For outgoing connections to them there is the NAT64 and DNS64 mechanism (RFC 6146 and RFC 6147): the host or a public service translates requests to IPv4 addresses into IPv6. If the host does not provide it, an IPv6-only server cannot reach such resources.

## Reverse DNS (PTR) for mail

An ordinary DNS record maps a name to an address (A for IPv4, AAAA for IPv6). A reverse PTR record maps an address to a name. It matters to mail servers: Google requires senders to have a PTR record for the sending address pointing to a name, and that name in turn must point back to the same address. Without this, mail to Gmail is rejected or lands in spam. The recommendation to keep a matching PTR and A for every address already appears in RFC 1912.

PTR is set by the owner of the address — the host. Usually it is a field in the server control panel or a request to support. The steps:

1. create an A record (and AAAA if mail will go out over IPv6), for example `mail.example.com` → the server address;
2. ask the host, or enter in the panel, a PTR for the same address: address → `mail.example.com`;
3. check with `dig -x server_address +short` — the answer must match the name from the A record;
4. if the server also sends mail over IPv6, the IPv6 address needs a PTR too, otherwise some messages will go out from an address without a reverse record.

On a NAT VPS you cannot set your own PTR: the address is shared. Another requirement for a mail server is an open outbound port 25: some hosts close it by default and open it on request. Plans where this is possible are in the collection [VPS for a mail server](https://accsly.io/en/vps/for-mail-server). For other plan terms worth checking before you pay, see [How to read hosting plans: the hidden limits](https://accsly.io/en/vps/guide/hidden-limits-in-hosting-plans).

## FAQ

### Why does an extra IPv4 address cost money?

Free IPv4 addresses have run out: the common IANA pool in 2011, Europe's RIPE NCC in November 2019. Hosts buy or lease addresses from other organisations and charge for them. According to the accsly catalog, the median is about $2.2 a month per address.

### What is a NAT VPS?

A server without its own public IPv4: several customers share the external address, each with a range of ports. It suits a bot and tests, but not a website on ports 80 and 443 or a mail server.

### What does IPv6 /64 mean?

A subnet in which the first 64 bits of the address are the network number and the last 64 the device number. Under the IPv6 standard it is the minimum subnet for a single network segment, and it holds more than 18 quintillion addresses.

### Can I host a website on IPv6 only?

Not directly: visitors without IPv6 will not be able to open it. What works is a setup where the site sits behind a CDN or proxy with an IPv4 address, which fetches pages from your server over IPv6.

### Why does a mail server need a PTR record?

Mail services check that the sender's address has a reverse DNS record pointing to a name that resolves back to the same address. Google requires this from all senders; without PTR, messages are rejected or go to spam.

### Who sets up PTR?

The owner of the address — the host. PTR is usually set in the server control panel or through a support request. On a NAT VPS you cannot set your own PTR.

_Updated: 2026-11-02_

# Bandwidth and traffic: what 1 Gbps and unlimited really mean

A server plan usually has two network lines: port speed and traffic volume. The first says how fast the server can send data, the second how much it can send in a month. They are linked by simple arithmetic, and once you know it, it is easy to see what "1 Gbps unlimited" actually offers and whether "5 TB" will be enough for you.

> Source: https://accsly.io/en/vps/guide/server-bandwidth-and-traffic · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

Speed is measured in bits per second (Mbps, Gbps), traffic in bytes (GB, TB). A byte has 8 bits and a month has about 2.6 million seconds, so the port and the quota are two sides of the same quantity. The port sets the ceiling, the quota sets the volume, and between them sit two more conditions that are mentioned less often: whether that speed is guaranteed to you and whether you share the port with neighbours.

## Port speed and guaranteed bandwidth

A "1 Gbps port" is the speed of the server's network connection, the maximum it cannot exceed. It is not a promise that you will always get 1 Gbps to any point on the internet. Real speed depends on the load on the host's network, its upstream links and the route to the recipient. Even on an idle port, useful TCP throughput is below the nominal figure because of packet headers: on 1 Gbps, tests usually show about 940 Mbps.

Guaranteed bandwidth (committed rate, CIR) is the speed the host commits to maintaining for you at all times. It is rarely stated for a VPS and more often for dedicated servers: for example, "1 Gbps port, 200 Mbps guaranteed". If no guarantee is stated, assume the port is shared and the speed is "up to".

## Shared port

Virtual servers on one physical host reach the network through the host's shared network cards. When a VPS plan promises 1 Gbps, that is usually the cap on your virtual interface, while the host's uplink is shared by all its customers. While the neighbours send little, you get almost the whole port; when someone saturates the link, everyone's speed drops. That is why hosts write "shared" or "up to 1 Gbps" and limit sustained link saturation in their usage rules.

On a dedicated server the port is usually yours, but behind it there is still a shared switch and the data centre's upstream links. If speed is critical, ask for a trial period or a test file and measure it yourself; how to do that is covered in [How to test VPS ping and speed before you pay](https://accsly.io/en/vps/guide/check-vps-speed-before-buying).

## How to convert terabytes into Mbps

The formula for a 30-day month: 1 TB of traffic equals an average speed of about 3.1 Mbps if it is sent evenly around the clock. The reverse: a port loaded at 100% all month moves 0.324 TB for every 1 Mbps.

| Monthly volume | Average speed | Port loaded at 100% | Monthly volume |
| --- | --- | --- | --- |
| 1 TB | 3.1 Mbps | 100 Mbps | 32.4 TB |
| 5 TB | 15.4 Mbps | 200 Mbps | 64.8 TB |
| 10 TB | 30.9 Mbps | 1 Gbps | 324 TB |
| 32 TB | 99 Mbps | 10 Gbps | 3,240 TB |

The calculation: 1 TB = 8,000,000 Mbit, a month = 2,592,000 seconds, 8,000,000 / 2,592,000 ≈ 3.09 Mbps. Average speed is not peak speed: website traffic is uneven, with more visitors by day than at night, so the port is chosen with headroom above the average.

An example. A page with images weighs 2 MB and gets 10,000 views a day. That is 20 GB a day and about 0.6 TB a month — it fits even a small quota, and the average throughput is under 2 Mbps. Distributing 1 GB files to a thousand people a day, on the other hand, is already 30 TB a month, and that calls for unlimited traffic or a large quota.

## What the 95th percentile is

This is how bandwidth is billed in data centres and on dedicated servers with heavy throughput. Every 5 minutes the host records the current speed. A 30-day month adds up to 8,640 samples. They are sorted, the top 5% — 432 samples, or about 36 hours of the highest traffic — are discarded, and the next value becomes the billable rate. The contract usually has a paid commit level, for example 500 Mbps, and any 95th percentile above it is billed separately per Mbps.

The upside of this scheme is that short peaks are free: a nightly backup or a spike after a publication does not affect the bill if together they take less than 36 hours a month. The downside is that the bill is not known in advance. For a VPS this scheme is almost never used: there you buy a quota in TB or unlimited traffic.

## What "unlimited" means

Unlimited traffic means the volume is not counted. The ceiling is set by the port: on 100 Mbps it is no more than 32.4 TB a month, on 1 Gbps 324 TB. On top of that, a fair use rule almost always applies: under constant link saturation the host may reduce the speed. More on such terms in [How to read hosting plans: the hidden limits](https://accsly.io/en/vps/guide/hidden-limits-in-hosting-plans).

What the accsly catalog shows as of 2 November 2026:

- unlimited traffic is offered on 43% of VPS plans with known traffic terms, 54% of dedicated servers and 64% of shared hosting plans;
- among VPS plans with a stated port speed, 46% are on 1 Gbps, 15% on 100 Mbps and 12% on 10 Gbps;
- among unlimited VPS plans with a stated speed, 18% come with a 100 Mbps port, which means a ceiling of about 32 TB a month;
- the median quota for VPS plans with metered traffic is 5 TB, for dedicated servers 15 TB.

Mind the direction as well: some hosts count only outbound traffic towards the quota, others the sum of inbound and outbound. If the server mostly receives data — for example, it stores backups of other machines — check how it is counted.

## Which connection to choose

- **Website, bot, API, control panel** — 100 Mbps and a quota of a few terabytes are enough. Port speed matters less than placing the server close to your visitors.
- **A website with lots of images and video** — 1 Gbps, a quota from 10 TB or unlimited; heavy files are better served through a CDN. Collection: [VPS with a 1 Gbps port](https://accsly.io/en/vps/1-gbit).
- **File distribution, mirrors, network backups** — unlimited traffic on a port of 1 Gbps or more: [VPS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic). For constant throughput, a dedicated server: [with unlimited traffic](https://accsly.io/en/dedicated/unlimited-traffic) or [with a 10 Gbps port](https://accsly.io/en/dedicated/10-gbit).
- **Short bulk transfers** — moving a database, syncing storage — [VPS with a 10 Gbps port](https://accsly.io/en/vps/10-gbit): the volume is the same, but the transfer takes ten times less time.
- **A website on shared hosting** — [hosting with unlimited traffic](https://accsly.io/en/hosting/unlimited-traffic); port speed is almost never stated there, and the limits apply to CPU and the number of processes instead.

A separate question is protecting the link against DDoS attacks: on a small port the server will not withstand an attack of several gigabits, however much traffic the plan includes. Plans with filtering are in the collection [VPS with DDoS protection](https://accsly.io/en/vps/ddos-protection).

## FAQ

### How much traffic per month does a 1 Gbps port give?

If the port is loaded at 100% around the clock, in 30 days it moves about 324 TB. A 100 Mbps port moves about 32.4 TB, a 10 Gbps port about 3,240 TB.

### How do I convert TB of traffic into Mbps?

For a 30-day month, 1 TB equals an average speed of about 3.1 Mbps. A 5 TB quota is roughly 15 Mbps if the data is sent evenly throughout the month.

### How does port speed differ from guaranteed bandwidth?

Port speed is the maximum the server cannot exceed. Guaranteed bandwidth is the speed the host commits to maintaining at all times. If no guarantee is stated, the port is usually shared and the speed is "up to".

### What is the 95th percentile in bandwidth billing?

Speed is sampled every 5 minutes; over the month the top 5% of samples (about 36 hours) are discarded and the bill is based on the next value. This way short peaks do not affect the price.

### Is unlimited traffic really without limits?

The volume is not counted, but the speed is capped by the port, and a fair use rule usually applies: under constant link saturation the host may reduce the speed.

### Does inbound traffic count?

It depends on the host: some count only outbound traffic, others the sum of inbound and outbound. This is a term of the specific plan: if the server mostly receives data, confirm it in advance.

_Updated: 2026-11-02_

# Docker on a VPS: getting started

Docker lets you run a bot, a website, a database and monitoring on one server without them getting in each other's way, and moving to another VPS comes down to copying a couple of files and the data. Installation takes five minutes; the real trouble starts later: database ports exposed to the internet, logs growing to tens of gigabytes and data that vanished along with a container. Here is how to avoid all of that from the start.

> Source: https://accsly.io/en/vps/guide/docker-on-vps · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A container is an application packaged into an image together with all its libraries and settings. On a server it starts with one command and behaves the same on any Linux. For a VPS this means you do not have to match Python, Node.js or PostgreSQL versions to the system, several projects can share one server, and a `compose.yaml` file describes the whole set of services so that it can be brought up on a new server in minutes.

## What kind of VPS Docker needs

**Virtualization: KVM.** Docker relies on Linux kernel features: namespaces, cgroups and its own network rules. On KVM the server has its own kernel, and Docker works without restrictions. On OpenVZ and LXC the kernel is shared with other customers, and Docker either does not start at all or runs with restrictions that depend on the host. More in [KVM or OpenVZ](https://accsly.io/en/vps/guide/kvm-or-openvz).

**Memory and cores.** Docker itself is light; it is the containers that eat memory. Guidelines:

- 1 GB — one or two light containers: a bot, a small API, monitoring;
- 2 cores and 2 GB — a website with a database and a reverse proxy, a few small services;
- 2–4 cores and 4 GB — several projects, PostgreSQL, Redis, building images right on the server;
- 8 GB or more — GitLab, n8n with many workflows, Elasticsearch and other heavy services.

**Disk.** Images take up space: a base image with Python or Node.js weighs hundreds of megabytes, and old versions pile up with every update. Take at least 30 GB on NVMe, and more if you build images on the server.

According to the accsly catalog as of 1 November 2026, a KVM plan with 2 cores and 2 GB of memory costs about $15 a month at the middle of the market, and a quarter of such plans are cheaper than about $9. With 2 cores and 4 GB the median is about $20, with a quarter cheaper than about $12 (the catalog stores prices in roubles; dollar figures are rounded). Selections: [VPS for Docker](https://accsly.io/en/vps/for-docker), [KVM VPS](https://accsly.io/en/vps/kvm), [VPS with 4 GB](https://accsly.io/en/vps/4-gb-ram). For experiments, [hourly billing](https://accsly.io/en/vps/hourly-billing) is handy: a server for an evening costs pocket change.

## Before installing

Take a fresh Ubuntu 22.04 or 24.04 LTS or Debian 12 and do the basic hardening first: updates, key-based sign-in, a separate user, a firewall. All of it is in [The first 10 steps after buying a VPS](https://accsly.io/en/vps/guide/vps-security-first-steps). A hosting control panel is usually unnecessary on a container server; why is explained in [Server control panels](https://accsly.io/en/vps/guide/server-control-panels).

## Installing from the official repository

The `docker.io` package from the Ubuntu repository often lags behind the current version and does not always include Compose. Installing from Docker's own repository is more reliable. The commands for Ubuntu, following the official documentation:

```
sudo apt update
sudo apt install ca-certificates curl
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc

sudo tee /etc/apt/sources.list.d/docker.sources <<EOF
Types: deb
URIs: https://download.docker.com/linux/ubuntu
Suites: $(. /etc/os-release && echo "${UBUNTU_CODENAME:-$VERSION_CODENAME}")
Components: stable
Architectures: $(dpkg --print-architecture)
Signed-By: /etc/apt/keyrings/docker.asc
EOF

sudo apt update
sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
```

For Debian the commands are the same, except that `linux/ubuntu` in the URLs becomes `linux/debian`, and `VERSION_CODENAME` is used instead of `UBUNTU_CODENAME`. Check the installation:

```
sudo docker run hello-world
docker compose version
```

There is also a one-command installer at get.docker.com, but Docker's own documentation advises against it for production servers: it installs many packages without asking and always takes the latest version.

**The docker group.** To avoid typing `sudo` before every command, the user is added to the docker group: `sudo usermod -aG docker $USER`, then sign in again. Keep in mind that this equals root rights: a member of the group can start a container with access to the server's entire file system. Add only your own working account to it.

## A first Docker Compose project

Separate `docker run` commands with a dozen options are quickly forgotten. It is more convenient to describe the project in a `compose.yaml` file in its own directory, for example `/opt/app`. Here is a web application with a PostgreSQL database:

```
services:
  app:
    image: ghcr.io/example/app:1.4.2
    restart: unless-stopped
    environment:
      DATABASE_URL: postgres://app:${DB_PASSWORD}@db:5432/app
    ports:
      - "127.0.0.1:8080:8080"
    depends_on:
      - db
  db:
    image: postgres:16
    restart: unless-stopped
    environment:
      POSTGRES_USER: app
      POSTGRES_PASSWORD: ${DB_PASSWORD}
    volumes:
      - db-data:/var/lib/postgresql/data

volumes:
  db-data:
```

Put the password next to it in a `.env` file with the line `DB_PASSWORD=...` and make it unreadable for other users: `chmod 600 .env`. Start with `docker compose up -d`, follow the log with `docker compose logs -f app`, stop with `docker compose down`.

Three things in this example matter:

- `restart: unless-stopped` — the containers come back up after a server reboot;
- the database has no `ports` section: the application reaches it by the name `db` on the project's internal network, and it is not reachable from outside;
- the application port is published only on `127.0.0.1`, and nginx or Caddy with a TLS certificate serves it to the outside world.

## Ports and the firewall

This is the main trap for beginners. When a container publishes a port as `"5432:5432"`, Docker adds iptables rules itself, and that port is opened to the internet regardless of your ufw or firewalld rules. Docker's documentation warns about this directly: published container ports are not subject to the firewall rules. This is exactly how PostgreSQL, MongoDB and Redis databases without a password most often end up on the internet.

The rule is simple: publish externally only what should be reachable by everyone — usually ports 80 and 443 of the reverse proxy. Everything else goes either without a `ports` section or bound to `127.0.0.1`. You can check what the server is actually listening on with `ss -tlnp`, and from outside, from another computer, with `nc -zv server-IP 5432`.

## Logs and disk space

By default Docker writes container output to JSON files with no size limit. A chatty application fills the disk in a couple of months, and the server stops working. Limit logs for all containers in `/etc/docker/daemon.json`:

```
{
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "10m",
    "max-file": "3"
  }
}
```

Then run `sudo systemctl restart docker`. The setting applies to containers created after it, so recreate your projects: `docker compose up -d --force-recreate`.

The second disk hog is old images. `docker system df` shows how much space is used, and `docker image prune -a` removes unused images. Do not run `docker system prune --volumes` unless you understand it: it also deletes the volumes of stopped projects along with their data.

## Where data lives and how to back it up

Anything the application wrote inside a container disappears when the container is recreated. Only what lives in volumes (`volumes`) or in mounted server directories survives. Before running any image, check its documentation for which directories need to go into a volume: for PostgreSQL it is `/var/lib/postgresql/data`, other applications have their own paths.

Copying database files while the database is running is unreliable. Take a dump through the container itself:

```
docker compose exec -T db pg_dump -U app app | gzip > /backup/app-$(date +%F).sql.gz
```

Add this command to cron and send the copies off the server, together with `compose.yaml` and `.env`. How to set up external storage and test the copies is covered in [VPS backups](https://accsly.io/en/vps/guide/vps-backups).

## Updating containers

Pin a specific image version in `compose.yaml` (`postgres:16`, `app:1.4.2`) rather than `latest`: then an update happens when you plan it, not on a random restart. The update procedure:

1. take a database dump;
2. change the version in `compose.yaml`;
3. `docker compose pull` and `docker compose up -d`;
4. check the log and that the application works, then remove the old image.

Major database versions, for example PostgreSQL 16 → 17, cannot be updated this way: the new version needs the data moved over with a dump and restore. Update the server's system and Docker itself with the usual `apt upgrade`.

## Where to go next

Once a server hosts several projects, it is worth adding a reverse proxy that obtains certificates on its own, plus uptime monitoring. A bot in Python or Node.js in a container needs only a small server; details in [VPS for a Telegram bot](https://accsly.io/en/vps/guide/vps-for-telegram-bot). If containers multiply and one server is no longer enough, the next step is several servers under an orchestrator; plans are in [VPS for Kubernetes](https://accsly.io/en/vps/for-kubernetes). For automation and CI in containers there are the [VPS for n8n](https://accsly.io/en/vps/for-n8n) and [VPS for GitLab](https://accsly.io/en/vps/for-gitlab) selections.

## FAQ

### Can I run Docker on any VPS?

You need KVM or another full virtualization with its own kernel. On OpenVZ and LXC the kernel is shared with other customers, and Docker either does not work there or works with restrictions.

### How much memory does a VPS for Docker need?

One or two light containers fit in 1 GB. For a website with a database and a reverse proxy, take 2 cores and 2 GB; for several projects with PostgreSQL and Redis, 4 GB. Disk: at least 30 GB on NVMe.

### How do I install Docker on Ubuntu?

Add the official Docker repository and install the docker-ce, docker-ce-cli, containerd.io, docker-buildx-plugin and docker-compose-plugin packages. Check the installation with sudo docker run hello-world.

### Why does ufw not close a container port?

Docker adds its own iptables rules for published ports, and they apply regardless of ufw. Do not publish database ports, and bind application ports to 127.0.0.1 and serve them through a reverse proxy.

### Why did Docker fill up the whole disk?

Most often the culprits are container logs, which have no size limit by default, and old images. Set max-size and max-file in /etc/docker/daemon.json and periodically remove unused images with docker image prune -a.

### Will data be lost if I delete a container?

Yes, if it was stored inside the container. Only data in volumes and mounted server directories survives. Additionally back up databases as dumps stored off the server.

_Updated: 2026-11-01_

# How to move a website from shared hosting to a VPS

The move itself takes a couple of hours; the mistakes usually happen around it: a forgotten cron job, .htaccess rules that nginx does not read, an AAAA record with the old address, or mail that disappeared along with the IP change. Below is the order of steps with commands and checks for a PHP and MySQL site.

> Source: https://accsly.io/en/vps/guide/move-site-hosting-to-vps · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

This article is about how to move. Whether to move at all and which server to get is covered in [When to move from shared hosting to a VPS](https://accsly.io/en/vps/guide/hosting-to-vps-when). Here we assume the VPS is already bought and the site runs on WordPress, Bitrix, Laravel or another PHP engine with a MySQL database. For other stacks the order is the same, only the commands change.

## Timeline: a move in four stages

1. **Two days before:** write down everything that runs on the hosting and lower the TTL of the DNS records.
2. **A day before:** prepare the server, copy the files and the database, test the site at the new address.
3. **Moving day:** close the site to writes, transfer the fresh data, change DNS.
4. **One to two weeks after:** keep the hosting running as a fallback.

## What to write down on the hosting

Almost all problems after a move are things that worked on the hosting by themselves and were forgotten. Go through the hosting control panel and write down:

- **The PHP version and extensions.** You can see them in the panel or over SSH with `php -v` and `php -m`. Install the same version on the VPS, and upgrade PHP separately, later.
- **The database version and size**, and the table encoding.
- **Cron jobs**: what runs and how often. File paths on the VPS will be different.
- **Rules in .htaccess**: redirects, friendly URLs, folder access restrictions.
- **Mail**: mailboxes, forwards, where the MX records point.
- **Subdomains and all DNS records**, including TXT records for service verification.
- **External services that know the site's IP.** Payment systems, 1C data exchange, partner APIs and mail services often accept requests only from allowed addresses. The new IP has to be added there in advance.

A day or two before the move, lower the TTL of the domain's A and AAAA records to 300 seconds. Then on switch-over day the new address will propagate in minutes rather than a day.

## Prepare the server

Start with basic protection: updates, key login, a firewall. All of this is collected in [First 10 steps after buying a VPS: security](https://accsly.io/en/vps/guide/vps-security-first-steps). Then there are two paths.

**With a control panel.** ISPmanager, FASTPANEL or aaPanel install the web server, the right PHP version and the database in a few clicks and give you an interface familiar from shared hosting. Plans with them: [VPS with ISPmanager](https://accsly.io/en/vps/ispmanager), [VPS with FASTPANEL](https://accsly.io/en/vps/fastpanel), [VPS with aaPanel](https://accsly.io/en/vps/aapanel). How the panels differ in price and features is covered in [Server control panels: ISPmanager, FASTPANEL, aaPanel](https://accsly.io/en/vps/guide/server-control-panels).

**Without a panel.** On Ubuntu and Debian the minimal set is installed with one command; packages without a version number pull in the PHP that ships with the system:

```
apt install nginx mariadb-server php-fpm php-mysql php-curl php-gd php-mbstring php-xml php-zip php-intl
```

If the hosting had an older or newer PHP version than the system's, install it from third-party repositories with PHP packages for Ubuntu and Debian.

Keep in mind the main difference from shared hosting: **nginx does not read .htaccess**. Redirects and friendly URLs have to be moved into the site configuration. For WordPress the main rule looks like this: `try_files $uri $uri/ /index.php?$args;`. If there are many rules, it is easier to put Apache behind nginx: that is how most panels work, and .htaccess keeps working.

## Move the files

If the hosting has SSH access, the fastest way is to pull the files directly from the VPS with rsync:

```
rsync -avz user@old-host.example:~/public_html/ /var/www/example.com/
```

Running the same command again transfers only what has changed, which will come in handy on moving day. If there is no SSH, there are two options: build an archive in the panel's file manager and download it to the server with `wget`, or fetch the files over FTP with the lftp utility:

```
lftp -u user old-host.example -e "mirror --parallel=4 public_html /var/www/example.com; quit"
```

Plain FTP sends the password in clear text, so if the hosting supports SFTP or FTPS, use them. After copying, give the files to the web server user and set the usual permissions:

```
chown -R www-data:www-data /var/www/example.com
find /var/www/example.com -type d -exec chmod 755 {} +
find /var/www/example.com -type f -exec chmod 644 {} +
```

## Move the database

Make a dump on the hosting. Over SSH:

```
mysqldump --single-transaction --default-character-set=utf8mb4 -u user -p dbname | gzip > db.sql.gz
```

Without SSH the dump is exported through phpMyAdmin, but it may not cope with large databases because of the hosting's time limits; in that case ask support for a dump or make it in parts. On the VPS, create the database and the user and load the dump:

```
mysql -e "CREATE DATABASE site CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
CREATE USER 'site'@'localhost' IDENTIFIED BY 'strong_password';
GRANT ALL PRIVILEGES ON site.* TO 'site'@'localhost';"
zcat db.sql.gz | mysql site
```

A common error during import is `Unknown collation: 'utf8mb4_0900_ai_ci'`. It means the dump was made in MySQL 8, while the VPS runs MariaDB, which does not know this collation. Either install the same DBMS on the VPS as on the hosting, or replace the collation in the dump with `utf8mb4_unicode_ci`.

Then put the new database credentials into the site settings: for WordPress that is `wp-config.php`, for Bitrix `/bitrix/.settings.php` and `/bitrix/php_interface/dbconn.php`, for Laravel the `.env` file. The database server is now `localhost`.

## Move the cron jobs

Run jobs as the site user, not as root: `crontab -u www-data -e`. Check the paths: on the hosting the site lived in something like `/home/user/public_html`, on the VPS in `/var/www/example.com`, and the path to PHP may differ too (`which php`). Separately check the tasks the host ran for you: Bitrix agents on cron, 1C data exchange, sending emails from the queue.

## Test the site before changing DNS

Visitors are still going to the hosting, while you can open the new server on your own machine. Map the domain to the server's IP in your computer's hosts file (`/etc/hosts` on Linux and macOS, `C:\Windows\System32\drivers\etc\hosts` on Windows):

```
203.0.113.10  example.com www.example.com
```

Go through the home page, catalog, product page, search, forms, cart and admin login, and upload an image. Watch the error log at the same time: `tail -f /var/log/nginx/error.log`. To quickly check the server's response without a browser: `curl -I --resolve example.com:80:203.0.113.10 http://example.com/`.

Typical problems at this step:

- **502 Bad Gateway**: nginx cannot reach PHP-FPM, because the socket path in the site configuration does not match the one in the PHP pool settings.
- **A blank page or error 500**: a PHP extension is missing. Its exact name will be in the error log.
- **Large files do not upload**: by default nginx limits the request body to 1 MB (`client_max_body_size`), and PHP limits it with `upload_max_filesize` and `post_max_size`.
- **Links lead to 404**: the .htaccess rules were not moved.

## TLS certificate

The usual domain validation for a free certificate goes over HTTP to the address DNS currently points to, that is, to the hosting. So before the switch there are three options:

- Get a certificate via DNS validation: `certbot certonly --manual --preferred-challenges dns -d example.com -d www.example.com`. certbot will ask you to add a TXT record. Such a certificate does not renew itself, so after the move issue a regular one.
- Temporarily move the current certificate and key from the hosting, if the panel lets you export them.
- Change DNS and immediately issue a certificate with `certbot --nginx -d example.com -d www.example.com`. For a few minutes the site will show an error over HTTPS; for a small site this is acceptable.

After issuing, check automatic renewal: `certbot renew --dry-run`.

## Moving day

1. Close the site to writes: turn on maintenance mode or at least stop taking orders and comments. For a shop this is a few minutes.
2. Run the same rsync command once more: it will transfer only the changes.
3. Make a fresh database dump and load it on the VPS over the old one.
4. Change the A record of the domain and www to the server's IP. If the domain has an **AAAA** record with the hosting's IPv6 address, replace it with the server's IPv6 or delete it, otherwise some visitors will keep landing on the old server.
5. Check that the new records are visible: `dig +short example.com A @8.8.8.8` and `dig +short example.com AAAA @8.8.8.8`.
6. Open the site for writes, now on the VPS.

## Do not lose your mail

This is the most common trouble with a move. Check where MX points: `dig +short example.com MX`. If it is `example.com` or `mail.example.com` that resolves to the same IP as the site, changing the A record will send mail to the VPS, where there is no mail server. Before the switch, create a separate record for mail with the hosting's old IP and put it in MX, or better, move the domain's mail to a separate mail service in advance.

If the site sends emails (orders, password resets), check them after the move. Emails from a new IP without an SPF record will land in spam: either add the server's IP to SPF, or send emails through a mail service's SMTP. Your own mail server on a VPS is a separate task; plans for it are in [VPS for a mail server](https://accsly.io/en/vps/for-mail-server).

## After the move, and rollback

Do not shut down the hosting for one or two weeks. In the first hours, check the old database: if someone placed an order on the old server between the final dump and the DNS change, move it over by hand. After a couple of days, look at the hosting's access log: if people are still coming there, the old address is left somewhere, most often in the AAAA or www record.

Rollback is simple while the hosting is running: put the old IP back in DNS, and thanks to the short TTL visitors will return to the hosting within minutes. When everything is stable, set the TTL back to normal values, set up backups following [VPS backups: strategies and tools](https://accsly.io/en/vps/guide/vps-backups), and add external monitoring. Plans for websites: [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for WordPress](https://accsly.io/en/vps/for-wordpress), [VPS for an online store](https://accsly.io/en/vps/for-online-store), [VPS for Bitrix](https://accsly.io/ru/vps/for-bitrix). For a first trial build, [hourly billing](https://accsly.io/en/vps/hourly-billing) is convenient.

## FAQ

### How long does it take to move a website to a VPS?

For an ordinary CMS site, preparing the server, copying and testing take from a couple of hours to a day. Moving day itself, with the final sync and DNS change, takes about an hour, and the site is closed to writes for a few minutes.

### Can I move a website without downtime?

Yes, if you lower the TTL of the DNS records in advance, build and test the site on the VPS via the hosts file, and on moving day close it to writes only for the duration of the final sync. Visitors can read the site the whole time.

### How do I move a website if the hosting has no SSH?

Files as an archive from the panel's file manager or over FTP with lftp, the database as an export through phpMyAdmin. If the database is large and the export breaks off, ask the hosting support for a dump.

### What happens to the domain's mail after the IP change?

If MX points to the domain itself or to a subdomain with the same IP as the site, mail will go to the VPS and be lost. Before the switch, point MX to a separate record with the old IP or move mail to a mail service.

### Do I need to move the SSL certificate?

Not necessarily. A free certificate can be issued again: before the DNS change via a TXT record, after it via the usual HTTP validation. A paid certificate is moved together with its private key.

### How do I roll back if something goes wrong on the VPS?

Put the hosting's old IP back in DNS. With a short TTL visitors will return within minutes, which is why the hosting is worth keeping on for one or two weeks after the move.

_Updated: 2026-10-31_

# Server control panels: ISPmanager, FASTPANEL, aaPanel

A panel turns a VPS into the kind of dashboard you know from shared hosting: sites, databases, mail and certificates are set up with a few clicks instead of editing config files. The three panels most often installed on Russian and budget international servers are ISPmanager, FASTPANEL and aaPanel. They differ in price, memory requirements and how much of the server they take over.

> Source: https://accsly.io/en/vps/guide/server-control-panels · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A control panel is a web interface on top of ordinary Linux. It installs a web server, several PHP versions, a database server, a mail server and FTP, and then writes their configuration itself whenever you add a site, a database or a mailbox. That is convenient if you are moving from shared hosting and would rather not learn nginx, or if one server hosts sites for several clients. The price of convenience is the memory the panel takes and the rule "configure only through the panel": it may overwrite manual edits to config files.

## In short: how the three panels differ

|  | ISPmanager 6 | FASTPANEL | aaPanel |
| --- | --- | --- | --- |
| Price | Lite €6.49, Pro €12.99, Host €22.99 a month; 14-day trial | Free, including for commercial use; extended licence €4.20 a month | Free edition; paid Pro with a 14-day trial |
| Number of sites | Lite — 10, Pro — 50, Host — unlimited | Unlimited | Unlimited |
| Minimum memory | 512 MB — 1 GB for a minimal install; 1.5 GB or more on AlmaLinux and Rocky | 1 GB, 5 GB of disk | 512 MB, 768 MB — 1 GB recommended |
| Needs a clean system | Preferably; the panel disables SELinux | Required | Required |
| Interface language | Russian, English | Russian, English | Mostly English |
| Hosts in the accsly catalog | 188 | 39 | 18 |

ISPmanager prices are from the international site and apply since 1 February 2026; the Russian site lists the same editions at 512, 1,026 and 1,832 ₽ a month as of 1 November 2026. Hosts often sell the licence cheaper or include it in the plan, so compare the total price of the server with the panel. The host count comes from the accsly catalog as of 1 November 2026: how many companies offer the panel when you order a VPS.

## ISPmanager: the Russian market standard

The most widespread panel in Russia: almost every large Russian host offers it, and if you have used shared hosting there, the interface is probably familiar. The editions differ in the number of sites: Lite is designed for 10 sites, Pro for 50 and adds Docker management and resource limits through CloudLinux, and Host removes the limit and is meant for those who resell hosting themselves.

What it does: different PHP versions for different sites, nginx in front of Apache or plain nginx, MySQL, MariaDB and PostgreSQL, mail with spam filtering, DNS, free certificates, scheduled backups, installing WordPress and other engines in a couple of clicks, importing sites from another server. For someone running several sites on 1C-Bitrix it is the most proven option: many Bitrix guides are written specifically for ISPmanager.

The downside is price: the licence is paid every month, and it became more expensive in 2026. If the host includes the panel in the plan, the downside goes away. Plans: [VPS with ISPmanager](https://accsly.io/en/vps/ispmanager).

## FASTPANEL: free and simple

FASTPANEL is free for end users and hosts, including for commercial use, with no limit on the number of sites. The paid extended licence adds metrics export, white label and help with the server, but an ordinary site owner does not need it.

The panel installs nginx and Apache, several PHP versions, MySQL or MariaDB (you pick the version during setup), PostgreSQL, a mail server with webmail, FTP and phpMyAdmin, takes backups and issues certificates. The interface is simpler than ISPmanager's and is designed for a single owner with a dozen or two sites.

Installation is one command on a fresh Debian, Ubuntu, AlmaLinux or Rocky Linux system:

```
wget https://repo.fastpanel.direct/install_fastpanel.sh -O - | bash -
```

Afterwards the panel opens at `https://server-IP:8888`; the installer prints the login and password at the end. On first sign-in the panel asks for an email address, where the free licence is sent. Important: FASTPANEL will not install on a server that already runs nginx, Apache or MySQL. Plans: [VPS with FASTPANEL](https://accsly.io/en/vps/fastpanel).

## aaPanel: lots of ready-made apps

aaPanel is the international version of BT Panel, a popular Chinese panel. The basic edition is free; the paid Pro adds extra modules. Its strong point is the app store: besides nginx or Apache with PHP and MySQL, you can install Redis, PostgreSQL, a Docker manager and other services in a couple of clicks.

The panel is lightweight: it needs about 60 MB of memory itself, so a 1 GB server still has room for sites. The interface, documentation and community are mostly in English. Like FASTPANEL, aaPanel requires a clean system with no web server, PHP or MySQL installed beforehand. Take the install command only from the official site aapanel.com: it changes with each panel version.

The installer prints the panel address with its port, the login and the password at the end. Save them and turn on HTTPS in the panel settings right away. Plans: [VPS with aaPanel](https://accsly.io/en/vps/aapanel).

## Which one to choose

- **One to three sites on WordPress or another CMS, minimal budget** — FASTPANEL: free, no limits, interface available in Russian and English.
- **Client sites, Bitrix, Russian-language support and separate access rights needed** — ISPmanager, preferably from a host that includes the licence in the plan.
- **A non-standard stack: Node.js, Redis, Docker alongside the sites** — aaPanel, if an English interface suits you.
- **cPanel or Plesk required**, for example because a client asks for it or the team is used to it — they cost more; plans are in [VPS with cPanel](https://accsly.io/en/vps/cpanel) and [VPS with Plesk](https://accsly.io/en/vps/plesk). A free alternative built on a similar idea is [HestiaCP](https://accsly.io/en/vps/hestiacp).

Count memory as the panel plus everything it runs. The panel itself is small, but the full set of services — web server, PHP-FPM, MySQL, mail with spam filtering — takes hundreds of megabytes before the first visitor arrives. A sensible minimum for a site with a panel is 2 GB of memory; for several sites with mail, 4 GB. More on memory and cores in [How much memory and how many cores a website needs](https://accsly.io/en/vps/guide/ram-and-cpu-for-website).

## When you do not need a panel

A panel is unnecessary if the server runs a single application that you deploy from Git or in containers: a bot, an API, a Python or Node.js service. The panel will get in the way: it expects sites to be created through it and may overwrite your changes to the nginx configuration. For such a server it is easier to install the packages you need by hand or run everything in Docker; see [Docker on a VPS: getting started](https://accsly.io/en/vps/guide/docker-on-vps).

Another case is when you already configure nginx and PHP-FPM confidently yourself. A couple of sites on plain nginx save memory and do not depend on panel updates.

## Panel security

A panel is root-level access through a browser, and its port gets scanned just like SSH. The minimum worth doing right after installation:

- change the administrator password issued by the installer or the host;
- turn on two-factor sign-in if the panel supports it;
- open the panel port in the firewall only for your own IP addresses and close it for everyone else;
- enable HTTPS for the panel itself and automatic updates;
- do not run two panels on one server at the same time, and do not install a panel on top of a server you have already configured by hand.

The remaining steps — updates, key-based sign-in, firewall — are collected in [The first 10 steps after buying a VPS](https://accsly.io/en/vps/guide/vps-security-first-steps). Backups made by the panel are stored on the same server by default, so set up copying to external storage as described in [VPS backups](https://accsly.io/en/vps/guide/vps-backups). If you are moving sites from shared hosting, the order of steps is in [How to move a website from shared hosting to a VPS](https://accsly.io/en/vps/guide/move-site-hosting-to-vps).

## FAQ

### Which VPS control panel is free?

FASTPANEL is free with no limit on the number of sites, including for commercial use. aaPanel has a free basic edition. ISPmanager is paid, but it works for 14 days after installation without payment, and many hosts include the licence in the plan.

### How much does ISPmanager cost?

On the international site, since 1 February 2026: Lite for 10 sites is €6.49 a month, Pro for 50 sites €12.99, and Host with unlimited sites €22.99. Hosts often sell the licence cheaper or include it in the server price.

### How much memory does a VPS with a control panel need?

The panels install on a server with 512 MB — 1 GB of memory, but together with the web server, PHP, MySQL and mail a sensible minimum for one site is 2 GB, and 4 GB for several sites with mail.

### Can I install a panel on a server that already runs a site?

FASTPANEL and aaPanel require a clean system and will not install on a configured server. For any panel, the more reliable route is to get a new server and move the sites to it.

### ISPmanager or FASTPANEL: which should I choose?

For a single owner with several sites, the free FASTPANEL is enough. ISPmanager is more convenient when the server hosts sites of different clients with separate access rights and resource limits, as well as for Bitrix and when you need Russian-language support.

### Do I need a panel for a bot or an app in Docker?

Usually not. A panel is built for sites and mail and may overwrite manual nginx settings. A single application is easier to deploy by hand or in containers.

_Updated: 2026-11-01_

# Windows VPS for 1C

A rented server for 1C saves you from the office PC under a desk that nobody updates or backs up. But 1C on a VPS has its own quirks: the software licence is tied to the parameters of the virtual machine, users need both 1C and Windows licences, and core speed matters more than core count. Here is how to put together a 1C server for a small company.

> Source: https://accsly.io/en/vps/guide/windows-vps-for-1c · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

This article is for a company where 1–10 people work in 1C:Accounting, Trade Management or Salary and HR Management and want to move the database from an office computer to a server in a data centre. How the Windows Server licence itself works and how to lock down RDP sign-in is covered in detail in [Windows VPS: licensing, RDP and secure sign-in](https://accsly.io/en/vps/guide/windows-vps-license-rdp). Here we cover what 1C adds on top.

## Three ways to run it

**File database and remote desktop.** The database sits on the server, the 1C platform is installed there too, and users connect to the server over RDP and work in their own sessions. This is the simplest option: you need nothing besides Windows and 1C. It suits 1–5 users. As the number of people and the size of the database grow, file mode starts to slow down under simultaneous writes, and if the database file is damaged in a crash, everyone is affected at once.

**Client-server option.** The VPS runs the 1C:Enterprise server and a database server — Microsoft SQL Server or PostgreSQL. Users connect with the thin client or over RDP. This setup handles more users and larger databases, but it needs a 1C server licence, more memory and an administrator who knows how to configure it. Companies usually switch to it when there are more than five people or the database has grown past a few gigabytes.

**Publishing on a web server.** The database is published through IIS or Apache, and users work in a browser or the thin client over HTTPS, without remote desktop. Then you need no licences for RDP sessions, but not every external data processor or piece of hardware works through the web client. This setup is often combined with RDP for the accountant who needs full access.

## 1C licences on a virtual server

- **Client licences** are always required: one per simultaneous connection. In file mode over RDP all users work on one server, and the licences are activated on it.
- **A 1C server licence** is needed only for the client-server option. For small companies there is the "Server MINI" edition for 5 connections; it still requires client licences.
- **A software licence is tied to the machine's parameters**: network name, amount of memory, processor and motherboard model, network card. For a virtual server these are the parameters the virtual machine reports. If the host moves the server to a node with a different processor or you reduce memory when changing plans, the licence may stop working.
- **Reactivation** is done with a spare PIN code: a licence comes with one main and two spare PIN codes. When the spare ones run out, the 1C company issues new PIN codes on request. Adding memory or disk usually does not reset the licence; reducing them does.

A hardware USB key cannot be attached to a virtual server directly, so software licences are used on a VPS. Before renting, ask the host whether the virtual machine's parameters change when it is moved between nodes and when you change plans. If the host promises to keep the processor model and MAC address, licences last for years.

## Windows licences for 1C users

Without additional licences, Windows Server allows two people to connect over RDP at the same time, and those connections are intended for administration. If three or more accountants work in 1C through remote desktop, you need the Remote Desktop Session Host role and a licence for each user. From a host this is a monthly RDS SAL, and for a small team it can cost about as much as the server itself. Check its price before ordering.

Another route is a 1C server on Linux. The platform supports the 1C:Enterprise server on Linux with PostgreSQL; then no Windows Server licence is needed, and users work through the thin client. This saves money but requires an administrator familiar with Linux and PostgreSQL.

## How much memory and how many cores

According to Microsoft's requirements, Windows Server 2022 itself starts with 2 GB of memory, and for Windows Server 2025 with the desktop experience Microsoft recommends 4 GB. On top of that, each 1C session over RDP takes 300–500 MB on average, and in the client-server option the 1C server and the database server use memory to cache the database. Guidelines for typical configurations:

| Users | Setup | Cores | Memory | Disk |
| --- | --- | --- | --- | --- |
| 1–2 | File database, RDP | 2 | 4 GB | 60 GB NVMe or more |
| 3–5 | File database, RDP | 4 | 8 GB | 80 GB NVMe or more |
| 5–10 | 1C server and database server, RDP or thin client | 4–8 | 16 GB | 120 GB NVMe or more |

These are starting points, not a rule: heavy configurations such as Integrated Automation and data exchange with a website need more. After a month of use, check the load in Task Manager and, if resources are short, move to a bigger plan, keeping the software licence in mind.

For 1C, core frequency matters more than the number of cores: posting documents and month-end closing run mostly in a single thread. Look for plans with processors from 3 GHz; the selection is [VPS with high CPU frequency](https://accsly.io/en/vps/high-frequency). Take NVMe disks only: a file database constantly reads and writes in small chunks; more in [NVMe or SSD](https://accsly.io/en/vps/guide/nvme-or-ssd).

## What a 1C server costs

According to the accsly catalog as of 1 November 2026, plans in Russian data centres that can run Windows cost the following (the catalog stores prices in roubles; dollar figures are rounded):

- **4 GB of memory**: about $16 a month at the middle of the market, a quarter of the plans cheaper than about $12;
- **8 GB**: median about $30, a quarter cheaper than about $21;
- **16 GB**: median about $66.

Note that some plans include the Windows licence in the price and others add it as an option, which raises the total. RDS licences for users and 1C licences are paid separately. Windows plans in Russia from hosts that invoice legal entities are collected in [VPS for 1C](https://accsly.io/ru/vps/for-1c); all Windows plans are in [VPS with Windows](https://accsly.io/en/vps/windows) and [RDP server](https://accsly.io/en/vps/rdp).

For 1C the server location is almost always Russia: under Russian law, personal data of employees and counterparties must be stored in databases inside the country, exchanges with banks and electronic document flow work faster, and the company receives the accounting documents it needs from the host. More in [How to choose a country for your server](https://accsly.io/en/vps/guide/choose-server-country).

## Database backups

Copies the host makes as disk snapshots protect against a server failure, but not against an accountant who deleted documents a week ago. 1C needs its own backups:

- **file database** — an export to a .dt file from the Designer or a copy of the 1Cv8.1CD file while nobody is working in the database, for example on a nightly schedule;
- **client-server database** — a regular dump with the database server's own tools: SQL Server backup or `pg_dump` for PostgreSQL.

Store the copies off the server and at least once a quarter check that the database can be restored from them. How to set up such copying is described in [VPS backups](https://accsly.io/en/vps/guide/vps-backups).

## Checklist before ordering

- The setup is chosen: file database over RDP, client-server option or publishing on a web server.
- 1C client licences are counted and, if needed, a server licence.
- The price of Windows in the plan is known, and of RDS SALs if there are more than two users.
- The host has confirmed that the virtual machine's parameters do not change when it is moved between nodes.
- Processor from 3 GHz, NVMe disk, memory with headroom according to the table above.
- The server is in Russia, and the host issues invoices and accounting documents to the company.
- RDP sign-in is open only to office and staff addresses, and database backups off the server are set up.

## FAQ

### Can I run 1C on a VPS?

Yes. Most often the database is placed on a Windows server and users work in it through remote desktop. For 5–10 users and large databases, a 1C server with SQL Server or PostgreSQL is installed, or the database is published on a web server.

### How much memory does a VPS for 1C need?

For 1–2 users of a file database over RDP, about 4 GB; for 3–5 users, 8 GB; for the client-server option with 5–10 users, 16 GB or more. Core frequency matters more than core count: from 3 GHz.

### Will my 1C licence stop working on a VPS?

A software licence is tied to the parameters of the virtual machine. It may need reactivation if you reduce memory or if the host moves the server to a node with a different processor. For this the licence comes with two spare PIN codes.

### Do I need a 1C server licence?

Only for the client-server option. With a file database that users work in over RDP, client licences are enough. For small companies there is "Server MINI" for 5 connections.

### How many accountants can work on a Windows VPS at the same time?

Without additional licences, Windows Server accepts two RDP connections for administration. If three or more people work on it, you need an RDS licence for each user; from a host these are paid monthly.

### How much does a VPS for 1C cost?

According to the accsly catalog as of 1 November 2026, a plan with 4 GB of memory in a Russian data centre that can run Windows costs about $16 a month at the middle of the market, and one with 8 GB about $30 (rounded from roubles). Windows, RDS and 1C licences may be paid separately.

_Updated: 2026-11-01_

# Windows VPS: licensing, RDP and secure sign-in

A Windows server costs more than Linux not only because of memory: the price includes a licence, and how it is arranged decides whether you are compliant and how many people can connect. An exposed RDP port is also the most common way such servers get hacked. Here are both topics.

> Source: https://accsly.io/en/vps/guide/windows-vps-license-rdp · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

Choosing the Windows Server version and the right amount of memory is covered on the selection pages. This article is about two things a plan usually describes in one line or not at all: on what basis the host gives you Windows, and how to make sure only you can sign in. Check both before paying: re-licensing a server or rebuilding it after a breach costs more than picking the right plan from the start.

## How hosts license Windows Server

A host does not buy a boxed copy of Windows for every customer. Providers use Microsoft's SPLA programme (Services Provider License Agreement): licences are rented and paid to Microsoft monthly based on actual use. That is why Windows is a monthly surcharge in the plan and why it disappears when you delete the server.

Under SPLA, Windows Server is licensed per core. When licensing by virtual machine, the host pays for as many core licences as the VM has virtual cores, but no fewer than eight per VM. So the Windows surcharge on a small 1–2 vCPU plan is almost the same as on an 8 vCPU plan, and as a share of the server price it looks large. On cheap plans Windows sometimes costs more than the server itself.

What to check in the plan description:

- it states explicitly that the licence is included in the price or added as an option, not just "Windows image" or "Windows installation";
- which edition: Standard or Datacenter. For a single VPS it usually makes no difference to you; what matters is that there is a licence;
- how much Windows costs on renewal and when you add cores.

If the plan only provides a system image without a licence, Windows will run unactivated with reminders and restrictions, and the compliance of that use is on you.

## Can you bring your own licence

Technically yes: on KVM you can boot your own ISO image. Legally it depends on the type of licence.

- **Retail and OEM keys** sold in online stores do not give the right to run Windows Server on a host's shared hardware. An OEM licence is also tied to one specific physical server.
- **Volume licences with Software Assurance or subscription licences** can since October 2022 be moved to third-party providers, including shared hardware (the Flexible Virtualization Benefit). The exception is the largest public clouds on Microsoft's list, which have separate rules.

If the company has no active Software Assurance, a plan with the host's licence is simpler and safer. Your own licence makes sense when it is already paid for under a volume agreement.

Desktop Windows 10 and 11 are a separate case. They are not part of SPLA, and their licence terms are not designed for rental on shared hardware. Details are on the [VPS with Windows 10](https://accsly.io/en/vps/windows-10) and [VPS with Windows 11](https://accsly.io/en/vps/windows-11) pages.

## How many people can connect over RDP

Without additional licences, Windows Server accepts two simultaneous RDP connections, intended for administration. If staff work on the server, such as accounting, managers or operators, you need the Remote Desktop Session Host role and a licence for each user.

| Scenario | What you need | Who pays |
| --- | --- | --- |
| 1–2 administrators | Nothing beyond the Windows Server licence | Included in the plan |
| Staff work on the server | RD Session Host role and a licence per user | From the host: an RDS SAL per user per month |
| Your own licence infrastructure | An RDS licensing server and rights to use it at a provider | The company, under its own agreement |

Under SPLA the per-user licence is called an RDS SAL and is counted monthly: if a user was given access for even one day of the month, the whole month is paid. Ask the host whether it sells these licences and at what price; for a small team this can double the server budget. How to size memory and cores per user is described on the [RDP server](https://accsly.io/en/vps/rdp) page.

## Why RDP is attacked most

Port 3389 is scanned constantly: a new Windows server with RDP open starts receiving sign-in attempts within minutes of getting its IP. There are two main threats.

- **Password guessing.** Bots try common usernames, Administrator first of all, and passwords from leaked databases. This is the most frequent cause of break-ins.
- **Vulnerabilities in the RDP service itself.** An example is BlueKeep (CVE-2019-0708) in 2019: a flaw in older Windows versions allowed code execution without a password. The fix shipped in updates, and no system without it should be on the internet.

Protection is built in layers: first limit who can reach RDP at all, then make sign-in harder, then close vulnerabilities with updates.

## Layer 1: network

- **IP allowlist.** Allow the RDP port in Windows Firewall for your own addresses only. If the host offers a network filter in its panel, duplicate the rule there so unwanted traffic never reaches the server.
- **Corporate private network.** If staff addresses change, connect them to the server through the company VPN gateway and let RDP listen only on the internal network. How to build that setup is explained in [Corporate network on a VPS](https://accsly.io/en/vps/guide/corporate-vpn-on-vps).
- **Remote Desktop Gateway (RD Gateway).** It carries RDP inside HTTPS over port 443, checks users against access policies and lets you add a second factor. Useful when there are many users and you would rather not install VPN clients for them.

Moving RDP off port 3389 reduces log noise but does not protect you: scanners find RDP on non-standard ports too.

## Layer 2: sign-in

- **Network Level Authentication (NLA).** The user enters credentials before the server opens a full session. This saves resources during brute-force attempts and blocks some vulnerabilities that trigger before sign-in. It should always be on.
- **Lockout policy.** On systems installed with the October 2022 updates or newer, a lockout of 10 minutes after 10 failed attempts applies by default, including for the built-in administrator. Older images may not have it; check in Local Security Policy.
- **Separate accounts.** Every employee gets their own account without administrator rights. Rename or disable the built-in Administrator, and change the password the host sent you at the first sign-in.
- **Second factor.** For servers with access to money and personal data, add two-factor authentication through RD Gateway or a third-party Windows sign-in solution.

## Layer 3: updates and recovery

Fixes for RDP, SMB and the Windows kernel ship every month on the second Tuesday. Turn on automatic installation with a reboot in a night window and keep an eye on the version's support dates: Windows Server 2016 receives fixes until 12 January 2027, 2019 until 9 January 2029, 2022 until 14 October 2031, and 2025 until 14 November 2034. A server on an unsupported version stays vulnerable no matter how well sign-in is locked down.

Keep a data backup off the server and a snapshot of the clean system after setup. If the security log shows a successful sign-in from an unknown address, it is safer to reinstall from a template and restore the data than to hunt for what the attacker changed. Version specifics are on the [Windows Server 2022](https://accsly.io/en/vps/windows-server-2022) and [Windows Server 2025](https://accsly.io/en/vps/windows-server-2025) pages.

## Checklist: the first hour on a Windows VPS

- The plan description mentions a Windows Server licence, and the renewal price is known.
- If there are more than two users, RDS SALs from the host are sorted out.
- The host's password is replaced, and the built-in Administrator is renamed or disabled.
- NLA is on, and the account lockout policy is in effect.
- RDP is open only to your IPs, through the company private network or through RD Gateway.
- Automatic updates are on, and the Windows version is still supported.
- There is a data backup off the server and a snapshot taken after setup.

Plans with the licence already included are collected in [VPS with Windows](https://accsly.io/en/vps/windows) and [cheap Windows VPS](https://accsly.io/en/vps/cheap-windows). How to put together a server for 1C is covered in [Windows VPS for 1C](https://accsly.io/en/vps/guide/windows-vps-for-1c), and general server selection criteria in [How to choose a VPS](https://accsly.io/en/vps/guide/how-to-choose-vps).

## FAQ

### Is the Windows licence included in the VPS price?

Usually yes, or it is added as a paid option. The host pays Microsoft monthly under the SPLA programme. Make sure the plan mentions the licence itself and not just a system image.

### Why is Windows so expensive on a cheap VPS?

Under SPLA, Windows Server is licensed per core with a minimum of eight core licences per virtual machine. Even for a 1–2 vCPU server the host pays as if it had eight cores.

### Can I buy a Windows Server key and install it on a VPS?

Retail and OEM keys do not give the right to run the system on a host's shared hardware. Volume licences with Software Assurance or subscription licences can be moved to a provider.

### How many users can work on a Windows VPS over RDP?

Without extra licences, two simultaneous sessions for administration. Staff need the RD Session Host role and per-user licences; from a host these are RDS SALs billed monthly.

### Is changing the RDP port enough?

No. A non-standard port reduces sign-in attempts in the log, but scanners still find it. What protects you is an IP allowlist, the company private network or RD Gateway, together with NLA and lockout after failed attempts.

### What should I do if someone else signed in to my Windows VPS?

Block RDP for every address except yours, change the passwords of all accounts and save the data you need. The safest option is to reinstall from a clean template and restore data from a backup taken before the incident.

_Updated: 2026-10-22_

# When to move from shared hosting to a VPS

A VPS does not make a site faster by itself: it gives you resources and freedom, and with them the job of running a server. Here is how to tell that hosting has become too small, when the problem can be solved without moving, and how to migrate a site so visitors notice nothing.

> Source: https://accsly.io/en/vps/guide/hosting-to-vps-when · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A move from shared hosting to a VPS often starts with "the site is slow". Sometimes that really is the ceiling of a shared server, and sometimes it is a heavy plugin, unoptimized images or missing caching, which will be just as slow on a VPS. Before paying more and taking on server administration, find out what exactly the site is hitting. Below: the signs that justify a move, the cases where it will not help, an honest cost estimate and a step-by-step plan.

## Signs that hosting has become too small

- **The site hits account limits.** Shared hosting limits CPU time, memory, concurrent processes and the number of files (inodes). When they are exceeded, the site returns 503 errors or 508 Resource Limit Is Reached, and the panel shows graphs pinned to the ceiling. If this happens on ordinary days, not only during spikes, the account does not have enough resources.
- **You need software the host will not install.** A Node.js or Python application that runs constantly, Redis, a search engine, job queues, non-standard PHP extensions, your own database version.
- **You need background processes.** Queue workers, websockets, bots, product imports more often than the host's cron allows, long scripts that the hosting kills on timeout.
- **There are many projects.** A dozen sites on one account share the same limits, and a problem with one slows the others. On a VPS you can split them into PHP pools with separate limits.
- **You need control over the environment.** Your own web server configuration, access to logs, custom firewall rules, isolation requirements from a client or an audit.

## When moving will not help

If the site is slow under light load, the cause is usually the site itself. On a VPS with the same settings it will be just as slow, only more expensive.

- Pages take long to build because of dozens of plugins or a heavy theme: page caching and a plugin audit help.
- A page weighs several megabytes because of images: compression, modern formats and lazy loading help.
- Slow database queries: indexes and cleaning up tables help.
- The hosting server is far from the audience: changing the hosting location is enough, no VPS required.

An intermediate step is a higher hosting plan with larger limits. If the only problem is limits and you need no software beyond the standard set, this is cheaper and needs no administration. Plans for several sites are collected in [hosting for 10 sites](https://accsly.io/en/hosting/10-sites).

## What a VPS really costs

Comparing the price of hosting with the price of a VPS directly is misleading: hosting already includes things you will have to pay for or do yourself on a VPS.

| Cost item | Shared hosting | VPS |
| --- | --- | --- |
| Server | Included in the plan | Plan price, usually from 2 GB of memory for a CMS site |
| Control panel | Included | Free or paid licence, or no panel |
| Backups | Usually included | Often a separate service or your own setup |
| Domain email | Included | Your own mail server or a separate service |
| Updates and security | Done by the host | Done by you or an administrator |

The main hidden cost is time. System updates, monitoring, certificate renewals and fixing problems at night are now yours. If nobody can administer the server, look for managed plans from the host or budget for an administrator.

## Which VPS to take for a site from shared hosting

Look at the usage graphs in the hosting panel for the last month: they show how much CPU and memory the site actually uses at peak.

- One or two sites on WordPress or another CMS: 2 vCPU, 2 GB of memory, 30–40 GB NVMe.
- A store with a catalogue of thousands of products or several busy sites: 2–4 vCPU, 4 GB of memory.
- Add a control panel to the estimate if you install one: it takes part of the memory and disk.

Ready-made selections: [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for WordPress](https://accsly.io/en/vps/for-wordpress) and [VPS for an online store](https://accsly.io/en/vps/for-online-store). How to read the other plan parameters is covered in [How to choose a VPS](https://accsly.io/en/vps/guide/how-to-choose-vps). For a first move, [hourly billing](https://accsly.io/en/vps/hourly-billing) is convenient: you can build the server, test the site and only then pay for a month.

## What to do before the move

- **Inventory.** Write down the PHP version and enabled extensions, the database version, cron jobs, redirects and .htaccess rules, mailboxes and forwards, subdomains.
- **Email.** On shared hosting, email usually lives on the same account. A mail server of your own on a VPS needs PTR, SPF, DKIM and DMARC set up, and many hosts block outgoing port 25 by default. It is often easier to move the domain's email to a separate mail service before moving the site. If you do want mail on your own server, see [VPS for a mail server](https://accsly.io/en/vps/for-mail-server).
- **DNS TTL.** A day or two before the switch, lower the TTL of the domain's A record to 300 seconds so the address change propagates quickly.
- **A fresh backup** of files and database on the hosting: your rollback point if something goes wrong.

## A migration plan without downtime

Here is the short version of the order; the detailed one, with commands and the usual mistakes, is in [How to move a website from shared hosting to a VPS](https://accsly.io/en/vps/guide/move-site-hosting-to-vps).

1. Prepare the VPS: update the system, create a user for SSH key login, enable the firewall, install the web server, the right PHP version and the database. Where to start with securing the server is covered in [First 10 steps after buying a VPS: security](https://accsly.io/en/vps/guide/vps-security-first-steps).
2. Move the site files and the database dump, create a database user with the same privileges, move the cron jobs.
3. Test the site on the new server without changing DNS: map the domain to the new IP in the hosts file on your computer and go through the main pages, forms and cart.
4. Issue a TLS certificate on the new server. If HTTP domain validation is not possible before the DNS change, use DNS record validation.
5. Put the site into read-only mode for the final sync (for a store, a few minutes without new orders) and move a fresh database dump.
6. Change the A record to the new IP. Thanks to the short TTL, most visitors will reach the new server within half an hour.
7. Keep the hosting for at least a week: watch the new server's logs and keep the old copy as a fallback.

## After the move

Set up automatic security updates, a daily backup off the server (how to set it up is in [VPS backups: strategies and tools](https://accsly.io/en/vps/guide/vps-backups)), external uptime monitoring and log rotation. Check disk and network speed on the new server; the method is in [How to test VPS ping and speed before you pay](https://accsly.io/en/vps/guide/check-vps-speed-before-buying). If after a few months the server is constantly loaded to the limit, the next step may be a larger plan or a [dedicated server](https://accsly.io/en/dedicated). And if it turns out you do not need a VPS, you can move back to [shared hosting](https://accsly.io/en/hosting) the same way.

## FAQ

### How do I know my site has outgrown shared hosting?

The site regularly returns 503 or 508 errors, and the CPU, memory or process graphs in the panel hit the limit on ordinary days. Another sign is that you need software or a background process the host does not allow.

### Will my site be faster on a VPS?

Only if it was hitting the limits of the shared server. If the problem is slow pages, heavy images or database queries, the site will be just as slow. Turn on caching and review plugins first.

### How much memory does a VPS need for a WordPress site?

For one or two sites, 2 GB and 2 vCPU with an NVMe disk are enough. For a store or several busy sites take 4 GB, and add a control panel to the estimate if you use one.

### What do I do with email when moving to a VPS?

The easiest option is to move the domain's email to a separate mail service before moving the site. Your own mail server on a VPS needs PTR, SPF, DKIM and DMARC, and many hosts block outgoing port 25 by default.

### How do I migrate a site without downtime?

Lower the DNS record TTL in advance, build and test the site on the VPS through the hosts file, move a fresh database and only then change the IP in DNS. Keep the old hosting for a week as a fallback.

### Do I need to know how to administer a server?

Yes, on a VPS updates, security and backups are your job. If nobody can administer it, choose a managed plan from the host or stay on a higher shared hosting plan.

_Updated: 2026-10-22_

# VPS backups: strategies and tools

On a VPS, backups are your job, even if the plan says "backups included". We go through what exactly to back up, why a host snapshot is not enough, how to set up restic or BorgBackup in half an hour, and how to make sure you can actually restore from a backup.

> Source: https://accsly.io/en/vps/guide/vps-backups · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

People usually remember backups at the moment they need one: an update broke the database, someone deleted the site folder, the host's disk failed or the server was hacked. In each of these cases what saves you is not just any copy, but one that is stored somewhere else, was made recently and that you have restored from at least once. Below is how to set up such a backup on an ordinary Linux server.

## A host snapshot is not a strategy yet

Many hosts offer disk snapshots and automatic backups in their control panel. This is useful, but such a copy has three weak points.

- **It is stored at the same host.** A billing error, a closed account, a data center outage or a stolen control panel password take away both the server and all its snapshots at once.
- **There are few copies and they are infrequent.** Often it is one or two latest copies made once a day or once a week. If a failure is noticed a few days later, there may be no good version left.
- **The database in a snapshot is not always intact.** A snapshot captures the disk at an arbitrary moment, as if the server had suddenly been switched off. InnoDB and PostgreSQL usually recover from this, but there is no guarantee, and MyISAM tables may end up corrupted.

A snapshot is handy as a quick restore point before an update. Your main backups are worth making with your own tools and storing separately.

## The 3-2-1 rule

The classic scheme goes like this: three copies of the data, on two different media or systems, one of them in another location. For a VPS this usually looks like this:

1. The working data on the server itself.
2. A copy on another server or in S3 object storage at another host, or at least in another data center.
3. One more copy: snapshots in the host's panel, a second backup server or a download to a storage device at home.

It is worth adding one more rule: at least one copy must be impossible to delete from the production server itself. If an attacker gets root, they also see the passwords to the backup storage. How to set this up is covered below in the section on protection from deletion.

## What to back up

There is usually no need to copy the whole system: a clean server comes up from a template in minutes. What is valuable is the data and the settings.

| What | Where it usually lives | How to back it up |
| --- | --- | --- |
| Site files and user uploads | `/var/www`, `/home` | As files |
| Databases | `/var/lib/mysql`, `/var/lib/postgresql` | Only as a dump, not as files |
| System and service settings | `/etc` | As files, together with the certificates from `/etc/letsencrypt` |
| Scheduled tasks | `/etc/cron.d`, users' `crontab -l` | As files or exported to text |
| Container data | Docker volumes, usually `/var/lib/docker/volumes` | As files with the container stopped, or as a dump of the database inside it |

Exclude caches, temporary files, logs and `node_modules`: they bloat the backup and rebuild themselves.

## Databases: dumps only

You must not copy the database files of a running server: they change while being copied, and the copy ends up inconsistent. The right way is a dump. For MySQL and MariaDB:

```
mysqldump --single-transaction --routines --triggers shop | gzip > /var/backups/shop-$(date +%F).sql.gz
```

The `--single-transaction` flag makes a consistent dump of InnoDB tables without stopping writes. It does not protect MyISAM tables: if you have any, convert them to InnoDB or dump with `--lock-all-tables`. On Debian and Ubuntu root logs in to MariaDB without a password through the socket, so the command works as is when run as root; for another user, put the login and password in `~/.my.cnf` with permissions 600.

For PostgreSQL:

```
sudo -u postgres pg_dump -Fc shop > /var/backups/shop-$(date +%F).dump
sudo -u postgres pg_dumpall --globals-only > /var/backups/pg-globals.sql
```

The second file saves roles and privileges that are not included in the dump of a single database. Such a dump is restored with `pg_restore -d shop file.dump`. If the database is tens of gigabytes and the dump takes too long, look at physical backups: mariabackup or Percona XtraBackup for MySQL, pgBackRest for PostgreSQL.

Put the dumps in one folder, for example `/var/backups`, and include it in the file backup, so everything goes to storage with a single command.

## Tools: rsync, restic, BorgBackup

|  | rsync | restic | BorgBackup |
| --- | --- | --- | --- |
| Backup versions | Only manually via `--link-dest` | Yes, snapshots | Yes, archives |
| Encryption | No, only in transit over SSH | Always, on the source server | Yes, optional when creating the repository |
| Deduplication | No | Yes | Yes, plus compression |
| Where it can store | Disk, SSH | Disk, SFTP, S3, its own REST server | Disk, SSH with borg on the other side |
| Append-only mode | No | Via rest-server | Via `borg serve --append-only` |

### rsync: a mirror, not a backup

rsync syncs folders quickly, but on its own it is not a backup: a file deleted or damaged on the server will be deleted or damaged in the mirror on the next run too. You can get versions with the `--link-dest` flag: each run creates a new folder, and the unchanged files in it are hard links to the previous one, so space is used only for changes. It is more convenient to run this on the backup server, which pulls the data from the production server itself:

```
rsync -a --delete --link-dest=/backup/web/2026-10-30 root@web.example.com:/var/www/ /backup/web/2026-10-31/
```

This is enough for a single site, but rsync gives you neither encryption nor integrity checks.

### restic

restic is a single program with no dependencies. It encrypts data before sending it, stores only new chunks of files and can write to SFTP, S3-compatible storage or its own rest-server. The repository is created once, after that a backup takes one command:

```
export RESTIC_REPOSITORY=sftp:backup@storage.example.com:/srv/restic/web1
export RESTIC_PASSWORD_FILE=/root/.restic-pass

restic init
restic backup /etc /var/www /var/backups --exclude-caches
restic forget --keep-daily 7 --keep-weekly 4 --keep-monthly 6 --prune
restic check
```

The `forget` command keeps 7 daily, 4 weekly and 6 monthly snapshots, and `--prune` frees the space taken by the rest. Without the password from `/root/.restic-pass` the repository cannot be decrypted at all, so keep a copy of it off the server, for example in a password manager.

### BorgBackup

Borg is similar to restic, but usually compresses better and is faster with large numbers of small files. It keeps the repository on a disk or on another server over SSH, where borg must also be installed; it does not support S3 directly. The stable branch in 2026 is 1.4; version 2.0 is still in beta and not recommended for production backups. Commands for 1.4:

```
export BORG_REPO=ssh://backup@storage.example.com/./web1
export BORG_PASSCOMMAND="cat /root/.borg-pass"

borg init --encryption=repokey-blake2
borg create --stats --compression zstd ::'{hostname}-{now}' /etc /var/www /var/backups
borg prune --keep-daily 7 --keep-weekly 4 --keep-monthly 6
borg compact
```

Since 1.2, space after `prune` is freed only by the `compact` command. In repokey mode the key is stored in the repository itself, protected by the passphrase; to be safe, export it with `borg key export` and keep it off the server.

If the server has a control panel, look at its built-in backups: in ISPmanager, FASTPANEL and aaPanel they are configured in the interface and can send archives to external storage. Plans with panels: [ISPmanager](https://accsly.io/en/vps/ispmanager), [FASTPANEL](https://accsly.io/en/vps/fastpanel), [aaPanel](https://accsly.io/en/vps/aapanel).

## Where to store backups

- **A separate VPS at another host.** Backups do not need a fast CPU, they need a large disk. Such plans are collected in [VPS for data storage](https://accsly.io/en/vps/storage), [VPS with HDD](https://accsly.io/en/vps/hdd) and [VPS for backups](https://accsly.io/en/vps/for-backups).
- **S3 object storage.** You pay for the gigabytes used, and restic writes there directly. If the storage supports object versioning or a time-limited delete lock, that also protects against deletion.
- **A storage device at home or in the office.** Good as a third copy: the backup server pulls the data over SSH itself, and nobody can connect to it from outside.

If the database holds personal data of Russian citizens, keep Federal Law 152-FZ in mind: backups are also better kept on servers in Russia, see [VPS for 152-FZ](https://accsly.io/ru/vps/for-152-fz).

## Protection from deletion

The worst case is when an attacker or a faulty script deletes both the data and the backups. There are three ways to prevent this.

- **Pull, do not push.** The backup server connects to the production server itself and pulls the data. The production server has no access to the backups at all.
- **Append-only mode.** For borg, the production server's key in `authorized_keys` on the backup server is given a command: `command="borg serve --append-only --restrict-to-path /srv/borg/web1",restrict ssh-ed25519 AAAA…`. New archives can be added, old ones cannot be deleted. For restic the same is done by rest-server started with the `--append-only` flag. Old backups are then pruned from a trusted machine with a different key.
- **Versioning and delete lock in S3.** The storage itself keeps previous versions of objects for a set period.

## Schedule and how often to back up

The frequency depends on how much data you are prepared to lose. For a blog, a daily backup is enough. For a shop where orders come in all day, dump the database every hour and back up the files once a day. Run the backup from cron or a systemd timer at night, for example with a `/etc/cron.d/backup` file containing the line `30 3 * * * root /usr/local/bin/backup.sh`.

A backup that has quietly stopped running is worse than no backup: you think you are protected. At the end of the script, send a signal to external monitoring (a plain `curl` to the check URL), and if the signal does not arrive on time, the monitoring will message you.

## Test the restore

Once a month, restore a backup to a clean server and check that the site opens and the data is in place. [Hourly billing](https://accsly.io/en/vps/hourly-billing) is convenient for this: you pay for the test server only for the hours it runs.

```
restic restore latest --target /tmp/restore --include /var/www/site
restic check --read-data-subset=10%
borg extract ::web1-2026-10-31T03:30:00 var/www/site   # archive name comes from borg list
borg check --verify-data
```

The second and fourth commands read the actual data in the repository, not just its index, and find damaged chunks. Write down the restore procedure in a separate file off the server: in the middle of an outage there is no time to recall commands. How to prepare the new server you will restore to is described in [First 10 steps after buying a VPS: security](https://accsly.io/en/vps/guide/vps-security-first-steps), and moving a whole site is covered in [How to move a website from shared hosting to a VPS](https://accsly.io/en/vps/guide/move-site-hosting-to-vps).

## FAQ

### How is a snapshot different from a backup?

A snapshot captures the whole disk at one moment and is stored at the same host. A backup is made with your own tools, stored elsewhere and contains several versions of the data. A snapshot is handy before an update, but it does not replace backups.

### Which is better: restic or BorgBackup?

Both encrypt data and store only changes. restic is easier to install and can write straight to S3; borg usually compresses better, but borg must also be installed on the backup server. For one or two servers the difference is small.

### How much space do backups need?

The first backup takes roughly the size of the data, less with borg thanks to compression. After that only changes are stored, so a month of daily backups of a site often fits into one and a half to two times the size of the data itself. The output of restic stats or borg info after a couple of weeks will give a more precise figure.

### Can I keep backups at the same host?

As an additional copy, yes, preferably in another data center. The main external copy is better kept at another host: then account problems or an outage will not affect both places at once.

### How often should I back up a website?

As often as the amount of data you are prepared to lose dictates. A blog is fine with once a day; a shop should dump the database every hour and back up files once a day. A sensible retention is 7 daily, 4 weekly and a few monthly backups.

### Can I copy the database folder instead of making a dump?

Only if the database server is stopped. On a running server the files change while being copied, and the copy may fail to start. Use mysqldump with --single-transaction or pg_dump.

_Updated: 2026-10-31_

# First 10 steps after buying a VPS: security

Bots start guessing passwords on a new server within minutes of it getting a public IP. Below are ten steps that close the most common holes in about an hour: commands for Ubuntu and Debian, the differences for AlmaLinux and Rocky Linux, and the checks that keep you from locking yourself out of your own server.

> Source: https://accsly.io/en/vps/guide/vps-security-first-steps · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

The server you have just paid for is already visible to the whole internet. Bots scan addresses one after another and try to log in over SSH as root with popular passwords, so the first attempts by strangers show up in the log within the same hour. The good news is that simple things protect you from mass attacks: key-only login, closed ports you do not need, and updates. Everything below is done once, in about an hour, ideally before the site and any data land on the server.

The commands are for Ubuntu and Debian; the differences for AlmaLinux and Rocky Linux are noted separately. Run them as root or with `sudo`.

## Before you start: a spare way in

Find the server console in your host's control panel: it is called VNC, KVM console or emergency console, and it shows the server's screen right in the browser. You can log in through it even when SSH no longer lets you in. While you change login settings, keep your current SSH session open and test every change in a second window. That way a config mistake costs a couple of minutes rather than a system reinstall.

## 1. Update the system

Hosts build their OS templates in advance, and by the time you install one it often has a dozen security fixes that have not been applied.

```
apt update && apt full-upgrade -y     # Ubuntu, Debian
dnf upgrade -y                         # AlmaLinux, Rocky Linux
```

If the kernel was updated, reboot the server. On Ubuntu and Debian the sign is the file `/var/run/reboot-required`: if it exists, a reboot is needed.

## 2. Create a separate user

Working as root all the time is inconvenient and dangerous: any typo runs with full privileges, and every bot knows the name root. Create your own user and give it `sudo` rights:

```
adduser deploy
usermod -aG sudo deploy      # Ubuntu, Debian
usermod -aG wheel deploy     # AlmaLinux, Rocky Linux
```

On AlmaLinux and Rocky Linux the `adduser` command asks nothing, and the password is set separately: `passwd deploy`. Pick any name except the obvious admin and user.

## 3. Log in with an SSH key

Unlike a password, a key cannot be guessed by brute force. Create the key pair on your own computer, not on the server, and copy the public part to the server:

```
ssh-keygen -t ed25519 -C "laptop"
ssh-copy-id deploy@SERVER_IP
```

Windows 10 and 11 have a built-in OpenSSH client but no `ssh-copy-id`. In that case open the `.pub` file and paste its line into `/home/deploy/.ssh/authorized_keys` on the server; the `.ssh` folder must have permissions 700, the file 600, and the owner must be the user. Many hosts let you add a key when you order, in which case it is already in root's account.

Check in a new window that login works without a password and that `sudo` is available: `ssh deploy@SERVER_IP`, then `sudo -v`. Only then move on to the next step.

## 4. Turn off password and root login

It is easiest not to edit the main file but to put your settings in a separate file in `/etc/ssh/sshd_config.d/`. One important detail: for each option sshd takes the first value it finds, and it reads the files in this folder in alphabetical order. Ubuntu cloud images sometimes have a `50-cloud-init.conf` file there with the line `PasswordAuthentication yes`, so give your file a number below 50, for example `/etc/ssh/sshd_config.d/10-hardening.conf`:

```
PermitRootLogin no
PasswordAuthentication no
KbdInteractiveAuthentication no
```

Check the syntax and which values the server will actually apply, then reload the settings:

```
sshd -t && sshd -T | grep -Ei 'permitrootlogin|passwordauthentication'
systemctl reload ssh       # Ubuntu, Debian
systemctl reload sshd      # AlmaLinux, Rocky Linux
```

Do not close the old session until you have logged in as your user with the key in a second window. An attempt to log in as root should be refused.

Moving SSH from port 22 to another one is optional. It removes almost all automated login attempts from the log, but the protection comes from the key, not the port number. If you do change it, open the new port in the firewall first. On Ubuntu 22.10 and later SSH is started through a systemd socket, and after changing `Port` you need to run `systemctl daemon-reload` and `systemctl restart ssh.socket`, otherwise the server keeps listening on 22.

## 5. Turn on the firewall

The rule is simple: all incoming connections are denied except those going to services that must be reachable from outside. For a website that means SSH, 80 and 443. On Ubuntu ufw is convenient; on Debian install it with `apt install ufw`:

```
ufw default deny incoming
ufw default allow outgoing
ufw allow OpenSSH
ufw allow 80,443/tcp
ufw enable
ufw status verbose
```

The order matters: allow SSH first, then enable. AlmaLinux and Rocky Linux already run firewalld, and SSH is allowed in it by default; the web ports are opened like this:

```
firewall-cmd --permanent --add-service=http --add-service=https
firewall-cmd --reload
firewall-cmd --list-all
```

If the server will run Docker, keep one of its quirks in mind: it writes its own iptables rules, and a published container port such as `-p 3306:3306` becomes reachable from the internet even if ufw does not allow it. Publish internal ports on the local address only: `-p 127.0.0.1:3306:3306`. Plans for containers are collected in [VPS for Docker](https://accsly.io/en/vps/for-docker).

Many hosts also have a network firewall in front of the server in their panel. It does not replace the system one, but it is useful as a second layer. DDoS protection is a separate service at the host's network level; plans that include it are in [VPS with DDoS protection](https://accsly.io/en/vps/ddos-protection).

## 6. Install fail2ban

fail2ban reads the logs and temporarily bans addresses that keep failing to log in. With key-only login it mostly keeps the log clean, but it is also handy for other services: control panels, mail, the site's login page.

```
apt install fail2ban python3-systemd
```

Put your settings in `/etc/fail2ban/jail.local`, not in `jail.conf`, which gets overwritten on update:

```
[sshd]
enabled = true
backend = systemd
maxretry = 5
bantime = 1h
```

The `backend = systemd` line is needed on Debian 12 and later: there is no `/var/log/auth.log` file by default, the login log lives in journald, and without this line fail2ban finds nothing to read. Without your own settings it bans an address for 10 minutes after 5 failed attempts within 10 minutes. After editing, run `systemctl restart fail2ban` and check: `fail2ban-client status sshd`. On AlmaLinux and Rocky Linux the package comes from the EPEL repository: `dnf install epel-release`, then `dnf install fail2ban` and `systemctl enable --now fail2ban`.

## 7. Turn on automatic security updates

Most server break-ins use vulnerabilities for which a fix has already been released and simply was not installed. On Ubuntu the unattended-upgrades package is installed and enabled by default; check it with `systemctl status unattended-upgrades`. On Debian you install and enable it like this:

```
apt install unattended-upgrades
dpkg-reconfigure -plow unattended-upgrades
```

By default it installs only security updates. The kernel will not be updated without a reboot: either reboot the server yourself when you see the sign from step 1, or enable an automatic night-time reboot with the `Unattended-Upgrade::Automatic-Reboot` and `Automatic-Reboot-Time` options in `/etc/apt/apt.conf.d/50unattended-upgrades`.

On AlmaLinux and Rocky Linux dnf-automatic does the same job. Install the package with `dnf install dnf-automatic`, set `upgrade_type = security` and `apply_updates = yes` in `/etc/dnf/automatic.conf` (without the latter, updates are only downloaded) and enable the timer: `systemctl enable --now dnf-automatic.timer`.

## 8. Check what the server is listening on

Host templates and control panels sometimes start services you never asked for. List all open ports:

```
ss -tulpn
```

Anything listening on `0.0.0.0` or `[::]` is reachable from outside if the firewall lets it through. Apart from SSH and the web server, there should be no such services. MySQL, MariaDB, PostgreSQL and Redis databases should listen only on `127.0.0.1`: the Debian and Ubuntu packages are set up that way by default, but after an install through Docker or a third-party script it is worth checking. Stop services you do not need and remove them from startup: `systemctl disable --now service_name`. To see the server the way an outsider does, run this from another computer: `nmap -Pn SERVER_IP`.

## 9. Time, logs and monitoring

Run `timedatectl` to check that the clock is synchronized (the line `System clock synchronized: yes`). Wrong time breaks certificate checks, one-time codes and log analysis. Who logged in to the server and when is shown by `last -a | head` and `journalctl -u ssh --since today` (on AlmaLinux the service is called `sshd`).

Connect external uptime monitoring: there are plenty of free services that open your site once a minute and message you when something fails. Set up a separate alert for disk usage too: a full disk is a common reason why a site and its database stop working in the middle of the night.

## 10. Make a restore point and secure the host's panel

Once the server is set up, take a disk snapshot in the host's panel if the feature is available: you will be able to return to the clean, configured system in minutes. A snapshot does not replace backups, because it is stored at the same host. How to set up real copies off the server is covered in [VPS backups: strategies and tools](https://accsly.io/en/vps/guide/vps-backups).

Turn on two-factor login for your account with the host. From that account the server can be reinstalled, the root password reset or the console opened, and a well-protected SSH means nothing if the account can be opened with a stolen password. Keep the private SSH key only on your own devices and protect it with a passphrase.

## What not to do

- **Do not disable SELinux** on AlmaLinux and Rocky Linux at the first permission error. Almost always the right label on the site folder or a single permission via `setsebool` is enough.
- **Do not set permissions to 777** on site folders. Files should be owned by the web server user or a separate site user, with 755 for folders and 644 for files.
- **Do not run applications as root.** A bot, a site or a task queue is fine with its own user without `sudo`.
- **Do not expose the control panel and phpMyAdmin** to everyone at their standard addresses. Allow access to them only from your own IP or through an SSH tunnel.

To pick a system for the new server, see [VPS with Ubuntu](https://accsly.io/en/vps/ubuntu), [VPS with Debian](https://accsly.io/en/vps/debian) and [VPS with AlmaLinux](https://accsly.io/en/vps/almalinux). If the server is for a site moving from shared hosting, the next step is described in [How to move a website from shared hosting to a VPS](https://accsly.io/en/vps/guide/move-site-hosting-to-vps), and what to look at when choosing the plan itself is in [How to choose a VPS: the 7 specs that matter](https://accsly.io/en/vps/guide/how-to-choose-vps).

## FAQ

### Should I move SSH to a non-standard port?

It is optional. Another port removes almost all automated login attempts from the log, but what protects the server is key login with passwords turned off. If you change the port, open it in the firewall first, and on Ubuntu 22.10 and later run systemctl daemon-reload and systemctl restart ssh.socket after the change.

### What if I lose access to the server after changing SSH settings?

Open the server console in the host's panel (VNC or emergency console), log in with the password and fix the file in /etc/ssh/sshd_config.d/. If no password is set, most hosts have a rescue mode in which the server's disk can be mounted and fixed.

### Is fail2ban enough if I keep password login?

No. fail2ban slows down guessing from a single address, but bots come from thousands of addresses. Reliable protection is key login with PasswordAuthentication no, and fail2ban is an extra layer.

### Do I need a system firewall if the host has a network one?

Yes. The host's network firewall is configured in the panel and not every host has one, while ufw or firewalld runs on the server itself and moves with it. It is best to use both.

### How often should I update a VPS?

Security updates are best installed automatically every day with unattended-upgrades or dnf-automatic. Updates that change program versions, and the reboot for a new kernel, are easier to do by hand every week or two, after a fresh backup.

### Do I need antivirus on a Linux server?

For the server itself, updates, key login and closed ports matter more. A scanner such as ClamAV makes sense if users upload files to the site that other people then download.

_Updated: 2026-10-31_

# How to choose a country for your server

Put the server where your visitors are. For an audience across Europe, Germany, the Netherlands and Finland are convenient; for North America, the US East Coast. If you serve EU users, keeping the data in the EU makes GDPR simpler. Price hardly decides it: at the same host a server in Frankfurt, Amsterdam or New York usually costs the same, and only Asia and Australia are noticeably more expensive.

> Source: https://accsly.io/en/vps/guide/choose-server-country · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A server country comes down to three questions, and the first two are usually enough. Where do the people who will open the site or connect to the server live? Does the site handle personal data, such as sign-ups, orders with names and addresses, or contact forms, and whose data is it? Only then, if two options are equal, comes the question of where it is cheaper and how it is easier to pay.

Below I go through each question, show what the same server costs in different countries, and how to measure in ten minutes which country is closer to your users, not on the map but over the network.

## Every thousand kilometres costs 10 ms

A signal in optical fibre travels about 200 km per millisecond. Ping measures the round trip, so every 100 km in a straight line adds about 1 ms, and a real cable is always longer than the straight line. Hence these rough figures:

| Server in | From London | From Frankfurt | From New York |
| --- | --- | --- | --- |
| London | 1–5 ms | 12–18 ms | 70–80 ms |
| Amsterdam | 5–10 ms | 7–10 ms | 75–85 ms |
| Frankfurt | 12–18 ms | 1–5 ms | 85–95 ms |
| Helsinki | 35–40 ms | 25–30 ms | 100–110 ms |
| US East Coast | 70–80 ms | 85–95 ms | 1–10 ms |
| US West Coast | 135–150 ms | 145–160 ms | 60–70 ms |
| Singapore | 160–180 ms | 150–170 ms | 220–240 ms |
| Tokyo | 220–240 ms | 230–250 ms | 160–180 ms |
| Sydney | 250–280 ms | 260–290 ms | 200–220 ms |

These are guidelines, not a promise. The route between two networks can go through a third country and double the delay, so check your candidates yourself, as shown below.

What does this mean for a website? On the first visit the browser exchanges three or four round trips with the server before it gets the first byte of the page: the connection, encryption, the request itself. The difference between a ping of 10 and 50 ms turns into 0.12–0.16 seconds on the first load. For a blog that is barely noticeable. For a shop where a page loads data with several requests, it is. And for a game server or a remote desktop, the difference between 20 and 120 ms is felt in every mouse movement.

## In a big country the city matters more than the country

If your visitors are in California and the server is in New York, they are 60–70 ms away, almost as far as New York is from London. For a site with an audience across the whole United States, the East Coast (New York, Virginia) or the centre of the country (Chicago, Dallas) is a sensible middle ground, because the main backbones of all large networks meet there. If nearly all your customers are on one coast, look for a data centre on that coast: [VPS in the USA](https://accsly.io/en/vps/usa).

Europe works the other way round: it is compact, and Frankfurt, Amsterdam and London are within 30–40 ms of most of the continent. For a European audience any of these hubs will do, and the choice comes down to the host and the price: [VPS in Europe](https://accsly.io/en/vps/europe).

## Personal data: where it sits and who is responsible

Personal data is not only passport numbers. A name and phone number in an order form, an email address at sign-up, a delivery address, even an IP address in your logs all count. Wherever the server is, three things apply to almost any site that collects such data:

- **Know where the data physically sits.** The database, the backups and the logs are all on servers in a specific country, and that country's law applies to them. Write it down: you will need it for the privacy policy and if a customer asks.
- **Publish a privacy policy.** It should say what data you collect, why, how long you keep it and who you share it with, including your hosting provider.
- **The host is your processor.** It stores the data on your behalf, so the contract with it matters. Reputable hosts publish a data processing agreement (DPA) that sets out how they protect data and when they can access it.

## GDPR if you have users in the EU

If the site serves people in the EU, the GDPR applies to you even if your company is outside the EU. The regulation does not require the server to be in Europe, but it does require that personal data sent outside the EU and EEA is protected to the same level.

The simplest option is to host in the EU or EEA, for example in Germany, the Netherlands or Finland, and sign the host's DPA. Then the data does not leave Europe and there is no transfer question. If you choose a host outside the EU, you need a DPA plus a legal basis for the transfer: the destination country is covered by an EU adequacy decision, or the host signs the standard contractual clauses. Most large international hosts offer both, but check before you put customer data on the server.

A blog without forms, comments or sign-ups has far less to worry about. This is not legal advice: if you are not sure what data you handle or which rules apply to you, ask a lawyer. It costs less than a fine.

## What the same server costs in different countries

I took VPS plans from the accsly catalog of 27 October 2026, picked servers with 2 and 4 GB of memory in each country and found the median monthly price, counting only countries with at least 40 such plans. The catalog stores prices in roubles, so the dollar figures are converted and rounded.

| Country | 2 GB | 4 GB |
| --- | --- | --- |
| Turkey | $8 | $14 |
| Russia | $9 | $15 |
| Finland | $10 | $16 |
| Germany | $10 | $18 |
| USA | $11 | $19 |
| Netherlands | $11 | $20 |
| Poland | $11 | $20 |
| France | $12 | $22 |
| United Kingdom | $15 | $23 |
| Singapore | $20 | $32 |
| Japan | $19 | $37 |
| Australia | $21 | $37 |

From the table the Netherlands looks 10–15% dearer than Germany. But that is a difference between markets, not between countries. The Netherlands has many hosts with expensive cloud platforms, while other markets have a larger share of low-cost plans. It is fairer to compare the same plan at the same host. I found 849 cases where a host sells an identical configuration in several countries as separate plans. Germany, the Netherlands, Russia, Finland and France cost the same at the median of this sample, and the US is only 7% dearer than Germany. Singapore is 38% dearer than Germany, Australia 47%, India 53% and Japan 57%.

The conclusion is simple. Within Europe and the US you do not choose a country by price, you choose a host. Take a server in Asia or Australia only if your users are there: you will pay about one and a half times as much for the same memory.

## Payment and support depend on the country too

International hosts take Visa and Mastercard almost everywhere, and many also accept PayPal. If you are an EU customer, expect VAT to be added at checkout unless you enter a valid VAT number for your business; compare prices including tax. Most hosts bill monthly, and many give a discount for a year paid in advance. Take the annual plan only after you have tested the host for a month or two.

Support in your language and your time zone also costs money, it is just not written in the plan. If the server goes down at 3 a.m. your time, an answer within an hour and an answer when the working day starts in California are two very different nights.

## Tasks where the country is already chosen

- **Telegram bot.** A server in Europe: Telegram's servers are in Amsterdam, and from Europe a bot responds quickly and reliably. Details in the article [VPS for a Telegram bot](https://accsly.io/en/vps/guide/vps-for-telegram-bot).
- **Remote desktops for an office.** The same city where the staff work, or the nearest large hub: [RDP VPS](https://accsly.io/en/vps/rdp).
- **Game server.** As close as possible to most of the players; latency matters more than anything else here: [VPS for game servers](https://accsly.io/en/vps/for-game-server).
- **A site for a specific region.** For Europe, the [Netherlands](https://accsly.io/en/vps/netherlands), [Germany](https://accsly.io/en/vps/germany) or [Finland](https://accsly.io/en/vps/finland); for North America, the [USA](https://accsly.io/en/vps/usa); for South-East Asia, [Singapore](https://accsly.io/en/vps/singapore).
- **Backups.** Not in the same data centre as the main server. A fire or an outage at one site should not take both the site and its copy. Selection: [VPS for backups](https://accsly.io/en/vps/for-backups).

## How to measure latency to candidate countries from your city

Pick two or three hosts in each country and find their test IP addresses or looking glass page, usually in the "Network" or "Data centres" section. Where to find them and how to read each tool is covered in detail in the article [how to check VPS ping and speed before paying](https://accsly.io/en/vps/guide/check-vps-speed-before-buying). Here is a short routine for comparing countries.

**Step 1. Measure from your computer.** On Linux and macOS, put in the candidates' addresses and run:

```
for h in 203.0.113.10 198.51.100.20 192.0.2.30; do
  echo "== $h"; ping -c 20 -q $h | tail -2
done
```

The last line for each address shows the minimum, average and maximum. On Windows, run `ping -n 20 address` for each address and look at the "Average" line. Use a cable rather than Wi-Fi: a wireless network adds milliseconds of its own.

**Step 2. The route to the two finalists.**

```
mtr -rwc 50 203.0.113.10
```

If the delay jumps at some hop and stays high to the end, the hop names show where the traffic takes a detour. It happens that packets to a server in Finland go via Frankfurt, and then Finland is no longer closer.

**Step 3. Measure from your users' cities.** Your computer is one point. If your visitors are spread across a country or a continent, use the free Globalping service: it runs ping from hundreds of probes at different providers. On the service's website you can do it in the browser, and from the console like this:

```
globalping ping 203.0.113.10 from London,Chicago,Singapore
```

**Step 4. Decide.** Write down the average for each city and country pair. If the candidates differ by less than 20 ms, choose by price, payment and host. If the difference is 50 ms or more, take the country that serves the largest group of your users best. And look at the worst city, not only your own.

## Country traps in a plan

**The IP address "lives" in another country.** IP geolocation services sometimes show the country where the host's network is registered rather than where the server stands. For visitors this means little, but services that choose a language or region by IP can get it wrong. Check the assigned address in two or three such services on the first day. If the country is wrong, write to the host: the databases are usually corrected at its request.

**"Europe" without a city.** If a plan just says "Europe" or "USA", ask for the exact city before paying. A server on the US West Coast is 70–80 ms further from a European audience than one on the East Coast.

**Expecting the server country to lift the site in search.** Search engines barely look at where the server is. Google works out a site's target region from its language, domain, hreflang tags and links. Choose the country for the speed it gives people, not for the crawlers.

You can filter plans by country and city in the [VPS search](https://accsly.io/en/vps). Regional selections: [VPS in Europe](https://accsly.io/en/vps/europe), [VPS in Asia](https://accsly.io/en/vps/asia).

## FAQ

### Which country is best for hosting a website on a VPS?

The one where most of your visitors live. For Europe, Germany, the Netherlands or Finland; for North America, the US East Coast or the centre of the country; for South-East Asia, Singapore.

### Do I have to host in the EU because of GDPR?

No, GDPR does not require the server to be in the EU. Hosting in the EU or EEA with the host's data processing agreement is the simplest route. With a host outside the EU you also need a basis for the transfer, such as an adequacy decision or standard contractual clauses. If you are unsure, ask a lawyer.

### Is a server in Asia or Australia more expensive than in Europe?

Yes. At the same host, a server in Germany, the Netherlands, Finland or France usually costs the same, and the US only about 7% more. Singapore is 38% dearer than Germany at the median, Japan 57%.

### How can I check the latency to a server in another country before buying?

Find the host's test IP address or looking glass page and run a 20-packet ping and mtr from your computer over a cable. To see the latency from other cities, use the Globalping service.

### Does the server country affect rankings in Google?

Hardly. Google works out a site's target region from its language, domain, hreflang tags and links. The server country affects loading speed, and only through that the behaviour of visitors.

### Where should I keep server backups?

In a different data centre from the main server, and better still in a different city or country. Then an outage at one site will not take both the site and its copy.

_Updated: 2026-10-28_

# Hourly billing: when it pays off

Hourly billing pays off if you need the server for less than three weeks a month: for a test, a build, a one-off heavy job. At most hosts an hour costs exactly the monthly price divided by 730 hours, so over a full month you hardly overpay. The overpayment hides elsewhere: hourly plans are dearer on average, and for a server that runs all year, monthly billing or a year paid in advance usually comes out cheaper.

> Source: https://accsly.io/en/vps/guide/hourly-billing-when-worth-it · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

With hourly billing you put money on your balance, and the host deducts the cost of the server from it every hour, some every 10 minutes or even every second. Delete the server and the charges stop. There is also daily billing: the same thing, only the step is a day.

The short answer to the question in the title. If you need a server for hours or days, hourly billing is almost always cheaper. If the server will run for months without a break, a monthly plan is cheaper, and a year paid in advance is cheaper still, if you trust the host. Between these cases a simple formula decides, and it is below.

## What an hour costs

I found 76 hosts whose plan pages show both an hourly and a monthly price, multiplied the hourly price by 730 (the number of hours in an average month) and compared the result with the monthly price.

At 47 hosts, almost two thirds, the difference is under 2%: an hour costs exactly the monthly price divided by 730. At 25 hosts a month paid by the hour comes out dearer than the monthly plan, usually by 9–17%. Some of them cap the bill at the monthly price: however many hours the server runs, you are never charged more than the monthly plan. At four more hosts an hour is even slightly cheaper.

Here is what it looks like in money at the hosts in this sample. The catalog stores prices in roubles, so the dollar figures in this article are converted and rounded. A server with 1 GB of memory costs from 0.7 to 1 cent an hour, with 2 GB from 1.2 to 2.1 cents, and with 4 GB from 1.6 to 4.2 cents. Running a server for an evening to try something out costs less than a cup of coffee.

## Who offers hourly billing

Hourly billing is offered mainly by cloud hosts, where a server is created and deleted automatically within a minute. According to the accsly catalog on 27 October 2026, it is confirmed at 170 hosts, which is 18% of all VPS plans. Many hosts do not publish their billing terms, so there are more options in reality. Selection: [VPS with hourly billing](https://accsly.io/en/vps/hourly-billing).

Flexibility usually comes at a price. Let us compare hosts that offer hourly billing with those that definitely do not. With 2 GB of memory, the median monthly price is about $12.30 for the first and $11.30 for the second, a difference of about 10%. With 4 GB the gap is already 24%: about $22 against $18. Clouds are dearer because they keep spare hardware for servers that customers create and delete at any moment.

## The formula: how many hours a month make hourly billing worth it

Divide the monthly price of the server you would otherwise take by the hourly price of the hourly one. The result is the number of hours after which the hourly option becomes more expensive.

```
break-even hours = monthly price of the other plan / price per hour
```

An example. A budget 2 GB server on a monthly plan costs about $8.70 a month. An hourly plan with the same memory costs 1.4 cents an hour. $8.70 / $0.014 is about 613 hours, or 25 days. If you need the server for less than 25 days a month, hourly is cheaper. If more, monthly is.

Hence a rule of thumb. Less than three weeks a month, pay by the hour. The whole month and beyond, switch to a month or a year.

## Four worked examples

### A test server for three days

You need to check a new version of a site or a CMS update before release. A 2 GB server at 1.4 cents an hour for 72 hours costs about $1. Add about $0.20 if the host charges separately for the public IP address, at around 0.3 cents an hour. That is about $1.20 instead of at least $8.70 for a month, a saving of about $7.50. Plans for this kind of work: [VPS for a test environment](https://accsly.io/en/vps/for-testing).

### A build server on working days

Building a project or running tests is fast on 4 cores and 8 GB of memory, but you only need such a server during working hours. Take a real plan: 5.1 cents an hour or $32 a month. Ten hours a day for 22 working days is 220 hours, or about $11.30. Monthly it is $32. That saves about $20 a month, but only if the server is deleted for the night and the weekend, not switched off. I explain below why that matters. Selection: [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci).

Note that a full month by the hour on this plan would cost 730 hours at 5.1 cents, about $37. That is 17% more than the monthly price. If you suddenly need the server all the time, switch to monthly billing.

### A one-off heavy job

You need to migrate a large database once, compress a photo archive or process an export of several gigabytes. A server with 32 GB of memory costs about $120 a month at the market median. If the host prices an hour as the monthly price divided by 730, that is about 16 cents an hour. Six hours of work cost about $1. A job that would keep a home laptop busy all night costs less than lunch.

### A site that runs all year

Here hourly billing loses. An hourly 2 GB server at about $10.30 a month comes to around $124 a year. A monthly plan at $8.70 comes to about $104. And if you pay a year in advance, hosts at the median give a 10% discount, so the same plan comes to about $93. The difference from the hourly option is $20–30 a year.

Whether to pay for a year at once depends on the host. A 10% discount is not worth being stuck for a year with a slow server. Almost a quarter of hosts give no annual discount at all, and then monthly billing loses nothing.

## What you are charged while the server is off

This is the main trap of hourly billing. At many hosts a switched-off server keeps costing money: the disk and the IP address are still reserved for you, and the host charges the full price or slightly less. The `shutdown` command inside the server and the "Power off" button in the panel stop the system, but not the bill. Charges stop only when the server is deleted.

If you need the server again tomorrow, take a disk snapshot and delete the server, then create a new one from the snapshot in the morning. Storing a snapshot costs many times less than a running server. How the host bills stopped servers and snapshots is stated in its terms. Read them before the first launch.

What else may be charged separately:

- **A public IPv4 address.** Some hosts charge about 0.2–0.3 cents an hour for it, which is $1.70–2.10 a month. On a 1 GB server at $6.20 that adds a third to the price, so compare the totals with the address included.
- **A minimum payment.** Some hosts require a minimum top-up of a few dollars or charge no less than a set amount. For a one-hour test it is still pocket change, but include it in the calculation.
- **Licences.** At some hosts Windows and paid control panels are billed separately and under their own rules. Check whether they are charged by the hour or for the whole month.

And the flip side: when the balance runs out, the host stops the server, and a few days later it may delete it along with the data. Turn on a low-balance alert or auto top-up in the panel if something important runs on an hourly server.

## How not to forget an hourly server

The most common overpayment is a test server forgotten for a month. Three simple habits:

- Right after creating it, put the date it should be deleted into the server name, for example `test-del-0511`.
- Set up an alert in the host's panel for daily spending or for a monthly total, if there is such a setting.
- If you create servers regularly, automate it. Hosts with an API let you create and delete a server with one command from a script or a build job. Selection: [VPS with an API](https://accsly.io/en/vps/api).

## When you do not need hourly billing

For a site, a bot or a database that runs all the time and does not change size, hourly billing means paying for flexibility you do not use. Take a monthly plan at a host you have tested.

A combination works well. For the first week you try candidates on hourly billing: launch the site, check the speed, compare two or three hosts for a few dollars. Then move the site to a monthly plan at the winner. How to check a server in its first hour is covered in the article [how to check VPS ping and speed](https://accsly.io/en/vps/guide/check-vps-speed-before-buying). If the host you want has no hourly billing, look for a [free trial](https://accsly.io/en/vps/free-trial) or a [money-back guarantee](https://accsly.io/en/vps/moneyback) in the first days.

## FAQ

### What is hourly VPS billing?

Money sits on your balance, and the host deducts the cost of the server every hour, some every 10 minutes or every second. Once the server is deleted, the charges stop.

### Is hourly billing more expensive than monthly?

Over a full month, usually not: at almost two thirds of the hosts that show both prices, an hour equals the monthly price divided by 730. But plans with hourly billing are on average 10–24% dearer than the plans of hosts that do not offer it.

### When is hourly billing cheaper?

When you need the server for less than three weeks a month. More precisely: divide the monthly price of a regular plan by the hourly price. If the server runs for fewer hours than that, hourly billing is cheaper.

### Am I charged for a switched-off server?

At many hosts, yes: the disk and the IP address stay reserved for you, and the charges continue. To stop them, the server has to be deleted. If you will need it again, take a disk snapshot before deleting it.

### How much does a VPS cost for one day?

A server with 2 GB of memory costs 1.2 to 2.1 cents an hour at the hosts in our sample, which is about 30 to 50 cents a day. If the public IP address is billed separately, add about 7 cents.

### What is cheaper for a permanent site: hourly billing or paying for a year?

Paying for a year, if you trust the host. An hourly 2 GB server at about $10.30 a month costs around $124 a year, while a monthly plan at $8.70 with a 10% annual discount comes to about $93.

_Updated: 2026-10-28_

# How much RAM and how many cores a website needs

Most websites are fine with 2 GB of memory and one or two cores; a shop with thousands of products needs 4 GB and two cores. Memory matters more than cores: when it runs out, the site slows down or crashes, while an extra core without memory adds almost nothing. Below I show how to work out the memory for your site and how to see what it actually uses.

> Source: https://accsly.io/en/vps/guide/ram-and-cpu-for-website · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

If the site is not live yet and you do not know what to take, start with 2 GB of memory and one or two cores. That is enough for a blog, a company website and a small WordPress shop, and most hosts let you upgrade the plan later without reinstalling. If the site is already running, there is no need to guess: in five minutes you can see how much memory it uses and pick a plan with about 30% headroom.

The most common mistake goes one way: people take four cores and 1 GB of memory because cores sound more impressive. For a website that is a bad pair. PHP and the database eat a gigabyte within minutes, the server starts swapping memory to disk, and pages take several seconds to open while the processor sits almost idle.

## What the money buys

I took about 27,700 VPS plans from 2,200 hosts in the accsly catalog of 27 October 2026, grouped them by monthly price and found the median memory, cores and disk for each tier. The catalog stores prices in roubles, so the dollar tiers are converted and rounded.

| Price per month | Memory | Cores | Disk |
| --- | --- | --- | --- |
| under $3 | 1 GB | 1 | 20 GB |
| $3–7 | 2 GB, a quarter have 1 GB | 1 | 25 GB |
| $7–11 | 2 GB | 2 | 40 GB |
| $11–22 | 4 GB | 2 | 60 GB |
| $22–45 | 8 GB | 4 | 100 GB |
| $45–90 | 12 GB | 6 | 160 GB |

The usual ratio on the market is one core per 2 GB of memory. Plans with 2 GB split almost evenly: half have one core, half have two. With 4 GB, 61% of plans have two cores; with 8 GB, 57% have four.

The location of the data centre moves the price as well. A 4 GB server costs about $20 a month at the median across all countries, while in the cheaper markets, such as Turkey or Russia, the same memory is closer to $14–15. Selections by size: [2 GB VPS](https://accsly.io/en/vps/2-gb-ram), [4 GB VPS](https://accsly.io/en/vps/4-gb-ram), [8 GB VPS](https://accsly.io/en/vps/8-gb-ram).

## Where the memory goes on a web server

A PHP site with a database shares memory between four consumers. Once you know their appetite, the size you need can be worked out on the back of an envelope.

- **The system itself.** A fresh Ubuntu or Debian takes 150–300 MB after boot.
- **The nginx web server** takes tens of megabytes; you can leave it out.
- **PHP-FPM.** Each PHP worker process takes 40–100 MB, and WordPress with a dozen plugins or Magento can take more. There are as many processes as requests the site handles at the same time.
- **MySQL or MariaDB.** The biggest consumer. The database keeps its buffer of data and indexes in memory, plus a few megabytes for each connection.

A control panel such as cPanel, Plesk or FastPanel adds another 200–500 MB, and Redis for caching anything from 50 MB up to the size of what you store in it.

Say you have a WooCommerce shop with 5,000 products and an 800 MB database. The system takes 300 MB, the database buffer for all the data with some room 1 GB, the database itself another 300 MB on top, 15 PHP processes at 80 MB each 1.2 GB, and Redis 100 MB. That comes to about 3 GB. On a 4 GB server a gigabyte is left over, which Linux uses as a file cache, and that is a good thing. The shop will also start on 2 GB, but you will have to halve the database buffer and the number of PHP processes, and during a sale the catalog pages will get slower.

## And how many cores?

Fewer than you might think. One core runs one PHP request at a time. If a page is built in 200 ms, a core can serve five such pages per second, and two cores ten.

Let us turn that into visitors. A site with 10,000 visitors a day shows about 30,000 pages. The busiest hour takes roughly a tenth of that, 3,000 pages, which is less than one per second. One core copes with that. A second one helps so that the admin area, product imports, backups and search engine crawlers do not slow the site down for visitors. And with a page cache turned on, most requests never reach PHP at all.

Cores are needed where many pages cannot be cached: catalog filters, search, the cart, customer accounts. Heavy background jobs also eat them, for example image processing, product feeds to marketplaces and price list imports. So do several sites on one server.

Paying for cores in advance hurts. With 4 GB of memory, a four-core plan costs about $27 at the market median and a two-core plan about $19, a difference of $8 a month. With 8 GB the difference between two and four cores is only about $3, so at that size four cores are almost free. For PHP the clock speed matters too: a single page is built on a single core, and at 4.5 GHz it will be ready noticeably faster than at 2.2 GHz. Such plans are in the [high-frequency CPU VPS](https://accsly.io/en/vps/high-frequency) selection.

## What to take for typical sites

- **A landing page, static site or business-card site without a database**: 1 GB and one core. These are the cheapest plans, and there is nothing to overpay for: [1 GB VPS](https://accsly.io/en/vps/1-gb-ram).
- **A WordPress blog or company website with caching**: 2 GB and one or two cores: [VPS for WordPress](https://accsly.io/en/vps/for-wordpress).
- **A shop with thousands of products** on WooCommerce, OpenCart or PrestaShop: 4 GB and two cores: [VPS for an online store](https://accsly.io/en/vps/for-online-store).
- **Magento or a shop with a large catalog**: from 4 GB, and 8 GB with four cores once the catalog runs into tens of thousands of products.
- **A Laravel application** with queues and Redis: 2–4 GB, because each queue worker keeps its own PHP process in memory. Selection: [VPS for Laravel](https://accsly.io/en/vps/for-laravel).
- **Several sites and a control panel**: add up what the sites need and add 0.5–1 GB for the panel.

## How much memory the site really uses

Log in to the server over SSH and run:

```
free -m
```

The output will look something like this:

```
               total        used        free      shared  buff/cache   available
Mem:            3915        1720         240          60        1955        1890
Swap:           1023          12        1011
```

Do not be alarmed by the small number in the `free` column. Linux uses spare memory for the file cache, which is the `buff/cache` column, and gives it back to programs as soon as they ask. The column to watch is `available`: here the server has 1.9 GB that programs can take right now. If `available` drops below 10% of `total` at peak hours, memory is short.

The second check is whether the server is swapping:

```
vmstat 1 10
```

The command prints a line of figures ten times, once a second. Look at the `si` and `so` columns: how much data the server reads from swap and writes to it per second. Zeros mean all is well, even if something is taken in the Swap line of `free`. If they constantly show hundreds or thousands, the server is moving memory to disk, and that slows a site down more than any other problem.

The third is whether the system has killed processes for lack of memory. When memory runs out completely, the Linux kernel picks the largest process, often MySQL, and terminates it. Visitors see this as an "Error establishing a database connection" or a 502 error.

```
journalctl -k | grep -i -E 'out of memory|killed process'
```

If the command finds anything, memory has run out at least once. Take a bigger plan or reduce the appetite of PHP and the database, as shown below.

## Who ate the memory: htop and ps

Start `htop` (on Ubuntu and Debian it installs with `apt install htop`) and press `M` to sort processes by memory. The `RES` column shows how much a process occupies in RAM. At the top you will usually see `mysqld` or `mariadbd` and a long tail of `php-fpm` processes.

You can count how much memory goes to PHP in total and per process with one line:

```
ps -eo rss,comm | awk '/php-fpm/ {s+=$1; n++} END {printf "%d processes, %.0f MB total, %.0f MB per process\n", n, s/1024, s/n/1024}'
```

The total comes out slightly high, because PHP processes share part of their memory. For an estimate that is good enough. Run the command during the day, when the site has visitors: at night the processes are idle and look smaller.

The average process size tells you how many PHP processes you can allow. Decide how much memory you give to PHP and divide it by the process size. For example, 1,200 MB at 80 MB per process gives 15 processes. This number goes into the `pm.max_children` setting in the pool file; on Ubuntu and Debian that is `/etc/php/8.3/fpm/pool.d/www.conf`, where 8.3 is your PHP version. Set it higher, and during a rush of visitors PHP will take all the memory and the system will start killing processes. Set it lower, and extra requests will wait in a queue, but the server will stay up.

## The MySQL buffer: the biggest consumer and the biggest lever

The database is fast as long as its data and indexes fit into the buffer in memory. You can find out how much the tables weigh with a query in the `mysql` console:

```
SELECT ROUND(SUM(data_length + index_length) / 1024 / 1024) AS mb
FROM information_schema.tables WHERE engine = 'InnoDB';
```

The current buffer size:

```
SHOW VARIABLES LIKE 'innodb_buffer_pool_size';
```

After installation it is often 128 MB. For a shop with an 800 MB database that is far too little: every catalog filter will read from disk. Two counters show whether the buffer is big enough:

```
SHOW GLOBAL STATUS LIKE 'Innodb_buffer_pool_read%';
```

Divide `Innodb_buffer_pool_reads` by `Innodb_buffer_pool_read_requests`. The first number is how many times the database had to go to disk, the second how many reads there were in total. If the result is below 0.01, meaning less than 1% of reads go to disk, the buffer is big enough. Look at these figures after the server has been running for at least a day.

Make the buffer equal to the data size plus 10–20% for growth, but on a server where PHP runs alongside, no more than half of all memory. The value is set with the line `innodb_buffer_pool_size = 1G` in the `[mysqld]` section of the configuration (on Ubuntu that is `/etc/mysql/mysql.conf.d/mysqld.cnf`, for MariaDB a file in `/etc/mysql/mariadb.conf.d/`), after which the database has to be restarted. If the database does not fit even into half the memory, that is an honest reason to take a bigger plan. A fast disk helps in that situation too; see the article [NVMe or SSD for a website](https://accsly.io/en/vps/guide/nvme-or-ssd).

## When to add memory and when to add cores

Memory is short if `available` drops below 10% at peak, `vmstat` shows non-zero `si` and `so`, or the log has killed processes. Adding cores is useless here.

Cores are short if memory is free but the site is slow under load. Check with `uptime`: the three numbers at the end of the line show the average load over 1, 5 and 15 minutes. Compare them with the number of cores from the `nproc` command. If the load stays above the number of cores for long periods at peak hours, and in `htop` the processor is busy with `php-fpm` processes, you need more cores or a page cache, which is often cheaper.

There are two cases where a bigger plan at the same host will not help. If `top` shows a high `st` value in the `%Cpu(s)` line, 10% or more, your neighbours on the physical server are taking processor time from you. Only another host or a plan with dedicated cores helps. If `wa` is high, the processor is waiting for the disk, and it is the disk that needs fixing, not the cores.

If you are torn between two sizes, take the smaller one at a host where the plan can be upgraded from the panel in a couple of minutes. Before buying, check in the description whether the plan can be changed without reinstalling. And if you want to try the site on several configurations, [hourly billing](https://accsly.io/en/vps/hourly-billing) is handy: a server for an evening costs well under a dollar. The other plan parameters are covered in the article [how to choose a VPS](https://accsly.io/en/vps/guide/how-to-choose-vps).

## FAQ

### How much RAM does a WordPress site need?

A blog or company website with page caching is fine with 2 GB. For a WooCommerce shop with thousands of products, 4 GB is better, so that the whole database fits in memory and there are enough PHP processes for a rush of customers.

### Is 1 GB of memory enough for a website?

For a static site or a landing page without a database, yes. A CMS site with MySQL will be cramped: the system, the database and a few PHP processes together take about a gigabyte, and at the first spike of visitors the server will start swapping.

### What matters more for a website, memory or cores?

Memory. When it runs out, the server moves data to disk and pages take several seconds to open. One core can build about five pages per second, while a site with 10,000 visitors a day needs less than one per second at its busiest hour.

### How do I find out how much memory my site uses?

Run free -m on the server and look at the available column: that is the memory programs can take right now. How much PHP and the database take separately is shown by htop sorted by memory (the M key).

### Why does free show almost no free memory?

Linux uses unused memory for the file cache, the buff/cache column, and gives it back to programs as soon as they ask. Worry only if the available value is low or the server is actively writing to swap.

### How much does a VPS with 4 GB of memory cost?

About $20 a month at the market median according to the accsly catalog on 27 October 2026, and closer to $14–15 in the cheaper markets. Most often a 4 GB plan comes with two cores.

_Updated: 2026-10-28_

# KVM or OpenVZ: which to choose

In 2026 KVM is almost always the right pick: it costs a dollar or two more per month than OpenVZ, but everything runs on it, from Docker to Windows. OpenVZ makes sense in one narrow case, explained below, and at the end you will find the commands to check your own server in a minute.

> Source: https://accsly.io/en/vps/guide/kvm-or-openvz · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

The short answer: take KVM. On KVM you have your own system kernel, and the server behaves like an ordinary computer: Docker, Windows and any Linux version install fine, and your own firewall and swap work. OpenVZ is a container that shares a kernel with the neighbours on the same physical machine. It is cheaper and lighter, but some familiar programs will not start in it, and you usually find that out after you have paid.

OpenVZ only makes sense if the task is simple, runs on Linux without Docker, and the price difference actually matters to you. Below I look at how big that difference is in practice and what exactly breaks in a container.

## How much cheaper OpenVZ really is

Less than you might think. I compared plans with the same amount of memory at the same host: I took the cheapest KVM plan and the cheapest OpenVZ plan and looked at the difference. That gave between 15 and 29 hosts depending on the memory size, using the accsly catalog data of 27 October 2026. The catalog stores prices in roubles, so the dollar amounts are rounded.

With 2 GB of memory, KVM at the median costs well under a dollar more per month, about 16%. With 4 GB the gap is larger, about $2 or 30%. Over a year that comes to somewhere between $8 and $25. And at a third of the hosts that sell both types, KVM of the same size costs the same or even less, so the first step is simply to compare plans within one host.

Choosing OpenVZ also narrows the field a lot. Of the 26,640 plans in the catalog, 501 run on OpenVZ, which is 1.9%, and they are sold by 84 hosts out of 2,175. KVM accounts for 93.5% of all plans (I counted in those where the host did not state the virtualization, because these days the default is almost always KVM). The rest are VMware, Hyper-V, Xen and LXC containers, and for you as a user the first three behave just like KVM.

So the saving on OpenVZ is roughly the price of a coffee a month, and you pay for it with restrictions. For work you would hate to lose, I would not make that trade.

## What will not work in an OpenVZ container

Anything that needs its own system kernel. In a container there is one kernel for the whole physical machine, and only the host can change its settings. In practice it looks like this.

**Docker often does not install or runs with errors.** Many hosts state in their terms that they do not support Docker on OpenVZ. On OpenVZ 7 it sometimes starts if the host has enabled the required features for the container, but you need to confirm that before paying. If your project is built on Docker or you plan to run n8n, GitLab Runner or Kubernetes, look only at [KVM](https://accsly.io/en/vps/kvm) or the [VPS for Docker](https://accsly.io/en/vps/for-docker) selection.

**Windows will not run at all.** The container uses the host's Linux kernel, so a different operating system is impossible inside it. The catalog has not a single OpenVZ plan with Windows, while among KVM plans Windows is available on about half. Selection: [Windows VPS](https://accsly.io/en/vps/windows).

**The kernel is old and cannot be upgraded.** OpenVZ 7 runs kernel 3.10, and the outdated OpenVZ 6 runs 2.6.32. Current distributions are designed for newer kernels, so the host may not have a template for the Ubuntu version you need. Anything added to the kernel later will not work either: for example, the BBR algorithm, which speeds up file delivery over long distances, needs kernel 4.9 or newer.

**You cannot load your own kernel modules.** This includes, for example, in-kernel WireGuard for a private network between an office and a server. It can be replaced with a version that works without the module, but only if the host has enabled the TUN network device for the container. How to build such a network on a regular KVM server is covered in the article [a corporate network on a VPS](https://accsly.io/en/vps/guide/corporate-vpn-on-vps).

**You cannot add swap.** The `swapon` command does not work in a container, so when memory runs out, the process is simply killed. On KVM you can create a 1–2 GB swap file in a minute and get through a load spike.

**Memory is counted differently.** OpenVZ plans often say something like "1 GB guaranteed, up to 2 GB", and the upper figure is only available while it is free on the host. Plan around the lower one.

## When OpenVZ is still a reasonable choice

When the task is small, runs on Linux and does not need Docker. Say you need a server for a simple Python bot, a static site, uptime monitoring of other sites or tests you would not mind losing. A container will cope with that, and over a year you will save roughly $10–12.

Another advantage of a container is that it has almost no overhead. The system boots in seconds, and none of the plan's memory goes to the virtualization itself. On 512 MB plans this is noticeable: on KVM the kernel and system services take about 100–150 MB of it, in a container less.

If this option suits you, the plans are collected in the [OpenVZ VPS](https://accsly.io/en/vps/openvz) selection. LXC, a container built along similar lines, is rarer, at about 0.6% of plans, and its limitations are almost the same: [LXC VPS](https://accsly.io/en/vps/lxc).

## Is KVM always more honest?

Not always. KVM by itself does not guarantee that the processor is not shared with a dozen neighbours: on inexpensive plans the cores are still shared. The difference is that overselling is easier to spot on KVM, because the system shows how much time the neighbours took away from your machine. I show how to check this below. If the processor will be busy all the time, look for plans with dedicated cores, and for fast single-threaded work, [high-frequency CPU VPS](https://accsly.io/en/vps/high-frequency).

## What to take for your task

A site on WordPress, Drupal or Laravel with a database: KVM. The site benefits from swap for traffic spikes and from a current PHP version, and it makes no sense to put up with an old kernel to save a dollar a month. Selection: [VPS for a website](https://accsly.io/en/vps/for-website).

Anything on Docker, including n8n, GitLab and Kubernetes: KVM only, there is no alternative. Windows and software built for it: also only KVM or Hyper-V.

A Telegram bot in Python or Node.js without Docker, monitoring, a test environment: OpenVZ will do, if it is noticeably cheaper at the same host. If the difference is only a dollar or so a month, I would still take KVM: when you move to Docker or a new system version, you will not have to change servers.

How both types work and a table of differences are in the article [VPS vs VDS](https://accsly.io/en/vps/guide/vps-vs-vds); here we move on to practice.

## How to find out what your server runs on

Hosts do not always state the virtualization in the plan, and sometimes they state it wrongly. You can check it in a minute by connecting to the server over SSH. The simplest command is available on any modern Linux:

```
systemd-detect-virt
```

It prints a single word. `kvm` means KVM, `openvz` an OpenVZ or Virtuozzo container, `lxc` an LXC container, `vmware` and `microsoft` VMware and Hyper-V, `xen` Xen. If the output is `none`, you got a physical machine without virtualization. `hostnamectl` shows the same thing in its Virtualization line.

If there is no systemd or you want to confirm the answer, there are three indirect signs:

```
ls /proc/user_beancounters /proc/vz 2>/dev/null   # these files exist only in OpenVZ
uname -r                                          # kernel version
lscpu | grep -i hypervisor                        # on KVM: Hypervisor vendor: KVM
```

If the first command printed anything, you are in an OpenVZ container. A kernel version like `2.6.32-042stab…` means OpenVZ 6, and one with `vz7` in the name means OpenVZ 7. There is also the `virt-what` utility, installed with `apt install virt-what` and run as root; it recognises more of the rare cases.

## How to tell that neighbours are crowding your server

On KVM, look at steal, the time the hypervisor gave to other machines while yours was asking for the processor:

```
vmstat 1 10
```

You need the `st` column on the right. If it shows 0–2, everything is fine. If under load it stays above 5–10, the neighbours are taking a noticeable share of the processor, and the server will run slower than the plan promises. The same figure appears in `top` as `st` in the %Cpu line.

In OpenVZ steal is usually not visible, but there is a counter of hit limits instead:

```
cat /proc/user_beancounters
```

Look at the last column, `failcnt`. A non-zero value in the `privvmpages` or `physpages` row means the container ran short of memory and some requests were refused. If the numbers keep growing, the plan is too small for your task, even if `free` shows free memory.

Run these checks in the first days after payment, while the refund period is still valid. Plans that offer one are in the [money-back VPS](https://accsly.io/en/vps/moneyback) and [free trial](https://accsly.io/en/vps/free-trial) selections.

## FAQ

### Which is better for a website, KVM or OpenVZ?

For a site with a database, KVM is better: you can add swap, install a current system version and any software. A simple PHP site will run on OpenVZ too, but the saving at one host is usually somewhere between half a dollar and two dollars a month.

### Does Docker work on OpenVZ?

Often not. Docker does not work on OpenVZ 6, and on OpenVZ 7 it only starts if the host has enabled it for the container. If your project uses Docker, take KVM.

### How much cheaper is OpenVZ than KVM?

At the same host with the same memory, KVM at the median costs well under a dollar more per month with 2 GB and about $2 more with 4 GB, according to the accsly catalog on 27 October 2026. At a third of these hosts, KVM costs the same or less.

### How can I find out which virtualization my VPS uses?

Run systemd-detect-virt on the server. It prints kvm, openvz, lxc, vmware, microsoft or xen. Another sign of OpenVZ is the presence of the /proc/user_beancounters file.

### Can I switch from OpenVZ to KVM without reinstalling?

No, they are different technologies, and a container cannot be turned into a virtual machine. You will have to order a new KVM server and move your files, databases and settings to it.

### How is LXC different from OpenVZ?

For the user, hardly at all: both are containers that share the host kernel, with no Windows and no custom kernel modules. LXC is common at hosts running Proxmox, and the kernel there is usually newer than on OpenVZ 7.

_Updated: 2026-10-28_

# NVMe or SSD: does it matter for a website

For a small site the difference between NVMe and SSD is barely noticeable, because pages are served from memory rather than from disk. It shows up in shops and sites with a large database. At the same host NVMe costs only about $0.50–1 a month more, and sometimes less, so what usually decides it is not the disk type but its size and how the host has limited it.

> Source: https://accsly.io/en/vps/guide/nvme-or-ssd · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

If you run a blog, a business-card site or a landing page, visitors will not notice whether the server has NVMe or a regular SSD. A cached page is served from memory in milliseconds, and the disk barely takes part. The difference becomes visible when the site constantly reads from and writes to its database: in an online shop with thousands of products, in catalog search, during price list imports, in the WordPress admin with WooCommerce or in Magento.

So the rule is simple. If NVMe costs the same or slightly more, take NVMe. If you would have to cut memory to get it, take more memory on SSD instead: 2 GB on SSD is more useful for a site than 1 GB on NVMe, because a database that fits in memory hardly touches the disk.

## How NVMe differs from SSD

Both are flash storage with no moving parts; the difference is how they connect to the computer. A regular SSD uses the SATA interface, which was originally designed for hard drives. Its ceiling is about 550 MB/s, and it handles a single queue of 32 commands. NVMe is connected directly to the PCIe bus: up to 3.5 GB/s on PCIe 3.0, up to 7 GB/s on PCIe 4.0, and there can be thousands of queues.

What matters for a site is not megabytes per second but the latency of small operations. A database reads and writes chunks of 4–16 KB in random places on the disk, and each visitor request may wait for dozens of such operations. On NVMe each operation takes less time, and under concurrent load the gap widens, because requests do not stand in a single queue.

There is an important caveat on a VPS. You do not get a physical disk but a virtual slice of shared storage, and the host almost always limits its speed so that one customer does not disturb the others. An "NVMe" disk with a tight limit can be slower than a good SSD without one. So the word in the plan is a reason to choose, not a guarantee, and the disk is worth testing on day one. I show how below.

## How much more NVMe costs

Hardly any more. I compared plans with the same memory at the same host: I took the cheapest NVMe plan and the cheapest SSD plan and looked at the difference, using the accsly catalog data of 27 October 2026. There were between 88 and 236 such host pairs depending on the memory size. The catalog stores prices in roubles, so the dollar amounts are rounded.

With 2 GB of memory, NVMe at the median costs about half a dollar more per month, around 8%. With 4 and 8 GB, about a dollar more, or 7–10%. Over a year the extra cost is roughly $6–12. Meanwhile, at 40–50% of hosts with 2–8 GB plans, NVMe costs the same as SSD or less. It looks as if many hosts have already moved their main hardware to NVMe, and SSD remains in older product lines that are not always cheaper.

The catch is elsewhere: NVMe plans usually come with less space. With 2 GB of memory the median disk size is 30 GB on NVMe versus 40 GB on SSD, and with 4 GB it is 60 versus 75 GB. For a site with a large media library, or for keeping backups on the server itself, this can tip the choice towards SSD.

NVMe is now found in 40% of the plans in the catalog. Selection: [NVMe VPS](https://accsly.io/en/vps/nvme). If you need cheap space for archives and backups and speed does not matter, there are also hard-drive plans: [HDD VPS](https://accsly.io/en/vps/hdd).

## When a site will feel NVMe

Take a WooCommerce shop with 20,000 products and a 3 GB database on a server with 4 GB of memory. The database does not fit entirely in memory, so catalog filters, search and checkout will read from the disk. Here NVMe speeds up the slowest pages, and that is worth the extra dollar. Plans for this kind of work: [VPS for an online store](https://accsly.io/en/vps/for-online-store).

The second case is heavy writing. By default, every committed change in MySQL or PostgreSQL is flushed to disk with a sync command, and the server waits until the disk confirms the write. A site with active comments, action logging, job queues or sessions stored in the database runs into exactly this. For such projects the [VPS for databases](https://accsly.io/en/vps/for-database) selection is worth a look.

For a business-card site or a WordPress blog with page caching, the difference disappears into measurement noise. It is better to spend the money on memory or on a server closer to your visitors: a data centre in Frankfurt or London for a European audience, in New York or Virginia for the US East Coast. Selection: [VPS for WordPress](https://accsly.io/en/vps/for-wordpress).

## Which disk you actually got

Inside a virtual machine the type of the physical disk is usually hidden. The command

```
lsblk -d -o NAME,ROTA,SIZE,MODEL
```

shows a disk with a name like `vda` or `sda` and an empty model. A value of 0 in the `ROTA` column means the system considers the disk non-rotational, but the host can set this to anything. The name `nvme0n1` appears when the host gives the machine a virtual NVMe device, yet even that says nothing about the real speed. Only a test tells the truth.

## Testing the disk: fio and how to read the results

The most accurate tool is fio. On Ubuntu and Debian it installs with `apt install fio`. Run the tests on a fresh server before a live site is on it, because they load the disk. Each test creates a 1 GB file, so make sure there is space.

**Test 1. Latency of a single operation.** This is closest to what a site experiences:

```
fio --name=lat --filename=/root/fio.test --size=1G --rw=randread --bs=4k \
    --iodepth=1 --direct=1 --ioengine=libaio --runtime=30 --time_based
```

In the output, find the `clat` line in the read block and the average value `avg` in it, then the percentile table below and the `99.00th` line. Units are shown in brackets: usec is microseconds, msec is milliseconds. On a good disk the average stays within 100–300 microseconds. If it is around a millisecond or higher and the 99th percentile goes into tens of milliseconds, the disk is overloaded or network-attached, and the database will be slow whatever the plan is called.

**Test 2. How many operations the disk sustains under load.**

```
fio --name=iops --filename=/root/fio.test --size=1G --rw=randrw --rwmixread=70 \
    --bs=4k --iodepth=32 --direct=1 --ioengine=libaio --runtime=60 --time_based
```

Look at `IOPS=` in the read and write lines. A few thousand operations per second is enough for a site or a small shop. If the plan is sold as NVMe but read plus write comes to less than 5,000–10,000, the host has capped the disk. A flat round number, for example exactly 10.0k on every run, also points to a limit.

**Test 3. Synchronous write speed.** This is how a database writes every committed change:

```
fio --name=sync --filename=/root/fio.test --size=256M --rw=write --bs=4k \
    --ioengine=sync --fsync=1 --runtime=30 --time_based
```

You need `IOPS=` in the write line: the number of confirmed writes per second. A thousand or more is good, and the database will write changes without waiting. If you get less than 200, every saved order or comment will wait for the disk.

The `--direct=1` flag in the first two tests is essential. Without it fio measures the memory cache, and the result comes out several times too high. After the tests, delete the file: `rm /root/fio.test`.

## A quick check with dd if fio is not available

The dd utility is present on every system. It is cruder but needs no installation. Sequential write:

```
dd if=/dev/zero of=/root/dd.test bs=1M count=1024 oflag=direct
```

The last line of the output shows the speed. A regular SATA SSD cannot deliver more than 550 MB/s, so figures above that indicate NVMe or fast storage. Less than 200 MB/s for an "NVMe" plan is a reason to ask the host about limits. But keep in mind that sequential writing hardly matters for a site: it is how large files are copied, not how requests are handled.

Synchronous writes in small blocks, closer to how a database works:

```
dd if=/dev/zero of=/root/dd.test bs=4k count=2000 oflag=dsync
```

Divide 2,000 by the number of seconds in the output, and you get how many writes per second the disk sustains. If dd finished in one or two seconds, that is a thousand writes per second or more, and all is well. If it took 10–20 seconds, each write takes 5–10 ms, and the database will feel it. After the check: `rm /root/dd.test`.

## How not to misread the results

Run the tests two or three times at different times of day, for example in the afternoon and late in the evening. If the results jump by a factor of several, the disk is shared with busy neighbours, and the site will be slower at peak hours. Compare servers with the same commands: figures from different tools and different settings cannot be compared with each other.

Do this in the first days, while the refund period is still valid. Plans that offer one are in the [money-back VPS](https://accsly.io/en/vps/moneyback) selection. Testing the network and the processor is covered in the article [how to check VPS speed](https://accsly.io/en/vps/guide/check-vps-speed-before-buying), and the other plan parameters in [how to choose a VPS](https://accsly.io/en/vps/guide/how-to-choose-vps).

## FAQ

### Do I need NVMe for a WordPress site?

For a blog or business-card site with page caching, the difference is barely noticeable. For a WooCommerce shop with thousands of products, NVMe speeds up filters, search and checkout, especially if the database does not fit in memory.

### How much more does NVMe cost than SSD on a VPS?

At the same host with the same memory, the cheapest NVMe plan at the median costs about $0.50–1 more per month, according to the accsly catalog on 27 October 2026. At 40–50% of hosts with 2–8 GB plans, NVMe costs the same or less.

### What matters more, NVMe or more memory?

For a site, memory matters more. A database that fits in RAM hardly touches the disk, so 2 GB on SSD is usually more useful than 1 GB on NVMe.

### How do I test disk speed on a VPS?

Install fio and run a random read test with 4 KB blocks and the --direct=1 flag. An average latency of up to 300 microseconds is a good result. If fio is not available, dd with oflag=direct or oflag=dsync gives a rough estimate.

### Why does the test show low speed on an NVMe plan?

The host almost always limits the speed of the virtual disk so that customers do not disturb each other, and neighbours may be loading the same storage. Repeat the test at different times, and if the result is consistently low, contact support or use the refund period.

### When is an HDD enough?

For archives, backups and files that are rarely read. Do not keep a site or a database on a hard drive: random operations on an HDD are hundreds of times slower.

_Updated: 2026-10-28_

# What is a VPS, in plain English

A VPS is a slice of a powerful physical server that you rent and that behaves like a separate computer, with its own operating system, its own IP address and full control. Below is how it differs from shared hosting, who needs one, what it costs and what to check right after you buy it.

> Source: https://accsly.io/en/vps/guide/what-is-vps · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A VPS (Virtual Private Server) is a computer in a data centre that runs around the clock on a fast internet connection, except that it is not a whole machine but a dedicated slice of a large server. The host puts a powerful machine in a rack, splits it with special software into several independent servers and rents each one out separately. You get your own operating system, your own IP address, your own memory and administrator rights. You can run a website, a bot, a database, company mail or any program for Linux or Windows on it.

The main difference from ordinary shared hosting is that you manage the server. That is both the upside and the downside: you can install anything you like, but you also have to look after the system yourself.

## Shared hosting, VPS and your own server: the difference in simple terms

The easiest way to picture it is housing. Shared hosting is like a room in a managed student residence: moving in is easy, the furniture is already there and the building manager takes care of the plumbing, but you cannot repaint the walls or bring your own stove. Hundreds of sites live on one server, and when a neighbour throws a party, everyone hears it.

A VPS is a flat in an apartment building. The walls, the lock and the keys are yours, you can do what you want inside, and the floor space is reserved for you. The building itself is shared, though: the foundation, the electricity and the lift are shared with the neighbours. In server terms, the foundation is the processor, the disks and the network of the physical machine.

A dedicated server is a detached house. All the hardware belongs to you alone and there are no neighbours, but it costs noticeably more, and if a disk fails, a replacement takes longer to arrive. Machines like that are collected in the [dedicated servers](https://accsly.io/en/dedicated) section.

This gives a simple rule. If you have a WordPress site and do not want to open a terminal, take [shared hosting](https://accsly.io/en/hosting). If you need a program that shared hosting will not let you install, or your site keeps hitting its limits, it is time for a VPS. How to tell that the moment has come is covered in the article [when to move from shared hosting to a VPS](https://accsly.io/en/vps/guide/hosting-to-vps-when).

## What you get for your money

First, administrator rights, usually called root access. This means you can install any software, change system settings and even reinstall the whole system. On shared hosting no customer has rights like that.

Second, your own IP address. Browsers, Telegram, payment systems and mail services find your server by it. You need your own address to point a domain at the server, get an HTTPS certificate and receive notifications from other services. Occasionally the very cheapest plans come without a dedicated IPv4 address, and such a server is almost unreachable from the outside, so the line about the IP in the plan is worth reading.

Third, reserved resources: processor cores, memory (RAM) and disk space. If the plan has 2 GB of memory, your programs can count on it no matter what the neighbours are doing. The processor is a little more complicated: on inexpensive plans the cores are shared, and under constant load the server may run slower than the number suggests.

Fourth, a choice of operating system. Most people install Ubuntu or Debian, which are free Linux distributions. Windows is available on almost half of the plans too (49% of the catalog), but the licence usually costs extra. How renting a Windows server works is explained in the article [Windows VPS: licence and RDP](https://accsly.io/en/vps/guide/windows-vps-license-rdp).

## What you will have to do yourself

To be honest, more than on shared hosting. The host is responsible for the hardware, the power and the network, while everything inside your virtual machine is your area. Updating the system, installing a web server, setting up protection against password guessing and making backups will be up to you or someone you hire.

It is less scary than it sounds. For a site on a popular CMS there are free control panels that install with a single command and give you almost the same interface as shared hosting. But remember one rule from the start: many hosts do not include backups in the price of a VPS. If the disk or the server fails and you have no copies, the data is gone. So set up backups on the very first day, even if the server is only for a trial.

## Who needs a VPS and who does not yet

You need a VPS when a program has to run constantly and on its own. A Telegram bot that waits for messages around the clock, an online shop with an order queue, a server for a small game with friends, an accounting system for an office: all of these are awkward or impossible to keep on shared hosting. Bots have their own guide: [VPS for a Telegram bot](https://accsly.io/en/vps/guide/vps-for-telegram-bot).

You also need a VPS when a site has outgrown its space. If your shared hosting regularly shows a "resource limit exceeded" error on ordinary days, not just at peak times, your own server with 2 GB of memory usually solves the problem.

A business-card site, a blog with ten posts a month or an ad landing page, on the other hand, does not need a VPS. It will not make them faster, it will only add chores. If a site is slow under light load, the cause is almost always the site itself: a heavy theme, uncompressed images or dozens of plugins.

## How much a VPS costs in 2026

I worked it out from 26,640 plans by 2,175 hosts in 97 countries that were in the accsly catalog on 27 October 2026: I took the price with monthly billing and found the median for each memory size. The catalog stores prices in roubles, so the dollar figures below are rounded and give the order of magnitude rather than exact amounts.

A server with 1 GB of memory costs about $7–8 a month at the middle of the market, and a quarter of such plans are cheaper than about $5. That is enough for a bot, a small API or a test environment, but tight for a site with a database.

With 2 GB of memory the median is around $12, and a quarter of the plans cost less than about $7–8. Location changes the price as well, so compare plans in the region where your visitors are: Frankfurt, Amsterdam or London for Europe, New York or Virginia for the US East Coast. For a first WordPress site or a shop with a few hundred products I would take 2 GB: with 1 GB, the database and PHP start to compete for memory at the first spike in visitors.

Very cheap plans for well under a dollar a month exist too, but they often have a catch: you have to pay for six months or a year up front, the core is shared with dozens of neighbours, and sometimes there is no IPv4 address of your own. Before buying a plan like that, look at the total amount due and the line about the IP. Selections by price and size: [cheap VPS](https://accsly.io/en/vps/cheap), [VPS with 1 GB](https://accsly.io/en/vps/1-gb-ram), [VPS with 2 GB](https://accsly.io/en/vps/2-gb-ram).

If you want to try first, look for [hourly billing](https://accsly.io/en/vps/hourly-billing): a server for an evening usually costs less than a dollar, and afterwards you can delete it. Some hosts also offer a [free trial](https://accsly.io/en/vps/free-trial).

## The first 15 minutes on the server: check what you were given

After payment the host sends you an IP address and a password. On Linux and macOS you connect from the terminal, on Windows 10 and 11 from PowerShell, and the command is the same:

```
ssh root@203.0.113.10
```

Replace 203.0.113.10 with your server's address. On the first login the system asks whether you trust this server; answer yes. Then run five commands that show whether what you got matches the plan:

```
nproc                   # how many cores the system sees
free -h                 # how much memory: row Mem, column total
df -h /                 # how much disk space: column Size
systemd-detect-virt     # virtualization type: kvm, openvz, lxc…
cat /etc/os-release     # which system is installed
```

The numbers should match the plan. Memory will look slightly smaller than advertised: 2 GB usually shows up as 1.9 GB because the system itself takes a share, and that is normal. But if you see 1 GB instead of 2 GB, or one core instead of two, contact support straight away.

The fourth command shows the virtualization type. The answer `kvm` means a full virtual machine on which almost everything works. The answer `openvz` or `lxc` means a container, where some programs, Docker for example, may not start. How they differ and which to choose is explained in the article [KVM or OpenVZ](https://accsly.io/en/vps/guide/kvm-or-openvz).

Right after the check, update the system. On Ubuntu and Debian it is a single command:

```
apt update && apt upgrade -y
```

Next, switch to key-based login instead of a password and turn on a firewall. Bots start guessing passwords on servers with open password login within the first few hours, and you can see it in the `/var/log/auth.log` file.

## Plan terms worth understanding

**vCPU** is a virtual core. Usually it is a processor thread shared with neighbours. If the plan says "dedicated cores" or dedicated vCPU, the core is reserved for you entirely, and such a plan costs more.

**KVM, OpenVZ, LXC** are virtualization types, that is, the way the host splits the physical server. The vast majority of plans today run on KVM: 93.5% of the catalog. Selection: [KVM VPS](https://accsly.io/en/vps/kvm).

**NVMe and SSD** are disk types. NVMe is faster at database operations, while for a small site the difference is barely noticeable. The details are in the article [NVMe or SSD](https://accsly.io/en/vps/guide/nvme-or-ssd), and plans are in the [NVMe VPS](https://accsly.io/en/vps/nvme) selection.

**Traffic and port** mean how much data the server can transfer per month and at what speed. Any plan with 1 TB of traffic is enough for a site or a bot; you only need to do the maths if you serve video or large files.

If a plan is called VDS rather than VPS, it is almost always the same thing. Where the two words come from is explained in the article [VPS vs VDS](https://accsly.io/en/vps/guide/vps-vs-vds), and all the parameters at once are covered in [how to choose a VPS](https://accsly.io/en/vps/guide/how-to-choose-vps).

## FAQ

### How is a VPS different from ordinary shared hosting?

On shared hosting you get space for a site, and the host manages the server, so you cannot install your own software. On a VPS the whole system is yours: you can install anything, but updating the server and making backups is up to you.

### How much does a VPS cost per month?

According to the accsly catalog on 27 October 2026, a server with 1 GB of memory costs about $7–8 a month at the middle of the market, and one with 2 GB about $12. A quarter of the 2 GB plans cost less than about $7–8.

### Do I need to know how to program to use a VPS?

You do not need to program, but you will have to run commands in a terminal. For a website you can install a free control panel and then work almost as you would on shared hosting.

### Can I install Windows on a VPS?

Yes, if the server runs on KVM, VMware or Hyper-V. Windows is available on almost half of the plans, but the licence is usually paid separately. Windows does not run in OpenVZ or LXC containers.

### What happens if the server breaks?

The host is responsible for the hardware: if it fails, the host moves the virtual machine or repairs the physical server. The data inside the machine is your responsibility, so set up backups on the very first day.

### How much memory should I get for my first site?

For a WordPress site or a small shop, take 2 GB. With 1 GB, the database and PHP start to compete for memory at the first spike in visitors, while 1 GB is enough for a bot or a small API.

_Updated: 2026-10-28_

# VPS for a Telegram bot: what the bot needs and how to pick a plan

A bot with a menu and a few commands runs fine on the cheapest server, while a bot with broadcasts, files and a database hits completely different limits. Here is what a bot really consumes, which Telegram limits shape the choice of server and how to avoid overpaying.

> Source: https://accsly.io/en/vps/guide/vps-for-telegram-bot · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A search for "VPS for a bot" usually ends with the cheapest plan, and half the time that is the right call. Problems show up later: a broadcast returns 429 errors, the bot cannot download a video a user sent, the webhook stops arriving after a move to a new server, or messages get lost during a night of downtime. Almost all of this comes from how the Bot API works, not from a lack of cores. Below: how to estimate your bot's load, which Telegram rules set the server requirements and what to check in a plan before paying.

## What a bot actually consumes

The bot itself is a small process that receives updates from Telegram and sends replies. The resources go to everything around it.

- **Network and latency.** Every bot action is an HTTPS request to api.telegram.org. For a menu bot, a stable connection matters more than bandwidth: traffic is measured in megabytes per day.
- **Database.** With a few hundred users SQLite is enough. Once there are thousands of users, orders, statistics and concurrent requests, you need PostgreSQL or MySQL, which means hundreds of megabytes of memory and a fast disk.
- **Queues and background jobs.** Broadcasts, scheduled reminders, payment processing through external services. Usually that is Redis plus a separate worker process.
- **Files.** Video conversion, image generation and PDF reports load the CPU and disk more than everything else combined.
- **External APIs.** A bot that forwards requests to an AI model over an API barely loads the server: it just waits for the answer. A bot with a local model is a job for a powerful server or a GPU.

Estimate not "how heavy the bot is" but how many such components it has and which of them run all the time.

## Bot API limits that affect the server

Telegram has limits that no amount of server power will lift. Know them before choosing a plan so you do not pay for resources the bot cannot use.

- **Sending rate.** Telegram advises against sending more than one message per second to a single chat, more than 20 messages per minute to a group, and bulk broadcasts faster than about 30 messages per second. Above that, the Bot API returns error 429 with a `retry_after` parameter. A broadcast to 10,000 users takes several minutes on any server, so you need a rate-limited queue, not extra cores.
- **File size.** Through the standard Bot API a bot downloads files up to 20 MB and uploads up to 50 MB. For more, you run your own Bot API server (the open-source telegram-bot-api project): it removes the download limit and allows uploads up to 2000 MB. That server keeps files on disk, so it needs spare disk space and memory.
- **Update retention.** While the bot is down, Telegram stores incoming updates, but for no longer than 24 hours. A day of downtime without monitoring and some user messages are gone for good.

## Webhook requirements for the server

The basic webhook rules, HTTPS and ports 443, 80, 88 or 8443, are covered on the [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot) page. A few more requirements usually come up only after the server is bought.

- **IPv4 only.** Telegram delivers webhooks to IPv4 addresses only; IPv6 is not supported. The cheapest plans without a dedicated IPv4 will not work for webhooks: you are left with long polling or a paid IPv4.
- **TLS 1.2 and newer.** Old SSL versions and TLS 1.0/1.1 are rejected. The certificate must match the domain; a self-signed certificate works if you upload it when calling `setWebhook`.
- **Source addresses.** Requests come from the subnets 149.154.160.0/20 and 91.108.4.0/22. You can open the webhook port in the firewall for these only.
- **Secret header.** The `secret_token` parameter of `setWebhook` makes Telegram add the `X-Telegram-Bot-Api-Secret-Token` header to every request. Check it in your app to drop forged requests.
- **Parallel connections.** By default Telegram keeps up to 40 simultaneous connections to the webhook (configurable from 1 to 100). If the handler is slow, requests pile up, so hand heavy work to a queue and answer Telegram right away.

While a webhook is set, you cannot receive updates with `getUpdates`. When moving to a new server, bring the bot up there first, then point the webhook to the new address; use the `drop_pending_updates` parameter only if you really do not need the queued updates.

## Which plan for which bot

Guidelines for a Linux server running a bot in Python, Node.js or Go. The figures include headroom for the system, logs and updates.

| Bot profile | What runs on the server | Plan |
| --- | --- | --- |
| Menu, commands, request forms | Bot and SQLite | 1 vCPU, 1 GB RAM, 10–20 GB SSD |
| Shop or appointment booking | Bot, PostgreSQL, Redis, admin panel | 2 vCPU, 2–4 GB RAM, 30–40 GB NVMe |
| Broadcasts to a large audience | Bot, database, queue, workers | 2 vCPU, 4 GB RAM, NVMe |
| Files and media | Bot, own Bot API server, conversion | 4 vCPU, 4–8 GB RAM, 80 GB disk or more |
| Several bots in Docker | Containers, reverse proxy, shared database | 2–4 vCPU, 4 GB RAM, KVM |

For the first two profiles see [VPS with 1 GB](https://accsly.io/en/vps/1-gb-ram) and [VPS with 2 GB](https://accsly.io/en/vps/2-gb-ram). If the bots live in containers you need KVM virtualization, see [VPS for Docker](https://accsly.io/en/vps/for-docker). A database with thousands of users benefits noticeably from NVMe, see [VPS for databases](https://accsly.io/en/vps/for-database).

## What to check in a plan

- **A dedicated IPv4** is mandatory for webhooks and makes working with external APIs easier.
- **Core type.** Shared cores are fine for a menu bot. For media conversion and scheduled broadcasts that coincide with the neighbours' peak hours, dedicated cores are more stable.
- **Hourly billing.** Handy for testing the bot under real load before a long payment period without paying for a test server for the whole month, see [VPS with hourly billing](https://accsly.io/en/vps/hourly-billing).
- **Snapshots and backups.** The bot's user database is the most valuable thing on the server. Check whether backups are included or cost extra.
- **Location.** For a bot, a stable route to Telegram and to external APIs matters more than ping to users. If the bot stores personal data, check the data residency rules that apply to your users, such as the GDPR in the EU.

How to compare different hosts' network and disk before paying is explained in [How to test VPS ping and speed before you pay](https://accsly.io/en/vps/guide/check-vps-speed-before-buying).

## Reliability: so the bot does not lose messages

Restarting after a crash via systemd or Docker is the minimum. It is not enough if the bot earns money.

- **External monitoring.** Every few minutes check that the bot responds: the `getWebhookInfo` method shows the number of pending updates and the last delivery error. A growing queue means the bot is stuck even though the process is formally alive.
- **Database backups off the server.** A daily dump to separate storage. A snapshot at the same host does not help if the problem is with the account or the data centre.
- **System updates.** Automatic security updates and reboots in a night window when the bot has the fewest users.
- **Log rotation.** A bot with verbose logs can fill a small disk within a few months, and then the database stops writing.

## The token and server access

The bot token gives full control over the bot: with it anyone can read incoming messages and post as the bot. Keep it in environment variables or in a file readable only by the bot's user, never in the repository. Run the bot under a separate user without root rights. Log in to the server with SSH keys and disable password login. If the token may have leaked, revoke it in @BotFather with the `/revoke` command and issue a new one.

If the bot takes payments, keep payment keys separate from the token and do not log full request bodies from the payment provider.

## When one VPS is not enough

A single server handles a bot with tens of thousands of users if heavy tasks go through a queue. Split things up when the database and workers get in each other's way: the database moves to a separate server with NVMe, media workers to a server with more cores. General principles for choosing CPU, memory and disk are in [How to choose a VPS](https://accsly.io/en/vps/guide/how-to-choose-vps). For bots on other messengers there are separate selections, such as [VPS for a Discord bot](https://accsly.io/en/vps/for-discord-bot).

## FAQ

### Is a VPS with 1 GB of RAM enough for a bot?

Yes, for a bot with a menu and commands on SQLite. With PostgreSQL, Redis, an admin panel or Docker take 2 GB, and for video processing or your own Bot API server start at 4 GB.

### Why does Telegram not deliver the webhook to my server?

Common causes: the server has no IPv4 (webhooks work only over IPv4), the port is not 443, 80, 88 or 8443, the certificate does not match the domain, or TLS below 1.2 is used. The getWebhookInfo method shows the last delivery error.

### Will a more powerful server speed up a broadcast?

No. Telegram limits bulk sending to about 30 messages per second and one message per second per chat. You need a rate-limited queue, not more cores.

### How can a bot handle files larger than 20 MB?

The standard Bot API lets a bot download files up to 20 MB and upload up to 50 MB. For larger files you run your own Bot API server, which needs spare disk space and memory.

### What happens to messages if the bot server goes down?

Telegram keeps incoming updates for up to 24 hours. If the bot comes back sooner it receives them; older updates are lost. That is why you need external monitoring.

### How do I protect a webhook from forged requests?

Set secret_token in setWebhook and check the X-Telegram-Bot-Api-Secret-Token header in your app. In addition, open the webhook port only to the Telegram subnets 149.154.160.0/20 and 91.108.4.0/22.

_Updated: 2026-10-22_

# How to test VPS ping and speed before you pay

The numbers in a plan do not tell you the latency to your users or how fast the disk really is. Most of this can be measured before you pay, the rest in the first hour after launch. Here are the tools and how to read the results.

> Source: https://accsly.io/en/vps/guide/check-vps-speed-before-buying · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

Two hosts with identical plans in the same city can give different ping to your users, different download speed and disks that differ several times in performance. The plan card will not tell you that, but you can check it. The network can almost always be measured before you pay: many hosts publish test addresses and looking glass pages. CPU and disk are checked in the first minutes after launch, and if the result is poor, the server can be returned within a trial period or deleted under hourly billing. Below is the order of checks and reference values for reading the results.

## What you can check before paying

Hosts that are confident in their network publish tools to test it. Look in the site footer, in the "Data centers" or "Network" section, or in the knowledge base.

- **A test IP address** for each location. You can ping it and run a trace from your own computer to see the real latency and route from your network.
- **Test files** of 100 MB, 1 GB or more. Downloading one shows how fast a server in that location delivers data to your provider.
- **Looking glass**: a web page where you can run ping or traceroute, or look up the BGP route from the host's router to any address. It is the view from the other side: how the host's network sees your office or your users.

The Accsly catalog collects hosts' test addresses and looking glass links and shows them where they are known. If a host has no such tools, ask support for a test IP; it usually takes a few minutes.

## Ping, mtr and traceroute: measuring latency

Measure latency from where the server's users are: from the office, from home and, for a public service, from several cities. A ping from one place says nothing about another.

- `ping -c 50 address` shows average latency and jitter. Look at the maximum and packet loss, not just the average: a steady 40 ms is better than 25 ms with spikes to 200.
- `mtr -rwc 100 address` (WinMTR or `pathping` on Windows) shows latency and loss at every hop. It is the main tool when you need to find where exactly time is lost.
- `traceroute` or `tracert` shows the packet path. Hop names reveal which networks and countries the traffic crosses: sometimes a server in a neighbouring country is reached through a route on the other side of the continent.

How to read mtr: loss at an intermediate hop with zero loss at the destination is usually not a problem, since many routers simply do not answer diagnostic requests. The warning sign is loss that starts at one hop and continues to the end of the route, or a sharp latency jump on a specific segment.

Reference values: within one city 1–5 ms, within a mid-sized European country 5–20 ms, Frankfurt to Amsterdam under 10 ms, Western Europe to the US East Coast 80–100 ms, US East to West Coast 60–80 ms, Europe to Asia 150 ms or more. For a website a difference of 30–40 ms is barely noticeable; for a game server, VoIP or remote desktop it is.

## Testing from several cities

If the server's audience is spread across a country or several countries, one measurement from the office is not enough. Free distributed testing services such as Globalping and RIPE Atlas run ping, traceroute and HTTP requests from hundreds of probes on different providers. They show which users have a long route to the data centre and where packets are lost. This is especially useful when choosing between two locations: a server that is 5 ms faster from London may be noticeably slower for users in Southern Europe or Scandinavia. For a service with users in several regions, a location with even latency for everyone is better than the fastest one for a single city.

## Download speed and test files

Download a 100 MB test file from each location you are considering: `curl -o /dev/null https://…/100mb.test` shows the average speed. Keep in mind that the result is limited by the slowest link: your home connection, Wi-Fi and your provider's evening congestion. So compare hosts with each other from the same computer at the same time, not with the figures in the plan.

Popular speed test sites measure the link to the server nearest to you, not to the host, so they are of little use for choosing a VPS. If a host has no test file, this check waits until the server is running.

## Trial periods, refunds and hourly billing

CPU and disk cannot be measured before launch, so it matters how cheaply you can try a server.

- **A free trial** of a day to a week on the plan or a reduced version of it. Some hosts require phone or ID verification. See [VPS with a free trial](https://accsly.io/en/vps/free-trial).
- **A money-back period** in the first days. Read the terms: refunds often cover only the first order, exclude licences and extra IPs, and go back only to the original payment method.
- **Hourly billing.** The easiest way to compare several hosts: start a server, run the tests within an hour and delete it, paying only for the time used. See [VPS with hourly billing](https://accsly.io/en/vps/hourly-billing).

With monthly billing and no trial or refund, start with the shortest term even if annual payment is cheaper: a yearly discount will not make up for a server that does not fit.

## What to measure in the first hour after launch

First check that you got what was promised: `lscpu` shows the CPU model and core count, `free -h` the memory, `lsblk` and `df -h` the disk. Then run three tests.

**Disk: fio.** For databases and websites, random I/O matters, not sequential writes. A typical test: `fio --name=rand --rw=randrw --bs=4k --size=1G --iodepth=32 --direct=1 --runtime=60 --time_based`. Reference values: a good NVMe drive gives tens of thousands of IOPS at 4 KB blocks, a SATA SSD from a few thousand to low tens of thousands, an HDD hundreds. If an "NVMe" plan delivers a couple of thousand IOPS, the disk is heavily throttled or overloaded by neighbours.

**CPU: sysbench or Geekbench.** `sysbench cpu --threads=1 run` and the same test on all cores show single-thread and whole-server performance. Geekbench is handy because the result can be compared with its public database. Run the test several times at different hours: if results jump around, the cores are shared and busy with neighbours.

**Network: iperf3.** A test between two of your servers or to a public iperf3 server shows the real port capacity: `iperf3 -c address -P 4 -t 30`, plus `-R` for the reverse direction. On a gigabit port expect 800–940 Mbps; if you get 100–200, the port is capped or shared.

If the server will send mail, also check that the assigned IP address is not on spam blocklists, and that latency from the server to your users matches what you measured before paying.

## Common testing mistakes

- **Testing over Wi-Fi.** A wireless network adds latency and loss that the host does not have. Use a cable for measurements.
- **One measurement at noon.** Networks and host neighbours behave differently in the morning and in the evening, so a single run can mislead you.
- **Disk test with cache.** Without `--direct=1`, fio measures memory rather than the disk, and the result is inflated several times.
- **A test that is too short.** Some plans are fast for the first minutes and then throttle the disk or CPU. Run tests for at least a minute.

## How to compare results

| Test | Normal result | Warning sign |
| --- | --- | --- |
| ping, mtr | Stable latency, no loss at the destination | Loss from 1% and latency spikes of several times |
| fio, 4 KB random | Tens of thousands of IOPS on NVMe | A few thousand IOPS on "NVMe" |
| sysbench, Geekbench | Repeated runs differ by a few percent | Spread of tens of percent |
| iperf3, 1 Gbps port | 800–940 Mbps in both directions | 100–200 Mbps or strong asymmetry |

- Compare hosts with the same set of tests, from the same points, at the same time of day.
- Repeat the measurements in the evening: overloaded hosts and links show up at peak hours.
- Look at consistency, not the best result: spread tells you more about overselling than the average.
- Write the results down in a table; a month later they help if the server starts to slow down.
- Judge by your task: for a website, disk and latency to the audience matter most; for code builds, the CPU; for file storage, the port.

Which plan parameters to check before testing is covered in [how to choose a VPS](https://accsly.io/en/vps/guide/how-to-choose-vps). You can filter plans with a trial, hourly billing and the right location in the [VPS search](https://accsly.io/en/vps).

## FAQ

### How can I check VPS ping before buying?

Find the test IP or looking glass page for the location on the host's website and run ping and mtr from your computer. If the address is not published, support usually provides it.

### What is a looking glass?

It is a web page that lets you run ping or traceroute, or look up the route from the host's router to any address. It shows how the host's network sees your office or users.

### What is a good ping for a VPS?

Within one city up to 5 ms, within a country 5–30 ms, to neighbouring European countries 10–40 ms. Stability matters more: no packet loss and no sharp latency spikes.

### How do I test disk speed on a VPS?

Run fio with a random read/write test at 4 KB blocks and direct I/O. A good NVMe drive shows tens of thousands of IOPS; a result several times lower means the disk is throttled or overloaded.

### Why does a speed test on a VPS differ from iperf3?

Speed test services measure the link to the chosen test server, and the result depends on its load. iperf3 between two known servers gives a more accurate picture of the port capacity.

### Can I test a VPS for free?

Yes, some hosts offer a free trial of a day to a week or a refund in the first days. With hourly billing a test costs only a few hours of server time.

_Updated: 2026-10-21_

# Corporate network on a VPS: remote access to the office

A rented server can become the hub of a company's private network: remote employees and branch offices connect through it to the ERP, file server, CRM and Git. Here are the common layouts, protocols, server requirements and security basics.

> Source: https://accsly.io/en/vps/guide/corporate-vpn-on-vps · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

When employees work from home, travel or sit in several offices, the company's internal systems have to be reachable for them but not for the whole internet. Exposing an ERP, a file server or a CRM directly is risky: bots start probing any open port within minutes. The standard answer is a private encrypted network: an employee first connects to the company gateway and only then reaches internal services. The gateway can live on the office router, but more and more companies put it on a rented VPS. Below is why, how the typical layouts work, which protocol and server to pick and what to do about security.

## Why move the gateway to a VPS

An office internet line is rarely a good entry point. The provider may not offer a permanent public IP address, office links are often asymmetric (fast download, slow upload), and a power cut in the building cuts off every remote employee at once. A VPS in a data centre has different conditions:

- a permanent dedicated IPv4 address that does not change on reboot;
- a symmetric 100 Mbps to 1 Gbps port and backup power in the data centre;
- the office connects to the gateway as an ordinary client, so no inbound ports have to be opened at the office;
- several offices and hundreds of employees connect to one point, with no tunnels to set up between every pair of sites.

If internal systems already run in the cloud or on rented servers, a gateway VPS in the same location adds almost no latency to them, and the office simply becomes one more member of the network.

## Typical corporate network layouts

**Remote access for employees.** A VPN server runs on the VPS and every employee has a personal connection profile. Once connected, the laptop gets an address in the internal network and sees only the resources the administrator allowed.

**Office to gateway (site-to-site).** The office router keeps a permanent tunnel to the VPS. A remote employee connects to the VPS and through it reaches the office subnet: the accounting server, file storage, printers. The office does not need a static IP for this.

**Hub and spoke for several branches.** Each branch builds a tunnel to the central gateway and exchanges data with the others through it. This is simpler than a full mesh, but the gateway becomes a single point of failure and needs a standby server.

All three layouts usually use split tunnelling: only internal subnets go into the tunnel, while the rest of the laptop's traffic goes out directly. The gateway is not loaded with system updates and video, and employees barely notice the connection in daily work.

## Which services to put behind the private network

- **ERP and accounting systems.** Desktop clients, web clients and remote desktop sessions to the accounting server stay inside the network. They are sensitive to latency, so put the gateway close to the database server.
- **File server.** SMB or NFS shares should never face the internet; over the private network they work as they do in the office.
- **CRM, wiki, ticket system, monitoring.** Web interfaces of internal systems can stay without a public address, hidden from crawlers and scanners.
- **Git and CI.** Repositories, the Docker image registry and build servers are reachable for developers only from the network; administrators also reach production servers over SSH from inside rather than through an open port.

## WireGuard, OpenVPN or IPsec

All three protocols encrypt traffic and suit a corporate network; they differ in speed, convenience and compatibility.

| Protocol | Strengths | When to choose it |
| --- | --- | --- |
| WireGuard | High speed, short config, key-based login, clients for every OS | Remote access for staff, small and mid-sized companies |
| OpenVPN | Certificates from your own CA, LDAP and Active Directory integration, runs over TCP | When user accounts are already managed centrally and directory checks are required |
| IPsec (IKEv2) | Supported by office routers and firewalls, built-in clients in Windows and macOS | Linking offices and branches, staff without an extra app |

A common combination is IPsec or WireGuard between offices and the gateway, plus WireGuard for employees' laptops and phones. Server requirements for each protocol are on the [VPS for WireGuard](https://accsly.io/en/vps/for-wireguard) and [VPS for OpenVPN](https://accsly.io/en/vps/for-openvpn) pages.

## What server to rent

A corporate gateway does not need powerful hardware, but a few parameters matter.

- **CPU and memory per number of users.** Up to 15 simultaneous connections run fine on 1 vCPU and 1 GB of RAM. For 15–50 employees take 2 vCPU and 2 GB, especially with OpenVPN, which encrypts in a single thread and is limited by per-core speed. More than 50 people or several branches: 2–4 vCPU and a second server on standby. If a user management panel and monitoring run on the same server, add another 1 GB of RAM.
- **KVM virtualization.** WireGuard and IPsec work at kernel level, and container platforms such as OpenVZ and LXC do not let you load a kernel module. Look for [KVM plans](https://accsly.io/en/vps/kvm).
- **Port and traffic.** The gateway carries report exports, file sync, backups and video calls. Ten employees easily use several hundred gigabytes a month, and nightly backups between offices use more. You need at least a 100 Mbps port, 1 Gbps for a whole office, and clear terms for traffic overage.
- **Location.** Put the gateway close to the office, most of the staff and the internal systems. For a team in Germany or the Netherlands, a data centre in the same country keeps latency in single-digit milliseconds. Before paying, ping the host's test IP from the office and from several employees' home connections.
- **Static IP.** A dedicated IPv4 is required: clients and the office router connect to it. Plans with NAT or a shared address do not work for a gateway.
- **Disk.** 10–20 GB is enough: the system, configs and connection logs take little space.

Plans that meet these requirements are collected on the [VPS for corporate VPN](https://accsly.io/en/vps/for-vpn) page.

## Basic gateway security

The gateway is the one point through which the internal network can be reached from outside, so it needs better protection than any other company server.

- **Personal keys and certificates.** Every employee gets a personal key, not a shared department password. A leaver is cut off with one command without touching anyone else; keys stay on the device instead of being sent around in messengers.
- **Two-factor authentication.** OpenVPN and IPsec connect to a user directory and one-time codes; for WireGuard the second factor is added through the portal that issues profiles. Administrators log in to the server itself with SSH keys only, password login disabled.
- **Firewall.** From outside only the VPN port is open, plus SSH restricted by source address if needed. Inside the tunnel access is split by role: finance gets the accounting system, developers get Git and test servers, everyone else gets the file server and CRM.
- **Logs.** Record who connected, when and from which address, and keep the logs away from the gateway. You need them for incident investigation and for internal audits.
- **Updates and redundancy.** Patch the OS and the VPN server regularly. A second gateway in another data centre and a spare profile on every device keep the company working if the main server goes down.

## How to roll it out to employees

The technical part takes a day; most problems appear when access is handed out. Prepare a short guide for staff: which app to install, how to import the profile, whom to contact if the connection fails. Issue profiles through a portal or a device management system rather than by email attachments. Start with a small group, such as finance or the development team, check how the accounting system and the file server perform through the tunnel, and only then move everyone else. Give internal services readable names in an internal DNS zone so that people open crm.office instead of a string of digits.

## The legal side

A private network for a company's own employees is ordinary information security practice: it protects business data and accounts, including when someone works from a hotel or an airport over public Wi-Fi. Put the rules in internal policies: who gets access, to which systems, how keys are issued and revoked. If personal data of customers or staff passes through the network, the GDPR applies in the EU: choose a host that signs a data processing agreement, keep servers with such data in a suitable jurisdiction and log access to them.

## Checklist before launch

- The layout is chosen: remote access, office link or hub and spoke.
- The protocol and the way profiles are issued to staff are decided.
- The server runs on KVM with headroom for simultaneous connections.
- Dedicated IPv4; port and traffic sized for backups and video calls.
- Latency to the gateway checked from the office and from employees' homes.
- Personal keys, a second factor, a firewall and connection logs.
- A standby gateway and an update plan exist.

You can filter servers by virtualization, location, port and price in the [VPS search](https://accsly.io/en/vps).

## FAQ

### How many employees can a VPS with 1 core and 1 GB of RAM handle?

With WireGuard it is about 10–15 simultaneous connections for normal office work. OpenVPN uses more CPU, so for 15 people or more take 2 cores and 2 GB.

### Which protocol is best for remote access to the office?

WireGuard is the simplest for staff with laptops and phones. OpenVPN suits setups that check users against Active Directory or LDAP, and IPsec is the usual choice for linking office routers and branches.

### Does the office need a static IP for a corporate network on a VPS?

No. The office router connects out to the gateway on the VPS, so only the server needs a static address.

### Can remote staff use the accounting system without exposing it to the internet?

Yes. The server stays in the internal network, and employees reach it through the corporate gateway with a desktop client, a web client or remote desktop.

### Why does a corporate VPN not work on OpenVZ?

WireGuard and IPsec work at Linux kernel level, and container virtualization does not let you load your own kernel module. Choose KVM for the gateway.

### Where should the corporate gateway be located?

Close to the office, most of the staff and the internal systems. Before paying, ping the host's test IP from the office and from employees' home connections.

_Updated: 2026-10-21_

# How to choose a VPS: the 7 specs that matter

Two plans with the same "2 cores, 4 GB, 50 GB" can differ several times in speed and twice in price a year later. Here is what stands behind each line of a VPS plan and what to check before you pay.

> Source: https://accsly.io/en/vps/guide/how-to-choose-vps · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

A virtual server plan usually fits in four lines: cores, memory, disk, price. That is not enough to compare offers from different hosts. Identical numbers can hide processors of different generations, shared or pinned cores, disks of very different speed, a port with a traffic cap and a price that goes up after the first month. Below are seven parameters in roughly the order they affect the result, with a short checklist at the end.

## 1. CPU: cores, allocation type and model

The vCPU count is the first thing you see in a plan, but not the most important. One vCPU is usually one thread of a physical processor, not a whole core. Three things matter more.

- **Shared or dedicated cores.** On shared cores, CPU time is split with the neighbours on the host: the server is fast in quiet hours and noticeably slower under common load. Dedicated cores are pinned to you and cost more. Shared cores are fine for a brochure site or a test environment; for a database, code builds and constant load, dedicated cores are the better choice.
- **Model and generation.** Older Xeon E5 chips offer many cores with low per-core performance. Current AMD EPYC chips are built for multi-threaded work, while Ryzen and other high-clock desktop chips shine where a single thread matters: game servers, PHP, some business applications.
- **Clock speed.** If a host only says "up to 3.5 GHz", that is the turbo peak, not the sustained frequency.

You can check what you got in the first minutes after launch: `lscpu` shows the CPU model, and a short benchmark such as sysbench or Geekbench shows per-core performance. If the result is clearly worse than expected, that is a reason to use the trial period or a refund.

If a plan does not name the CPU model, assume it is not the newest hardware and ask support before paying.

## 2. Memory

RAM is the most common bottleneck on small servers. Rough guidelines for Linux: 1 GB is enough for a simple nginx site or a small bot, 2 GB for a CMS site with a database, 4 GB or more for several Docker containers, a control panel or a store with real traffic. Windows Server needs at least 4 GB and is comfortable from 8 GB.

Check whether memory is guaranteed. With some virtualization types a host may show "up to 4 GB" while guaranteeing less. Swap on disk is not a substitute for memory: once the server starts using it heavily, it slows down dramatically.

## 3. Disk: type and size

The disk type affects the speed of a site and a database more than an extra core does.

| Type | Good for | Keep in mind |
| --- | --- | --- |
| NVMe | Databases, online stores, CI, anything that reads and writes a lot | Several times faster than SATA SSD on random operations |
| SSD (SATA) | Websites, bots, small services | A good middle ground if NVMe is expensive |
| HDD | Backups, archives, file storage | Slow on random access, not for databases |

Plans with fast disks are collected on the [NVMe VPS](https://accsly.io/en/vps/nvme) page. Size the disk with headroom: the OS and packages take 5–10 GB, and logs and Docker images grow quietly. Check whether backups and snapshots are included in the price; many hosts sell them separately.

## 4. Network: port, traffic, IP and location

- **Port speed.** 100 Mbps and 1 Gbps is a tenfold difference when serving or downloading files. Sometimes a gigabit port is shared by several customers and less is guaranteed.
- **Traffic.** Unlimited traffic on a slow port and 2 TB on a gigabit port are different terms. Check what happens when you go over: a charge per terabyte or a speed cap.
- **IPv4 and IPv6.** One IPv4 address is usually included; extra ones cost money. The cheapest plans sometimes come with IPv6 only, and some users and services will not be able to connect to such a server.
- **Location and latency.** Pick a data centre close to your audience. Within Western Europe, latency between major hubs such as Frankfurt, Amsterdam, London and Paris is usually 5–20 ms; across the Atlantic it is around 70–100 ms, and from Europe to Asia often more than 150 ms. For a website 40 ms is barely noticeable; for a game server or voice calls it is.

For public services, ask about DDoS protection: basic filtering is often included, advanced protection is sold separately. Also check how the data centre is connected: a host with several upstream providers has more stable connectivity and shorter routes to users in other regions.

## 5. Virtualization: KVM vs OpenVZ and LXC

The virtualization type determines what you can run on the server at all.

**KVM** is full virtualization: the server has its own OS kernel, you can install any system including Windows, change the kernel, load modules and run Docker and Kubernetes without restrictions. Resources are usually strictly allocated. See [KVM VPS](https://accsly.io/en/vps/kvm).

**OpenVZ and LXC** are container virtualization: all customers on the host share one Linux kernel. This is cheaper and starts quickly, but you cannot install Windows or load your own kernel modules, and Docker does not always work or works with limitations. Memory and CPU on such plans are more often oversold.

If you need Windows, Docker, your own WireGuard private network for remote office access, or a custom kernel, choose KVM. For a simple Linux site or bot a container will do.

## 6. Operating system and control panel

Almost every host offers ready images of Ubuntu, Debian, AlmaLinux and Rocky Linux. Check that the version you need is available and whether you can install from your own ISO image; on KVM this is usually possible.

Windows Server almost always requires a licence, either included in the plan price or billed separately every month. Compare the total; ready-made offers are on the [Windows VPS](https://accsly.io/en/vps/windows) page.

A server control panel (cPanel, Plesk, ISPmanager, or free HestiaCP and aaPanel) makes it easier to manage sites and mail, but paid panels add a noticeable amount to the bill, and the panel itself uses some memory. If you are comfortable in the console, you do not need one. If all you want is a website without server administration, shared web hosting is simpler.

## 7. Price: what you will actually be charged

The price on the storefront and the amount on the invoice a year later often differ. Check five things.

- **Promo price vs renewal price.** A discount on the first month or first year is common. Look at the renewal price: that is what you will keep paying.
- **Billing term.** A low monthly price often applies only when you pay for one or three years in advance. Month to month, the same plan costs more.
- **VAT and fees.** In the EU, VAT is often added at checkout depending on your country and whether you buy as a business with a VAT ID. Compare prices on the same basis.
- **Hourly billing.** Handy for tests and temporary tasks: you can delete the server after a day and pay only for the hours it ran. See [VPS with hourly billing](https://accsly.io/en/vps/hourly-billing).
- **Trial and money-back.** A free trial of a few days or a refund window lets you test disk speed and network before a long commitment. Such plans are on the [VPS with a free trial](https://accsly.io/en/vps/free-trial) page.

Also look at payment methods: bank cards, PayPal, invoices for companies, and with some hosts cryptocurrency. And read the contract: if the server will store personal data of EU residents, check where the data centre is located and whether the host offers a data processing agreement under the GDPR.

## When a VPS is not the best choice

If the CPU is busy around the clock and the VPS plan is approaching the price of a physical machine, look at [dedicated servers](https://accsly.io/en/dedicated). Neural network training and rendering need GPU servers. And the difference between the terms VPS and VDS is covered in the article [VPS or VDS](https://accsly.io/en/vps/guide/vps-vs-vds).

## Checklist before renting a VPS

- Cores are shared or dedicated; the CPU model is stated.
- Memory has 30–50% headroom for peak load.
- NVMe or SSD disk with room for logs and copies; backups are included or priced separately.
- Port speed, traffic allowance and overage terms.
- A dedicated IPv4 address; the data centre is close to your audience.
- KVM virtualization if you need Windows, Docker or your own kernel.
- The OS you need is available; Windows licence and panel are included or extra.
- Renewal price, not just the first month; VAT; billing term.
- Hourly billing, a trial or a money-back guarantee.
- A convenient payment method and a clear contract.

You can filter plans by all of these parameters at once in the [VPS search](https://accsly.io/en/vps).

## FAQ

### How much RAM does a VPS need for a website?

A simple Linux site runs on 1 GB, a CMS such as WordPress with a database needs 2 GB, and a store or several sites with a control panel need 4 GB or more. Windows Server needs at least 4 GB.

### Which is better: KVM or OpenVZ?

KVM gives you a full virtual machine with its own kernel, so Windows, Docker and any kernel modules work. OpenVZ is cheaper but suits only Linux tasks without special kernel requirements.

### What is the difference between dedicated and shared vCPU?

Shared cores split CPU time with neighbours on the physical server, so speed drops under load. Dedicated cores are pinned to you and give stable performance, but cost more.

### Do I need NVMe for a small website?

For a static site the difference is barely noticeable. For a CMS with a database, an online store or code builds, NVMe makes a clear difference, especially with concurrent requests.

### Why did my VPS get more expensive after the first month?

Many hosts advertise a promo price for the first period and renew at the regular rate. Before paying, find the renewal price in the terms and compare that.

### Which VPS location should I choose?

Choose the data centre closest to most of your users. For an EU audience a location in the EU also simplifies GDPR compliance; for a US audience pick the coast or region where most visitors are.

_Updated: 2026-10-21_

# VPS vs VDS: is there a difference and what actually matters

In most markets VPS and VDS mean the same thing: a virtual server. The difference that really affects your work is hidden not in the name but in the virtualization type and whether resources are guaranteed.

> Source: https://accsly.io/en/vps/guide/vps-vs-vds · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

"Which is better, VPS or VDS?" is a question people ask all the time, and the answers are confident but contradictory. Some hosts claim a VDS is a "more dedicated" server, others use both words as synonyms on the same page. Let us look at where the terms came from, what they mean technically and which lines of a plan to read instead of the name.

## Where the two terms come from

VPS stands for Virtual Private Server. VDS stands for Virtual Dedicated Server. Both describe the same thing: a physical server split into several isolated virtual machines, with each customer getting their own, with root access, an own IP address and an own operating system.

Internationally, VPS is the standard term. VDS is rare outside Russian-speaking and some Eastern European markets, and large cloud platforms do not use either: they say "virtual machine" or "instance". Where both words took root, an informal convention appeared:

- **VPS** means container virtualization (OpenVZ, LXC), with resources shared with neighbours;
- **VDS** means full virtualization (KVM, VMware, Hyper-V), with resources reserved for the customer.

The logic is clear: in a container the customer really shares the system kernel and often memory with neighbours, while a KVM virtual machine is closer to a separate server. The word "dedicated" in VDS stressed exactly that. Since then KVM has become the standard, OpenVZ has moved to the budget segment, and the marketing names have stopped reflecting how a plan works.

The convention is not written down anywhere. Some hosts sell a "VPS" on KVM with dedicated cores, others a "VDS" on shared resources. So the plan name guarantees nothing. In the Accsly catalog both kinds are listed in a single [VPS search](https://accsly.io/en/vps), and filters for virtualization and resources tell them apart.

## What really differs: the virtualization type

The key difference is how isolation works.

|  | KVM (full virtualization) | OpenVZ / LXC (containers) |
| --- | --- | --- |
| OS kernel | Each server has its own | Shared Linux kernel of the host |
| Windows | Can be installed | Not possible |
| Docker, Kubernetes | Work without restrictions | Not always, or with limitations |
| Kernel modules, in-kernel WireGuard | Yes | Only if the host allows it |
| Install from your own ISO | Usually yes | No, templates only |
| Overselling | Less common, resources reserved | More common |
| Price | Higher | Lower |

On KVM a virtual machine behaves almost like a physical server: you can change the kernel, configure a kernel-level firewall, set up a private network for employees to reach the office, and run nested containers. See [KVM VPS](https://accsly.io/en/vps/kvm) plans.

OpenVZ and LXC are lighter and cheaper: a container starts in seconds, and the host fits more customers on one machine. For a PHP site, a chat bot or a small API on Linux this is enough. Limitations start when you need Windows, a recent kernel or Docker. Such plans are on the [OpenVZ VPS](https://accsly.io/en/vps/openvz) page.

## Is a cloud server a third option?

Next to VPS and VDS you often see a third term: "cloud server". Technically it is the same virtual machine, most often on KVM. The differences are in the tooling around it: billing by the hour or even the minute, resizing without reinstalling, snapshots, load balancers, network disks that survive a physical host failure, and an API for automation. A classic VPS is usually billed monthly and lives on the local disks of one server.

That line is blurred too: many hosts have added hourly billing and snapshots to regular plans, and "cloud" is used for any virtual server. If you need to create and delete machines quickly for tests, look at hourly billing and an API rather than the word "cloud".

## VPS vs shared hosting: where the line is

Another common confusion is between a virtual server and shared web hosting. With hosting you get a folder for your site, a database and a control panel, while the host manages the server: updates the system, takes care of security, configures PHP. There is no root access and you cannot install your own software. On a VPS or VDS the whole system is yours, but so is the administration. If you only need a site on a popular CMS and do not want to work in the console, [web hosting](https://accsly.io/en/hosting) is more convenient.

## Guaranteed vs burst resources

The second thing that matters more than the name is whether resources are guaranteed.

**Guaranteed** resources are reserved for your server: if a plan says 4 GB of memory and 2 dedicated cores, they are always available, whatever the neighbours are doing.

**Burst** means the server can briefly use more than the guaranteed amount if the host has spare capacity. In a plan it looks like "1 GB guaranteed, up to 2 GB burst". It sounds generous, but you cannot rely on the upper figure: when the neighbours need resources too, they will not be there.

The CPU works similarly. Shared vCPUs are a share of CPU time, and the host counts on customers not loading the processor at the same moment. Some hosts state the allowed average load in their terms, for example "no more than 50% of a core sustained". If your service keeps the CPU busy all the time, look for plans with dedicated cores, called dedicated vCPU, CPU-optimized or simply dedicated cores, whether the plan is labelled VPS or VDS.

Signs of overselling you can see after launch: steal time in `top` is clearly above zero, disk speed changes a lot during the day, and benchmarks give different results in the morning and in the evening.

## When you need a dedicated server rather than a VPS or VDS

Even the best virtual server shares a physical machine with others. A dedicated server makes sense when:

- the CPU is constantly busy, and a virtual server with dedicated cores already costs as much as a physical machine;
- a database is limited by disk latency and needs direct NVMe access without a virtualization layer;
- software is licensed per physical CPU or socket;
- security or audit requirements rule out a shared hypervisor;
- you need your own resource layout: your own hypervisor and your own virtual machines inside it.

Keep the other side in mind. A physical server takes longer to provision, is usually billed monthly, sometimes with a setup fee, and replacing a failed disk or power supply takes time. A virtual server in the same situation is moved to another host, often without your involvement. So for small projects a virtual machine with dedicated cores is often more reliable and cheaper than the most basic dedicated server.

Physical machine configurations are collected in the [dedicated servers](https://accsly.io/en/dedicated) section, and servers with graphics cards in the [GPU servers](https://accsly.io/en/gpu) section.

## How to read a plan instead of its name

To understand what you are renting, ignore the words VPS or VDS and find answers to six questions in the plan description.

- **Virtualization.** KVM, VMware or Hyper-V is full virtualization; OpenVZ, Virtuozzo or LXC is a container. If the type is not stated, ask support.
- **Cores.** Shared or dedicated; is the CPU model stated.
- **Memory.** Guaranteed or "up to N GB"; is there a burst clause.
- **Disk.** NVMe, SSD or HDD; local or network storage; are there I/O limits.
- **Network.** Port speed, guaranteed bandwidth, traffic allowance.
- **Acceptable use.** Limits on average CPU load, what is allowed and forbidden on the server.

Example: a plan is called "VDS Start", but the terms say OpenVZ and "up to 2 GB of memory". In fact it is a container with burst memory, not a virtual machine with reserved resources. The reverse example: a "Cloud VPS" on KVM with two dedicated cores is exactly what other terminology would call a VDS.

A detailed look at the other parameters, from CPU and disks to network and renewal price, is in the article [how to choose a VPS](https://accsly.io/en/vps/guide/how-to-choose-vps).

## Common mistakes

- **Choosing by the word VDS and expecting dedicated resources.** Without an explicit "dedicated cores" and a stated virtualization type it is just a name.
- **Taking OpenVZ for Windows or Docker.** Windows will not run there, and Docker may be unstable. For these tasks there are [Windows VPS](https://accsly.io/en/vps/windows) plans and KVM plans.
- **Comparing core counts only.** Two dedicated cores of a current processor are faster than four shared cores of an old Xeon.
- **Not testing the server in the first days.** If the host offers a trial or a refund window, use it to benchmark disk, network and CPU.

## In short

In 2026 the difference between VPS and VDS is a matter of marketing, not technology. What counts is the virtualization type, the resource guarantees and the hardware. For Windows, Docker and steady load choose KVM with reserved resources; for simple Linux tasks an inexpensive container will do. When a virtual server becomes too small, the next step is a dedicated server.

## FAQ

### Are VPS and VDS the same thing?

In practice, yes: both terms mean a virtual server with root access. Sometimes VDS is used for KVM servers with reserved resources and VPS for OpenVZ containers, but there is no common rule, so check the plan description.

### Which should I choose for a website, VPS or VDS?

Look at the virtualization and resources, not the name. A CMS site runs well on KVM with 2 GB of memory and an NVMe disk; a simple site is fine on an inexpensive container.

### Can I install Windows on a VPS?

Yes, if the server uses full virtualization such as KVM, VMware or Hyper-V. Windows cannot be installed on OpenVZ or LXC, because containers share the Linux kernel of the host.

### What is burst memory in a VPS plan?

It is memory above the guaranteed amount that the server can use temporarily if it is free on the host. You cannot rely on it: when neighbours are busy, it is not available.

### How can I tell if resources are oversold?

After launch, check steal time in top or htop and run disk and CPU benchmarks at different times of day. High steal time and widely varying results point to an overloaded host.

### When should I move from a VPS to a dedicated server?

When load is consistently high and a large virtual server costs about as much as a physical machine. A dedicated server is also needed for per-socket licences and full isolation requirements.

_Updated: 2026-10-21_

# VPS for a corporate VPN

A corporate VPN — staff access to the office and internal servers — needs just 1 core and 1 GB of RAM; bandwidth, traffic allowance and KVM (for WireGuard and OpenVPN) matter more. Here: KVM plans with unmetered traffic. Cheapest first.

> Source: https://accsly.io/en/vps/for-vpn · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 7,195, hosts: 689
- Price: from 0.49 $, a quarter below 17.95 $, median 39.95 $
- NVMe: 48 %, unlimited traffic: 100 %, hourly billing: 11 %
- RAM → price from: 1 GB — 0.49 $, 2 GB — 2.68 $, 4 GB — 4.05 $, 8 GB — 5.58 $, 16 GB — 7.95 $
- Countries: USA (1783), Germany (1266), Netherlands (1116), United Kingdom (806), France (671), Singapore (483)
- Cheapest hosts: [Sindad](https://accsly.io/en/vps/hosting/sindad) — 1.71 $, [Servera](https://accsly.io/en/vps/hosting/servera) — 2.12 $, [NLCloud](https://accsly.io/en/vps/hosting/nordlights) — 2.30 $, [Netcup](https://accsly.io/en/vps/hosting/netcup-eu) — 2.51 $, [Teknosos.com.tr](https://accsly.io/en/vps/hosting/teknosos-com) — 2.51 $

## Cheapest plans — 7,195 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | STARDUST1-S | 1 × 2.1 GHz | 1 GB | — | FR, NL, PL | — | 0.49 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Pico | 1 | 128 MB | 5 GB SSD | US | Crypto | 0.50 $ |
| [uaVPS](https://accsly.io/en/vps/hosting/uavps) | VPS-PROMO | 1 | 512 MB | 10 GB NVMe | UA, PL, FR, DE, NL | — | 0.90 $ |
| [RuVPS](https://accsly.io/en/vps/hosting/ruvps) | VPS-0 | 1 | 768 MB | 7 GB NVMe | NL, PL, UA | Visa/MC, Crypto | 0.95 $ |
| [Jink Host](https://accsly.io/en/vps/hosting/jink) | Dirt | 1 | 512 MB | 20 GB NVMe | US, NL | Visa/MC, PayPal, Crypto | 1.00 $ (total when paying for 3 mo (3.00 $)) |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Nano | 1 | 256 MB | 10 GB SSD | US | Crypto | 1.00 $ |
| [Host Media Ltd](https://accsly.io/en/vps/hosting/hostmedia) | Developer VPS 512MB IPv6-only | 1 | 512 MB | 10 GB SSD | GB | Visa/MC | 1.01 $ (total when paying for year (12.07 $)) |
| [myPrepaid-Server](https://accsly.io/en/vps/hosting/myprepaid-server) | 1 Euro Server | 1 × 3.5 GHz | 512 MB | 20 GB NVMe | DE | Visa/MC, PayPal, Invoice | 1.12 $ |
| [myPrepaid-Server](https://accsly.io/en/vps/hosting/myprepaid-server) | ONLY IPv6 | 1 | 512 MB | 15 GB SSD | DE | Visa/MC, PayPal, Invoice | 1.12 $ |
| [WebHosting24](https://accsly.io/en/vps/hosting/webhosting24) | Munich NVMe KVM 512MB | 1 × 2.4 GHz | 512 MB | 10 GB NVMe | DE | Visa/MC, PayPal, Crypto, Invoice | 1.39 $ (total when paying for year (16.79 $)) |
| [Sprintbox](https://accsly.io/en/vps/hosting/sprintbox) | Студент | 1 | 600 MB | 7 GB NVMe | RU, NL, DE, US, BY, AM… | — | 1.70 $ |
| [Sindad](https://accsly.io/en/vps/hosting/sindad) | Personal (شخصی), по скорости | 1 | 1 GB | 30 GB SSD | IR, US | — | 1.71 $ |
| [Hostmaze](https://accsly.io/en/vps/hosting/hostmaze) | KVM SSD 2C/256MB | 2 | 256 MB | 15 GB SSD | RO | PayPal, Visa/MC, Crypto | 1.87 $ (total when paying for year (22.39 $)) |
| [Microtronix ESolutions, LLC](https://accsly.io/en/vps/hosting/microtronixdc) | 512MB KVM | 2 | 512 MB | 20 GB SSD | US | Visa/MC, Crypto | 2.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Micro | 1 | 512 MB | 20 GB SSD | US | Crypto | 2.00 $ |
| [BuyVM](https://accsly.io/en/vps/hosting/buyvm) | SLICE 512 | 1 × 3.5 GHz | 512 MB | 10 GB SSD | US, LU | — | 2.00 $ (total when paying for year (24.00 $)) |
| [Host Media Ltd](https://accsly.io/en/vps/hosting/hostmedia) | Developer VPS 512MB | 1 | 512 MB | 10 GB SSD | GB | Visa/MC | 2.01 $ (total when paying for year (24.13 $)) |
| [Host Media Ltd](https://accsly.io/en/vps/hosting/hostmedia) | VPS 512MB IPv6-only | 1 | 512 MB | 15 GB SSD | GB | Visa/MC | 2.01 $ (total when paying for year (24.13 $)) |
| [Servera](https://accsly.io/en/vps/hosting/servera) | Linux VPS XS | 1 | 1 GB | 10 GB NVMe | SE, PL | Visa/MC | 2.12 $ (when paying for 2 years: 1.79 $/mo) |
| [1-VPS](https://accsly.io/en/vps/hosting/1-vps) | 0 KVM | 1 | 512 MB | 5 GB SSD | US, GB | Visa/MC | 2.18 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/for-vpn?format=json

## How to choose a VPS for a corporate VPN

A corporate VPN on a rented server joins staff, the office and internal systems into one private network. Remote employees use it to reach the accounting system, file storage and CRM, branches exchange data over an encrypted link, and administrators reach servers from inside the network instead of through SSH exposed to the whole internet. It also encrypts laptop connections on hotel, airport and café Wi-Fi. None of this needs a powerful server: what matters is bandwidth, traffic, the virtualization type and how access is issued.

### Protocol: WireGuard, OpenVPN or IPsec

**WireGuard** is the fastest and simplest: a short config, keys instead of passwords, clients for Windows, macOS, Linux, iOS and Android. It suits remote access for employees and linking two or three offices. Requirements and plans are on the [VPS for WireGuard](https://accsly.io/en/vps/for-wireguard) page.

**OpenVPN** is slower, but it also runs over TCP, checks certificates from your own certificate authority and plugs into LDAP or Active Directory, which helps when employee accounts are already managed centrally. It encrypts in a single thread, so core frequency matters more than core count: see [VPS for OpenVPN](https://accsly.io/en/vps/for-openvpn).

**IPsec** (strongSwan, IKEv2) is the usual choice for site-to-site links: office routers and firewalls support it out of the box, and so do the built-in clients of Windows and macOS, so employees do not need to install anything.

### Sizing by number of employees

- **Up to 10–15 people**: 1 core and 1 GB of memory is plenty for WireGuard or OpenVPN plus a simple user management panel.
- **15–50 people**: 2 cores and 2 GB, especially for OpenVPN; when a whole department works at once, a single core becomes the bottleneck.
- **More than 50 people or several branches**: 2–4 cores, a port of 1 Gbit/s or more and a second server on standby. If the only gateway goes down, the whole company loses its internal systems.
- **Disk** hardly matters: 10–20 GB holds the system, configs and several months of logs.

Virtualization should be [KVM](https://accsly.io/en/vps/kvm) only. OpenVZ and LXC do not let you load a kernel module or fully configure the network stack, so WireGuard and IPsec either will not start there or will run slowly. The table above already lists KVM only.

### Bandwidth and traffic

A corporate VPN carries more than requests to internal systems: report exports, backups, file sync and video meetings go through it too. Ten employees working with shared files and calls easily use several hundred gigabytes a month, and replication between branches adds terabytes. That is why this selection has plans without a traffic cap; all of them are on the [unlimited traffic VPS](https://accsly.io/en/vps/unlimited-traffic) page. Look at the port speed too: 100 Mbit/s is shared by everyone connected at the same time, so a team or an office needs 1 Gbit/s. With some hosts «unlimited» means fair use, and speed can be cut under constant load, so read the terms before paying.

### Where to put the server

Place the gateway close to the people who use it: the office, most of the staff, or the internal systems they need to reach. Every extra ten milliseconds shows in remote desktop, accounting software and voice calls. If the team is spread across cities or countries, test the ping from several of them to the host's test IP or looking glass, since the route to the same data centre differs between providers. A company needs a dedicated IPv4 address: plans with NAT and a shared address are awkward for accepting incoming connections from employees.

### Logs, access control and GDPR

Give every employee their own key or certificate instead of a shared password, so a person who leaves can be cut off in a minute without touching anyone else. Keep a connection log (who, when, from which address), allow logins to the server itself with SSH keys only and close unused ports with a firewall. Inside the tunnel, open only the subnets each group needs: finance gets the accounting system, developers get the test servers.

If personal data of customers or staff passes through the VPN, GDPR applies. The host becomes a data processor, so you need a data processing agreement (DPA) with it, and a server inside the EU or EEA keeps the setup simple. Connection logs with IP addresses are personal data as well: set a retention period in your internal policy and do not keep them longer.

## FAQ

### How many employees can a VPN on a small VPS handle?

WireGuard on one core and 1 GB of memory comfortably serves 10–15 simultaneous connections with normal office work. The port speed usually becomes the limit before the CPU does.

### WireGuard or OpenVPN for remote access to the office?

WireGuard is faster and easier to set up. OpenVPN is chosen when you need TCP, certificates from your own certificate authority or logins with Active Directory accounts.

### How do I link two offices through a VPS?

Run WireGuard or IPsec on the server, connect the routers of both offices to it as clients and add routes to each other's subnets. Most office routers and firewalls can do this out of the box.

### Why won't WireGuard install on my VPS?

Most often the server runs on OpenVZ or LXC, where kernel modules cannot be loaded. You need KVM virtualization, where WireGuard installs normally.

### How much traffic does a corporate VPN use?

Office work takes tens of gigabytes per employee a month, and 100–300 GB with video meetings and files. Backups and branch sync add terabytes, so plans without a traffic cap are more convenient.

### How does a corporate VPN protect staff on public Wi-Fi?

The laptop's connection to the company gateway is encrypted, so the hotspot owner and other users on the network cannot read or alter it. This matters for logging in to company mail, CRM and banking.

### Do I need a DPA with the hosting provider?

Yes, if personal data of people in the EU passes through or is stored on the server: the host acts as a processor under GDPR. Most European hosts offer a standard DPA in the control panel or on request.

## More selections

- Tasks: [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS for a website

A WordPress, Bitrix or Laravel site needs at least 2 GB of RAM and 20 GB of NVMe, and DDoS protection shields it from bots and attacks. Here are plans that meet these requirements.

> Source: https://accsly.io/en/vps/for-website · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 7,331, hosts: 700
- Price: from 1.19 $, a quarter below 18.00 $, median 39.99 $
- NVMe: 100 %, unlimited traffic: 38 %, hourly billing: 13 %
- RAM → price from: 1 GB — 1.19 $, 2 GB — 1.19 $, 4 GB — 1.70 $, 8 GB — 4.19 $, 16 GB — 6.66 $
- Countries: USA (2155), Germany (1780), United Kingdom (1229), Netherlands (1181), Singapore (657), India (604)
- Cheapest hosts: [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 1.19 $, [EVL Gaming, LLC](https://accsly.io/en/vps/hosting/evlbox) — 2.08 $, [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 2.17 $, [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) — 2.18 $, [ByteHosting](https://accsly.io/en/vps/hosting/bytehosting) — 2.24 $

## Cheapest plans — 7,331 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-01 | 1 | 2 GB | 40 GB NVMe | DE, FI | PayPal, Invoice | 1.19 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-02 | 2 | 4 GB | 70 GB NVMe | DE, FI | PayPal, Invoice | 1.70 $ |
| [EVL Gaming, LLC](https://accsly.io/en/vps/hosting/evlbox) | General Purpose 2GB | 1 | 2 GB | 25 GB NVMe | US | Visa/MC | 2.08 $ (total when paying for year (25.00 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | ExtraVPS-4096 | 3 × 3.1 GHz | 4 GB | 60 GB NVMe | FI | Visa/MC, PayPal, Crypto | 2.17 $ (total when paying for 3 mo (6.49 $)) |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-1 | 1 × 3.3 GHz | 4 GB | 50 GB NVMe |  | PayPal, Visa/MC, Crypto | 2.18 $ (total when paying for year (26.19 $)) |
| [HostBrr](https://accsly.io/en/vps/hosting/hostbrr) | Value 2GB (Performance VDS / Value Optimized) | 1 × 3.4 GHz | 2 GB | 25 GB NVMe | DE | Visa/MC, PayPal, Crypto | 2.24 $ (when paying for year: 1.87 $/mo) |
| [ByteHosting](https://accsly.io/en/vps/hosting/bytehosting) | Xeon - 4GB | 1 | 4 GB | 30 GB NVMe | DE | PayPal, Crypto | 2.24 $ (total when paying for year (26.87 $)) |
| [Voyar Cloud](https://accsly.io/en/vps/hosting/voyar) | CV-10 | 2 | 2 GB | 40 GB NVMe | TR | Invoice | 2.45 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | CentralVPS-2048 Premier | 2 × 4.8 GHz | 2 GB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 2.50 $ (total when paying for 3 mo (7.49 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | CentralVPS-3072 US | 3 × 3.0 GHz | 3 GB | 40 GB NVMe | US | Visa/MC, PayPal, Crypto | 2.50 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | FullVPS-2048 Plus | 2 | 2 GB | 40 GB NVMe | NL | Visa/MC, PayPal, Crypto | 2.50 $ |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | VPS-1 (Xeon) | 2 | 4 GB | 40 GB NVMe | TR | Invoice | 2.59 $ |
| [FastHosts](https://accsly.io/en/vps/hosting/fasthosts-co) | VPS 1 | 1 | 2 GB | 60 GB NVMe | GB | — | 2.68 $ |
| [Hostlab.com](https://accsly.io/en/vps/hosting/hostlab) | SSD VDS (Paket 2) | 2 | 2 GB | 35 GB NVMe | TR | Visa/MC, Invoice | 2.79 $ (when paying for year: 2.33 $/mo) |
| [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | VPS L-TR 2GB | 1 | 2 GB | 30 GB NVMe | TR | Visa/MC | 2.79 $ (yearly: 2.79 $/mo) |
| [DediRock](https://accsly.io/en/vps/hosting/dedirock) | i9 Dream Core | 1 | 2 GB | 30 GB NVMe | US | PayPal, Visa/MC | 2.92 $ (total when paying for year (34.99 $)) |
| [HostUp](https://accsly.io/en/vps/hosting/hostup) | VPSNano | 1 | 2 GB | 25 GB NVMe | SE | — | 2.96 $ |
| [Rabisu.com](https://accsly.io/en/vps/hosting/rabisu) | Aydın VPS x4 | 2 | 4 GB | 40 GB NVMe | AU, BG, CA, DE, GB, HK… | Visa/MC, PayPal, Crypto, Invoice | 2.99 $ (when paying for year: 2.46 $/mo) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-03 | 3 | 6 GB | 125 GB NVMe | DE, FI | PayPal, Invoice | 2.99 $ |
| [Antihost](https://accsly.io/en/vps/hosting/antihost) | LITE S 1 | 1 | 2 GB | 30 GB NVMe | US, DE | Visa/MC, Invoice | 2.99 $ (when paying for 3 years: 2.54 $/mo) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/for-website?format=json

## What kind of VPS does a website need

Moving from shared hosting to a VPS usually happens for one of three reasons: the site has hit its CPU limits, you need a PHP version or module the hosting doesn't offer, or too many projects have piled up on one account. A virtual server removes these restrictions, but in exchange configuration and updates become your responsibility.

### How many resources to take for a CMS and traffic

Don't go by the number of visitors; go by how many requests actually reach PHP and the database. A rough scale for typical sites:

- **Landing page, business card site, static site** — 1 core and 1 GB RAM. Serving HTML through nginx costs almost nothing.
- **Blog or company website on a CMS** with caching, up to several thousand visitors a day — 1–2 cores and 2 GB. For the most popular engine there's a separate selection, [VPS for WordPress](https://accsly.io/en/vps/for-wordpress).
- **Online store** with a catalogue, filters and a cart — 2 cores and 4 GB or more. You can't fully cache the cart and customer accounts, so the load on the database is noticeably higher.
- **Several sites on one server** — add up their needs and add 30–50 % headroom: at peak hours the projects load the server at the same time.

Memory almost always runs out before the CPU does. Once the server starts swapping, the site slows down more than it would from a lack of cores.

### SSD or NVMe

There's no point in taking an HDD for a website today: the database does lots of small random reads, and a slow disk becomes the main bottleneck. A regular SSD is enough for most projects. NVMe gives a noticeable gain on large databases, stores with thousands of products and frequent backups. Work out the size like this: site files, database, logs and two or three local backups, plus room for system updates. 20 GB is enough for a small site; a store with product photos needs more. You can compare disks on the [NVMe VPS](https://accsly.io/en/vps/nvme) page.

### Control panel or console

If you're not ready to configure nginx, PHP-FPM, the database and SSL certificates by hand, install a panel. It takes care of virtual hosts, mailboxes, backups and certificate issuance. Keep two things in mind: some panels are paid, and the panel itself eats 300–500 MB of memory. On a 1 GB server that's significant, so with a panel it's better to take 2 GB or more. One option is a [VPS with ISPmanager](https://accsly.io/en/vps/ispmanager); free alternatives include FASTPANEL, aaPanel and HestiaCP.

Without a panel the server is lighter and more secure, but every change has to be made in the console, and you have to keep track of updates yourself.

### Where to put the server

Place the server close to your audience. For a European audience, Germany or the Netherlands are a good fit; for an American one, the USA. Also check whether local data-protection rules require you to store your visitors' personal data in a particular country. A CDN partly smooths out the distance for static files, but dynamic pages are still generated on the server.

The plans in the table above are sorted by price, and the "Payment" column shows how you can pay each host.

## FAQ

### Why is a VPS better for a website than regular hosting?

On a VPS the resources are reserved for you, and you can install any PHP versions, modules and services. The downside is that administration, updates and security fall on you or on an administrator you hire.

### How many websites can I host on one VPS?

There are no technical limits; it all comes down to memory and disk. A server with 2 GB of RAM usually runs 5–10 small cached sites without trouble.

### Do I need a control panel on a VPS for a website?

Not necessarily, but without one you'll have to configure the web server, PHP, database and SSL by hand. A panel makes life easier, but it uses part of the memory and sometimes costs money.

### How do I install an SSL certificate on a VPS?

A free Let’s Encrypt certificate is issued with the certbot utility or through the control panel and renews automatically. The only requirement is that the domain already points to the server's IP.

### What should I do if my site on a VPS has become slow?

First check whether there's enough memory and whether the server is swapping, then look at slow database queries. Page caching often helps, and only after that is it worth upgrading the plan.

### Can I move a site to a VPS without downtime?

Yes: deploy a copy on the new server, test it via the hosts file, then sync the database and switch DNS. Lower the record's TTL in advance so the switch happens faster.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS for a Telegram bot

A Python or Node.js bot runs fine on 1 GB of RAM, and hourly billing lets you start and stop the server without paying for a full month. Here: plans with 1 GB+ and hourly billing under 6 $ a month.

> Source: https://accsly.io/en/vps/for-telegram-bot · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 95, hosts: 48
- Price: from 0.49 $, a quarter below 3.36 $, median 5.00 $
- NVMe: 56 %, unlimited traffic: 14 %, hourly billing: 100 %
- RAM → price from: 1 GB — 0.49 $, 2 GB — 1.71 $, 4 GB — 2.17 $
- Countries: Netherlands (55), USA (50), Germany (40), United Kingdom (29), Singapore (23), Poland (20)
- Cheapest hosts: [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 1.33 $, [3HCloud](https://accsly.io/en/vps/hosting/3hcloud) — 1.50 $, [HostVDS](https://accsly.io/en/vps/hosting/hostvds) — 1.67 $, [DataPasa](https://accsly.io/en/vps/hosting/datapasa) — 1.99 $, [Aeza](https://accsly.io/en/vps/hosting/aeza) — 2.23 $

## Cheapest plans — 95 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | STARDUST1-S | 1 × 2.1 GHz | 1 GB | — | FR, NL, PL | — | 0.49 $ |
| [TierHive](https://accsly.io/en/vps/hosting/tierhive) | Калькулятор (конфигурация по умолчанию) | 1 | 1 GB | 20 GB NVMe | NL, CA, DE, FR, US, GB… | — | 1.01 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | CentralVPS-1536 | 2 × 3.1 GHz | 1.5 GB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 1.33 $ (total when paying for 3 mo (3.99 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | FullVPS-1024 Essential | 1 | 1 GB | 30 GB NVMe | NL | Visa/MC, PayPal, Crypto | 1.43 $ (total when paying for 3 mo (4.29 $)) |
| [3HCloud](https://accsly.io/en/vps/hosting/3hcloud) | 1 GB 1 vCPU Shared Pool | 1 | 1 GB | — | PL, US, PH | Visa/MC | 1.50 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-1024 Premier | 1 × 4.8 GHz | 1 GB | 15 GB NVMe | FI | Visa/MC, PayPal, Crypto | 1.50 $ (total when paying for 3 mo (4.49 $)) |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 1 | 1 | 1 GB | 10 GB NVMe | FR, LV, NL, FI | Visa/MC, Crypto | 1.67 $ |
| [TierHive](https://accsly.io/en/vps/hosting/tierhive) | STANDARD | 1 | 2 GB | 25 GB NVMe | NL, CA, DE, FR, US, GB… | — | 1.71 $ |
| [DataPasa](https://accsly.io/en/vps/hosting/datapasa) | VPS-1 | 1 | 1 GB | 16 GB NVMe | DE | Visa/MC, PayPal, Crypto | 1.99 $ |
| [RamNode](https://accsly.io/en/vps/hosting/ramnode) | Lite VPS 1GB (IPv6 only) | 1 | 1 GB | 15 GB NVMe | US, NL | PayPal, Visa/MC, Crypto | 2.00 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | ExtraVPS-4096 | 3 × 3.1 GHz | 4 GB | 60 GB NVMe | FI | Visa/MC, PayPal, Crypto | 2.17 $ (total when paying for 3 mo (6.49 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | JumboDisk 500GB CorePlus | 2 × 3.0 GHz | 1 GB | 510 GB HDD | DE | Visa/MC, PayPal, Crypto | 2.19 $ |
| [Aeza](https://accsly.io/en/vps/hosting/aeza) | SWE-PROMO | 1 | 4 GB | 10 GB NVMe | SE | Visa/MC | 2.23 $ |
| [Tiktalik.com](https://accsly.io/en/vps/hosting/tiktalik) | Tiktalik VPS Standard (1 GB) | 2 | 1 GB | 20 GB HDD | PL | Visa/MC, Invoice | 2.42 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | CentralVPS-2048 Premier | 2 × 4.8 GHz | 2 GB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 2.50 $ (total when paying for 3 mo (7.49 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | FullVPS-2048 Plus | 2 | 2 GB | 40 GB NVMe | NL | Visa/MC, PayPal, Crypto | 2.50 $ |
| [RareCloud](https://accsly.io/en/vps/hosting/rarecloud) | KVM VPS Starter | 1 | 1 GB | 25 GB NVMe | US, GB, NL, DE, RO, HK… | Visa/MC, PayPal, Crypto, Invoice | 2.75 $ (total when paying for year (33.06 $)) |
| [HostUp](https://accsly.io/en/vps/hosting/hostup) | VPSNano | 1 | 2 GB | 25 GB NVMe | SE | — | 2.96 $ |
| [3HCloud](https://accsly.io/en/vps/hosting/3hcloud) | 2 GB 1 vCPU Shared Pool | 1 | 2 GB | — | PL, US, PH | Visa/MC | 3.00 $ |
| [RamNode](https://accsly.io/en/vps/hosting/ramnode) | Lite VPS 2GB (IPv6 only) | 1 | 2 GB | 20 GB NVMe | US, NL | PayPal, Visa/MC, Crypto | 3.00 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/for-telegram-bot?format=json

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS for Docker

Docker runs on KVM; for several containers, take at least 2 cores, 2 GB of RAM and 30 GB of NVMe. Plans with the cheapest cores first.

> Source: https://accsly.io/en/vps/for-docker · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 9,982, hosts: 1,083
- Price: from 2.17 $, a quarter below 23.45 $, median 48.69 $
- NVMe: 100 %, unlimited traffic: 35 %, hourly billing: 12 %
- RAM → price from: 1 GB — 2.17 $, 2 GB — 2.17 $, 4 GB — 2.17 $, 8 GB — 4.19 $, 16 GB — 6.66 $
- Countries: USA (2654), Germany (1999), Netherlands (1535), United Kingdom (1391), India (716), Russia (711)
- Cheapest hosts: [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 2.17 $, [Voyar Cloud](https://accsly.io/en/vps/hosting/voyar) — 2.45 $, [BalHost](https://accsly.io/en/vps/hosting/balhost-net) — 2.59 $, [Hostlab.com](https://accsly.io/en/vps/hosting/hostlab) — 2.79 $, [Rabisu.com](https://accsly.io/en/vps/hosting/rabisu) — 2.99 $

## Top plans of the selection (Cheaper per core) — 9,982 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [SpeedHost247.com](https://accsly.io/en/vps/hosting/speedhost247) | Premium VPS | 12 | 48 GB | 250 GB NVMe | GB, SG, IN | — | 7.95 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | ExtraVPS-4096 | 3 × 3.1 GHz | 4 GB | 60 GB NVMe | FI | Visa/MC, PayPal, Crypto | 2.17 $ (total when paying for 3 mo (6.49 $)) |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | VPS-2 (Xeon) | 4 | 6 GB | 60 GB NVMe | TR | Invoice | 2.99 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | CentralVPS-3072 US | 3 × 3.0 GHz | 3 GB | 40 GB NVMe | US | Visa/MC, PayPal, Crypto | 2.50 $ |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | VDS-7 | 8 | 8 GB | 120 GB NVMe | TR | Invoice | 6.78 $ |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | VDS-6 | 6 | 8 GB | 100 GB NVMe | TR | Invoice | 5.68 $ |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | VPS-4 (Xeon) | 6 | 12 GB | 120 GB NVMe | TR | Invoice | 5.68 $ |
| [SpeedHost247.com](https://accsly.io/en/vps/hosting/speedhost247) | Mega Premium VPS | 64 | 125 GB | 650 GB NVMe | GB, SG, IN | — | 65.00 $ |
| [almas.host](https://accsly.io/en/vps/hosting/almas) | VPSx-90 | 24 | 96 GB | 200 GB NVMe | IR | — | 25.05 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | FullVPS-4096 Max | 4 | 4 GB | 50 GB NVMe | NL | Visa/MC, PayPal, Crypto | 4.19 $ |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | VDS-4 | 4 | 6 GB | 65 GB NVMe | TR | Invoice | 4.19 $ |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | VPS-3 (Xeon) | 4 | 8 GB | 80 GB NVMe | TR | Invoice | 4.19 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | ExtraVPS-6144 US | 4 × 3.0 GHz | 6 GB | 40 GB NVMe | US | Visa/MC, PayPal, Crypto | 4.29 $ |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-2 | 4 × 3.3 GHz | 10 GB | 100 GB NVMe |  | PayPal, Visa/MC, Crypto | 4.42 $ (yearly: 4.42 $/mo) |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-3 | 6 × 3.3 GHz | 16 GB | 200 GB NVMe |  | PayPal, Visa/MC, Crypto | 6.66 $ |
| [OrangeVPS](https://accsly.io/en/vps/hosting/orangevps) | SP26-6 | 6 | 8 GB | 80 GB NVMe | US, SG, HK, JP | Visa/MC, PayPal, Crypto, Invoice | 6.88 $ |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | VDS-5 | 4 | 8 GB | 75 GB NVMe | TR | Invoice | 4.79 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | FullVPS-6144 Max Plus | 5 | 6 GB | 50 GB NVMe | NL | Visa/MC, PayPal, Crypto | 5.98 $ |
| [OrangeVPS](https://accsly.io/en/vps/hosting/orangevps) | SP26-4 | 4 | 4 GB | 45 GB NVMe | US, SG, HK, JP | Visa/MC, PayPal, Crypto, Invoice | 4.88 $ |
| [Voyar Cloud](https://accsly.io/en/vps/hosting/voyar) | CV-10 | 2 | 2 GB | 40 GB NVMe | TR | Invoice | 2.45 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/for-docker?format=json

## VPS requirements for Docker

What makes Docker convenient is that the whole project — application, database, queue, reverse proxy — is described in a single `compose.yaml` file and moves from server to server in minutes. But it places demands on the virtual server that an ordinary PHP site doesn't. The table above already lists only the plans that meet them: KVM, 2+ cores, 2 GB of memory and 30 GB on NVMe, with the cheapest per core shown first.

### Virtualization: why KVM

Containers rely on Linux kernel mechanisms: namespaces, cgroups, network bridges, iptables. On KVM a VDS has its own kernel, and Docker installs from the official repository without surprises. On OpenVZ and LXC the kernel is shared with the host machine: Docker either doesn't start at all or works only with special settings from the host, with network restrictions and old versions. It isn't worth spending an evening finding out — go straight for a [KVM VPS](https://accsly.io/en/vps/kvm).

The second point is the storage driver. By default Docker uses overlay2, which needs OverlayFS support in the kernel. Without it, Docker falls back to the vfs driver, which copies every image layer in full: the disk fills up several times faster and builds are slow. You can check the driver with `docker info` right after installation.

### How much memory several containers need

The Docker daemon itself takes about 100 MB. From there, count by what's in your stack:

- Nginx or Caddy — 20–50 MB;
- an application in Python, Node.js or PHP-FPM — 100–300 MB per process;
- PostgreSQL or MySQL — from 200 MB, noticeably more under load;
- Redis — tens of megabytes plus the size of the data.

A typical "proxy + app + database + Redis" stack fits into 1–1.5 GB, so 2 GB is a sensible minimum, and for several projects on one server [4 GB RAM](https://accsly.io/en/vps/4-gb-ram) is better. Set memory limits for containers and add a swap file: without them, one bloated process will take down its neighbours via the OOM killer.

### Disk: space disappears quietly

Images weigh anywhere from tens of megabytes to a gigabyte, and with every update the old versions stay on disk. Container logs are written with no size limit by default. Hence three rules: configure log rotation in `daemon.json` (the `max-size` and `max-file` options), run `docker system prune` periodically, and don't take less than 30 GB. If databases live in your containers, look at [NVMe plans](https://accsly.io/en/vps/nvme) — for random writes the difference from SATA SSD is tangible.

### Network, security and payment

A common trap: ports published with `-p` are opened by Docker bypassing UFW, so firewall rules don't apply to them. Bind internal services to `127.0.0.1` or use compose's internal networks. Pulling images from Docker Hub can at times be slow or restricted, so set up a registry mirror in advance. Payment methods for each plan are in the "Payment" column; prices are shown in your currency and updated from the hosts' websites.

## FAQ

### Can I run Docker on OpenVZ?

On old OpenVZ 6 — no; on OpenVZ 7 and LXC only if the host supports it, and with limitations. KVM, where the server has its own kernel, is the most reliable choice for Docker.

### Is 1 GB of memory enough for Docker?

For one or two lightweight containers without a database — yes, especially with a swap file. A stack with PostgreSQL and Redis runs comfortably from 2 GB.

### Why does Docker eat disk space so fast?

Old images, stopped containers, build cache and unrotated logs pile up. docker system prune and a log size limit in daemon.json help.

### Why doesn't UFW block a container's port?

Docker adds its own iptables rules for published ports, and they fire before UFW's rules. Publish the port only on 127.0.0.1 or put the service behind a reverse proxy.

### Which is better for Docker: Ubuntu or Debian?

Both are officially supported by Docker and work equally well. Pick the one you're used to; what matters is a current release with a kernel that supports overlay2.

### Do I need Kubernetes on a single VPS?

Usually not: for one server Docker Compose is simpler and uses fewer resources. If you need orchestration, small machines use lightweight distributions like k3s, but they need 2 GB of memory or more.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS for a game server

Minecraft, CS2 and other game servers need fast cores: 3 GHz+, 4 GB+ of RAM and NVMe. Fastest first.

> Source: https://accsly.io/en/vps/for-game-server · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 1,797, hosts: 172
- Price: from 2.17 $, a quarter below 27.87 $, median 54.17 $
- NVMe: 100 %, unlimited traffic: 38 %, hourly billing: 13 %
- RAM → price from: 1 GB — 2.17 $, 2 GB — 2.17 $, 4 GB — 2.17 $, 8 GB — 4.42 $, 16 GB — 6.66 $
- Countries: Germany (325), Russia (255), Netherlands (230), USA (203), United Kingdom (130), Poland (101)
- Cheapest hosts: [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 2.17 $, [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) — 2.18 $, [ServerCheap](https://accsly.io/en/vps/hosting/servercheap) — 3.00 $, [myPrepaid-Server](https://accsly.io/en/vps/hosting/myprepaid-server) — 4.47 $, [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) — 4.60 $

## Top plans of the selection (Faster core) — 1,797 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [QCKL Network Solutions](https://accsly.io/en/vps/hosting/qckl) | HiCPU VDS — Hyperion | 2 × 6.0 GHz | 4 GB | 60 GB NVMe | NL, DE | Crypto, Invoice | 30.21 $ (when paying for year: 27.69 $/mo) |
| [QCKL Network Solutions](https://accsly.io/en/vps/hosting/qckl) | HiCPU VDS — Hyperion (Москва) | 2 × 6.0 GHz | 4 GB | 60 GB NVMe | RU | Crypto, Invoice | 39.27 $ |
| [QCKL Network Solutions](https://accsly.io/en/vps/hosting/qckl) | HiCPU VDS — Supernova | 4 × 6.0 GHz | 8 GB | 120 GB NVMe | NL, DE | Crypto, Invoice | 50.36 $ (when paying for year: 41.96 $/mo) |
| [QCKL Network Solutions](https://accsly.io/en/vps/hosting/qckl) | HiCPU VDS — Supernova (Москва) | 4 × 6.0 GHz | 8 GB | 120 GB NVMe | RU | Crypto, Invoice | 65.46 $ |
| [QCKL Network Solutions](https://accsly.io/en/vps/hosting/qckl) | HiCPU VDS — UltraForce | 8 × 6.0 GHz | 16 GB | 240 GB NVMe | NL, DE | Crypto, Invoice | 89.54 $ (when paying for year: 74.61 $/mo) |
| [QCKL Network Solutions](https://accsly.io/en/vps/hosting/qckl) | HiCPU VDS — UltraForce (Москва) | 8 × 6.0 GHz | 16 GB | 240 GB NVMe | RU | Crypto, Invoice | 116 $ |
| [BoxToPlay](https://accsly.io/en/vps/hosting/boxtoplay) | VPS Server | 2 × 5.7 GHz | 4 GB | 40 GB NVMe |  | Visa/MC, PayPal | 6.25 $ |
| [dashserv](https://accsly.io/en/vps/hosting/dashserv) | Ryzen-FFM Starter | 2 × 5.7 GHz | 4 GB | 60 GB NVMe | DE | PayPal, Invoice | 8.90 $ |
| [Alpenhost e.U.](https://accsly.io/en/vps/hosting/alpenhost) | Ryzen Shared Micro | 2 × 5.7 GHz | 4 GB | 40 GB NVMe | AT, NL | Invoice, PayPal | 11.07 $ |
| [VPSLab](https://accsly.io/en/vps/hosting/vpslab) | R9 Start | 2 × 5.7 GHz | 6 GB | 30 GB NVMe | NL, DE | Crypto, PayPal, Visa/MC | 11.18 $ |
| [LIGA HOSTING](https://accsly.io/en/vps/hosting/ligahosting) | VPS Performance S | 2 × 5.7 GHz | 4 GB | 200 GB NVMe | DE | Visa/MC, PayPal, Crypto | 11.19 $ |
| [Spacecore.pro](https://accsly.io/en/vps/hosting/spacecore) | NL U20 | 2 × 5.7 GHz | 4 GB | 75 GB NVMe | NL | Crypto, Visa/MC, PayPal | 11.73 $ (total when paying for year (141 $)) |
| [Chicagoservers](https://accsly.io/en/vps/hosting/chicagoservers) | Amsterdam-Enterprise | 2 × 5.7 GHz | 4 GB | 200 GB NVMe | NL | Visa/MC, Crypto | 13.00 $ |
| [Chicagoservers](https://accsly.io/en/vps/hosting/chicagoservers) | Chicago-Enterprise | 2 × 5.7 GHz | 4 GB | 200 GB NVMe | US | Visa/MC, Crypto | 13.00 $ |
| [Chicagoservers](https://accsly.io/en/vps/hosting/chicagoservers) | Dallas-Enterprise | 2 × 5.7 GHz | 4 GB | 200 GB NVMe | US | Visa/MC, Crypto | 13.00 $ |
| [Chicagoservers](https://accsly.io/en/vps/hosting/chicagoservers) | Los Angeles-Enterprise | 2 × 5.7 GHz | 4 GB | 200 GB NVMe | US | Visa/MC, Crypto | 13.00 $ |
| [Chicagoservers](https://accsly.io/en/vps/hosting/chicagoservers) | Miami-Enterprise | 2 × 5.7 GHz | 4 GB | 200 GB NVMe | US | Visa/MC, Crypto | 13.00 $ |
| [Spacecore.pro](https://accsly.io/en/vps/hosting/spacecore) | DE U20 | 2 × 5.7 GHz | 4 GB | 75 GB NVMe | DE | Crypto, Visa/MC, PayPal | 13.33 $ |
| [Sebek Sp z o.o.](https://accsly.io/en/vps/hosting/sebekvps) | 7950X-4G | 1 × 5.7 GHz | 4 GB | 60 GB NVMe | DE | Visa/MC, PayPal | 13.43 $ (when paying for year: 12.09 $/mo) |
| [Senko Digital](https://accsly.io/en/vps/hosting/senko-digital) | DE-RZ9-2 | 2 × 5.7 GHz | 4 GB | 80 GB NVMe | DE | Visa/MC, PayPal, Invoice, Crypto | 14.43 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/for-game-server?format=json

## VPS for a game server: what to look for

A game server loads a machine differently from a website. A site answers requests and then sits idle, while a game recalculates the world dozens of times a second without a break, and any delay is instantly visible to players. That's why four parameters matter for games: CPU clock speed, ping to players, attack protection and a fast disk. By default the table above is sorted by clock speed and shows plans with 3 GHz or more, 4 GB of memory and NVMe.

### CPU

Almost all game engines process the world in one main thread. Sixteen slow cores will lose to four fast ones, so look at the CPU's clock speed and generation, not the number of vCPUs. Plans on [AMD Ryzen](https://accsly.io/en/vps/ryzen) and modern Intel Core perform well. Keep in mind that on cheap plans vCPUs are shared with neighbours: if your game keeps a core busy constantly, look for plans with dedicated cores or a guaranteed CPU share.

### How many resources popular games ask for

The figures are approximate and depend on the number of players, mods and map size:

- **SA-MP, CRMP, MTA, Terraria** — 1–2 GB of memory, one or two cores.
- **Valheim, Garry's Mod, Don't Starve Together** — 2–4 GB, two cores.
- **Project Zomboid, Minecraft with plugins** — 4–8 GB; more about blocks on the [VPS for Minecraft](https://accsly.io/en/vps/for-minecraft) page.
- **Rust, Palworld** — 8–16 GB and the fastest CPU you're willing to pay for.
- **ARK: Survival Ascended** — 12–16 GB or more; the dedicated server is officially released for Windows only.

Most Steam servers are installed through SteamCMD and run perfectly on Linux, which wastes no resources on a graphical shell and needs no licence. Take Windows only if the game won't run without it.

### Ping to players

Put the server where most of your players live. Within one country or region, ping is usually 10–60 ms. A server in Germany or the Netherlands suits a mixed audience spread across Europe. Another continent is almost always too far for players. Before paying, ping the host's test IP from different cities.

### DDoS and disk

Public game servers get attacked regularly — sometimes simply by sore losers. Games run over UDP, and ordinary web protection won't save them: you need network-level filtering that understands game traffic. Look for such plans in the [VPS with DDoS protection](https://accsly.io/en/vps/ddos-protection) section and ask the host whether the game ports specifically are protected.

NVMe isn't needed for FPS but for map loading, saves and restarts: a large Rust or ARK world takes minutes to come up from a slow disk. Copy your saves to another server regularly.

Prices in the table are shown in your currency, and payment methods are listed for each plan — hosts vary widely in which cards, wallets and cryptocurrencies they accept.

## FAQ

### Which is better for a game server: a VPS or a dedicated server?

A VPS with a fast CPU is enough for a small community. A dedicated server is needed when a Rust or ARK server for dozens of players runs out of resources, or when you host several games at once.

### How many cores does a game server need?

Two to four fast cores are usually enough, because the game mostly loads one. More cores are needed if there are several servers on the machine or heavy modpacks.

### Can I run a game server on Linux?

Yes, most Steam dedicated servers are released for Linux and installed through SteamCMD. There are exceptions: ARK: Survival Ascended, for example, officially supports only Windows.

### Where should I host a game server?

As close as possible to where most of your players are. For a mixed audience across Europe, Germany, the Netherlands or Finland are good choices.

### Does ordinary anti-DDoS protection protect a game server?

Not always: protection designed for websites filters HTTP, while games run over UDP. Ask the host whether there is filtering for game traffic.

### Why does a game lag on a cheap VPS when the load is low?

On inexpensive plans the CPU is shared with neighbours, and at peak hours your server gets fewer cycles. Plans with dedicated cores or a more powerful CPU help.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# Windows VPS/VDS

Plans where you can install Windows Server — for RDP, 1C and Windows software. Turn on “Windows included” to see plans with the license already paid for.

> Source: https://accsly.io/en/vps/windows · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 16,082, hosts: 1,243
- Price: from 0.80 $, a quarter below 22.37 $, median 48.44 $
- NVMe: 46 %, unlimited traffic: 34 %, hourly billing: 14 %
- RAM → price from: 1 GB — 0.80 $, 2 GB — 0.80 $, 4 GB — 1.60 $, 8 GB — 3.19 $, 16 GB — 3.46 $
- Countries: USA (4406), Germany (3204), Netherlands (2729), United Kingdom (2456), Singapore (1753), India (1353)
- Cheapest hosts: [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 0.80 $, [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) — 1.33 $, [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 2.17 $, [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) — 2.18 $, [Aeza](https://accsly.io/en/vps/hosting/aeza) — 2.23 $

## Cheapest plans — 16,082 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS1 Fransa | 1 × 4.0 GHz | 2 GB | 15 GB SSD | FR | PayPal, Invoice | 0.80 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS3 Türkiye | 2 × 3.4 GHz | 2 GB | 25 GB SSD | TR | PayPal, Invoice | 0.90 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-01 | 1 | 2 GB | 40 GB NVMe | DE, FI | PayPal, Invoice | 1.19 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS4 Türkiye | 3 × 3.4 GHz | 2 GB | 30 GB SSD | TR | PayPal, Invoice | 1.20 $ |
| [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) | Старт0 SSD 2026 | 1 | 2 GB | 10 GB SSD | RU | Invoice, MIR, SBP, YooMoney | 1.33 $ (when paying for 2 years: 1.00 $/mo) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS2 Fransa | 1 × 4.0 GHz | 4 GB | 25 GB SSD | FR | PayPal, Invoice | 1.60 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-02 | 2 | 4 GB | 70 GB NVMe | DE, FI | PayPal, Invoice | 1.70 $ |
| [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) | Старт1 SSD 2026 | 2 | 3 GB | 15 GB SSD | RU | Invoice, MIR, SBP, YooMoney | 1.94 $ (when paying for 2 years: 1.45 $/mo) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS5 Türkiye | 3 × 4.2 GHz | 3 GB | 45 GB SSD | TR | PayPal, Invoice | 2.00 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | ExtraVPS-4096 | 3 × 3.1 GHz | 4 GB | 60 GB NVMe | FI | Visa/MC, PayPal, Crypto | 2.17 $ (total when paying for 3 mo (6.49 $)) |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-1 | 1 × 3.3 GHz | 4 GB | 50 GB NVMe |  | PayPal, Visa/MC, Crypto | 2.18 $ (total when paying for year (26.19 $)) |
| [Server Hosh](https://accsly.io/en/vps/hosting/serverhosh) | 10yrs Special Package | 4 | 10 GB | 100 GB SSD | US | Visa/MC, PayPal, Crypto, Invoice | 2.20 $ (total when paying for 10 years (265 $)) |
| [Aeza](https://accsly.io/en/vps/hosting/aeza) | SWE-PROMO | 1 | 4 GB | 10 GB NVMe | SE | Visa/MC | 2.23 $ |
| [HostBrr](https://accsly.io/en/vps/hosting/hostbrr) | Value 2GB (Performance VDS / Value Optimized) | 1 × 3.4 GHz | 2 GB | 25 GB NVMe | DE | Visa/MC, PayPal, Crypto | 2.24 $ (when paying for year: 1.87 $/mo) |
| [ByteHosting](https://accsly.io/en/vps/hosting/bytehosting) | Xeon - 4GB | 1 | 4 GB | 30 GB NVMe | DE | PayPal, Crypto | 2.24 $ (total when paying for year (26.87 $)) |
| [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) | Power0 NVMe 2026 | 1 × 3.2 GHz | 2 GB | 20 GB NVMe | RU | Invoice, MIR, SBP, YooMoney | 2.30 $ (when paying for 2 years: 1.84 $/mo) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS3 Fransa | 2 × 4.0 GHz | 6 GB | 35 GB SSD | FR | PayPal, Invoice | 2.39 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS6 Türkiye | 4 × 4.2 GHz | 4 GB | 50 GB SSD | TR | PayPal, Invoice | 2.40 $ |
| [Voyar Cloud](https://accsly.io/en/vps/hosting/voyar) | CV-10 | 2 | 2 GB | 40 GB NVMe | TR | Invoice | 2.45 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | CentralVPS-2048 Premier | 2 × 4.8 GHz | 2 GB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 2.50 $ (total when paying for 3 mo (7.49 $)) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/windows?format=json

## Windows VPS: versions, licences and resources

People choose Windows on a virtual server not out of love for the system, but because the task can't be done without it: the program exists only for Windows, a familiar graphical interface is needed, or the server has to become part of an Active Directory infrastructure. In every other case Linux will be cheaper and need fewer resources.

### Which Windows Server version to choose

Hosts usually offer several editions, and the difference between them is more than cosmetic:

- **Windows Server 2016** — Microsoft's extended support ends in January 2027. It only makes sense for old software that won't run on newer versions.
- **Windows Server 2019** — a proven option for accounting software and trading terminals, supported until January 2029.
- **[Windows Server 2022](https://accsly.io/en/vps/windows-server-2022)** — a sensible default: supported until October 2031, with modern TLS and protocol stack.
- **Windows Server 2025** — the newest version with the longest support, but its resource requirements are higher, and compatibility with older programs is worth checking in advance.

Desktop Windows 10 and 11 also turn up on VPS plans. Keep in mind that Microsoft's licensing terms for hosting providers are designed for server versions, so legally, client Windows on a rented server is not so clear-cut.

### Licence: what's included in the plan

Windows is paid software, and the host pays Microsoft for every machine, so the same server almost always costs more with Windows than with Linux. Some hosts include the licence in the plan price, others add it as an option when you order. When comparing plans, look at the total cost with the licence. A separate expense is RDS CAL client licences: without them only two administrators can connect to the server at the same time. More on multi-user work is on the [RDP server](https://accsly.io/en/vps/rdp) page.

### Resources: Windows is hungrier than Linux

A Linux server without a GUI runs on 512 MB of memory. Windows Server with the desktop takes about 1.5–2 GB right after boot, plus background updates, antivirus and indexing. Practical guidelines:

- 2 GB RAM — the absolute minimum for one lightweight program; it will be cramped;
- 4 GB — comfortable for one user and a couple of always-running applications;
- 8 GB or more — for several users, accounting systems or SQL Server.

Plan for a disk of 40–50 GB or more: the system itself with accumulated updates takes 20–30 GB. Server Core mode without the graphical shell saves memory, but it suits only those who administer the server through PowerShell.

### What people use a Windows VPS for

- a remote workstation with programs running around the clock;
- MetaTrader and QUIK trading terminals — there's a dedicated selection, [VPS for Forex](https://accsly.io/en/vps/for-forex);
- accounting and business management systems;
- applications on .NET Framework, IIS and MS SQL;
- automation programs and software that needs a desktop.

If your budget is tight, start with the selection of [cheap Windows VPS](https://accsly.io/en/vps/cheap-windows). Prices are shown in your currency everywhere, and the "Payment" column shows whether the host accepts cards, PayPal or cryptocurrency.

## FAQ

### Why is a Windows VPS more expensive than a Linux one?

The host pays Microsoft for the Windows Server licence and includes that amount in the plan. On top of that, Windows needs more memory and disk, so the minimum workable configuration is more expensive in itself.

### Which Windows Server version is best for a VPS?

For new tasks, Windows Server 2022 or 2025: they have the longest support. Windows Server 2016 is worth taking only for old programs; its support ends in January 2027.

### How much RAM does Windows Server need?

At least 2 GB to work with the graphical interface, 4 GB or more to be comfortable. For several users, accounting systems or SQL Server take 8 GB or more.

### Can I install my own Windows on a VPS?

Technically yes, if the host lets you attach an ISO image. Legally, you can't always use your own licence on someone else's hardware — it depends on its terms — so it's easier to take a plan with the licence already included.

### How do I connect to a Windows VPS?

Through Remote Desktop Connection (mstsc) in Windows or Microsoft's client for macOS, iOS and Android. The host sends the IP address, administrator login and password once the server is activated.

### Do I need an antivirus on a Windows VPS?

The built-in Microsoft Defender is enough for most tasks. It's more important to close RDP to outsiders, install updates regularly and not run unverified software on the server.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS for a proxy server

For 3proxy or Squid: IPv6 addresses for a large pool of outgoing IPs and unlimited traffic.

> Source: https://accsly.io/en/vps/for-proxy · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 4,077, hosts: 305
- Price: from 0.49 $, a quarter below 16.54 $, median 37.52 $
- NVMe: 49 %, unlimited traffic: 100 %, hourly billing: 13 %
- RAM → price from: 1 GB — 0.49 $, 2 GB — 2.60 $, 4 GB — 2.99 $, 8 GB — 4.59 $, 16 GB — 8.40 $
- Countries: USA (845), Netherlands (721), Germany (641), France (451), Russia (379), United Kingdom (371)
- Cheapest hosts: [Inoventica](https://accsly.io/en/vps/hosting/invs) — 1.20 $, [VDS4YOU](https://accsly.io/en/vps/hosting/vds4you) — 2.17 $, [NLCloud](https://accsly.io/en/vps/hosting/nordlights) — 2.30 $, [Time-Host](https://accsly.io/en/vps/hosting/time-host) — 2.41 $, [Relevate](https://accsly.io/en/vps/hosting/relevate) — 2.42 $

## Cheapest plans — 4,077 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | STARDUST1-S | 1 × 2.1 GHz | 1 GB | — | FR, NL, PL | — | 0.49 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Pico | 1 | 128 MB | 5 GB SSD | US | Crypto | 0.50 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Nano | 1 | 256 MB | 10 GB SSD | US | Crypto | 1.00 $ |
| [Host Media Ltd](https://accsly.io/en/vps/hosting/hostmedia) | Developer VPS 512MB IPv6-only | 1 | 512 MB | 10 GB SSD | GB | Visa/MC | 1.01 $ (total when paying for year (12.07 $)) |
| [ReconV](https://accsly.io/en/vps/hosting/reconv) | LXC 512 MB | 1 | 512 MB | 6 GB NVMe | PL, FR | PayPal | 1.02 $ |
| [myPrepaid-Server](https://accsly.io/en/vps/hosting/myprepaid-server) | 1 Euro Server | 1 × 3.5 GHz | 512 MB | 20 GB NVMe | DE | Visa/MC, PayPal, Invoice | 1.12 $ |
| [myPrepaid-Server](https://accsly.io/en/vps/hosting/myprepaid-server) | ONLY IPv6 | 1 | 512 MB | 15 GB SSD | DE | Visa/MC, PayPal, Invoice | 1.12 $ |
| [eServer RU](https://accsly.io/en/vps/hosting/eserver-ru) | KVM VPS Econom Bronze-1 | 1 | 512 MB | 10 GB SSD | RU | WebMoney, MIR, Crypto, Invoice | 1.20 $ (when paying for year: 1.00 $/mo) |
| [Inoventica](https://accsly.io/en/vps/hosting/invs) | LUNA PROMO | 1 | 1 GB | 20 GB SSD | RU | YooMoney | 1.20 $ |
| [VDS4YOU](https://accsly.io/en/vps/hosting/vds4you) | Гибрид VDS MINI | 1 | 512 MB | 20 GB HDD | RU | MIR, Visa/MC, WebMoney, YooMoney, PayPal, Invoice, Crypto | 1.20 $ |
| [WebHosting24](https://accsly.io/en/vps/hosting/webhosting24) | Munich NVMe KVM 512MB | 1 × 2.4 GHz | 512 MB | 10 GB NVMe | DE | Visa/MC, PayPal, Crypto, Invoice | 1.39 $ (total when paying for year (16.79 $)) |
| [Time-Host](https://accsly.io/en/vps/hosting/time-host) | KVM-MINI-NVMe | 1 | 768 MB | 7 GB NVMe |  | — | 1.68 $ |
| [Sprintbox](https://accsly.io/en/vps/hosting/sprintbox) | Студент | 1 | 600 MB | 7 GB NVMe | RU, NL, DE, US, BY, AM… | — | 1.70 $ |
| [Hostmaze](https://accsly.io/en/vps/hosting/hostmaze) | KVM SSD 2C/256MB | 2 | 256 MB | 15 GB SSD | RO | PayPal, Visa/MC, Crypto | 1.87 $ (total when paying for year (22.39 $)) |
| [JustHost RU](https://accsly.io/en/vps/hosting/just) | VPS Promo | 1 | 512 MB | 5 GB NVMe |  | Visa/MC, MIR, YooMoney, WebMoney, Invoice | 1.99 $ |
| [Microtronix ESolutions, LLC](https://accsly.io/en/vps/hosting/microtronixdc) | 512MB KVM | 2 | 512 MB | 20 GB SSD | US | Visa/MC, Crypto | 2.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Micro | 1 | 512 MB | 20 GB SSD | US | Crypto | 2.00 $ |
| [BuyVM](https://accsly.io/en/vps/hosting/buyvm) | SLICE 512 | 1 × 3.5 GHz | 512 MB | 10 GB SSD | US, LU | — | 2.00 $ (total when paying for year (24.00 $)) |
| [Host Media Ltd](https://accsly.io/en/vps/hosting/hostmedia) | Developer VPS 512MB | 1 | 512 MB | 10 GB SSD | GB | Visa/MC | 2.01 $ (total when paying for year (24.13 $)) |
| [Host Media Ltd](https://accsly.io/en/vps/hosting/hostmedia) | VPS 512MB IPv6-only | 1 | 512 MB | 15 GB SSD | GB | Visa/MC | 2.01 $ (total when paying for year (24.13 $)) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/for-proxy?format=json

## How to set up your own proxy server on a VPS

Your own proxy on a rented VPS means IP addresses used by you alone. There's no need to guess what was done with a purchased proxy before you, or to pay for every gigabyte. In exchange you'll have to set up the server yourself and make sure it isn't misused: the host will hold you responsible for everything that comes from your IP.

### Which software to choose

- **3proxy** — a lightweight server that provides HTTP and SOCKS5 proxies in one program. Convenient when you have many ports and addresses: the configuration is easy to generate with a script.
- **Squid** — a classic HTTP proxy with flexible access rules and caching. Good for an office or a team that needs lists of allowed sites.
- **Dante** — a dedicated SOCKS5 server, if that's the only protocol you need.

Be sure to enable login and password authentication or an IP allowlist. Scanners find an open proxy within hours, it starts being used to send spam, and the address ends up on blacklists.

### Many addresses via IPv6

An extra IPv4 costs money and is issued one at a time. IPv6 is different: many hosts give a server a /64 subnet, which is more addresses than you'll ever use. Addresses from the subnet are added to the interface, and 3proxy assigns each port its own outgoing address. That gives you hundreds of exit IPs on one server. More about the protocol on the [IPv6 VPS](https://accsly.io/en/vps/ipv6) page.

This approach has two honest limitations. First, it only works with sites that support IPv6, and far from all of them do. Second, large services often apply limits to the whole /64 subnet, so a hundred addresses from it look like one user to them. If you need truly different addresses, take several IPv4 addresses or several servers.

### Resources and traffic

The proxy itself barely loads the server: one core and 1 GB of memory handle hundreds of simultaneous connections. The bottleneck is bandwidth. Every byte through a proxy passes twice, in and out, so a traffic cap gets used up fast. The table above is already filtered to plans with IPv6 and unlimited traffic; also check the port speed and fair-use terms. For heavy data collection the [VPS for scraping](https://accsly.io/en/vps/for-parsing) section will be useful, and for high throughput [1 Gbps VPS](https://accsly.io/en/vps/1-gbit).

### Hosts' rules

Before paying, read the acceptable use policy. Almost everywhere, mass mailings, password brute-forcing and scanning other networks are prohibited, and servers get blocked over complaints about your IP. Some hosts specifically prohibit reselling proxies, and many block outgoing port 25 by default. Keep connection logs for at least a few days: they make it easier to deal with a complaint. Payment methods for each plan are shown in the "Payment" column; prices are shown in your currency.

## FAQ

### Why is your own proxy on a VPS better than a purchased one?

The IP addresses belong only to you, their history is known, and traffic usually isn't billed per gigabyte. The downside is that you take on the setup and the responsibility for how the addresses are used.

### Which should I choose: 3proxy or Squid?

3proxy is simpler and lighter, supports SOCKS5 and is convenient for many ports and addresses. Squid is better suited to an HTTP proxy with access rules and caching, for example in an office.

### How many IPv6 addresses can I get on one VPS?

Usually the host allocates a /64 subnet, which has practically unlimited addresses. But many sites apply limits to the whole subnet, so to them it isn't hundreds of different users.

### How much does an extra IPv4 address cost?

Each host sets its own price, usually comparable to the monthly cost of a small plan. Many limit the number of addresses per server.

### Why did my proxy end up on a blacklist?

Most often because it was left open without a password and used for spam. Enable authentication, close unnecessary ports and ask the host for a new address if the old one is already tainted.

### Do I need a powerful server for a proxy?

No, a proxy barely loads the CPU and memory. Port speed, traffic volume and clean IP addresses matter more.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS for web scraping

A scraper needs cores and traffic: at least 2 cores, 2 GB of RAM and unmetered traffic, so you don't pay for every gigabyte downloaded.

> Source: https://accsly.io/en/vps/for-parsing · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 8,142, hosts: 922
- Price: from 0.90 $, a quarter below 22.67 $, median 46.95 $
- NVMe: 47 %, unlimited traffic: 100 %, hourly billing: 10 %
- RAM → price from: 1 GB — 0.90 $, 2 GB — 0.90 $, 4 GB — 2.39 $, 8 GB — 3.19 $, 16 GB — 6.38 $
- Countries: USA (1622), Germany (1177), Netherlands (1036), United Kingdom (748), Russia (708), France (649)
- Cheapest hosts: [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 0.90 $, [Prohoster](https://accsly.io/en/vps/hosting/prohoster) — 2.60 $, [Brnchost internet ve bilişim hizmetleri](https://accsly.io/en/vps/hosting/brnchost) — 2.79 $, [Hostlab.com](https://accsly.io/en/vps/hosting/hostlab) — 2.79 $, [almas.host](https://accsly.io/en/vps/hosting/almas) — 2.88 $

## Top plans of the selection (Cheaper per core) — 8,142 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS4 Türkiye | 3 × 3.4 GHz | 2 GB | 30 GB SSD | TR | PayPal, Invoice | 1.20 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS3 Türkiye | 2 × 3.4 GHz | 2 GB | 25 GB SSD | TR | PayPal, Invoice | 0.90 $ |
| [Server Hosh](https://accsly.io/en/vps/hosting/serverhosh) | 10yrs Special Package | 4 | 10 GB | 100 GB SSD | US | Visa/MC, PayPal, Crypto, Invoice | 2.20 $ (total when paying for 10 years (265 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS6 Türkiye | 4 × 4.2 GHz | 4 GB | 50 GB SSD | TR | PayPal, Invoice | 2.40 $ |
| [SpeedHost247.com](https://accsly.io/en/vps/hosting/speedhost247) | Premium VPS | 12 | 48 GB | 250 GB NVMe | GB, SG, IN | — | 7.95 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS5 Türkiye | 3 × 4.2 GHz | 3 GB | 45 GB SSD | TR | PayPal, Invoice | 2.00 $ |
| [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | VDS L-TR 4GB | 4 | 4 GB | 40 GB NVMe | TR | Visa/MC | 3.49 $ |
| [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | VPS L-TR 8GB | 6 | 8 GB | 60 GB NVMe | TR | Visa/MC | 5.78 $ (yearly: 5.78 $/mo) |
| [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | VPS L-TR 12GB | 8 | 12 GB | 80 GB NVMe | TR | Visa/MC | 7.78 $ (yearly: 7.78 $/mo) |
| [SpeedHost247.com](https://accsly.io/en/vps/hosting/speedhost247) | Mega Premium VPS | 64 | 125 GB | 650 GB NVMe | GB, SG, IN | — | 65.00 $ |
| [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | VPS L-TR 13GB | 8 | 13 GB | 85 GB NVMe | TR | Visa/MC | 8.27 $ (yearly: 8.28 $/mo) |
| [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | VPS L-TR 9GB | 6 | 9 GB | 65 GB NVMe | TR | Visa/MC | 6.29 $ (yearly: 6.28 $/mo) |
| [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | VDS L-TR 6GB | 4 | 6 GB | 50 GB NVMe | TR | Visa/MC | 4.29 $ |
| [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | VPS L-TR 14GB | 8 | 14 GB | 90 GB NVMe | TR | Visa/MC | 8.77 $ (yearly: 8.77 $/mo) |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-2 | 4 × 3.3 GHz | 10 GB | 100 GB NVMe |  | PayPal, Visa/MC, Crypto | 4.42 $ (yearly: 4.42 $/mo) |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-3 | 6 × 3.3 GHz | 16 GB | 200 GB NVMe |  | PayPal, Visa/MC, Crypto | 6.66 $ |
| [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | VPS L-TR 10GB | 6 | 10 GB | 70 GB NVMe | TR | Visa/MC | 6.78 $ (yearly: 6.78 $/mo) |
| [Brnchost internet ve bilişim hizmetleri](https://accsly.io/en/vps/hosting/brnchost) | VDS Kirala 4 | 4 | 8 GB | 45 GB SSD | TR | Visa/MC | 4.59 $ |
| [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | VPS L-TR 15GB | 8 | 15 GB | 95 GB NVMe | TR | Visa/MC | 9.28 $ (yearly: 9.27 $/mo) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS3 Fransa | 2 × 4.0 GHz | 6 GB | 35 GB SSD | FR | PayPal, Invoice | 2.39 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/for-parsing?format=json

## VPS for web scraping: what matters for data collection

A scraper needs a server that runs around the clock, doesn't depend on your home internet connection and doesn't hit a traffic cap. But the right configuration depends heavily on how exactly you collect data. Before renting a VPS, work out which of two types your scraper belongs to.

### HTTP scraper or headless browser

**Scrapers built on direct requests** — Scrapy, aiohttp, httpx, Go clients — download HTML or JSON and parse it. Most of the time they're waiting on the network, so a single core can handle hundreds of concurrent async requests, and 1–2 GB of memory is enough. The CPU load comes from parsing: lxml and regular expressions over thousands of pages a minute will noticeably heat up the CPU. For scripts like these a regular [VPS for Python](https://accsly.io/en/vps/for-python) will do.

**Headless browsers** — Playwright, Puppeteer, Selenium — are needed where content is rendered by JavaScript. Every Chromium tab eats hundreds of megabytes of memory and a sizeable share of a core. Size your resources by the number of concurrent tabs: 2 cores and 4 GB can reasonably run a few, while dozens call for 8–16 GB and a matching number of cores.

When running Chromium in Docker, increase `/dev/shm` (the `--shm-size` option) — with the default 64 MB, tabs crash on heavy pages.

### Traffic and port speed

Scraping is mostly inbound traffic, and its volume is easy to underestimate: a page with images and scripts weighs megabytes, and you fetch hundreds of thousands of them a day. Choose a plan with unmetered traffic — this filter is already applied on this page, and similar plans are collected in the [unmetered traffic VPS](https://accsly.io/en/vps/unlimited-traffic) section. Check the port speed too: "unlimited" at 100 Mbps and at 1 Gbps are very different things. In headless mode, turn off loading of images, fonts and video if you don't need them.

### IP addresses

One server means one IPv4 address, and with active collection sites quickly start rate-limiting it. Hosts charge extra for additional IPv4 addresses and don't always provide them. Many plans include an IPv6 /64 subnet, but you can only use it on sites that accept IPv6 — see the [IPv6 VPS](https://accsly.io/en/vps/ipv6) selection. You can also run your own proxies on your server; see the [VPS for a proxy server](https://accsly.io/en/vps/for-proxy) page.

Pick the location based on your target sites: many sites serve region-specific content, so a server in the same country sees the same pages as local visitors.

### What not to do

1. Don't hammer other people's sites until they go down: keep reasonable delays and follow the site's rules. Site owners send complaints to your host, and the host may shut your server down.
2. Don't collect personal data without a legal basis — that carries separate legal liability.
3. Don't keep results only on the server. Export them to a database or storage and make backups.

Prices in the table above are already shown in your currency, and the "Payment" column shows which methods each host accepts.

## FAQ

### How many scraping threads can a VPS handle?

An async HTTP scraper handles hundreds of concurrent requests on a single core, limited by the network and HTML parsing. With a headless browser you're talking a few tabs per core and hundreds of megabytes of memory for each.

### Do I need unmetered traffic for scraping?

Almost always, yes: the volume of downloaded pages grows fast, and going over the limit costs money or throttles your speed. While you're at it, check the port speed that the unmetered traffic applies to.

### Can I get several IP addresses on a VPS?

Many hosts sell additional IPv4 addresses for an extra fee and in limited numbers. An IPv6 subnet is often free, but not every site accepts it.

### Which OS should I choose for a scraping server?

Usually Linux, such as Ubuntu or Debian: it makes installing Python, Node.js and browsers for Playwright easier. You only need Windows for programs that run exclusively on it.

### Why does Chromium crash on my VPS?

Most often because of insufficient memory or a small /dev/shm in a Docker container. Reduce the number of concurrent tabs, increase shm-size or add memory.

### Can a host block my server for scraping?

Yes, if the server draws complaints about excessive load or if the host's rules prohibit it. Keep your request rate reasonable and read the acceptable use policy before paying.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS for a database

For MySQL, PostgreSQL or Redis: 2 GB of RAM and 40 GB of NVMe or more — a database is limited by memory and disk speed. Plans with the cheapest gigabyte of RAM first.

> Source: https://accsly.io/en/vps/for-database · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 10,642, hosts: 1,121
- Price: from 1.19 $, a quarter below 22.33 $, median 47.49 $
- NVMe: 100 %, unlimited traffic: 35 %, hourly billing: 12 %
- RAM → price from: 1 GB — 1.19 $, 2 GB — 1.19 $, 4 GB — 1.70 $, 8 GB — 4.19 $, 16 GB — 6.66 $
- Countries: USA (2799), Germany (2137), Netherlands (1633), United Kingdom (1515), India (807), Singapore (742)
- Cheapest hosts: [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 1.19 $, [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 2.17 $, [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) — 2.18 $, [Voyar Cloud](https://accsly.io/en/vps/hosting/voyar) — 2.45 $, [BalHost](https://accsly.io/en/vps/hosting/balhost-net) — 2.59 $

## Top plans of the selection (Cheaper per 1 GB RAM) — 10,642 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [SpeedHost247.com](https://accsly.io/en/vps/hosting/speedhost247) | Premium VPS | 12 | 48 GB | 250 GB NVMe | GB, SG, IN | — | 7.95 $ |
| [SSD Nodes](https://accsly.io/en/vps/hosting/ssdnodes) | Performance KVM / 16X-LARGE | 12 | 96 GB | 1920 GB NVMe | US, GB, NL, DE, IN, SG… | — | 23.00 $ (total when paying for 3 years (828 $)) |
| [almas.host](https://accsly.io/en/vps/hosting/almas) | VPSx-90 | 24 | 96 GB | 200 GB NVMe | IR | — | 25.05 $ |
| [SSD Nodes](https://accsly.io/en/vps/hosting/ssdnodes) | Performance KVM / 8X-LARGE | 12 | 64 GB | 1200 GB NVMe | US, GB, NL, DE, IN, SG… | — | 18.00 $ (total when paying for 3 years (648 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-05 | 6 | 24 GB | 500 GB NVMe | DE, FI | PayPal, Invoice | 7.97 $ |
| [almas.host](https://accsly.io/en/vps/hosting/almas) | vpsx-80 | 8 | 32 GB | 145 GB NVMe | IR | — | 10.66 $ |
| [SSD Nodes](https://accsly.io/en/vps/hosting/ssdnodes) | Performance KVM / 4X-LARGE | 12 | 48 GB | 720 GB NVMe | US, GB, NL, DE, IN, SG… | — | 16.41 $ (total when paying for 3 years (591 $)) |
| [Square Brothers](https://accsly.io/en/vps/hosting/squarebrothers) | Power | 8 | 32 GB | 200 GB NVMe | IN | Visa/MC, PayPal | 12.78 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-04 | 4 | 12 GB | 250 GB NVMe | DE, FI | PayPal, Invoice | 4.98 $ |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-3 | 6 × 3.3 GHz | 16 GB | 200 GB NVMe |  | PayPal, Visa/MC, Crypto | 6.66 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-02 | 2 | 4 GB | 70 GB NVMe | DE, FI | PayPal, Invoice | 1.70 $ |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-5 | 12 × 3.3 GHz | 56 GB | 400 GB NVMe |  | PayPal, Visa/MC, Crypto | 24.57 $ |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-2 | 4 × 3.3 GHz | 10 GB | 100 GB NVMe |  | PayPal, Visa/MC, Crypto | 4.42 $ (yearly: 4.42 $/mo) |
| [Smart Host BD](https://accsly.io/en/vps/hosting/smarthostbd) | Streaming RDP - 4 | 6 | 64 GB | 50 GB NVMe |  | Visa/MC, PayPal, Crypto, Invoice | 29.00 $ |
| [BinaryRacks.com](https://accsly.io/en/vps/hosting/binaryracks) | Linux VPS 128 GB | 16 | 128 GB | 800 GB NVMe | GB, EG | Visa/MC, PayPal | 60.32 $ |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | VPS-4 (Xeon) | 6 | 12 GB | 120 GB NVMe | TR | Invoice | 5.68 $ |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-4 | 8 × 3.3 GHz | 28 GB | 300 GB NVMe |  | PayPal, Visa/MC, Crypto | 13.37 $ |
| [ByteHosting](https://accsly.io/en/vps/hosting/bytehosting) | Xeon Gold – 14GB | 3 | 14 GB | 50 GB NVMe | DE | PayPal, Crypto | 6.70 $ |
| [Virtarix (FZC)](https://accsly.io/en/vps/hosting/virtarix) | VPS XXL | 16 | 128 GB | 600 GB NVMe | US, DE, ZA | Visa/MC, PayPal, Crypto | 62.23 $ |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-7 | 24 × 3.3 GHz | 96 GB | 1 TB NVMe |  | PayPal, Visa/MC, Crypto | 46.95 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/for-database?format=json

## How to choose a VPS for a database

A database on your own VPS means a predictable price and full control over the settings: you can install the version you need, enable extensions and set up backups your way. Managed cloud databases are more convenient, but cost several times more for the same amount of memory. If you're prepared to handle updates and backups yourself, a database server pays for itself quickly.

### Memory matters more than cores

Databases keep hot data in RAM: PostgreSQL in `shared_buffers` and the filesystem cache, MySQL and MariaDB in the InnoDB buffer pool, Redis keeps everything there. As long as the working set fits in memory, queries return in milliseconds; once it stops fitting, every query goes to disk and speed drops by an order of magnitude or more. So first estimate the size of your active data and choose memory with headroom:

- **up to 5 GB of data** — a blog, a small shop, a bot backend: [2 GB of RAM](https://accsly.io/en/vps/2-gb-ram) is enough;
- **10–30 GB** — a CRM, an online store with a catalog, analytics: from [4 GB](https://accsly.io/en/vps/4-gb-ram), preferably 8 GB;
- **over 50 GB** or hundreds of queries per second — 16 GB or more and dedicated cores.

Cores are needed for parallel queries and heavy reports. For a typical web workload 2 cores are enough, and the table above is sorted by price per gigabyte of memory by default — the key metric for a database.

### Storage: NVMe only

A database constantly performs small random reads and writes, and the transaction log needs fast synchronous writes. On HDDs and cheap shared SATA SSDs this turns into latency and stalls at every checkpoint. Choose [NVMe plans](https://accsly.io/en/vps/nvme) and plan for three times your current data size: indexes, WAL or binlog files, temporary sort files and local backups take up at least as much as the tables themselves.

### PostgreSQL, MySQL or Redis

- **PostgreSQL** — the all-round choice for new projects: strict transactions, JSON, full-text search, extensions such as PostGIS. More on its requirements on the [VPS for PostgreSQL](https://accsly.io/en/vps/for-postgresql) page.
- **MySQL and MariaDB** — the standard for WordPress, Bitrix and most CMSs; they use less memory at small data sizes. See [VPS for MySQL](https://accsly.io/en/vps/for-mysql).
- **Redis** — caching, queues and sessions; everything is stored in memory, so memory size is what determines the plan. See [VPS for Redis](https://accsly.io/en/vps/for-redis).

### Security and backups

Never expose your database port to the internet: PostgreSQL (5432), MySQL (3306) and Redis (6379) should listen only on `127.0.0.1` or a private network. If the application runs on another server, connect them through WireGuard or an SSH tunnel. Scanners find exposed databases within hours, and ransomware gangs encrypt the data.

A backup on the same server is not a backup. Set up a daily dump (`pg_dump`, `mysqldump`) or continuous log archiving and copy it somewhere else: to object storage or to a [separate backup VPS](https://accsly.io/en/vps/for-backups). Once a month, check that you can actually restore from the copy.

### Where to host it

Put the database in the same data center as the application: every extra 30–50 ms of network latency is multiplied by the number of queries per page. If you store personal data of Russian citizens, Federal Law 152-FZ requires the database to be in Russia — for that there's the [VPS in Russia](https://accsly.io/en/vps/russia) selection.

## FAQ

### How much memory does a database need?

Go by the size of your active data: it should fit in memory together with the indexes. Small projects get by with 2 GB, shops and CRMs need 4–8 GB, and large databases 16 GB or more.

### Can I keep the database and the website on one VPS?

Yes, for small projects that's the usual setup: lower latency and a single bill. It's worth splitting them once the database starts taking memory away from the application or you need separate replication.

### Will a SATA SSD do instead of NVMe?

For a small database with infrequent writes, yes. But NVMe is noticeably faster at small random operations and synchronous log writes, so for a production database NVMe is the better choice.

### Which is better: my own VPS or a managed cloud database?

A managed database takes care of updates and backups, but costs 2–4 times more for the same memory. Your own VPS is better value if you're ready to set up backups and monitoring yourself.

### How do I secure a database on a VPS?

Listen only on localhost or a private network, close the port with a firewall, use strong passwords and keep it updated. Remote access should go through an SSH tunnel or WireGuard.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS for a mail server

Providers where outbound port 25 is open or opened on request — without it, your own mail server (Postfix, Mailcow) can't send email.

> Source: https://accsly.io/en/vps/for-mail-server · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 1,602, hosts: 98
- Price: from 0.90 $, a quarter below 12.31 $, median 29.99 $
- NVMe: 51 %, unlimited traffic: 31 %, hourly billing: 8 %
- RAM → price from: 1 GB — 0.97 $, 2 GB — 1.33 $, 4 GB — 2.24 $, 8 GB — 4.19 $, 16 GB — 7.85 $
- Countries: USA (357), Germany (301), Netherlands (296), United Kingdom (205), Japan (104), Poland (102)
- Cheapest hosts: [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) — 0.97 $, [Nuyek](https://accsly.io/en/vps/hosting/nuyek) — 1.49 $, [hostEONS.com](https://accsly.io/en/vps/hosting/hosteons) — 1.74 $, [DataPasa](https://accsly.io/en/vps/hosting/datapasa) — 1.99 $, [ByteHosting](https://accsly.io/en/vps/hosting/bytehosting) — 2.24 $

## Cheapest plans — 1,602 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [uaVPS](https://accsly.io/en/vps/hosting/uavps) | VPS-PROMO | 1 | 512 MB | 10 GB NVMe | UA, PL, FR, DE, NL | — | 0.90 $ |
| [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) | Промо SSD 2026 | 1 | 1 GB | 6 GB SSD | RU | Invoice, MIR, SBP, YooMoney | 0.97 $ |
| [hostEONS.com](https://accsly.io/en/vps/hosting/hosteons) | OVZ256 | 1 | 256 MB | 5 GB SSD | US | PayPal, Visa/MC, Crypto, Invoice | 1.00 $ |
| [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) | Старт0 SSD 2026 | 1 | 2 GB | 10 GB SSD | RU | Invoice, MIR, SBP, YooMoney | 1.33 $ (when paying for 2 years: 1.00 $/mo) |
| [Nuyek](https://accsly.io/en/vps/hosting/nuyek) | VPS-1 | 1 | 1 GB | 20 GB NVMe | US | Visa/MC, Crypto | 1.49 $ (total when paying for year (17.95 $)) |
| [hostEONS.com](https://accsly.io/en/vps/hosting/hosteons) | Gigabit VPS 1 | 1 | 1 GB | 10 GB SSD | US | PayPal, Visa/MC, Crypto, Invoice | 1.74 $ (total when paying for year (21.01 $)) |
| [Hostmaze](https://accsly.io/en/vps/hosting/hostmaze) | KVM SSD 2C/256MB | 2 | 256 MB | 15 GB SSD | RO | PayPal, Visa/MC, Crypto | 1.87 $ (total when paying for year (22.39 $)) |
| [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) | Старт1 SSD 2026 | 2 | 3 GB | 15 GB SSD | RU | Invoice, MIR, SBP, YooMoney | 1.94 $ (when paying for 2 years: 1.45 $/mo) |
| [DataPasa](https://accsly.io/en/vps/hosting/datapasa) | VPS-1 | 1 | 1 GB | 16 GB NVMe | DE | Visa/MC, PayPal, Crypto | 1.99 $ |
| [hostEONS.com](https://accsly.io/en/vps/hosting/hosteons) | RYZEN 512 MB | 1 × 3.5 GHz | 512 MB | 10 GB NVMe | US | PayPal, Visa/MC, Crypto, Invoice | 2.00 $ (total when paying for year (24.00 $)) |
| [ByteHosting](https://accsly.io/en/vps/hosting/bytehosting) | Xeon - 4GB | 1 | 4 GB | 30 GB NVMe | DE | PayPal, Crypto | 2.24 $ (total when paying for year (26.87 $)) |
| [FinalTek.com](https://accsly.io/en/vps/hosting/shop-finaltek) | Core | 1 | 1 GB | 10 GB SSD |  | Visa/MC, PayPal, Crypto, Invoice | 2.30 $ |
| [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) | Power0 NVMe 2026 | 1 × 3.2 GHz | 2 GB | 20 GB NVMe | RU | Invoice, MIR, SBP, YooMoney | 2.30 $ (when paying for 2 years: 1.84 $/mo) |
| [Final Tek](https://accsly.io/en/vps/hosting/finaltek) | V-Server Core | 1 | 1 GB | 10 GB SSD |  | — | 2.30 $ |
| [Time4VPS](https://accsly.io/en/vps/hosting/time4vps) | Storage 0.25 TB Plan | 1 | 512 MB | 256 GB SSD | LT | PayPal, Visa/MC, Invoice, Crypto | 2.48 $ |
| [Nuyek](https://accsly.io/en/vps/hosting/nuyek) | VPS-2 | 1 | 2 GB | 30 GB NVMe | US | Visa/MC, Crypto | 2.50 $ |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | VPS-1 (Xeon) | 2 | 4 GB | 40 GB NVMe | TR | Invoice | 2.59 $ |
| [IT-garage](https://accsly.io/en/vps/hosting/it-garage) | DEs-PROMO | 1 | 1 GB | 10 GB SSD | DE | Visa/MC, Crypto | 2.68 $ |
| [Citra Host](https://accsly.io/en/vps/hosting/citrahost) | Cloud Starter | 1 | 1 GB | 20 GB SSD | ID | Visa/MC | 2.76 $ |
| [Citra Host](https://accsly.io/en/vps/hosting/citrahost) | VPSID 1 GB | 1 | 1 GB | 20 GB SSD | ID | Visa/MC | 2.76 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/for-mail-server?format=json

## How to set up your own mail server on a VPS

Your own mail on a VPS means mailboxes on your own domain with no per-user fees, full control over your messages and the ability to send newsletters and notifications from your own applications. In exchange you'll have to get to grips with DNS records and look after your IP's reputation: mail providers are strict about checking who sends messages.

### The key requirement: an open port 25

Mail servers pass messages to each other over SMTP on port 25. Many hosts block outbound port 25 by default to keep spam from leaving their networks. Without it your server can receive mail but can't send it. That's why this selection includes only plans from hosts where the port is open or can be opened on request to support. Even if it's blocked at first, it's usually enough to write to support and explain that you're setting up mail for your own domain.

### What to install

- **Mailcow** — a ready-made Docker bundle: Postfix, Dovecot, SOGo webmail, Rspamd anti-spam and a convenient admin panel. Needs 4 GB of memory and 2 cores or more, and is the easiest to set up.
- **Mail-in-a-Box** and **iRedMail** — all-in-one installers that configure the server and DNS step by step. They run on 1–2 GB of memory.
- **Postfix + Dovecot** by hand — minimal resources (1 GB is enough), but more manual configuration work.

If the server will run Docker with Mailcow and the ClamAV antivirus, choose [4 GB of RAM or more](https://accsly.io/en/vps/4-gb-ram): ClamAV alone takes about a gigabyte.

### DNS: without it your mail ends up in spam

- **PTR (reverse record)** — the server's IP should point to your mail host's name, for example `mail.example.com`. The host sets it up in the control panel or on request — check that this option is available.
- **SPF** — a TXT record listing the servers allowed to send mail on behalf of your domain.
- **DKIM** — a digital signature for messages; the mail server generates the key, and you publish the public part in DNS.
- **DMARC** — a policy for what to do with messages that fail the checks; start with `p=none` mode and reports.

### IP reputation

Before launch, check the server's IP against blacklists (Spamhaus, Barracuda and others) — the address may have been inherited from a previous owner who sent spam. If it's listed, ask the host for a different one. Start with small volumes: a new address takes weeks to "warm up", and a sudden mass mailing from it will almost certainly land in spam. For large campaigns it's better to use a dedicated service and keep your own server for work mail and notifications.

### Storage and backups

Mailboxes grow for years: plan for 20–40 GB or more for a small team and keep an eye on quotas. Store backups of messages and DKIM keys off the server, for example on a [separate backup VPS](https://accsly.io/en/vps/for-backups).

## FAQ

### Why isn't mail going out from my VPS?

Most often the host has blocked outbound port 25. Test it with telnet or nc against an external mail server and, if the port is blocked, ask support to open it.

### How much memory does a mail server need?

Postfix and Dovecot run on 1 GB. Mailcow with webmail and anti-spam needs 4 GB or more, and with the ClamAV antivirus 6–8 GB is better.

### What is a PTR record and where do I set it up?

It's a reverse DNS record that links the server's IP to the mail host's name. The host sets it up, either in the control panel or on request to support.

### Why does my mail end up in spam?

Usually SPF, DKIM, DMARC or PTR is missing, or the IP is on a blacklist. Check your setup with services such as mail-tester and warm up a new address gradually.

### Can I send mass mailings from my own VPS?

Technically yes, but most hosts prohibit mass mailings in their rules, and a new IP will quickly land in spam. A specialised service is a more reliable option for campaigns.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS for CI/CD runners

GitLab and GitHub Actions runners need cores for the duration of the build — hourly billing is more convenient.

> Source: https://accsly.io/en/vps/for-ci · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 4,030, hosts: 163
- Price: from 4.19 $, a quarter below 105 $, median 320 $
- NVMe: 25 %, unlimited traffic: 16 %, hourly billing: 100 %
- RAM → price from: 1 GB — 4.19 $, 2 GB — 4.19 $, 4 GB — 4.19 $, 8 GB — 6.18 $, 16 GB — 10.49 $
- Countries: USA (1634), Netherlands (1484), Germany (1233), United Kingdom (1186), Singapore (1129), Australia (923)
- Cheapest hosts: [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 4.19 $, [Voyar Cloud](https://accsly.io/en/vps/hosting/voyar) — 4.89 $, [Hostnic  ID](https://accsly.io/en/vps/hosting/hostnic) — 5.97 $, [Phylex Platforms](https://accsly.io/en/vps/hosting/phylex) — 6.18 $, [Sive Host](https://accsly.io/en/vps/hosting/sive) — 6.30 $

## Cheapest plans — 4,030 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | FullVPS-4096 Max | 4 | 4 GB | 50 GB NVMe | NL | Visa/MC, PayPal, Crypto | 4.19 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | ExtraVPS-6144 US | 4 × 3.0 GHz | 6 GB | 40 GB NVMe | US | Visa/MC, PayPal, Crypto | 4.29 $ |
| [Voyar Cloud](https://accsly.io/en/vps/hosting/voyar) | CV-20 | 4 | 4 GB | 60 GB NVMe | TR | Invoice | 4.89 $ |
| [Hostnic  ID](https://accsly.io/en/vps/hosting/hostnic) | VPS Plus (Pay As You Go, пример 4 core/4 GB/20 GB) | 4 | 4 GB | 20 GB NVMe | ID | Visa/MC, PayPal | 5.97 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | FullVPS-6144 Max Plus | 5 | 6 GB | 50 GB NVMe | NL | Visa/MC, PayPal, Crypto | 5.98 $ |
| [Phylex Platforms](https://accsly.io/en/vps/hosting/phylex) | AXV 2 | 4 | 8 GB | 100 GB NVMe | NL | — | 6.18 $ |
| [Sive Host](https://accsly.io/en/vps/hosting/sive) | uMsunduzi River | 4 | 8 GB | 200 GB SSD | ZA | PayPal, Visa/MC, Crypto | 6.30 $ (when paying for 2 years: 4.46 $/mo) |
| [Priente Cloud](https://accsly.io/en/vps/hosting/prientecloud) | g.small | 4 | 4 GB | 60 GB SSD | TR | Visa/MC | 6.89 $ (when paying for year: 6.20 $/mo) |
| [Sive Host](https://accsly.io/en/vps/hosting/sive) | Blyde River | 6 | 12 GB | 300 GB SSD | ZA | PayPal, Visa/MC, Crypto | 7.22 $ (total when paying for year (86.69 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | FullVPS-8192 Top | 6 | 8 GB | 50 GB NVMe | NL | Visa/MC, PayPal, Crypto | 7.49 $ |
| [CloudCone](https://accsly.io/en/vps/hosting/cloudcone) | SSD VPS 4 | 8 | 4 GB | 120 GB SSD | US | Visa/MC, Invoice | 7.67 $ (total when paying for year (91.99 $)) |
| [cal.pl](https://accsly.io/en/vps/hosting/cal) | n8n Gold | 4 | 8 GB | 80 GB NVMe | DE | Visa/MC, Invoice | 7.67 $ |
| [IDCloudHost.com](https://accsly.io/en/vps/hosting/idcloudhost) | Rocket VPS 2 | 4 × 2.9 GHz | 4 GB | 80 GB NVMe | ID | Visa/MC, PayPal, Invoice | 8.01 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | ExtraVPS-12G US | 4 × 3.0 GHz | 12 GB | 50 GB NVMe | US | Visa/MC, PayPal, Crypto | 8.29 $ |
| [RackGenius](https://accsly.io/en/vps/hosting/rackgenius) | 6GB LTO VPS | 4 | 6 GB | 75 GB SSD | US | — | 8.50 $ |
| [Euronodes](https://accsly.io/en/vps/hosting/euronodes) | Cloud 4C/8G | 4 | 8 GB | 150 GB SSD | PT, CZ | Visa/MC, PayPal, Invoice, Crypto | 8.93 $ |
| [Phylex Platforms](https://accsly.io/en/vps/hosting/phylex) | EPC 2 | 4 | 8 GB | 100 GB NVMe | DE | — | 8.95 $ |
| [iqhost](https://accsly.io/en/vps/hosting/iqhost-ru) | Сервер для clawbot | 4 × 2.1 GHz | 8 GB | 30 GB NVMe | RU, NL, US | MIR, YooMoney, Invoice, Crypto | 8.96 $ |
| [HostUp](https://accsly.io/en/vps/hosting/hostup) | VPSSM | 4 | 8 GB | 100 GB NVMe | SE | — | 9.06 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | VPS 2027 VPS-2 | 4 | 8 GB | 75 GB NVMe | AU, CA, DE, FR, GB, IN… | PayPal, Visa/MC | 9.50 $ (when paying for year: 8.07 $/mo) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/for-ci?format=json

## VPS for development and CI/CD: what matters

Your own server for builds and tests pays off as soon as the free minutes in GitHub Actions or GitLab CI stop being enough. A self-hosted runner has no time limits and keeps dependency and Docker image caches, which makes repeat builds several times faster. The same VPS also works well as a remote development environment or a staging server.

### Cores and memory: builds need a lot, but not for long

Compilation, frontend builds and test runs are parallelised across cores, so for a runner the core count matters more than for a web server. Rough guidelines:

- **2 cores and 4 GB** — small Node.js, Python or PHP projects, linters and unit tests;
- **4 cores and 8 GB** — building Docker images, Webpack or Vite frontends, integration tests with a database;
- **8 cores and 16 GB** — compiling Go, Rust, Java or C++, Android builds, parallel jobs.

If you only run a few builds a day, the server sits idle most of the time. That's where [hourly billing](https://accsly.io/en/vps/hourly-billing) helps: you spin up a powerful server for the job and delete it afterwards, paying only for the hours used. Many hosts let you do this through an API, so the runner can be started automatically.

### Storage: caches take up more than you'd think

Docker images, npm, pip, Maven or Gradle caches and build artifacts quickly add up to tens of gigabytes. Choose [NVMe](https://accsly.io/en/vps/nvme) with 50–80 GB or more and set up cleanup: a scheduled `docker system prune` and a retention limit for artifacts. Disk speed directly affects how long dependencies take to install — on a slow disk that can take longer than the build itself.

### How to connect a runner

- **GitHub Actions** — a self-hosted runner is installed with a single command from the repository or organisation settings and runs as a service.
- **GitLab CI** — `gitlab-runner` with the Docker executor: each job runs in a clean container, and images are cached on the server.
- **Gitea, Forgejo, Woodpecker, Drone** — lightweight alternatives if you also host the repository on your own server; see also [VPS for GitLab](https://accsly.io/en/vps/for-gitlab).

### Virtualisation and security

Docker builds need KVM: under container virtualisation Docker often won't start or runs with restrictions (more on the [VPS for Docker](https://accsly.io/en/vps/for-docker) page). Don't connect a self-hosted runner to public repositories: someone else's pull request could run arbitrary code on your server. Pass secrets through CI variables instead of storing them on disk, and update the runner along with the system.

### Where to host it

A server closer to your Git hosting and image registry downloads dependencies faster. For GitHub and Docker Hub, servers in Europe and the US are convenient; from Russia some registries can be hard to reach, so set up mirrors or a pull-through cache in advance.

## FAQ

### How many cores does a CI runner need?

For small projects, 2 cores and 4 GB of memory are enough. Building Docker images and frontends is comfortable on 4 cores and 8 GB, and compiling large projects calls for 8 cores or more.

### Is my own runner cheaper than GitHub Actions minutes?

If you run lots of builds, yes: a VPS costs a fixed amount, and the caches on it speed up repeat builds. For occasional builds, hourly billing helps — the server is created only for the duration of the job.

### Is OpenVZ suitable for Docker builds?

As a rule, no: Docker runs reliably on KVM, where the server has its own kernel. On OpenVZ and LXC there may be restrictions, or it may not start at all.

### Can I use one VPS as both a runner and a staging server?

Yes, if you have plenty of spare resources. But builds max out the CPU, so a staging server that needs to respond reliably is better kept separate.

### Is it safe to connect a self-hosted runner to a public repository?

No: any pull request could run code on your server. Use your own runners only for private repositories or with approval-gated runs.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS for CPU-only AI models (Ollama)

7–8B-parameter models in Ollama or llama.cpp run without a GPU if there's enough memory: at least 16 GB and 8 cores.

> Source: https://accsly.io/en/vps/for-ollama · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 9,212, hosts: 1,413
- Price: from 7.95 $, a quarter below 80.99 $, median 173 $
- NVMe: 43 %, unlimited traffic: 28 %, hourly billing: 30 %
- RAM → price from: 1 GB — 7.95 $, 2 GB — 7.95 $, 4 GB — 7.95 $, 8 GB — 7.95 $, 16 GB — 7.95 $
- Countries: USA (2949), Germany (2231), Netherlands (1961), United Kingdom (1935), Singapore (1485), India (1398)
- Cheapest hosts: [SpeedHost247.com](https://accsly.io/en/vps/hosting/speedhost247) — 7.95 $, [Keyubu](https://accsly.io/en/vps/hosting/keyubu) — 9.78 $, [BalHost](https://accsly.io/en/vps/hosting/balhost-net) — 10.58 $, [Hostlab.com](https://accsly.io/en/vps/hosting/hostlab) — 10.58 $, [Webyne](https://accsly.io/en/vps/hosting/webyne) — 10.65 $

## Cheapest plans — 9,212 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [SpeedHost247.com](https://accsly.io/en/vps/hosting/speedhost247) | Premium VPS | 12 | 48 GB | 250 GB NVMe | GB, SG, IN | — | 7.95 $ |
| [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | VPS L-TR 16GB | 8 | 16 GB | 100 GB NVMe | TR | Visa/MC | 9.78 $ (yearly: 9.77 $/mo) |
| [Hostlab.com](https://accsly.io/en/vps/hosting/hostlab) | SSD VDS (Paket 8) | 10 | 16 GB | 200 GB SSD | TR | Visa/MC, Invoice | 10.58 $ (when paying for year: 8.81 $/mo) |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | VDS-8 | 8 | 16 GB | 240 GB NVMe | TR | Invoice | 10.58 $ |
| [Webyne](https://accsly.io/en/vps/hosting/webyne) | Gold VPS Linux 2 | 8 | 16 GB | 200 GB SSD | IN | Visa/MC, Invoice | 10.65 $ |
| [Webyne](https://accsly.io/en/vps/hosting/webyne) | Speed VPS2 | 8 | 16 GB | 400 GB SSD | IN | Visa/MC, Invoice | 10.65 $ |
| [almas.host](https://accsly.io/en/vps/hosting/almas) | vpsx-80 | 8 | 32 GB | 145 GB NVMe | IR | — | 10.66 $ |
| [Brnchost internet ve bilişim hizmetleri](https://accsly.io/en/vps/hosting/brnchost) | VDS Kirala 6 | 8 | 16 GB | 80 GB SSD | TR | Visa/MC | 10.77 $ |
| [DatabaseMart.com](https://accsly.io/en/vps/hosting/databasemart) | Professional Linux VPS | 8 | 18 GB | 240 GB SSD | US | Visa/MC, PayPal | 10.81 $ |
| [SSD Nodes](https://accsly.io/en/vps/hosting/ssdnodes) | Standard KVM / 2X-LARGE | 8 | 32 GB | 480 GB SSD | US, GB, NL, DE, IN, SG… | — | 11.08 $ (total when paying for 3 years (399 $)) |
| [Dyjix](https://accsly.io/en/vps/hosting/dyjix) | VPS SSD 16 | 8 | 16 GB | 200 GB SSD | FR | Visa/MC, PayPal | 11.18 $ |
| [Webyne](https://accsly.io/en/vps/hosting/webyne) | General VPS Professional | 8 | 16 GB | 250 GB SSD | IN | Visa/MC, Invoice | 11.71 $ (total when paying for year (141 $)) |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | Forex 8C/32GB/300GB | 8 | 32 GB | 300 GB SSD | IN | Invoice | 11.97 $ |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | General Professional | 8 | 64 GB | 500 GB SSD | IN | Invoice | 11.97 $ |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | Speed 8C/16GB/400GB | 8 | 16 GB | 400 GB SSD | IN | Invoice | 11.97 $ |
| [Brnchost internet ve bilişim hizmetleri](https://accsly.io/en/vps/hosting/brnchost) | VDS Kirala 7 | 10 | 18 GB | 100 GB SSD | TR | Visa/MC | 12.16 $ |
| [Hostika](https://accsly.io/en/vps/hosting/hostika) | VM40 | 8 | 16 GB | 150 GB HDD | LT | PayPal, Crypto, Invoice, Visa/MC | 12.20 $ (when paying for 3 years: 9.76 $/mo) |
| [Square Brothers](https://accsly.io/en/vps/hosting/squarebrothers) | Power | 8 | 32 GB | 200 GB NVMe | IN | Visa/MC, PayPal | 12.78 $ |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-4 | 8 × 3.3 GHz | 28 GB | 300 GB NVMe |  | PayPal, Visa/MC, Crypto | 13.37 $ |
| [Prox Group](https://accsly.io/en/vps/hosting/pulseheberg) | ECO-16 | 8 | 16 GB | 160 GB NVMe | FR | Visa/MC, PayPal, Crypto | 13.43 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/for-ollama?format=json

## AI models on a VPS without a GPU: what you can really run

A GPU in the cloud is expensive, but many tasks don't need one. Language models with 3–8 billion parameters in compressed form run on an ordinary CPU: they respond more slowly than ChatGPT, but your data never leaves your server and you pay a fixed amount with no request limits. It's a good option for internal bots, document processing, classification and experiments.

### Memory decides which model fits

The whole model is loaded into RAM. With 4-bit quantisation (Q4), one billion parameters takes roughly 0.6–0.7 GB, plus headroom for the context and the system:

- **8 GB RAM** — models up to 3–4 billion parameters: Llama 3.2 3B, Phi, Qwen 2.5 3B;
- **16 GB RAM** — 7–8 billion models: Llama 3.1 8B, Qwen 2.5 7B, Mistral 7B — the most popular class;
- **32 GB or more** — 13–14 billion models or several models at once.

That's why this selection starts at [16 GB of memory](https://accsly.io/en/vps/16-gb-ram) and 8 cores — the minimum for working comfortably with 7–8 billion parameter models.

### Speed depends on cores and memory

Text generation on a CPU is limited by memory bandwidth and the number of cores. On 8 modern cores a 7B model produces around 5–10 tokens per second — enough for a chatbot serving one or two users at a time. Pay attention to the CPU's clock speed and generation: [high-frequency plans](https://accsly.io/en/vps/high-frequency) on recent AMD EPYC and Ryzen chips are noticeably faster than old Xeons. If AVX2 and AVX-512 instructions are supported, llama.cpp uses them automatically.

### What to install

- **Ollama** — the simplest option: one command to install, models are downloaded by name, and there's an OpenAI-compatible HTTP API.
- **llama.cpp** — the engine behind most of these tools; it gives you maximum control over parameters and speed.
- **Open WebUI** — a ChatGPT-style web interface on top of Ollama, handy for a team.
- **Whisper.cpp** — speech recognition on the CPU, works even with 4 GB.

If you only need models as part of an automation, they're easy to wire up to [n8n](https://accsly.io/en/vps/for-n8n) or a bot. And if cloud models are enough, a regular server that calls their APIs will do — see [VPS for Python](https://accsly.io/en/vps/for-python).

### Storage and limitations

Models weigh 2 to 10 GB each, so choose NVMe with 50 GB or more to keep several models and load them quickly. Keep the limits in mind: image generation (Stable Diffusion) on a CPU takes minutes per picture, and training models without a GPU is practically impossible — that requires a GPU server. Don't expose the Ollama API to the internet without authentication: close port 11434 with a firewall and put access behind a password-protected reverse proxy.

## FAQ

### Can I run an AI model on a VPS without a GPU?

Yes, language models up to 7–8 billion parameters in Q4 format run on the CPU via Ollama or llama.cpp. They're slower than on a GPU, but fast enough for a chatbot or document processing.

### How much memory does a 7B model need?

About 5–6 GB for the model itself in Q4 format, plus headroom for the context and the system. In practice, go for 16 GB of RAM or more for stable operation.

### How fast does a model run on a CPU?

On 8 modern cores a 7B model produces about 5–10 tokens per second. That's roughly reading speed: comfortable for one or two users at a time.

### Can I generate images on a VPS like this?

Technically yes, but Stable Diffusion on a CPU takes minutes per image. Image generation and model training need a server with a GPU.

### How do I secure Ollama on a server?

Don't expose port 11434 to the internet: have the API listen on localhost and route external access through a reverse proxy with authentication or a VPN.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS in Russia

Plans with servers in Russia. Compare price, processor, RAM and payment methods; cheapest first.

> Source: https://accsly.io/en/vps/russia · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 1,813, hosts: 188
- Price: from 0.71 $, a quarter below 10.53 $, median 24.71 $
- NVMe: 54 %, unlimited traffic: 50 %, hourly billing: 17 %
- RAM → price from: 1 GB — 0.71 $, 2 GB — 1.20 $, 4 GB — 3.62 $, 8 GB — 5.45 $, 16 GB — 12.11 $
- Cheapest hosts: [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) — 0.71 $, [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) — 0.97 $, [Inoventica](https://accsly.io/en/vps/hosting/invs) — 1.20 $, [OnlineVDS](https://accsly.io/en/vps/hosting/onlinevds) — 1.56 $, [Macloud](https://accsly.io/en/vps/hosting/macloud) — 1.82 $

## Cheapest plans — 1,813 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) | IaaS Lite 1 vCPU / 1 ГБ | 1 | 1 GB | 10 GB NVMe | RU | MIR, SBP, Crypto, WebMoney, Invoice | 0.71 $ |
| [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) | Промо SSD 2026 | 1 | 1 GB | 6 GB SSD | RU | Invoice, MIR, SBP, YooMoney | 0.97 $ |
| [LandVPS](https://accsly.io/en/vps/hosting/landvps) | Cloud VPS MSK/SPB/UFA-0 | 1 × 2.2 GHz | 700 MB | 10 GB SSD | RU | MIR, Invoice | 1.14 $ |
| [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) | IaaS Lite 1 vCPU / 2 ГБ | 1 | 2 GB | 20 GB NVMe | RU | MIR, SBP, Crypto, WebMoney, Invoice | 1.20 $ |
| [eServer RU](https://accsly.io/en/vps/hosting/eserver-ru) | KVM VPS Econom Bronze-1 | 1 | 512 MB | 10 GB SSD | RU | WebMoney, MIR, Crypto, Invoice | 1.20 $ (when paying for year: 1.00 $/mo) |
| [Inoventica](https://accsly.io/en/vps/hosting/invs) | LUNA PROMO | 1 | 1 GB | 20 GB SSD | RU | YooMoney | 1.20 $ |
| [VDS4YOU](https://accsly.io/en/vps/hosting/vds4you) | Гибрид VDS MINI | 1 | 512 MB | 20 GB HDD | RU | MIR, Visa/MC, WebMoney, YooMoney, PayPal, Invoice, Crypto | 1.20 $ |
| [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) | Старт0 SSD 2026 | 1 | 2 GB | 10 GB SSD | RU | Invoice, MIR, SBP, YooMoney | 1.33 $ (when paying for 2 years: 1.00 $/mo) |
| [1hs](https://accsly.io/en/vps/hosting/1hs) | SSD-VPS-1 | 1 | 512 MB | 10 GB SSD | RU | Visa/MC, YooMoney, WebMoney, PayPal, Invoice | 1.44 $ (when paying for year: 1.30 $/mo) |
| [Firstbyte](https://accsly.io/en/vps/hosting/firstbyte) | MSK-KVM-SAS-1 | 1 | 768 MB | 20 GB HDD | RU | Invoice, PayPal, Crypto | 1.56 $ |
| [Firstbyte](https://accsly.io/en/vps/hosting/firstbyte) | MSK-KVM-SSD-1 | 1 | 768 MB | 10 GB SSD | RU | Invoice, PayPal, Crypto | 1.56 $ |
| [OnlineVDS](https://accsly.io/en/vps/hosting/onlinevds) | Мини | 1 | 1 GB | 10 GB NVMe | RU | SBP, Visa/MC, YooMoney, Invoice | 1.56 $ |
| [UltraVDS](https://accsly.io/en/vps/hosting/ultravds) | UltraLite | 1 × 2.0 GHz | 512 MB | 10 GB SSD | RU | MIR, Visa/MC, YooMoney, Invoice | 1.64 $ (when paying for year: 1.31 $/mo) |
| [Sprintbox](https://accsly.io/en/vps/hosting/sprintbox) | Студент | 1 | 600 MB | 7 GB NVMe | RU, NL, DE, US, BY, AM… | — | 1.70 $ |
| [Макхост](https://accsly.io/en/vps/hosting/mchost) | KVM-NEW | 1 × 2.4 GHz | 600 MB | 10 GB SSD | RU, NL | WebMoney, YooMoney, MIR, Visa/MC, Crypto, Invoice | 1.73 $ |
| [KVMka](https://accsly.io/en/vps/hosting/kvmka) | RU-MSK-PROMO | 1 | 512 MB | 5 GB NVMe | RU | MIR, Visa/MC, YooMoney, Invoice | 1.80 $ |
| [RuVDS](https://accsly.io/en/vps/hosting/ruvds) | Самый дешёвый VPS | 1 × 2.0 GHz | 512 MB | 10 GB HDD | RU | Visa/MC, MIR, SBP, YooMoney | 1.80 $ |
| [Macloud](https://accsly.io/en/vps/hosting/macloud) | Cloud 1CPU/1GB/10GB | 1 | 1 GB | 10 GB NVMe | RU | WebMoney, Invoice, MIR | 1.82 $ |
| [1BX.host](https://accsly.io/en/vps/hosting/1bx) | KVM.SSD Альфа | 1 × 3.3 GHz | 512 MB | 10 GB SSD | RU | SBP, Visa/MC, MIR, Invoice, WebMoney | 1.82 $ (total when paying for 3 mo (5.45 $)) |
| [LandVPS](https://accsly.io/en/vps/hosting/landvps) | Cloud VPS A-MSK-0 | 1 × 2.4 GHz | 700 MB | 10 GB NVMe | RU | MIR, Invoice | 1.91 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/russia?format=json

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS in the Netherlands

Plans with servers in the Netherlands. Compare price, processor, RAM and payment methods; cheapest first.

> Source: https://accsly.io/en/vps/netherlands · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 5,651, hosts: 424
- Price: from 0.42 $, a quarter below 21.10 $, median 60.00 $
- NVMe: 37 %, unlimited traffic: 22 %, hourly billing: 35 %
- RAM → price from: 1 GB — 0.49 $, 2 GB — 1.71 $, 4 GB — 3.32 $, 8 GB — 5.90 $, 16 GB — 8.40 $
- Cheapest hosts: [V.PS](https://accsly.io/en/vps/hosting/v) — 0.93 $, [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 1.43 $, [ChunkServ](https://accsly.io/en/vps/hosting/chunkserve) — 1.45 $, [HostVDS](https://accsly.io/en/vps/hosting/hostvds) — 1.67 $, [RackNerd](https://accsly.io/en/vps/hosting/racknerd) — 1.83 $

## Cheapest plans — 5,651 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ NL 256MB NAT | 1 | 256 MB | 5 GB SSD | NL | — | 0.42 $ (total when paying for year (4.99 $)) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | STARDUST1-S | 1 × 2.1 GHz | 1 GB | — | FR, NL, PL | — | 0.49 $ |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-512-LXC | 1 | 512 MB | 6 GB SSD | SG, HK, TW, JP, DE, TR… | Crypto | 0.64 $ (total when paying for year (7.70 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-512-KVM | 1 | 512 MB | 6 GB SSD | SG, HK, JP, TW, DE, TR… | Crypto | 0.73 $ (total when paying for year (8.79 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ NL 1024MB NAT | 1 | 1 GB | 5 GB SSD | NL | — | 0.86 $ (total when paying for year (10.30 $)) |
| [uaVPS](https://accsly.io/en/vps/hosting/uavps) | VPS-PROMO | 1 | 512 MB | 10 GB NVMe | UA, PL, FR, DE, NL | — | 0.90 $ |
| [V.PS](https://accsly.io/en/vps/hosting/v) | Nano | 1 | 1 GB | 15 GB SSD | NL, DE | PayPal, Visa/MC, Invoice | 0.93 $ (total when paying for year (11.13 $)) |
| [RuVPS](https://accsly.io/en/vps/hosting/ruvps) | VPS-0 | 1 | 768 MB | 7 GB NVMe | NL, PL, UA | Visa/MC, Crypto | 0.95 $ |
| [Jink Host](https://accsly.io/en/vps/hosting/jink) | Dirt | 1 | 512 MB | 20 GB NVMe | US, NL | Visa/MC, PayPal, Crypto | 1.00 $ (total when paying for 3 mo (3.00 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-1024-LXC | 2 | 1 GB | 8 GB SSD | SG, HK, TW, JP, DE, TR… | Crypto | 1.00 $ (total when paying for year (12.01 $)) |
| [ChangeIP](https://accsly.io/en/vps/hosting/changeip) | VPS $1 | 1 | 256 MB | 15 GB SSD | US, NL, DE, SG | Visa/MC, Crypto | 1.00 $ |
| [TierHive](https://accsly.io/en/vps/hosting/tierhive) | Калькулятор (конфигурация по умолчанию) | 1 | 1 GB | 20 GB NVMe | NL, CA, DE, FR, US, GB… | — | 1.01 $ |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-1024-KVM | 2 | 1 GB | 12 GB SSD | SG, HK, JP, TW, DE, TR… | Crypto | 1.17 $ (total when paying for year (14.00 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | FullVPS-1024 Essential | 1 | 1 GB | 30 GB NVMe | NL | Visa/MC, PayPal, Crypto | 1.43 $ (total when paying for 3 mo (4.29 $)) |
| [ChunkServ](https://accsly.io/en/vps/hosting/chunkserve) | Xeon Standard 1 | 1 | 1 GB | 15 GB NVMe | NL | — | 1.45 $ |
| [VirMach](https://accsly.io/en/vps/hosting/virmach) | Value+ LITE | 1 | 512 MB | 10 GB SSD | US, NL, JP | Visa/MC, PayPal, Crypto | 1.50 $ |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 1 | 1 | 1 GB | 10 GB NVMe | FR, LV, NL, FI | Visa/MC, Crypto | 1.67 $ |
| [Sprintbox](https://accsly.io/en/vps/hosting/sprintbox) | Студент | 1 | 600 MB | 7 GB NVMe | RU, NL, DE, US, BY, AM… | — | 1.70 $ |
| [TierHive](https://accsly.io/en/vps/hosting/tierhive) | STANDARD | 1 | 2 GB | 25 GB NVMe | NL, CA, DE, FR, US, GB… | — | 1.71 $ |
| [Макхост](https://accsly.io/en/vps/hosting/mchost) | KVM-NEW | 1 × 2.4 GHz | 600 MB | 10 GB SSD | RU, NL | WebMoney, YooMoney, MIR, Visa/MC, Crypto, Invoice | 1.73 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/netherlands?format=json

## Why VPS in the Netherlands are so popular

The Netherlands is one of the most hosting-dense countries in the world. The reason is geography and infrastructure: transatlantic and Northern European cables run through Amsterdam, and the AMS-IX internet exchange is among the largest on the planet. Thousands of carriers exchange traffic right in the city, so routes from Amsterdam are short in almost any direction.

### Amsterdam as an internet hub

For a server owner this means three things. First, high connectivity: London, Frankfurt and Paris are a few milliseconds away, the US east coast about 80 ms. Second, competition: there are hundreds of hosts here, and virtual server prices are lower than in many neighbouring countries. Third, choice: from tiny 512 MB plans to powerful NVMe machines. Most Dutch plans are hosted in [Amsterdam](https://accsly.io/en/vps/amsterdam) and its suburbs.

### Ping

Thanks to these short routes, a server in Amsterdam gives low latency across most of Europe — enough for a website, an API, remote desktop and voice calls. Countries even closer to you may give a slightly lower ping. The real value depends on your provider: many hosts have a test IP or a looking glass, so check the ping before paying.

### What people use a VDS in the Netherlands for

- **A corporate VPN** for remote office access and for protecting traffic on public networks. What matters here is KVM virtualization, unlimited or plentiful traffic and a port of 1 Gbps or more. Configurations for this task are collected on the [VPS for WireGuard](https://accsly.io/en/vps/for-wireguard) page.
- **Websites for a European audience**: stores, landing pages, SaaS. From Amsterdam a page loads quickly across the whole EU.
- **Proxies, scraping, monitoring** — tasks that need a stable European IP.
- **A backup location** for a project hosted elsewhere: a copy of the data in another jurisdiction.

Keep in mind that Dutch hosts respond to complaints from rights holders and about spam. Mailings and torrents from a European IP quickly get a server blocked.

### Payment

Payment methods vary from host to host: most Dutch providers take cards, and many also accept cryptocurrency or payment through intermediaries. The "Payment" column in the table above shows the methods for each plan, and we convert prices into your currency to make comparison easier.

One last thing: a hosting provider may ask you to verify your identity if a payment or sign-up looks suspicious. Give your real details — this reduces the risk of your account being blocked.

## FAQ

### What ping can I expect to the Netherlands?

Within Western Europe usually a few milliseconds to London, Frankfurt and Paris, and about 80 ms to the US east coast. The exact value depends on your provider, so check the host's test IP before paying.

### What is AMS-IX?

It's an internet exchange point in Amsterdam, one of the largest in the world. Thanks to it, servers in the Netherlands have short routes to most networks in Europe.

### Is a VPS in the Netherlands suitable for a corporate network or remote office access?

Yes: short routes from Amsterdam make it a good hub for a team spread across Europe. Choose KVM, plentiful or unlimited traffic and a port of 1 Gbps or more.

### Do Dutch hosts block servers over complaints?

Yes, they respond quickly to complaints about spam, port scanning and copyright infringement. Usually a warning comes first, but repeat cases get the server switched off.

### Do I need a passport to rent a VPS in the Netherlands?

Most often an email address is enough, but the host has the right to request documents if a sign-up or payment looks suspicious.

### Does GDPR apply to a server in the Netherlands?

Yes, the Netherlands is in the EU and the host operates under GDPR. If you process Europeans' data, the regulation's requirements apply to you as the project owner too.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS in Germany

Plans with servers in Germany. Compare price, processor, RAM and payment methods; cheapest first.

> Source: https://accsly.io/en/vps/germany · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 5,921, hosts: 462
- Price: from 0.44 $, a quarter below 19.44 $, median 50.37 $
- NVMe: 44 %, unlimited traffic: 23 %, hourly billing: 27 %
- RAM → price from: 1 GB — 0.93 $, 2 GB — 1.19 $, 4 GB — 1.70 $, 8 GB — 4.47 $, 16 GB — 7.97 $
- Cheapest hosts: [V.PS](https://accsly.io/en/vps/hosting/v) — 0.93 $, [h2 NEXUS](https://accsly.io/en/vps/hosting/h2) — 1.00 $, [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 1.19 $, [Hostablanca.com](https://accsly.io/en/vps/hosting/hostablanca) — 1.45 $, [StorageBase UG](https://accsly.io/en/vps/hosting/storage-base) — 1.67 $

## Cheapest plans — 5,921 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ Germany 256MB NAT | 1 | 256 MB | 5 GB SSD | DE | — | 0.44 $ (total when paying for year (5.31 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-512-LXC | 1 | 512 MB | 6 GB SSD | SG, HK, TW, JP, DE, TR… | Crypto | 0.64 $ (total when paying for year (7.70 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ DE 512 MB NAT | 1 | 512 MB | 5 GB SSD | DE | — | 0.67 $ (total when paying for year (8.00 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-512-KVM | 1 | 512 MB | 6 GB SSD | SG, HK, JP, TW, DE, TR… | Crypto | 0.73 $ (total when paying for year (8.79 $)) |
| [uaVPS](https://accsly.io/en/vps/hosting/uavps) | VPS-PROMO | 1 | 512 MB | 10 GB NVMe | UA, PL, FR, DE, NL | — | 0.90 $ |
| [V.PS](https://accsly.io/en/vps/hosting/v) | Nano | 1 | 1 GB | 15 GB SSD | NL, DE | PayPal, Visa/MC, Invoice | 0.93 $ (total when paying for year (11.13 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-1024-LXC | 2 | 1 GB | 8 GB SSD | SG, HK, TW, JP, DE, TR… | Crypto | 1.00 $ (total when paying for year (12.01 $)) |
| [h2 NEXUS](https://accsly.io/en/vps/hosting/h2) | RED-PROMO | 1 × 3.3 GHz | 1 GB | 10 GB NVMe | DE, FI, PL | — | 1.00 $ |
| [ChangeIP](https://accsly.io/en/vps/hosting/changeip) | VPS $1 | 1 | 256 MB | 15 GB SSD | US, NL, DE, SG | Visa/MC, Crypto | 1.00 $ |
| [Hostablanca.com](https://accsly.io/en/vps/hosting/hostablanca) | Cheap VPS (слайдер, по умолчанию) | 1 | 512 MB | 10 GB NVMe | ES, DE | Crypto, Visa/MC | 1.01 $ (when paying for year: 0.93 $/mo) |
| [TierHive](https://accsly.io/en/vps/hosting/tierhive) | Калькулятор (конфигурация по умолчанию) | 1 | 1 GB | 20 GB NVMe | NL, CA, DE, FR, US, GB… | — | 1.01 $ |
| [myPrepaid-Server](https://accsly.io/en/vps/hosting/myprepaid-server) | 1 Euro Server | 1 × 3.5 GHz | 512 MB | 20 GB NVMe | DE | Visa/MC, PayPal, Invoice | 1.12 $ |
| [DeinServerHost](https://accsly.io/en/vps/hosting/deinserverhost) | KVM vServer FLEX | 1 | 1 GB | 10 GB NVMe | DE | PayPal, Invoice, Visa/MC, Crypto | 1.12 $ |
| [myPrepaid-Server](https://accsly.io/en/vps/hosting/myprepaid-server) | ONLY IPv6 | 1 | 512 MB | 15 GB SSD | DE | Visa/MC, PayPal, Invoice | 1.12 $ |
| [Hostablanca.com](https://accsly.io/en/vps/hosting/hostablanca) | VPS 11 | 1 | 600 MB | 11 GB NVMe | ES, DE | Crypto, Visa/MC | 1.12 $ (when paying for year: 1.02 $/mo) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-1024-KVM | 2 | 1 GB | 12 GB SSD | SG, HK, JP, TW, DE, TR… | Crypto | 1.17 $ (total when paying for year (14.00 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-01 | 1 | 2 GB | 40 GB NVMe | DE, FI | PayPal, Invoice | 1.19 $ |
| [Hostablanca.com](https://accsly.io/en/vps/hosting/hostablanca) | VPS 12 | 1 | 700 MB | 12 GB NVMe | ES, DE | Crypto, Visa/MC | 1.24 $ (when paying for year: 1.12 $/mo) |
| [Hostablanca.com](https://accsly.io/en/vps/hosting/hostablanca) | VPS 13 | 1 | 800 MB | 13 GB NVMe | ES, DE | Crypto, Visa/MC | 1.34 $ (when paying for year: 1.21 $/mo) |
| [WebHosting24](https://accsly.io/en/vps/hosting/webhosting24) | Munich NVMe KVM 512MB | 1 × 2.4 GHz | 512 MB | 10 GB NVMe | DE | Visa/MC, PayPal, Crypto, Invoice | 1.39 $ (total when paying for year (16.79 $)) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/germany?format=json

## VPS in Germany: Frankfurt, big data centres and the rules of the game

Germany is Europe's largest hosting market. It has electricity for data centres that's cheap by European standards, a dense backbone network and several providers that have built huge facilities of their own. Hence the choice: from budget plans to servers on the latest CPUs with NVMe.

### Frankfurt and DE-CIX

Frankfurt am Main is home to DE-CIX, one of the world's largest internet exchange points by peak traffic. Hundreds of carriers from Europe, Asia and the Middle East are connected to it, so a server in Frankfurt has short routes to almost any European network. If connectivity matters more to you than the lowest price, look at plans in [Frankfurt](https://accsly.io/en/vps/frankfurt): the points of presence of clouds and financial services are there too.

### Falkenstein and Nuremberg

Two small cities in Saxony and Bavaria are known for the large in-house campus of one of Germany's biggest hosts. A server here is usually cheaper than a Frankfurt one with the same specs, and for most tasks the quality of the network is no different. The plans are collected separately: [Falkenstein](https://accsly.io/en/vps/falkenstein) and [Nuremberg](https://accsly.io/en/vps/nuremberg). For a website, backend, CI runner or backups, this is a popular choice for value for money.

### GDPR and personal data

Germany is in the EU, and German supervisory authorities are considered among the strictest in enforcing GDPR. The host signs a data processing agreement (DPA) with a customer who processes the personal data of Europeans.

### Abuse policy: what can get you blocked

German providers are known for taking complaints seriously. A server may be restricted or shut down if it is the source of:

- port scanning and password brute-forcing — even if it's done by your own server after it's been hacked;
- mass mailings and anything that looks like spam;
- torrent seeding of copyrighted content — in Germany this actively draws legal claims;
- mining, if the plan's terms prohibit it.

The practical takeaway: set up SSH key login instead of a password right away, install fail2ban, keep the system updated and reply to abuse emails within the stated deadline. Many blocks happen not because of malicious intent but because an unprotected server got hacked.

### Sign-up and payment

Large German providers often vet new customers: they may ask for an ID document or prepayment, and they may reject a sign-up. Small hosts and resellers are usually simpler. Payment methods vary from host to host, and many accept cryptocurrency as well as cards. The "Payment" column in the table above shows the methods for each plan, and prices are shown in your currency.

## FAQ

### Is Germany a good location for low latency in Europe?

Yes: Frankfurt, with the DE-CIX exchange, has short routes to almost any European network, and Nuremberg and Falkenstein are close behind. The exact ping depends on your provider's route.

### How does Frankfurt differ from Falkenstein?

Frankfurt is the country's main network hub with the DE-CIX exchange point; connectivity is better there and prices are higher. Falkenstein is a large hosting campus where servers are usually cheaper with comparable quality for websites and backends.

### Why did a German host block my server?

Most often because of a complaint: port scanning, spam, torrents, or a hacked server followed by malicious activity. Reply to the abuse email, fix the cause and ask for the block to be lifted.

### Do I have to comply with GDPR if my server is in Germany?

If you process the personal data of EU residents, GDPR applies regardless of where the server is. A host in Germany will provide a data processing agreement on request.

### Do German hosts require documents at sign-up?

Large providers often vet new customers and may ask for a document or refuse registration. Small hosts and resellers usually make do with an email address.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS in Finland

Plans with servers in Finland. Compare price, processor, RAM and payment methods; cheapest first.

> Source: https://accsly.io/en/vps/finland · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 1,116, hosts: 112
- Price: from 0.42 $, a quarter below 17.89 $, median 40.02 $
- NVMe: 55 %, unlimited traffic: 20 %, hourly billing: 19 %
- RAM → price from: 1 GB — 1.00 $, 2 GB — 1.19 $, 4 GB — 1.70 $, 8 GB — 4.98 $, 16 GB — 7.97 $
- Cheapest hosts: [h2 NEXUS](https://accsly.io/en/vps/hosting/h2) — 1.00 $, [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 1.19 $, [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 1.33 $, [HostVDS](https://accsly.io/en/vps/hosting/hostvds) — 1.67 $, [Tietokettu](https://accsly.io/en/vps/hosting/tietokettu) — 2.80 $

## Cheapest plans — 1,116 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-II 384 Europe | 1 × 3.1 GHz | 384 MB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 0.42 $ (total when paying for 6 mo (2.50 $)) |
| [h2 NEXUS](https://accsly.io/en/vps/hosting/h2) | RED-PROMO | 1 × 3.3 GHz | 1 GB | 10 GB NVMe | DE, FI, PL | — | 1.00 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-01 | 1 | 2 GB | 40 GB NVMe | DE, FI | PayPal, Invoice | 1.19 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | CentralVPS-1536 | 2 × 3.1 GHz | 1.5 GB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 1.33 $ (total when paying for 3 mo (3.99 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-1024 Premier | 1 × 4.8 GHz | 1 GB | 15 GB NVMe | FI | Visa/MC, PayPal, Crypto | 1.50 $ (total when paying for 3 mo (4.49 $)) |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 1 | 1 | 1 GB | 10 GB NVMe | FR, LV, NL, FI | Visa/MC, Crypto | 1.67 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-02 | 2 | 4 GB | 70 GB NVMe | DE, FI | PayPal, Invoice | 1.70 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | ExtraVPS-4096 | 3 × 3.1 GHz | 4 GB | 60 GB NVMe | FI | Visa/MC, PayPal, Crypto | 2.17 $ (total when paying for 3 mo (6.49 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | CentralVPS-2048 Premier | 2 × 4.8 GHz | 2 GB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 2.50 $ (total when paying for 3 mo (7.49 $)) |
| [LandVPS](https://accsly.io/en/vps/hosting/landvps) | Cloud VPS DE/FL/NL-0 | 1 | 700 MB | 10 GB NVMe | DE, FI, NL, US | MIR, Invoice | 2.54 $ |
| [Tietokettu](https://accsly.io/en/vps/hosting/tietokettu) | Mini | 1 | 2 GB | 20 GB SSD | FI | Visa/MC, Invoice, PayPal | 2.80 $ |
| [Potenting](https://accsly.io/en/vps/hosting/potenting) | FIN-512MB | 1 × 3.1 GHz | 512 MB | 25 GB NVMe | FI | PayPal, Visa/MC, Crypto | 2.90 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-03 | 3 | 6 GB | 125 GB NVMe | DE, FI | PayPal, Invoice | 2.99 $ |
| [IT-garage](https://accsly.io/en/vps/hosting/it-garage) | FI-MX-1 | 1 | 1 GB | 10 GB NVMe | FI | Visa/MC, Crypto | 3.13 $ |
| [Firstbyte](https://accsly.io/en/vps/hosting/firstbyte) | EU-KVM-SSD-START (зарубежные локации) | 1 | 768 MB | 5 GB SSD | NL, FI, DE, FR, ES, BG… | Invoice, PayPal, Crypto | 3.14 $ |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 2 | 1 | 2 GB | 20 GB NVMe | FR, LV, NL, FI | Visa/MC, Crypto | 3.34 $ |
| [UpCloud.com](https://accsly.io/en/vps/hosting/upcloud) | Starter 1 GB / 1 vCPU | 1 | 1 GB | 10 GB SSD | NO, DK, SE, FI, GB, PL… | Visa/MC, PayPal | 3.36 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | CentralVPS-3072 Premier | 3 × 4.8 GHz | 3 GB | 25 GB NVMe | FI | Visa/MC, PayPal, Crypto | 3.49 $ |
| [DeepHost](https://accsly.io/en/vps/hosting/deephost) | AMS/HL/NY/FR/SG-01 | 1 × 2.4 GHz | 2 GB | 20 GB NVMe | NL, FI, US, DE, SG | YooMoney, MIR, Visa/MC, Invoice | 3.80 $ |
| [xzn.ir](https://accsly.io/en/vps/hosting/xzn) | UVPS3 | 2 | 2 GB | 30 GB NVMe | DE, US, FR, FI | — | 4.05 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/finland?format=json

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS in the USA

Plans with servers in the USA. Compare price, processor, RAM and payment methods; cheapest first.

> Source: https://accsly.io/en/vps/usa · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 8,858, hosts: 653
- Price: from 0.40 $, a quarter below 20.00 $, median 51.00 $
- NVMe: 38 %, unlimited traffic: 21 %, hourly billing: 25 %
- RAM → price from: 1 GB — 0.90 $, 2 GB — 1.71 $, 4 GB — 2.99 $, 8 GB — 5.00 $, 16 GB — 8.50 $
- Cheapest hosts: [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 0.90 $, [HostVDS](https://accsly.io/en/vps/hosting/hostvds) — 0.99 $, [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) — 1.00 $, [TNA Hosting](https://accsly.io/en/vps/hosting/tnahosting) — 1.33 $, [Nuyek](https://accsly.io/en/vps/hosting/nuyek) — 1.49 $

## Cheapest plans — 8,858 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-384 Low-Cost Special US | 1 × 3.0 GHz | 384 MB | 12 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.40 $ (total when paying for 6 mo (2.39 $)) |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Pico | 1 | 128 MB | 5 GB SSD | US | Crypto | 0.50 $ |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM Texas 300 MB NAT | 1 | 300 MB | 5 GB SSD | US | — | 0.58 $ (total when paying for year (6.99 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-1024 US | 2 × 3.0 GHz | 1 GB | 30 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.90 $ (total when paying for 3 mo (2.69 $)) |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 1 | 1 | 1 GB | 10 GB NVMe | US, HK | Visa/MC, Crypto | 0.99 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Dedicated Server 4 Cheolistic | 4 × 1.8 GHz | 1 GB | 32 GB SSD | US | Crypto | 1.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Dedicated Server 5 Pennam | 4 × 1.8 GHz | 1 GB | 16 GB SSD | US | Crypto | 1.00 $ |
| [Jink Host](https://accsly.io/en/vps/hosting/jink) | Dirt | 1 | 512 MB | 20 GB NVMe | US, NL | Visa/MC, PayPal, Crypto | 1.00 $ (total when paying for 3 mo (3.00 $)) |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Nano | 1 | 256 MB | 10 GB SSD | US | Crypto | 1.00 $ |
| [hostEONS.com](https://accsly.io/en/vps/hosting/hosteons) | OVZ256 | 1 | 256 MB | 5 GB SSD | US | PayPal, Visa/MC, Crypto, Invoice | 1.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | VDS 1 Vaporia | 2 × 1.5 GHz | 1 GB | 16 GB SSD | US | Crypto | 1.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | VDS 6 Corket | 4 × 1.1 GHz | 1 GB | 8 GB SSD | US | Crypto | 1.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | VDS 8 Emi | 4 × 1.2 GHz | 1 GB | 16 GB SSD | US | Crypto | 1.00 $ |
| [ChangeIP](https://accsly.io/en/vps/hosting/changeip) | VPS $1 | 1 | 256 MB | 15 GB SSD | US, NL, DE, SG | Visa/MC, Crypto | 1.00 $ |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | VPS-512-KVM-US | 1 | 512 MB | 5 GB SSD | US | Crypto | 1.00 $ (total when paying for 6 mo (6.00 $)) |
| [TierHive](https://accsly.io/en/vps/hosting/tierhive) | Калькулятор (конфигурация по умолчанию) | 1 | 1 GB | 20 GB NVMe | NL, CA, DE, FR, US, GB… | — | 1.01 $ |
| [Hostodo](https://accsly.io/en/vps/hosting/hostodo) | KVM-512 | 1 × 2.6 GHz | 512 MB | 20 GB SSD | US | Visa/MC, PayPal, Crypto | 1.25 $ (total when paying for year (14.99 $)) |
| [BigBoxHost](https://accsly.io/en/vps/hosting/bigboxhost) | OpenVZ Box | 1 | 128 MB | 15 GB SSD | US, IT, IN | — | 1.33 $ (total when paying for year (15.95 $)) |
| [TNA Hosting](https://accsly.io/en/vps/hosting/tnahosting) | SSD KVM 1GB | 2 | 1 GB | 30 GB SSD | US | — | 1.33 $ |
| [ITL DC](https://accsly.io/en/vps/hosting/itldc) | HD VDS 100G | 1 | 512 MB | 100 GB HDD | BG, CZ, PL, US | WebMoney, PayPal, Visa/MC, Crypto | 1.49 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/usa?format=json

## When you need a VPS in the USA and which coast to choose

The USA is the largest VPS market by number of hosts and plans. But if you and your users are elsewhere — in Europe, for example — an American server is a deliberate choice rather than the default: it's far away, and latency is noticeably higher. It's justified when your users, partners or the services you depend on are in North America.

### When a US location makes sense

- **An audience in the USA and Canada.** A website, online store or game server for Americans should be in America; otherwise every page load loses 100 ms or more.
- **Working with American APIs and services.** Payment gateways, cloud APIs and ad dashboards respond faster if the server is close to them.
- **A US IP address** for testing websites, checking ads and regional search results.
- **Trading robots** connected to brokers in New York: ping to the broker affects order execution. There's a separate selection for this, [Forex VPS in New York](https://accsly.io/en/vps/forex-new-york).

### East coast or west coast

From Europe the east coast is noticeably closer than the west, with the central states somewhere in between. Hence a simple rule:

- an audience in Europe plus the USA — the east: [New York](https://accsly.io/en/vps/new-york), New Jersey, [Ashburn](https://accsly.io/en/vps/ashburn) in Virginia, home to one of the world's largest data centre clusters;
- the whole country evenly — the centre: Dallas, Chicago;
- an audience in the west or in Asia — the west: [Los Angeles](https://accsly.io/en/vps/los-angeles), Seattle, San Jose.

For a corporate VPN with a team in Europe, an American server almost always loses to a European one because of latency; take it if your offices or employees are in North America.

### Traffic and bandwidth

Many American plans come with a traffic cap of a few terabytes a month, and going over is billed separately or throttles the speed. Cheap offers sometimes have a shared port with no guaranteed bandwidth. If you serve files or video or have many users, compare the traffic cap and port speed, not just the price. Also check whether an IPv4 address is included in the price.

Another nuance is DDoS protection. American data centres are frequent targets of attacks, and many providers include basic filtering in the plan, while cheap offers may have none at all. For a game server or a public API this matters more than an extra gigabyte of memory. Finally, consider time zones: an American host's support works US business hours, which may be night-time where you are.

### Payment

American hosts most often take cards and PayPal, and a noticeable share also accept cryptocurrency. Be prepared for checks: some providers verify new customers and may ask for documents before activating the server. The "Payment" column in the table above shows the methods for each plan; prices are shown in your currency and sorted in ascending order.

## FAQ

### Which US coast is closer to Europe?

The east coast: from Europe the ping there is noticeably lower than to the west coast. For a website that's tolerable either way, but for games and voice calls the difference is noticeable.

### Which US city should I choose for a server?

For an audience in Europe and the eastern USA — New York or Ashburn; for the west coast and Asia — Los Angeles or Seattle; for even coverage of the country — Dallas or Chicago.

### Is a US VPS suitable for a corporate network with a team in Europe?

It will work, but latency is higher than with European servers. An American server for remote office access makes sense if your offices or employees are in North America.

### Do US VPS plans have traffic limits?

Many plans have a monthly cap of a few terabytes; if you exceed it, the speed is cut or you pay extra. Check the cap and port speed in the plan description.

### What is Ashburn and why are there so many servers there?

Ashburn, Virginia, is one of the world's largest concentrations of data centres. Many clouds and carriers have facilities there, so connectivity with American services is excellent.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS in Poland

Plans with servers in Poland. Compare price, processor, RAM and payment methods; cheapest first.

> Source: https://accsly.io/en/vps/poland · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 2,137, hosts: 122
- Price: from 0.49 $, a quarter below 28.99 $, median 100 $
- NVMe: 37 %, unlimited traffic: 23 %, hourly billing: 45 %
- RAM → price from: 1 GB — 0.49 $, 2 GB — 1.71 $, 4 GB — 3.42 $, 8 GB — 7.67 $, 16 GB — 12.79 $
- Cheapest hosts: [h2 NEXUS](https://accsly.io/en/vps/hosting/h2) — 1.00 $, [3HCloud](https://accsly.io/en/vps/hosting/3hcloud) — 1.50 $, [Servera](https://accsly.io/en/vps/hosting/servera) — 2.12 $, [Tiktalik.com](https://accsly.io/en/vps/hosting/tiktalik) — 2.42 $, [awHost](https://accsly.io/en/vps/hosting/awhost) — 3.06 $

## Cheapest plans — 2,137 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | STARDUST1-S | 1 × 2.1 GHz | 1 GB | — | FR, NL, PL | — | 0.49 $ |
| [uaVPS](https://accsly.io/en/vps/hosting/uavps) | VPS-PROMO | 1 | 512 MB | 10 GB NVMe | UA, PL, FR, DE, NL | — | 0.90 $ |
| [RuVPS](https://accsly.io/en/vps/hosting/ruvps) | VPS-0 | 1 | 768 MB | 7 GB NVMe | NL, PL, UA | Visa/MC, Crypto | 0.95 $ |
| [h2 NEXUS](https://accsly.io/en/vps/hosting/h2) | RED-PROMO | 1 × 3.3 GHz | 1 GB | 10 GB NVMe | DE, FI, PL | — | 1.00 $ |
| [TierHive](https://accsly.io/en/vps/hosting/tierhive) | Калькулятор (конфигурация по умолчанию) | 1 | 1 GB | 20 GB NVMe | NL, CA, DE, FR, US, GB… | — | 1.01 $ |
| [ReconV](https://accsly.io/en/vps/hosting/reconv) | LXC 512 MB | 1 | 512 MB | 6 GB NVMe | PL, FR | PayPal | 1.02 $ |
| [ITL DC](https://accsly.io/en/vps/hosting/itldc) | HD VDS 100G | 1 | 512 MB | 100 GB HDD | BG, CZ, PL, US | WebMoney, PayPal, Visa/MC, Crypto | 1.49 $ |
| [3HCloud](https://accsly.io/en/vps/hosting/3hcloud) | 1 GB 1 vCPU Shared Pool | 1 | 1 GB | — | PL, US, PH | Visa/MC | 1.50 $ |
| [TierHive](https://accsly.io/en/vps/hosting/tierhive) | STANDARD | 1 | 2 GB | 25 GB NVMe | NL, CA, DE, FR, US, GB… | — | 1.71 $ |
| [ReconV](https://accsly.io/en/vps/hosting/reconv) | LXC 1024 MB | 2 | 1 GB | 12 GB NVMe | PL, FR | PayPal | 2.04 $ |
| [Servera](https://accsly.io/en/vps/hosting/servera) | Linux VPS XS | 1 | 1 GB | 10 GB NVMe | SE, PL | Visa/MC | 2.12 $ (when paying for 2 years: 1.79 $/mo) |
| [eXone.pl](https://accsly.io/en/vps/hosting/exone) | Cloud VPS (конфигуратор, базовая конфигурация) | 1 | 512 MB | 30 GB SSD | PL | — | 2.30 $ |
| [Tiktalik.com](https://accsly.io/en/vps/hosting/tiktalik) | Tiktalik VPS Standard (1 GB) | 2 | 1 GB | 20 GB HDD | PL | Visa/MC, Invoice | 2.42 $ |
| [ProfitServer](https://accsly.io/en/vps/hosting/profitserver) | Storage-100 | 1 | 512 MB | 100 GB HDD | PL, US, BG, CZ | WebMoney, YooMoney, SBP | 2.79 $ (total when paying for 3 mo (8.36 $)) |
| [Evoxt Enterprise](https://accsly.io/en/vps/hosting/evoxt) | VM-0.5 (Standard) | 1 | 512 MB | 5 GB SSD | US, GB, CA, DE, PL, NL… | Visa/MC, PayPal, Crypto | 2.99 $ |
| [3HCloud](https://accsly.io/en/vps/hosting/3hcloud) | 2 GB 1 vCPU Shared Pool | 1 | 2 GB | — | PL, US, PH | Visa/MC | 3.00 $ |
| [awHost](https://accsly.io/en/vps/hosting/awhost) | Najtańszy do nauki | 1 | 1 GB | 10 GB NVMe | PL | PayPal | 3.06 $ |
| [Sprint Datacenter](https://accsly.io/en/vps/hosting/sprintdatacenter) | VPS.mini | 1 | 1 GB | 10 GB SSD | PL | Visa/MC, PayPal | 3.06 $ |
| [MiroHost](https://accsly.io/en/vps/hosting/mirohost) | Cloud E-00 | 1 | 1 GB | 10 GB NVMe | UA, PL | Visa/MC, Invoice | 3.17 $ |
| [NetGrid Host](https://accsly.io/en/vps/hosting/netgrid-host) | Starter | 1 | 1 GB | 10 GB NVMe | BG, CH, CZ, DE, ES, GR… | Visa/MC, Crypto, Invoice | 3.33 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/poland?format=json

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS in Kazakhstan

Plans with servers in Kazakhstan. Compare price, processor, RAM and payment methods; cheapest first.

> Source: https://accsly.io/en/vps/kazakhstan · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 134, hosts: 17
- Price: from 6.66 $, a quarter below 18.32 $, median 40.98 $
- NVMe: 54 %, unlimited traffic: 68 %, hourly billing: 22 %
- RAM → price from: 1 GB — 6.66 $, 2 GB — 7.74 $, 4 GB — 13.31 $, 8 GB — 23.13 $, 16 GB — 78.50 $
- Cheapest hosts: [CloudVPS.by](https://accsly.io/en/vps/hosting/cloudvps) — 6.66 $, [Hoster.kz](https://accsly.io/en/vps/hosting/hoster-kz) — 6.91 $, [Hostry.com](https://accsly.io/en/vps/hosting/hostry) — 7.00 $, [FirstVDS](https://accsly.io/en/vps/hosting/firstvds) — 7.74 $, [Megahost](https://accsly.io/en/vps/hosting/megahost) — 7.80 $

## Cheapest plans — 134 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [CloudVPS.by](https://accsly.io/en/vps/hosting/cloudvps) | Micro | 1 × 3.6 GHz | 1 GB | 15 GB NVMe | BY, RU, KZ, DE, NL, FI… | Visa/MC, MIR, Invoice | 6.66 $ (when paying for 3 years: 4.99 $/mo) |
| [Hoster.kz](https://accsly.io/en/vps/hosting/hoster-kz) | Cloud 1-1-25 | 1 | 1 GB | 25 GB NVMe | KZ | Visa/MC | 6.91 $ (yearly: 6.91 $/mo) |
| [Hostry.com](https://accsly.io/en/vps/hosting/hostry) | 1vCPU 1GB 20GB (группа 3) | 1 | 1 GB | 20 GB NVMe | GB, LU, AZ, FR, KZ, HU… | Crypto | 7.00 $ |
| [FirstVDS](https://accsly.io/en/vps/hosting/firstvds) | Старт Амстердам | 1 × 4.5 GHz | 2 GB | 40 GB NVMe | NL, KZ | Invoice, MIR, Visa/MC, SBP, YooMoney | 7.74 $ (yearly: 7.74 $/mo) |
| [Megahost](https://accsly.io/en/vps/hosting/megahost) | SSD-mini | 1 × 3.3 GHz | 1 GB | 20 GB SSD | KZ | Visa/MC, MIR, Invoice | 7.80 $ |
| [PS.kz](https://accsly.io/en/vps/hosting/ps-kz) | Basic-1 | 1 | 1 GB | 20 GB SSD | KZ | Invoice | 8.35 $ |
| [GOhost.kz](https://accsly.io/en/vps/hosting/gohost) | CLOUD VPS NVME 1vCPU/1GB | 1 | 1 GB | 10 GB NVMe | KZ | Visa/MC, MIR, PayPal, Invoice | 8.47 $ |
| [CloudVPS.by](https://accsly.io/en/vps/hosting/cloudvps) | Start | 1 × 3.6 GHz | 2 GB | 30 GB NVMe | BY, RU, KZ, DE, NL, FI… | Visa/MC, MIR, Invoice | 9.99 $ (when paying for 3 years: 7.50 $/mo) |
| [Onehost.kz](https://accsly.io/en/vps/hosting/onehost) | KVM-SSD-0 | 1 × 2.2 GHz | 1 GB | 10 GB SSD | KZ | Visa/MC, Invoice, PayPal | 10.02 $ |
| [Megahost](https://accsly.io/en/vps/hosting/megahost) | SSD-1 | 2 × 3.3 GHz | 1 GB | 40 GB SSD | KZ | Visa/MC, MIR, Invoice | 10.02 $ |
| [Hoster.kz](https://accsly.io/en/vps/hosting/hoster-kz) | Cloud 1-2-50 | 1 | 2 GB | 50 GB NVMe | KZ | Visa/MC | 10.70 $ (yearly: 10.69 $/mo) |
| [Beget](https://accsly.io/en/vps/hosting/beget) | Prime (Казахстан) | 2 | 2 GB | 30 GB NVMe | KZ | MIR, SBP, Invoice, YooMoney | 10.90 $ |
| [Goodhost](https://accsly.io/en/vps/hosting/goodhost) | VDS-B | 2 × 2.6 GHz | 1 GB | 20 GB SSD | KZ | Visa/MC, YooMoney, PayPal, Invoice | 10.91 $ |
| [Onehost.kz](https://accsly.io/en/vps/hosting/onehost) | NVMe-0 | 1 × 2.8 GHz | 1 GB | 10 GB NVMe | KZ | Visa/MC, Invoice, PayPal | 11.47 $ |
| [Serverspace.io](https://accsly.io/en/vps/hosting/serverspace-io) | Fixed 1 Core / 1 GB | 1 | 1 GB | 25 GB SSD | NL, US, CA, KZ, BR, AE | Visa/MC, PayPal, Crypto | 11.90 $ |
| [Hostry.com](https://accsly.io/en/vps/hosting/hostry) | 2vCPU 2GB 40GB (группа 3) | 2 | 2 GB | 40 GB NVMe | GB, LU, AZ, FR, KZ, HU… | Crypto | 12.01 $ |
| [Smart Host BD](https://accsly.io/en/vps/hosting/smarthostbd) | Kazakhstan VPS - 1 | 1 | 1 GB | 25 GB SSD | KZ | Visa/MC, PayPal, Crypto, Invoice | 12.01 $ |
| [Onehost.kz](https://accsly.io/en/vps/hosting/onehost) | KVM-SSD-1 | 1 × 2.2 GHz | 1 GB | 20 GB SSD | KZ | Visa/MC, Invoice, PayPal | 12.48 $ |
| [Smart Host BD](https://accsly.io/en/vps/hosting/smarthostbd) | Kazakhstan VPS - 2 | 2 | 2 GB | 40 GB SSD | KZ | Visa/MC, PayPal, Crypto, Invoice | 13.00 $ |
| [FirstVDS](https://accsly.io/en/vps/hosting/firstvds) | Разгон Амстердам | 2 × 4.5 GHz | 4 GB | 60 GB NVMe | NL, KZ | Invoice, MIR, Visa/MC, SBP, YooMoney | 13.31 $ (yearly: 13.31 $/mo) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/kazakhstan?format=json

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS in Turkey

Plans with servers in Turkey. Compare price, processor, RAM and payment methods; cheapest first.

> Source: https://accsly.io/en/vps/turkey · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 890, hosts: 74
- Price: from 0.58 $, a quarter below 10.58 $, median 24.89 $
- NVMe: 52 %, unlimited traffic: 43 %, hourly billing: 5 %
- RAM → price from: 1 GB — 0.70 $, 2 GB — 0.90 $, 4 GB — 2.40 $, 8 GB — 4.19 $, 16 GB — 8.27 $
- Cheapest hosts: [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 0.70 $, [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) — 1.67 $, [Priente Cloud](https://accsly.io/en/vps/hosting/prientecloud) — 2.28 $, [Keyubu](https://accsly.io/en/vps/hosting/keyubu) — 2.29 $, [Poyraz Hosting](https://accsly.io/en/vps/hosting/poyrazhosting-com) — 2.37 $

## Cheapest plans — 890 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM Turkey 256MB NAT | 1 | 256 MB | 5 GB SSD | TR | — | 0.58 $ (total when paying for year (6.99 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-512-LXC | 1 | 512 MB | 6 GB SSD | SG, HK, TW, JP, DE, TR… | Crypto | 0.64 $ (total when paying for year (7.70 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS1 Türkiye | 1 × 3.4 GHz | 1 GB | 15 GB SSD | TR | PayPal, Invoice | 0.70 $ |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-512-KVM | 1 | 512 MB | 6 GB SSD | SG, HK, JP, TW, DE, TR… | Crypto | 0.73 $ (total when paying for year (8.79 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS2 Türkiye | 2 × 3.4 GHz | 1 GB | 20 GB SSD | TR | PayPal, Invoice | 0.80 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS3 Türkiye | 2 × 3.4 GHz | 2 GB | 25 GB SSD | TR | PayPal, Invoice | 0.90 $ |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-1024-LXC | 2 | 1 GB | 8 GB SSD | SG, HK, TW, JP, DE, TR… | Crypto | 1.00 $ (total when paying for year (12.01 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-1024-KVM | 2 | 1 GB | 12 GB SSD | SG, HK, JP, TW, DE, TR… | Crypto | 1.17 $ (total when paying for year (14.00 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | VPS-512-KVM-TR | 1 | 512 MB | 6 GB SSD | TR | Crypto | 1.17 $ (total when paying for year (14.00 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS4 Türkiye | 3 × 3.4 GHz | 2 GB | 30 GB SSD | TR | PayPal, Invoice | 1.20 $ |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | VPS-1024-KVM-TR | 1 | 1 GB | 12 GB SSD | TR | Crypto | 1.67 $ (total when paying for year (20.00 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS5 Türkiye | 3 × 4.2 GHz | 3 GB | 45 GB SSD | TR | PayPal, Invoice | 2.00 $ |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | VPS-2048-KVM-TR | 2 | 2 GB | 24 GB SSD | TR | Crypto | 2.08 $ (total when paying for year (25.00 $)) |
| [Priente Cloud](https://accsly.io/en/vps/hosting/prientecloud) | e.nano | 1 | 1 GB | 20 GB SSD | TR | Visa/MC | 2.28 $ (when paying for year: 2.06 $/mo) |
| [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | VPS L-TR 1GB | 1 | 1 GB | 20 GB NVMe | TR | Visa/MC | 2.29 $ (yearly: 2.29 $/mo) |
| [Poyraz Hosting](https://accsly.io/en/vps/hosting/poyrazhosting-com) | YPH1 | 1 × 4.0 GHz | 1 GB | 10 GB SSD | TR | Invoice | 2.37 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS6 Türkiye | 4 × 4.2 GHz | 4 GB | 50 GB SSD | TR | PayPal, Invoice | 2.40 $ |
| [Voyar Cloud](https://accsly.io/en/vps/hosting/voyar) | CV-10 | 2 | 2 GB | 40 GB NVMe | TR | Invoice | 2.45 $ |
| [Teknosos.com.tr](https://accsly.io/en/vps/hosting/teknosos-com) | Ekonomik Sunucu 1 | 1 | 1 GB | 40 GB NVMe | TR | Invoice | 2.51 $ (yearly: 2.51 $/mo) |
| [Hostlab.com](https://accsly.io/en/vps/hosting/hostlab) | SSD VDS (Paket 1) | 1 | 1 GB | 20 GB SSD | TR | Visa/MC, Invoice | 2.59 $ (when paying for year: 2.16 $/mo) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/turkey?format=json

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS in Latvia

Plans with servers in Latvia. Compare price, processor, RAM and payment methods; cheapest first.

> Source: https://accsly.io/en/vps/latvia · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 355, hosts: 33
- Price: from 1.67 $, a quarter below 16.48 $, median 44.76 $
- NVMe: 72 %, unlimited traffic: 39 %, hourly billing: 12 %
- RAM → price from: 1 GB — 1.67 $, 2 GB — 3.34 $, 4 GB — 5.58 $, 8 GB — 11.18 $, 16 GB — 22.37 $
- Cheapest hosts: [HostVDS](https://accsly.io/en/vps/hosting/hostvds) — 1.67 $, [NetGrid Host](https://accsly.io/en/vps/hosting/netgrid-host) — 3.33 $, [ITL DC](https://accsly.io/en/vps/hosting/itldc) — 4.47 $, [Unlimit Space](https://accsly.io/en/vps/hosting/unlimit-space) — 4.54 $, [Hosting.Energy](https://accsly.io/en/vps/hosting/hosting-energy) — 4.80 $

## Cheapest plans — 355 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 1 | 1 | 1 GB | 10 GB NVMe | FR, LV, NL, FI | Visa/MC, Crypto | 1.67 $ |
| [NetGrid Host](https://accsly.io/en/vps/hosting/netgrid-host) | Starter | 1 | 1 GB | 10 GB NVMe | BG, CH, CZ, DE, ES, GR… | Visa/MC, Crypto, Invoice | 3.33 $ |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 2 | 1 | 2 GB | 20 GB NVMe | FR, LV, NL, FI | Visa/MC, Crypto | 3.34 $ |
| [Friend Hosting](https://accsly.io/en/vps/hosting/friendhosting) | Micro+ NVMe | 1 | 512 MB | 10 GB NVMe | GR, NL, BG, ES, RO, DE… | Visa/MC, PayPal | 4.47 $ |
| [ITL DC](https://accsly.io/en/vps/hosting/itldc) | NVMe VDS 1G | 1 | 1 GB | 10 GB NVMe | NL, GR, ES, BG, LV, CZ… | WebMoney, PayPal, Visa/MC, Crypto | 4.47 $ |
| [Unlimit Space](https://accsly.io/en/vps/hosting/unlimit-space) | 1G | 1 | 1 GB | 10 GB SSD | NL, LV, BG, CZ, PL, CH… | Visa/MC | 4.54 $ |
| [Justhost](https://accsly.io/en/vps/hosting/justhost) | NVMe VPS IPv6 | 1 | 512 MB | 5 GB NVMe | AL, AT, BG, CA, CH, CZ… | MIR, Visa/MC, PayPal, YooMoney, Invoice | 4.65 $ (when paying for 3 years: 2.79 $/mo) |
| [Hosting.Energy](https://accsly.io/en/vps/hosting/hosting-energy) | VDS 1G | 1 × 3.5 GHz | 1 GB | 10 GB SSD | NL, CH, PL, LV, CZ, BG… | Visa/MC, MIR, WebMoney, PayPal, Crypto | 4.80 $ |
| [Host-Stage](https://accsly.io/en/vps/hosting/host-stage) | Unmanaged Linux VPS Level 1 | 1 × 3.0 GHz | 1 GB | 20 GB SSD | SG, AE, IN, JP, US, DE… | Crypto | 4.95 $ |
| [ML CLOUD](https://accsly.io/en/vps/hosting/ml) | ML25 | 1 | 1 GB | 25 GB NVMe | RU, LV, NL, PL, DE | — | 4.99 $ |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | High Frequency 1 | 1 | 2 GB | 30 GB NVMe | LV | Visa/MC, Crypto | 5.58 $ |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | Highload 1 | 1 | 4 GB | 30 GB NVMe | FR, LV, NL, FI | Visa/MC, Crypto | 5.58 $ |
| [Serva](https://accsly.io/en/vps/hosting/serva-one) | Micro | 1 | 1 GB | 10 GB NVMe | NL, DE, PL, LV, CH, US… | Visa/MC, Invoice, Crypto | 5.58 $ |
| [Friend Hosting](https://accsly.io/en/vps/hosting/friendhosting) | Start NVMe | 1 | 1 GB | 10 GB NVMe | GR, NL, BG, ES, RO, DE… | Visa/MC, PayPal | 5.58 $ |
| [YourServer](https://accsly.io/en/vps/hosting/yourserver) | Linux VPS 1GB | 1 | 1 GB | 10 GB SSD | SE, LV | PayPal, Visa/MC, Crypto | 5.60 $ |
| [Veesp](https://accsly.io/en/vps/hosting/veesp) | VM 1 | 1 | 1 GB | 20 GB NVMe | LV, NL, SE | — | 5.60 $ |
| [Hostry.com](https://accsly.io/en/vps/hosting/hostry) | 1vCPU 1GB (группа 1) | 1 | 1 GB | 10 GB NVMe | BG, CZ, CH, LV, US, PL… | Crypto | 6.00 $ |
| [Justhost](https://accsly.io/en/vps/hosting/justhost) | Sirius IPv6 | 1 | 1 GB | 20 GB NVMe | AL, AT, BG, CA, CH, CZ… | MIR, Visa/MC, PayPal, YooMoney, Invoice | 6.02 $ (when paying for 3 years: 3.61 $/mo) |
| [Justhost](https://accsly.io/en/vps/hosting/justhost) | NVMe VPS Avior IPv6 only | 1 | 1 GB | 5 GB NVMe | AL, AT, BG, CA, CH, CZ… | MIR, Visa/MC, PayPal, YooMoney, Invoice | 6.03 $ (when paying for 3 years: 3.62 $/mo) |
| [Justhost](https://accsly.io/en/vps/hosting/justhost) | Supernova | 1 | 1 GB | 10 GB NVMe | AL, AT, BG, CA, CH, CZ… | MIR, Visa/MC, PayPal, YooMoney, Invoice | 6.04 $ (total when paying for 3 mo (18.13 $)) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/latvia?format=json

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS in Europe

Servers in the Netherlands, Germany, Finland, Poland and other European countries. Low latency across Europe and a wide choice of plans.

> Source: https://accsly.io/en/vps/europe · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 15,779, hosts: 1,206
- Price: from 0.42 $, a quarter below 19.03 $, median 48.12 $
- NVMe: 44 %, unlimited traffic: 27 %, hourly billing: 24 %
- RAM → price from: 1 GB — 0.49 $, 2 GB — 0.80 $, 4 GB — 1.60 $, 8 GB — 3.19 $, 16 GB — 6.38 $
- Countries: Germany (5921), Netherlands (5651), USA (5511), United Kingdom (4811), Singapore (2895), France (2803)
- Cheapest hosts: [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 0.80 $, [V.PS](https://accsly.io/en/vps/hosting/v) — 0.93 $, [h2 NEXUS](https://accsly.io/en/vps/hosting/h2) — 1.00 $, [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 1.33 $, [ChunkServ](https://accsly.io/en/vps/hosting/chunkserve) — 1.45 $

## Cheapest plans — 15,779 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-II 384 Europe | 1 × 3.1 GHz | 384 MB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 0.42 $ (total when paying for 6 mo (2.50 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ NL 256MB NAT | 1 | 256 MB | 5 GB SSD | NL | — | 0.42 $ (total when paying for year (4.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ Germany 256MB NAT | 1 | 256 MB | 5 GB SSD | DE | — | 0.44 $ (total when paying for year (5.31 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ Sweden 256MB NAT | 1 | 256 MB | 5 GB SSD | SE | — | 0.46 $ (total when paying for year (5.50 $)) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | STARDUST1-S | 1 × 2.1 GHz | 1 GB | — | FR, NL, PL | — | 0.49 $ |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM UK 256 MB NAT | 1 | 256 MB | 5 GB SSD | GB | — | 0.58 $ (total when paying for year (6.99 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-512-LXC | 1 | 512 MB | 6 GB SSD | SG, HK, TW, JP, DE, TR… | Crypto | 0.64 $ (total when paying for year (7.70 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ DE 512 MB NAT | 1 | 512 MB | 5 GB SSD | DE | — | 0.67 $ (total when paying for year (8.00 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-512-KVM | 1 | 512 MB | 6 GB SSD | SG, HK, JP, TW, DE, TR… | Crypto | 0.73 $ (total when paying for year (8.79 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS1 Fransa | 1 × 4.0 GHz | 2 GB | 15 GB SSD | FR | PayPal, Invoice | 0.80 $ |
| [EUGameHost](https://accsly.io/en/vps/hosting/eugamehost) | Nano Edge | 1 | 512 MB | 5 GB NVMe | GB | PayPal, Visa/MC | 0.86 $ (when paying for year: 0.67 $/mo) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ NL 1024MB NAT | 1 | 1 GB | 5 GB SSD | NL | — | 0.86 $ (total when paying for year (10.30 $)) |
| [uaVPS](https://accsly.io/en/vps/hosting/uavps) | VPS-PROMO | 1 | 512 MB | 10 GB NVMe | UA, PL, FR, DE, NL | — | 0.90 $ |
| [V.PS](https://accsly.io/en/vps/hosting/v) | Nano | 1 | 1 GB | 15 GB SSD | NL, DE | PayPal, Visa/MC, Invoice | 0.93 $ (total when paying for year (11.13 $)) |
| [RuVPS](https://accsly.io/en/vps/hosting/ruvps) | VPS-0 | 1 | 768 MB | 7 GB NVMe | NL, PL, UA | Visa/MC, Crypto | 0.95 $ |
| [Privex](https://accsly.io/en/vps/hosting/privex) | VNANO-SE-SSD | 1 | 256 MB | 5 GB SSD | SE | Crypto, Invoice | 0.99 $ |
| [Jink Host](https://accsly.io/en/vps/hosting/jink) | Dirt | 1 | 512 MB | 20 GB NVMe | US, NL | Visa/MC, PayPal, Crypto | 1.00 $ (total when paying for 3 mo (3.00 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-1024-LXC | 2 | 1 GB | 8 GB SSD | SG, HK, TW, JP, DE, TR… | Crypto | 1.00 $ (total when paying for year (12.01 $)) |
| [h2 NEXUS](https://accsly.io/en/vps/hosting/h2) | RED-PROMO | 1 × 3.3 GHz | 1 GB | 10 GB NVMe | DE, FI, PL | — | 1.00 $ |
| [ChangeIP](https://accsly.io/en/vps/hosting/changeip) | VPS $1 | 1 | 256 MB | 15 GB SSD | US, NL, DE, SG | Visa/MC, Crypto | 1.00 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/europe?format=json

## How to choose a country for a VPS in Europe

Europe offers the widest choice of virtual servers: hundreds of hosts, dozens of countries, plans from the simplest to the most powerful. But "VPS in Europe" isn't one place — the conditions vary a lot. The country determines ping, laws, how complaints are handled and price. Below is how to narrow the choice down to two or three options.

### Latency

The rule is simple: the closer the server is to you and your users, the lower the ping. A rough map of the continent:

- **North and the Baltics** — Finland, Estonia, Latvia, Lithuania; selections — [Finland](https://accsly.io/en/vps/finland) and [the Baltics](https://accsly.io/en/vps/baltics).
- **Central hubs** — Poland, Germany, the Netherlands, Czechia, Sweden. Most of the continent's large data centres are here.
- **West** — France, the United Kingdom, Switzerland, Austria.
- **South** — Spain, Italy, Portugal, Greece.

Actual numbers depend on your provider's routing: sometimes traffic to a neighbouring country goes via Frankfurt. Before buying, check the ping to the host's test IP.

### Laws and rules

GDPR applies in every EU country, but the strictness of the supervisory authorities differs. Germany and the Netherlands are known for reacting quickly to complaints from rights holders and about spam. Switzerland isn't in the EU; it has its own data protection law and a reputation as a neutral jurisdiction, but prices there are higher. Moldova, Serbia and the United Kingdom have their own rules; for a project this is more often a question of the host's policy than of the law.

### Prices

The most affordable plans are usually in countries with large hosting clusters — Germany, the Netherlands, Finland — and in Eastern Europe: Bulgaria, Romania, Moldova. A list of countries in the east of the continent is on the [VPS in Eastern Europe](https://accsly.io/en/vps/eastern-europe) page. Switzerland, Scandinavia and the United Kingdom are the most expensive. Sorting the table above by price will immediately show where it's cheaper right now.

When comparing prices, look beyond the monthly fee. One host includes an IPv4 address, unlimited traffic and snapshots in the price, another charges for all of these separately, and a European VDS that looks cheap at first ends up costing more. Another factor is the exchange rate: almost all European plans are billed in euros, so the amount in your currency changes from month to month.

### A short selection algorithm

1. Need the lowest ping — pick the country nearest to you or your users.
2. Need maximum connectivity and choice — Germany or [the Netherlands](https://accsly.io/en/vps/netherlands).
3. Lowest price — Eastern Europe or the large clusters in Germany.
4. An audience in a specific country — a server in that country or a neighbouring one.
5. Check the payment methods: hosts differ in which cards and wallets they accept, and many also take cryptocurrency.

We collect plans from the hosts' own websites and update them every hour, and the "Payment" column shows which methods each of them accepts.

## FAQ

### Which European country gives the lowest ping?

The one closest to you. For most of the continent, the central hubs — Germany and the Netherlands — give short routes. The actual value depends on your provider's routing.

### Where in Europe are the cheapest VPS?

Usually in Germany, the Netherlands and Eastern Europe — Bulgaria, Romania, Moldova. Sort the table by price to see current offers.

### What should I choose for a site with a European audience?

Germany or the Netherlands: from there routes to almost every EU country are short. For an audience in one country, a server in that country is better.

### Does GDPR apply to a VPS in Europe?

In EU countries hosts operate under GDPR, and if you process Europeans' data, the regulation applies to you as well. Switzerland, the United Kingdom and Serbia apply their own data laws.

### Do European hosts differ in how they handle complaints?

Yes. In Germany and the Netherlands complaints about spam and copyright infringement get a quick response, up to the server being switched off. The terms are always described in the specific host's rules.

### Is the United Kingdom included in European VPS?

Geographically yes, and it's included in the selection. But the country is outside the EU, so the British version of the data protection law applies there.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS in the CIS

Servers in Kazakhstan, Uzbekistan, Armenia, Moldova and other CIS countries.

> Source: https://accsly.io/en/vps/cis · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 638, hosts: 64
- Price: from 1.70 $, a quarter below 20.58 $, median 43.44 $
- NVMe: 40 %, unlimited traffic: 49 %, hourly billing: 9 %
- RAM → price from: 1 GB — 3.27 $, 2 GB — 3.27 $, 4 GB — 6.00 $, 8 GB — 14.00 $, 16 GB — 18.73 $
- Countries: USA (195), Moldova (179), Netherlands (145), Kazakhstan (134), Germany (133), United Kingdom (106)
- Cheapest hosts: [HytHost](https://accsly.io/en/vps/hosting/hythost) — 3.27 $, [UltraVPS.eu](https://accsly.io/en/vps/hosting/ultravps) — 3.36 $, [AvenaCloud.com](https://accsly.io/en/vps/hosting/avenacloud) — 3.91 $, [Sprintbox](https://accsly.io/en/vps/hosting/sprintbox) — 4.85 $, [VIP.hosting](https://accsly.io/en/vps/hosting/vip-hosting) — 5.00 $

## Cheapest plans — 638 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Sprintbox](https://accsly.io/en/vps/hosting/sprintbox) | Студент | 1 | 600 MB | 7 GB NVMe | RU, NL, DE, US, BY, AM… | — | 1.70 $ |
| [Sprintbox](https://accsly.io/en/vps/hosting/sprintbox) | Джун 10 | 1 | 600 MB | 10 GB NVMe | RU, NL, DE, US, BY, AM… | — | 2.67 $ |
| [Revenue Server](https://accsly.io/en/vps/hosting/revenueserver) | Lifetime VPS | 1 | 1 GB | 12 GB SSD | NL, MD | Crypto, PayPal, Visa/MC, Invoice, WebMoney | 2.75 $ (total when paying for 3 years (99.00 $)) |
| [HytHost](https://accsly.io/en/vps/hosting/hythost) | VPS 0 | 1 | 2 GB | 10 GB NVMe | MD | Visa/MC, PayPal | 3.27 $ |
| [UltraVPS.eu](https://accsly.io/en/vps/hosting/ultravps) | Storage-250 | 1 | 512 MB | 250 GB SSD | DE, NL, US, GB, LT, MD | — | 3.36 $ |
| [UltraVPS.eu](https://accsly.io/en/vps/hosting/ultravps) | UltraKVM-30 | 1 | 1.5 GB | 30 GB HDD | DE, NL, US, GB, LT, MD | — | 3.36 $ |
| [AvenaCloud.com](https://accsly.io/en/vps/hosting/avenacloud) | KVM VPS/VDS 10 | 1 | 1 GB | 10 GB SSD | MD | Visa/MC, PayPal, WebMoney, Crypto | 3.91 $ |
| [MivoCloud](https://accsly.io/en/vps/hosting/mivocloud) | Hourly Cloud (мин. 1 vCPU/0.5 ГБ/10 ГБ) | 1 | 512 MB | 10 GB NVMe | US, GB, DE, MD | PayPal, Crypto, Visa/MC, Invoice | 4.58 $ |
| [HytHost](https://accsly.io/en/vps/hosting/hythost) | VPS 1 | 2 | 2 GB | 20 GB NVMe | MD | Visa/MC, PayPal | 4.70 $ |
| [Sprintbox](https://accsly.io/en/vps/hosting/sprintbox) | Джун 20 | 1 | 1 GB | 20 GB NVMe | RU, NL, DE, US, BY, AM… | — | 4.85 $ |
| [VIP.hosting](https://accsly.io/en/vps/hosting/vip-hosting) | Tier 1 [MD] | 2 | 2 GB | 30 GB NVMe | MD | Crypto, SBP | 5.00 $ |
| [UltraVPS.eu](https://accsly.io/en/vps/hosting/ultravps) | Cloud-30 | 2 | 2 GB | 30 GB SSD | DE, NL, US, GB, LT, MD | — | 5.04 $ |
| [AvenaCloud.com](https://accsly.io/en/vps/hosting/avenacloud) | KVM VPS/VDS 20 | 1 | 2 GB | 20 GB SSD | MD | Visa/MC, PayPal, WebMoney, Crypto | 5.60 $ |
| [MivoCloud](https://accsly.io/en/vps/hosting/mivocloud) | SSD KVM VPS S1 | 1 | 2 GB | 30 GB SSD | US, MD | PayPal, Crypto, Visa/MC, Invoice | 5.60 $ |
| [UltraVPS.eu](https://accsly.io/en/vps/hosting/ultravps) | Storage-500 | 1 | 1 GB | 500 GB SSD | DE, NL, US, GB, LT, MD | — | 5.60 $ |
| [Trabia](https://accsly.io/en/vps/hosting/trabia) | VDS-1G | 1 | 1 GB | 25 GB SSD | MD | — | 5.60 $ |
| [AvaHost](https://accsly.io/en/vps/hosting/ava-hosting) | VPS One | 1 | 2 GB | 25 GB NVMe | MD | Visa/MC, PayPal, WebMoney, Crypto | 5.60 $ (when paying for year: 4.76 $/mo) |
| [MivoCloud](https://accsly.io/en/vps/hosting/mivocloud) | NVMe VPS N1 | 1 | 2 GB | 30 GB NVMe | US, GB, DE, FR, MD | PayPal, Crypto, Visa/MC, Invoice | 5.71 $ |
| [VIP.hosting](https://accsly.io/en/vps/hosting/vip-hosting) | Tier 2 [MD] | 2 | 4 GB | 50 GB NVMe | MD | Crypto, SBP | 6.00 $ |
| [EDBB](https://accsly.io/en/vps/hosting/edbb) | STARTER Core | 1 | 1 GB | 20 GB SSD | AE, AT, AU, BE, BG, CA… | Visa/MC, Crypto | 6.14 $ (when paying for year: 5.63 $/mo) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/cis?format=json

## How to choose a country for a VPS in the CIS

This selection covers servers in Kazakhstan, Uzbekistan, Kyrgyzstan, Armenia, Azerbaijan, Georgia, Belarus and Moldova; Russian locations have their own page, [VPS in Russia](https://accsly.io/en/vps/russia). These countries have more in common than it seems: Russian-language support at many hosts, routes to Russia that don't pass through Western Europe, and their own personal data laws, which often require citizens' data to be kept inside the country. They differ in market size, latency and payment methods, so the place to start is the question of where your users live.

### Three groups of countries by task

- **Central Asia**: Kazakhstan, Uzbekistan, Kyrgyzstan. Servers are rented mainly for a local audience and to meet data storage requirements. The region's largest market is [Kazakhstan](https://accsly.io/en/vps/kazakhstan), where the main locations are in Almaty; Uzbekistan and Kyrgyzstan have a noticeably smaller choice.
- **The South Caucasus**: Armenia, Georgia, Azerbaijan. Small markets with data centres in the capitals, Yerevan, Tbilisi and Baku. A server here is needed by companies with offices and customers in these countries; a cable runs from Georgia to Bulgaria along the bed of the Black Sea, giving the region a separate route to Europe.
- **The west of the region**: Belarus and Moldova. Minsk is close to Moscow in latency and convenient for a Belarusian audience. Moldova stands out because Chisinau is home to hosts that sell servers worldwide, so there are more plans than you'd expect from the size of the country.

### Latency from Moscow

Benchmarks over a direct route: Minsk 10–20 ms, Chisinau 30–45 ms, Yerevan, Tbilisi and Baku 40–70 ms, Almaty 50–80 ms, Tashkent 60–90 ms, Bishkek 70–100 ms. These are general ranges: real latency depends on your provider and on which nodes the host exchanges traffic through. Some traffic from Central Asia and the South Caucasus goes through Russia, so routes from Moscow are usually shorter than from Europe. Test the host's IP or looking glass from your own connection before paying for a long period.

For a site aimed at a Russian audience, a server in the CIS rarely beats Moscow. It makes sense when the users are in the country itself or when you need a server under a specific jurisdiction.

### Data laws: each country has its own

There is no single rule for the region. In Kazakhstan and Uzbekistan the law explicitly requires databases with citizens' personal data to be stored inside the country, the equivalent of Russia's personal data law 152-FZ. Belarus has had a Law on Personal Data Protection with a dedicated supervisory body since 2021. Armenia, Azerbaijan, Kyrgyzstan and Moldova have their own personal data laws, and Georgia and Moldova are bringing their regulation closer to the European GDPR. If a project serves customers in several countries, one location may not be enough: each country's database has to be kept wherever its law requires.

For data of Russian citizens, 152-FZ still applies: the primary database must be located in Russia, and a server in a neighbouring country doesn't replace that. The selection for this requirement is VPS for 152-FZ.

### Typical tasks

- online shops, delivery services and online schools for residents of a specific country;
- accounting systems and 1C for a branch of a Russian company;
- a corporate VPN for staff working in several countries of the region;
- a backup of a project in another jurisdiction with short latency to Russia.

Before ordering, check where the server physically is: some plans with a neighbouring country's flag are actually located in another state, and for data localisation requirements that is the decisive question. Also check the virtualisation type (Docker and a corporate VPN need KVM), the port bandwidth towards foreign networks and whether a dedicated IPv4 address is included. In small markets external links are more expensive, and "unlimited" sometimes means full speed only within the country.

### Payment and documents

Local hosts usually invoice in the national currency (tenge, som, dram, lari, manat, Belarusian roubles or lei) and primarily accept cards from their own banks. Few accept Russian Mir cards, and SBP fast payments are even rarer; some hosts accept international cards and cryptocurrency as a payment method, and companies pay by invoice. Several Russian providers have locations in Kazakhstan, Uzbekistan, Armenia and Belarus, and with them you can pay in roubles and receive closing documents. The "Payment" column in the table above shows the methods for each plan, with prices converted to roubles. Keep the exchange rate in mind: if the invoice is in local currency, the renewal amount changes.

## FAQ

### Which countries are in the CIS VPS selection?

Kazakhstan, Uzbekistan, Kyrgyzstan, Armenia, Azerbaijan, Georgia, Belarus and Moldova. Servers in Russia are collected on a separate page.

### Which CIS country has the lowest ping from Moscow?

Belarus: Minsk is usually 10–20 ms away over a direct route. Next come Moldova and the South Caucasus, and the highest latency is to Central Asia.

### In which CIS countries must citizens' data be stored inside the country?

A direct localisation requirement exists in Kazakhstan and Uzbekistan, among others. Rules differ elsewhere, so check them with a local lawyer for each country.

### Do hosts in the CIS offer support in Russian?

Most local providers do, especially in Kazakhstan, Kyrgyzstan, Belarus and Moldova. In Georgia and Azerbaijan Russian is less common, but still widespread.

### Can I store Russian users' data on a server in the CIS?

Under 152-FZ the primary database with Russian citizens' data must be located in Russia. A server in a neighbouring country can be used for a backup or for other tasks.

### Is a VPS in the CIS suitable for a corporate network?

Yes, if your staff or offices are in these countries. Put the gateway close to most of the users and choose KVM virtualisation.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS in Asia

Servers in Hong Kong, Singapore, Japan, Turkey and other Asian countries — for projects with an audience in the region.

> Source: https://accsly.io/en/vps/asia · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 8,893, hosts: 572
- Price: from 0.58 $, a quarter below 20.10 $, median 53.27 $
- NVMe: 33 %, unlimited traffic: 25 %, hourly billing: 23 %
- RAM → price from: 1 GB — 0.70 $, 2 GB — 0.90 $, 4 GB — 2.40 $, 8 GB — 3.46 $, 16 GB — 3.46 $
- Countries: USA (3988), Singapore (3571), India (2862), Germany (2837), United Kingdom (2816), Japan (2386)
- Cheapest hosts: [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 0.70 $, [HostVDS](https://accsly.io/en/vps/hosting/hostvds) — 0.99 $, [3HCloud](https://accsly.io/en/vps/hosting/3hcloud) — 1.50 $, [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) — 1.67 $, [Sindad](https://accsly.io/en/vps/hosting/sindad) — 1.71 $

## Cheapest plans — 8,893 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM India 256MB NAT | 1 | 256 MB | 5 GB SSD | IN | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM SG 400MB NAT | 1 | 400 MB | 5 GB NVMe | SG | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM Turkey 256MB NAT | 1 | 256 MB | 5 GB SSD | TR | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ HK 256MB NAT | 1 | 256 MB | 5 GB SSD | HK | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ Japan 256MB NAT | 1 | 256 MB | 5 GB SSD | JP | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ Pakistan 256MB NAT | 1 | 256 MB | 5 GB SSD | PK | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ SG 400MB NAT (KVM) | 1 | 400 MB | 5 GB SSD | SG | — | 0.58 $ (total when paying for year (6.99 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-512-LXC | 1 | 512 MB | 6 GB SSD | SG, HK, TW, JP, DE, TR… | Crypto | 0.64 $ (total when paying for year (7.70 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS1 Türkiye | 1 × 3.4 GHz | 1 GB | 15 GB SSD | TR | PayPal, Invoice | 0.70 $ |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-512-KVM | 1 | 512 MB | 6 GB SSD | SG, HK, JP, TW, DE, TR… | Crypto | 0.73 $ (total when paying for year (8.79 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS2 Türkiye | 2 × 3.4 GHz | 1 GB | 20 GB SSD | TR | PayPal, Invoice | 0.80 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS3 Türkiye | 2 × 3.4 GHz | 2 GB | 25 GB SSD | TR | PayPal, Invoice | 0.90 $ |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ Taiwan 256MB NAT | 1 | 256 MB | 5 GB SSD | TW | — | 0.92 $ (total when paying for year (10.99 $)) |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 1 | 1 | 1 GB | 10 GB NVMe | US, HK | Visa/MC, Crypto | 0.99 $ |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-1024-LXC | 2 | 1 GB | 8 GB SSD | SG, HK, TW, JP, DE, TR… | Crypto | 1.00 $ (total when paying for year (12.01 $)) |
| [ChangeIP](https://accsly.io/en/vps/hosting/changeip) | VPS $1 | 1 | 256 MB | 15 GB SSD | US, NL, DE, SG | Visa/MC, Crypto | 1.00 $ |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | VPS-512-KVM-Lite-HK | 1 | 512 MB | 5 GB SSD | HK | Crypto | 1.00 $ (total when paying for year (12.01 $)) |
| [TierHive](https://accsly.io/en/vps/hosting/tierhive) | Калькулятор (конфигурация по умолчанию) | 1 | 1 GB | 20 GB NVMe | NL, CA, DE, FR, US, GB… | — | 1.01 $ |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ Japan 1024MB NAT | 1 | 1 GB | 5 GB SSD | JP | — | 1.02 $ (total when paying for year (12.30 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ SG 512 MB NAT | 1 | 512 MB | 5 GB SSD | SG | — | 1.17 $ (total when paying for year (13.99 $)) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/asia?format=json

## VPS in Asia: which hub to choose for your audience and local laws

Asia is not one market but several network regions. Tokyo and Mumbai are about 6,700 km apart, nearly three times the distance from Moscow to London, and a single server cannot serve Japan, Indonesia and India equally well. So a VPS in Asia is chosen not by country but by the hub closest to your users: Singapore, Hong Kong, Tokyo, Mumbai and a few growing locations around them.

### Map of hubs and latency

- **[Singapore](https://accsly.io/en/vps/singapore)** is the centre of Southeast Asia. Kuala Lumpur and Jakarta are 10–20 ms away, Bangkok about 30 ms, Hong Kong 30–40 ms, Chennai and Mumbai 30–70 ms. If your audience is spread across the whole region, this is usually where you start.
- **[Hong Kong](https://accsly.io/en/vps/hong-kong)** and Taiwan are the approach to mainland China. Latency to Shenzhen can be a few milliseconds, but quality depends entirely on the route: ordinary transit through congested gateways loses packets in the evening, while premium routes from Chinese carriers (such as CN2 GIA) cost noticeably more.
- **[Japan](https://accsly.io/en/vps/japan)** and South Korea cover Northeast Asia. Tokyo to Seoul is about 30–35 ms, and this is also the shortest path across the Pacific to the US west coast, about 100 ms.
- **[India](https://accsly.io/en/vps/india)** is a separate large market with its own cable landing stations in Mumbai and Chennai. Distances inside the country are large, and a server in Mumbai is not always closer than a Singapore one for users in the east of the country.
- **Vietnam, Indonesia, Malaysia, Thailand, the Philippines** are local locations for their own country. For neighbours, their connectivity is usually worse than Singapore's.

From Moscow any of these hubs is 130–250 ms away, and from Western Europe typically 150–280 ms, so for a European or Russian audience an Asian server is not needed: a European one will be closer. From the US west coast, Tokyo and Hong Kong are roughly 100–150 ms. Turkey is also listed under Asia in the catalogue, but in network terms it is more an extension of Europe: from Moscow to Istanbul is 40–70 ms; details are on the [VPS in Turkey](https://accsly.io/en/vps/turkey) page.

### Data laws: what concerns the server owner

- **Mainland China** requires ICP registration for a website running on a Chinese server and identification of the account owner; the PIPL personal data law restricts exporting data out of the country. So for a Chinese audience without a local legal entity, Hong Kong or Japan is the more common choice.
- **India.** A 2022 CERT-In directive obliges VPS and cloud providers to keep customer details (name, contacts, addresses, purpose of use) for five years. Because of this, Indian hosts more often ask you to verify your identity. The Digital Personal Data Protection Act (DPDP Act) also applies.
- **Vietnam and Indonesia** require certain categories of data to be stored in the country: for government systems, financial services and some online services. For an ordinary website this is rarely critical; for fintech it is the first thing to check.
- **Singapore, Japan, South Korea** regulate personal data with the PDPA, APPI and PIPA. They are close to GDPR in logic, and transfers abroad are allowed under conditions, but hosts here are strict about spam and copyright complaints.

### Prices and traffic

The main difference between Asian and European plans is the cost of bandwidth. Transit in Singapore, Hong Kong and Tokyo is several times more expensive than in Frankfurt or Amsterdam, so budget plans usually come with a traffic quota of 1–2 TB and overage charges, while "unlimited" is rarer and often comes with a 100 Mbit/s port. Before ordering, check:

- whether inbound traffic is counted or only outbound, and how much overage costs;
- whether an optimised route to China is included in the price, if you need it;
- ping and mtr from a test IP to your users' networks, especially in Vietnam, Indonesia and India, where connectivity quality varies a lot between hosts.

Japan and Korea are usually more expensive than Singapore, India and Vietnam cheaper, but with a wide spread in network quality. Asian hosts rarely accept Russian Mir cards; international cards, PayPal or cryptocurrency are more commonly available, and the methods for each plan are shown in the "Payment" column.

### Where to start

If a project is only entering the region's market, a sensible setup is one VPS in Singapore or Tokyo plus a CDN for static content. Separate servers in India or China are worth adding once a noticeable share of users comes from there and it is clear which carriers they mainly use. Mind the time zones too: a maintenance window convenient in European or Moscow time falls in the Singapore working day, so plan updates and reboots for the local night. For APIs and bots that need an Asian IP address, check its geolocation in several databases right after ordering: addresses recently moved from another region are sometimes still listed under their previous country.

## FAQ

### Where is the best place for a server for an audience in Southeast Asia?

Most often Singapore: Malaysia, Indonesia and Thailand are 10–30 ms away from there. A local server is only needed if almost all users are in one country.

### Which VPS should I choose for users in China without ICP registration?

Usually Hong Kong, Taiwan or Japan. The route into Chinese networks matters more than the country: ask whether the plan has an optimised connection and check the evening ping.

### What is the ping from Moscow or Europe to servers in Asia?

Usually 130–250 ms from Moscow and 150–280 ms from Western Europe, depending on the hub and the provider's route. For an audience in Russia or Europe a European server will be faster.

### Why is traffic limited on Asian VPS plans?

Backbone bandwidth in Asia costs several times more than in Europe, and hosts build that into the quota. Check the overage price if the server serves a lot of data.

### Why does an Indian host ask for documents?

A CERT-In directive obliges VPS providers to keep customer data for five years, so identity checks are more common there than in Europe.

### Will one server in Singapore cover Japan and India?

For a website and an API, yes: Tokyo is about 70 ms away, India 30–70 ms. For games and voice, a local server in each region is better.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS paid with cryptocurrency

Providers that accept cryptocurrency payments.

> Source: https://accsly.io/en/vps/pay-with-crypto · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 10,506, hosts: 549
- Price: from 0.40 $, a quarter below 17.00 $, median 40.00 $
- NVMe: 46 %, unlimited traffic: 29 %, hourly billing: 11 %
- RAM → price from: 1 GB — 0.71 $, 2 GB — 1.20 $, 4 GB — 2.17 $, 8 GB — 4.42 $, 16 GB — 6.66 $
- Countries: USA (3458), Netherlands (2485), Germany (2244), United Kingdom (1481), Singapore (1333), France (932)
- Cheapest hosts: [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) — 0.71 $, [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 0.90 $, [HostVDS](https://accsly.io/en/vps/hosting/hostvds) — 0.99 $, [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) — 1.00 $, [Sive Host](https://accsly.io/en/vps/hosting/sive) — 1.22 $

## Cheapest plans — 10,506 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-384 Low-Cost Special US | 1 × 3.0 GHz | 384 MB | 12 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.40 $ (total when paying for 6 mo (2.39 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-II 384 Europe | 1 × 3.1 GHz | 384 MB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 0.42 $ (total when paying for 6 mo (2.50 $)) |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Pico | 1 | 128 MB | 5 GB SSD | US | Crypto | 0.50 $ |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-512-LXC | 1 | 512 MB | 6 GB SSD | SG, HK, TW, JP, DE, TR… | Crypto | 0.64 $ (total when paying for year (7.70 $)) |
| [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) | IaaS Lite 1 vCPU / 1 ГБ | 1 | 1 GB | 10 GB NVMe | RU | MIR, SBP, Crypto, WebMoney, Invoice | 0.71 $ |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-512-KVM | 1 | 512 MB | 6 GB SSD | SG, HK, JP, TW, DE, TR… | Crypto | 0.73 $ (total when paying for year (8.79 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-1024 US | 2 × 3.0 GHz | 1 GB | 30 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.90 $ (total when paying for 3 mo (2.69 $)) |
| [RuVPS](https://accsly.io/en/vps/hosting/ruvps) | VPS-0 | 1 | 768 MB | 7 GB NVMe | NL, PL, UA | Visa/MC, Crypto | 0.95 $ |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 1 | 1 | 1 GB | 10 GB NVMe | US, HK | Visa/MC, Crypto | 0.99 $ |
| [Privex](https://accsly.io/en/vps/hosting/privex) | VNANO-SE-SSD | 1 | 256 MB | 5 GB SSD | SE | Crypto, Invoice | 0.99 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Dedicated Server 4 Cheolistic | 4 × 1.8 GHz | 1 GB | 32 GB SSD | US | Crypto | 1.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Dedicated Server 5 Pennam | 4 × 1.8 GHz | 1 GB | 16 GB SSD | US | Crypto | 1.00 $ |
| [Jink Host](https://accsly.io/en/vps/hosting/jink) | Dirt | 1 | 512 MB | 20 GB NVMe | US, NL | Visa/MC, PayPal, Crypto | 1.00 $ (total when paying for 3 mo (3.00 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-1024-LXC | 2 | 1 GB | 8 GB SSD | SG, HK, TW, JP, DE, TR… | Crypto | 1.00 $ (total when paying for year (12.01 $)) |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Nano | 1 | 256 MB | 10 GB SSD | US | Crypto | 1.00 $ |
| [hostEONS.com](https://accsly.io/en/vps/hosting/hosteons) | OVZ256 | 1 | 256 MB | 5 GB SSD | US | PayPal, Visa/MC, Crypto, Invoice | 1.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | VDS 1 Vaporia | 2 × 1.5 GHz | 1 GB | 16 GB SSD | US | Crypto | 1.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | VDS 6 Corket | 4 × 1.1 GHz | 1 GB | 8 GB SSD | US | Crypto | 1.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | VDS 8 Emi | 4 × 1.2 GHz | 1 GB | 16 GB SSD | US | Crypto | 1.00 $ |
| [ChangeIP](https://accsly.io/en/vps/hosting/changeip) | VPS $1 | 1 | 256 MB | 15 GB SSD | US, NL, DE, SG | Visa/MC, Crypto | 1.00 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/pay-with-crypto?format=json

## How to pay for a VPS with cryptocurrency without losing money

Many hosting providers list cryptocurrency among their payment methods. But the method has its own mechanics, and most problems — underpayment, a payment on the wrong network, a stuck invoice — come down to small details. Below is what's worth knowing before you pay for a VPS with crypto for the first time.

### Which coins and networks are accepted

- **USDT** — the most convenient option: its rate is pegged to the dollar, so the invoice amount doesn't "drift". Most often it's accepted on TRON (TRC-20), BNB Smart Chain (BEP-20) and Ethereum (ERC-20), sometimes on TON, Polygon and Solana.
- **BTC** — accepted almost everywhere, but confirmation can take from ten minutes to an hour or more, and the fee depends on network congestion.
- **LTC** — fast and cheap transfers, a good option for small amounts.
- **ETH, TON and others** — depending on the host's payment gateway.

The main rule: the network you send on must match the network stated in the invoice. USDT sent on BEP-20 to a TRC-20 address won't be seen by the host, and most often it can't be recovered.

### Fees and the exact amount

The sender pays the network fee, and the host must receive no less than the amount on the invoice. On Ethereum the fee can be comparable to the price of a cheap plan, so for small payments TRC-20, BEP-20 or LTC are better value.

An invoice usually has a 15–60 minute timer: the rate is locked only for that time. If you pay later or pay less, the payment will hang in "partially paid" status and you'll have to contact support.

### Refunds and balance

A crypto payment can't be charged back like a card payment. If the server doesn't suit you, most hosts refund the money to the internal account balance, not to your wallet. Read the refund terms before paying and, if in doubt, start with one month or with [hourly billing](https://accsly.io/en/vps/hourly-billing) — that makes it easier to test the server without unnecessary spending.

### KYC and checks

A host that accepts cryptocurrency usually doesn't ask for documents at sign-up, but it has the right to request them after a complaint or suspicious activity. Paying with crypto doesn't guarantee anonymity: blockchain transactions are public.

### Accounting and companies

For a private project it is one of the available payment options. For a company it's often a poor option: the expense is hard to support with documents, and rules on using digital currencies for payments can be restrictive. A business is better off choosing a host that accepts bank transfers or cards.

The table above collects plans from hosts that accept cryptocurrency, with prices in your currency. If you need a specific country, there are separate selections — for example, [VPS in the Netherlands paid with crypto](https://accsly.io/en/vps/netherlands-pay-with-crypto).

## FAQ

### Which cryptocurrency is best for paying for a VPS?

Most often the most convenient is USDT on TRC-20 or BEP-20: the amount doesn't depend on the exchange rate, and the fee is moderate. LTC also works well for small payments.

### What happens if I send USDT on the wrong network?

The host won't see the payment, and most often the coins can't be recovered. Always compare the network in the invoice and in your wallet before sending.

### What should I do if I underpaid a crypto invoice?

Write to the host's support with the transaction hash. Usually they offer to pay the difference or credit the received amount to your account balance.

### Can I get a refund for a VPS paid with crypto?

Refunds are usually made to the internal account balance, not to your wallet. The refund terms are described in the host's rules; it's worth reading them before paying.

### Do I need to pass KYC to pay for a server with cryptocurrency?

With the host, most often not at sign-up, but it may request documents later in case of complaints or suspicious activity. Paying with crypto does not make the payment anonymous: blockchain transactions are public.

### Can a company pay for a VPS with cryptocurrency?

For a company it often creates problems with documentation and expense accounting, and rules on digital currencies can restrict their use in payments. A business is better off paying by bank transfer.

### How long does a crypto payment take to be credited?

On TRON, BNB Smart Chain and Litecoin usually a few minutes. Bitcoin can take from ten minutes to an hour to confirm, and longer when the network is congested.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS paid with PayPal

Providers that accept PayPal.

> Source: https://accsly.io/en/vps/pay-with-paypal · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 14,273, hosts: 1,011
- Price: from 0.40 $, a quarter below 17.97 $, median 40.00 $
- NVMe: 42 %, unlimited traffic: 33 %, hourly billing: 12 %
- RAM → price from: 1 GB — 0.70 $, 2 GB — 0.80 $, 4 GB — 1.60 $, 8 GB — 3.19 $, 16 GB — 6.38 $
- Countries: USA (4776), Germany (3082), Netherlands (2892), United Kingdom (2300), Singapore (1790), Canada (1403)
- Cheapest hosts: [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 0.70 $, [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 0.90 $, [V.PS](https://accsly.io/en/vps/hosting/v) — 0.93 $, [Sive Host](https://accsly.io/en/vps/hosting/sive) — 1.22 $, [Hostodo](https://accsly.io/en/vps/hosting/hostodo) — 1.67 $

## Cheapest plans — 14,273 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-384 Low-Cost Special US | 1 × 3.0 GHz | 384 MB | 12 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.40 $ (total when paying for 6 mo (2.39 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-II 384 Europe | 1 × 3.1 GHz | 384 MB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 0.42 $ (total when paying for 6 mo (2.50 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS1 Türkiye | 1 × 3.4 GHz | 1 GB | 15 GB SSD | TR | PayPal, Invoice | 0.70 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS1 Fransa | 1 × 4.0 GHz | 2 GB | 15 GB SSD | FR | PayPal, Invoice | 0.80 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS2 Türkiye | 2 × 3.4 GHz | 1 GB | 20 GB SSD | TR | PayPal, Invoice | 0.80 $ |
| [EUGameHost](https://accsly.io/en/vps/hosting/eugamehost) | Nano Edge | 1 | 512 MB | 5 GB NVMe | GB | PayPal, Visa/MC | 0.86 $ (when paying for year: 0.67 $/mo) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-1024 US | 2 × 3.0 GHz | 1 GB | 30 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.90 $ (total when paying for 3 mo (2.69 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS3 Türkiye | 2 × 3.4 GHz | 2 GB | 25 GB SSD | TR | PayPal, Invoice | 0.90 $ |
| [V.PS](https://accsly.io/en/vps/hosting/v) | Nano | 1 | 1 GB | 15 GB SSD | NL, DE | PayPal, Visa/MC, Invoice | 0.93 $ (total when paying for year (11.13 $)) |
| [Jink Host](https://accsly.io/en/vps/hosting/jink) | Dirt | 1 | 512 MB | 20 GB NVMe | US, NL | Visa/MC, PayPal, Crypto | 1.00 $ (total when paying for 3 mo (3.00 $)) |
| [hostEONS.com](https://accsly.io/en/vps/hosting/hosteons) | OVZ256 | 1 | 256 MB | 5 GB SSD | US | PayPal, Visa/MC, Crypto, Invoice | 1.00 $ |
| [ReconV](https://accsly.io/en/vps/hosting/reconv) | LXC 512 MB | 1 | 512 MB | 6 GB NVMe | PL, FR | PayPal | 1.02 $ |
| [myPrepaid-Server](https://accsly.io/en/vps/hosting/myprepaid-server) | 1 Euro Server | 1 × 3.5 GHz | 512 MB | 20 GB NVMe | DE | Visa/MC, PayPal, Invoice | 1.12 $ |
| [DeinServerHost](https://accsly.io/en/vps/hosting/deinserverhost) | KVM vServer FLEX | 1 | 1 GB | 10 GB NVMe | DE | PayPal, Invoice, Visa/MC, Crypto | 1.12 $ |
| [myPrepaid-Server](https://accsly.io/en/vps/hosting/myprepaid-server) | ONLY IPv6 | 1 | 512 MB | 15 GB SSD | DE | Visa/MC, PayPal, Invoice | 1.12 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-01 | 1 | 2 GB | 40 GB NVMe | DE, FI | PayPal, Invoice | 1.19 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS4 Türkiye | 3 × 3.4 GHz | 2 GB | 30 GB SSD | TR | PayPal, Invoice | 1.20 $ |
| [VDS4YOU](https://accsly.io/en/vps/hosting/vds4you) | Гибрид VDS MINI | 1 | 512 MB | 20 GB HDD | RU | MIR, Visa/MC, WebMoney, YooMoney, PayPal, Invoice, Crypto | 1.20 $ |
| [Sive Host](https://accsly.io/en/vps/hosting/sive) | Kunene River | 1 | 1 GB | 10 GB SSD | ZA | PayPal, Visa/MC, Crypto | 1.22 $ (yearly: 1.22 $/mo) |
| [Hostodo](https://accsly.io/en/vps/hosting/hostodo) | KVM-512 | 1 × 2.6 GHz | 512 MB | 20 GB SSD | US | Visa/MC, PayPal, Crypto | 1.25 $ (total when paying for year (14.99 $)) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/pay-with-paypal?format=json

## Paying for a VPS with PayPal: subscriptions, conversion and disputes

PayPal on a host's website means the payment goes through your PayPal account: a card or bank account is linked to it, and the host sees only the payer's email. For hosting, this method has three important particulars: subscriptions that live separately from the service, PayPal's own currency conversion, and buyer protection rules that work differently for services than for goods.

### One-off payment and subscription

At checkout, PayPal usually offers one of two options:

- **A one-off invoice payment.** You pay for a specific period, and the next invoice will have to be paid manually again.
- **A subscription or automatic payment** ("Automatic payments" in PayPal settings). You authorise the host to charge you once, and after that the payment goes out every month without confirmation.

A PayPal subscription is not directly tied to the service. If you have deleted the server in the host's panel but not cancelled the subscription, charges may continue, and the money will go to a balance that nothing spends any more. So when giving up a server, take two steps: cancel the service with the host, then open the automatic payments section in PayPal and revoke the authorisation for that merchant. The opposite happens too: the subscription has been cancelled but the service hasn't; the host will then issue an unpaid invoice and suspend the server a few days later.

### Currency and fees

For the buyer, paying through PayPal is usually free; the seller pays the fee. But if the host's billing currency differs from the currency of your account or card, PayPal converts the amount at its own rate with a markup, which is noticeably higher than the bank's. In the payment settings you can often choose who does the conversion: PayPal or the bank that issued the card. Compare both options on a small amount.

Some hosts pass their fee on to the customer and add a few per cent to the invoice when PayPal is chosen; others set a minimum top-up amount. This is visible only at the last step of checkout, so compare the total, not the plan price.

Pay attention to the funding source as well. If your PayPal balance doesn't cover the amount, the payment will be taken from the linked card or account, and for a subscription, from the source chosen when it was created. The primary source is changed in the account settings; if the card has been reissued, update it there in advance, or the next renewal will fail.

A PayPal receipt confirms the transfer but does not replace the host's invoice. If a company pays for the server, download the invoice from the provider's account: it shows the company details, the service period and the taxes.

### Restrictions on the hosts' side

Payment systems consider hosting a high-risk category because of disputes and fraudulent orders, so the conditions for PayPal can be stricter than for cards:

- payment is accepted only from a verified account;
- a new customer goes through manual review, and the server is not provisioned straight away;
- the country of the PayPal account must match the country in the host's profile;
- PayPal is available for renewals but not for balance top-ups, or the other way round.

Whether PayPal works depends on the country where the account is registered: in Russia the service has not processed payments since 2022. The table shows which hosts accept PayPal on their website; whether it is available to you is determined by your account's country.

### Refunds and buyer protection

A refund for an unused period is issued by the host: the money goes back to your PayPal account and from there to the funding source. If the host refuses, you can open a dispute in PayPal, usually within 180 days of the payment. However, the buyer protection programme is designed primarily for physical goods, and for intangible services its coverage is limited in a number of countries. In addition, a host almost always blocks the account against which a dispute has been opened, together with all its servers.

It is safer to choose plans with a refund written into the terms in advance; they are collected in the [VPS with a money-back guarantee](https://accsly.io/en/vps/moneyback) selection. For short tasks, [hourly billing](https://accsly.io/en/vps/hourly-billing) works well: you top up the balance through PayPal, and only the time actually used is deducted.

### PayPal or a card

PayPal is convenient when you don't want to enter card details on every new host's website and want to keep all automatic payments in one list. A card is simpler if the host adds a surcharge for PayPal or requires manual review; more about cards on the [VPS paid with a foreign card](https://accsly.io/en/vps/pay-with-foreign-card) page. The payment methods of each plan are shown in the "Payment" column.

## FAQ

### How do I cancel an automatic VPS payment in PayPal?

In PayPal settings, open the automatic payments section, choose the host and revoke the authorisation. Separately, cancel the service itself in the host's panel, or an unpaid invoice will remain.

### Does PayPal charge the buyer a fee when paying for hosting?

Usually not; the seller pays the fee. But when currencies differ, PayPal converts the amount at its own rate with a markup, and some hosts add a percentage for this payment method.

### Why was the server not provisioned immediately after paying through PayPal?

Many hosts review new customers manually when they pay through PayPal because of the risk of disputes. The review usually takes from a few minutes to a day.

### Can I get money back for a VPS through a PayPal dispute?

You can open a dispute, usually within 180 days. But buyer protection for services is limited, and after a dispute the host as a rule blocks the account.

### Do I need a verified PayPal account?

With some hosts, yes: payment is accepted only from an account with a confirmed card or bank account. This is stated in the payment terms or communicated at checkout.

### What happens to the subscription if I delete the server?

The PayPal subscription will not cancel itself. Charges will continue until you turn off the automatic payment in PayPal or the host closes the service on its side.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS with hourly billing

A server for a few hours or days: you pay only for the time it actually runs.

> Source: https://accsly.io/en/vps/hourly-billing · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 5,621, hosts: 176
- Price: from 0.40 $, a quarter below 39.00 $, median 144 $
- NVMe: 28 %, unlimited traffic: 18 %, hourly billing: 100 %
- RAM → price from: 1 GB — 0.49 $, 2 GB — 1.20 $, 4 GB — 2.17 $, 8 GB — 6.18 $, 16 GB — 10.49 $
- Countries: USA (2197), Netherlands (1989), Germany (1622), United Kingdom (1559), Singapore (1456), Australia (1180)
- Cheapest hosts: [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) — 0.71 $, [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 0.90 $, [HostVDS](https://accsly.io/en/vps/hosting/hostvds) — 0.99 $, [Sive Host](https://accsly.io/en/vps/hosting/sive) — 1.22 $, [3HCloud](https://accsly.io/en/vps/hosting/3hcloud) — 1.50 $

## Cheapest plans — 5,621 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-384 Low-Cost Special US | 1 × 3.0 GHz | 384 MB | 12 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.40 $ (total when paying for 6 mo (2.39 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-II 384 Europe | 1 × 3.1 GHz | 384 MB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 0.42 $ (total when paying for 6 mo (2.50 $)) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | STARDUST1-S | 1 × 2.1 GHz | 1 GB | — | FR, NL, PL | — | 0.49 $ |
| [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) | IaaS Lite 1 vCPU / 1 ГБ | 1 | 1 GB | 10 GB NVMe | RU | MIR, SBP, Crypto, WebMoney, Invoice | 0.71 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-1024 US | 2 × 3.0 GHz | 1 GB | 30 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.90 $ (total when paying for 3 mo (2.69 $)) |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 1 | 1 | 1 GB | 10 GB NVMe | US, HK | Visa/MC, Crypto | 0.99 $ |
| [TierHive](https://accsly.io/en/vps/hosting/tierhive) | Калькулятор (конфигурация по умолчанию) | 1 | 1 GB | 20 GB NVMe | NL, CA, DE, FR, US, GB… | — | 1.01 $ |
| [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) | IaaS Lite 1 vCPU / 2 ГБ | 1 | 2 GB | 20 GB NVMe | RU | MIR, SBP, Crypto, WebMoney, Invoice | 1.20 $ |
| [Sive Host](https://accsly.io/en/vps/hosting/sive) | Kunene River | 1 | 1 GB | 10 GB SSD | ZA | PayPal, Visa/MC, Crypto | 1.22 $ (yearly: 1.22 $/mo) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | CentralVPS-1536 | 2 × 3.1 GHz | 1.5 GB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 1.33 $ (total when paying for 3 mo (3.99 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | FullVPS-1024 Essential | 1 | 1 GB | 30 GB NVMe | NL | Visa/MC, PayPal, Crypto | 1.43 $ (total when paying for 3 mo (4.29 $)) |
| [3HCloud](https://accsly.io/en/vps/hosting/3hcloud) | 1 GB 1 vCPU Shared Pool | 1 | 1 GB | — | PL, US, PH | Visa/MC | 1.50 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-1024 Premier | 1 × 4.8 GHz | 1 GB | 15 GB NVMe | FI | Visa/MC, PayPal, Crypto | 1.50 $ (total when paying for 3 mo (4.49 $)) |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 1 | 1 | 1 GB | 10 GB NVMe | FR, LV, NL, FI | Visa/MC, Crypto | 1.67 $ |
| [TierHive](https://accsly.io/en/vps/hosting/tierhive) | STANDARD | 1 | 2 GB | 25 GB NVMe | NL, CA, DE, FR, US, GB… | — | 1.71 $ |
| [RuVDS](https://accsly.io/en/vps/hosting/ruvds) | Самый дешёвый VPS | 1 × 2.0 GHz | 512 MB | 10 GB HDD | RU | Visa/MC, MIR, SBP, YooMoney | 1.80 $ |
| [RareCloud](https://accsly.io/en/vps/hosting/rarecloud) | KVM VPS Micro | 1 | 768 MB | 15 GB NVMe | US, GB, NL, DE, RO, HK… | Visa/MC, PayPal, Crypto, Invoice | 1.82 $ (total when paying for year (21.85 $)) |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 2 | 1 | 2 GB | 20 GB NVMe | US, HK | Visa/MC, Crypto | 1.99 $ |
| [DataPasa](https://accsly.io/en/vps/hosting/datapasa) | VPS-1 | 1 | 1 GB | 16 GB NVMe | DE | Visa/MC, PayPal, Crypto | 1.99 $ |
| [Karvl](https://accsly.io/en/vps/hosting/karvl) | Basic 1vCPU/1GB | 1 | 1 GB | 20 GB SSD | US, SG, JP, HK | Visa/MC | 2.00 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/hourly-billing?format=json

## When an hourly-billed VPS beats a monthly plan

With hourly billing you top up your balance, create a server, and the host charges for every hour the server exists. Delete it after three hours — you pay for three hours. The model comes from the cloud and suits tasks that have a beginning and an end. For a server that runs around the clock for months, it's usually no cheaper than ordinary monthly rental.

### Which tasks an hourly VDS is for

- **Tests and experiments.** Try a new OS version, run a database migration, compare the performance of two configurations.
- **Builds and CI.** A powerful machine is needed for the duration of the build, not around the clock. For permanent runners see the [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci) page.
- **One-off computations.** Video conversion, a large [scraping](https://accsly.io/en/vps/for-parsing) job, load testing your own site.
- **Temporary projects.** A weekend gaming tournament, a demo environment for a client, a work server for the duration of a trip.

If your goal is simply to get to know a host, look at plans with a [trial period](https://accsly.io/en/vps/free-trial): there the trial days are free or nearly free.

### How an hourly price becomes a monthly one

A month has about 720–730 hours. Multiply the hourly rate by that number and compare it with the same host's monthly plan. Many hosts cap the charges: if the server ran for the whole month, you pay no more than the monthly price. Others have no such cap, and round-the-clock operation comes out noticeably more expensive. Check this in the plan description before launching.

Two more nuances. The hourly rate sometimes doesn't include a dedicated IPv4, snapshots or backups — they're billed separately. And whatever is left of the minimum top-up after you delete the server stays on the balance; not every host will refund it to your card.

### Stopping is not deleting

A common mistake is to shut the server down and assume billing has stopped. With most hosts a stopped machine still occupies disk space and an IP address, and you're charged for them, sometimes at the full rate. For charges to end, the server must be deleted. If you'll need the data later, take a snapshot: storing it is usually cheaper than keeping a stopped machine, and a server comes up from a snapshot in a few minutes.

### Automation via API

An hourly plan shows its full potential when the server is created and deleted by a script. Cloud hosts offer an API for this, and some have a Terraform provider. The pipeline spins up a machine, runs the job and deletes it, and you pay for hours of work, not idle time. Turn on spending notifications so a forgotten server doesn't eat your budget.

The hourly model is offered mostly by large clouds, and their payment options can be narrower than those of ordinary hosts. The "Payment" column in the table above shows the methods for each plan; prices are shown in your currency.

## FAQ

### Am I charged for a stopped VPS?

With most hosts, yes: a stopped server occupies disk space and an IP address, and you keep being charged for them. For billing to stop, the server must be deleted.

### Which is cheaper: hourly or monthly VPS billing?

For tasks lasting hours or days, hourly is cheaper. If the server runs all month, at best it equals the monthly price, and with hosts that have no charge cap it comes out more expensive.

### How many hours are in a month with hourly billing?

Hosts usually count 720 or 730 hours. Look for the exact formula and whether there's a cap in the plan terms.

### Is a partial hour billed?

As a rule, a partial hour is rounded up to a full one. Some clouds bill per minute or per second; this is stated in the plan terms.

### How do I save data before deleting an hourly server?

Take a disk snapshot or copy the data to object storage. A snapshot is billed separately, but usually costs less than a running server.

### How do I avoid forgetting to delete an hourly server?

Create and delete servers with a script via the host's API and turn on spending notifications. A small balance also limits potential losses.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS with a free trial

Providers that let you test a server for free before paying.

> Source: https://accsly.io/en/vps/free-trial · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 4,678, hosts: 242
- Price: from 1.20 $, a quarter below 27.00 $, median 89.54 $
- NVMe: 32 %, unlimited traffic: 23 %, hourly billing: 50 %
- RAM → price from: 1 GB — 1.20 $, 2 GB — 2.60 $, 4 GB — 4.60 $, 8 GB — 5.90 $, 16 GB — 8.40 $
- Countries: USA (1593), Germany (1509), Netherlands (1455), United Kingdom (1244), Singapore (1079), Sweden (1065)
- Cheapest hosts: [Inoventica](https://accsly.io/en/vps/hosting/invs) — 1.20 $, [Karvl](https://accsly.io/en/vps/hosting/karvl) — 2.00 $, [Relevate](https://accsly.io/en/vps/hosting/relevate) — 2.42 $, [Prohoster](https://accsly.io/en/vps/hosting/prohoster) — 2.60 $, [FreakHosting.com](https://accsly.io/en/vps/hosting/freakhosting) — 2.79 $

## Cheapest plans — 4,678 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Inoventica](https://accsly.io/en/vps/hosting/invs) | LUNA PROMO | 1 | 1 GB | 20 GB SSD | RU | YooMoney | 1.20 $ |
| [Noez](https://accsly.io/en/vps/hosting/noez) | LXC vServer (конфигуратор, по умолчанию) | 1 | 256 MB | 10 GB SSD | DE | Visa/MC, PayPal, Crypto, Invoice | 1.44 $ |
| [RuVDS](https://accsly.io/en/vps/hosting/ruvds) | Самый дешёвый VPS | 1 × 2.0 GHz | 512 MB | 10 GB HDD | RU | Visa/MC, MIR, SBP, YooMoney | 1.80 $ |
| [JustHost RU](https://accsly.io/en/vps/hosting/just) | VPS Promo | 1 | 512 MB | 5 GB NVMe |  | Visa/MC, MIR, YooMoney, WebMoney, Invoice | 1.99 $ |
| [Karvl](https://accsly.io/en/vps/hosting/karvl) | Basic 1vCPU/1GB | 1 | 1 GB | 20 GB SSD | US, SG, JP, HK | Visa/MC | 2.00 $ |
| [1Gb.ua](https://accsly.io/en/vps/hosting/1gb-ua) | VZ-Лайт | 1 × 2.4 GHz | 192 MB | 3 GB SSD | UA, DE | Visa/MC, Invoice | 2.18 $ |
| [eXone.pl](https://accsly.io/en/vps/hosting/exone) | Cloud VPS (конфигуратор, базовая конфигурация) | 1 | 512 MB | 30 GB SSD | PL | — | 2.30 $ |
| [xost.su](https://accsly.io/en/vps/hosting/xost) | ECO VDS-1 | 1 | 512 MB | 10 GB NVMe | RU | SBP, Invoice, MIR, YooMoney, WebMoney | 2.41 $ |
| [Relevate](https://accsly.io/en/vps/hosting/relevate) | SSD-1024 | 1 × 2.4 GHz | 1 GB | 15 GB SSD | RU | Visa/MC, Invoice | 2.42 $ (when paying for year: 2.01 $/mo) |
| [Nt-vps](https://accsly.io/en/vps/hosting/nt-vps) | Старт | 1 | 256 MB | 40 GB HDD |  | — | 2.54 $ |
| [Prohoster](https://accsly.io/en/vps/hosting/prohoster) | KVM-VPS-512-1 | 1 | 512 MB | 10 GB SSD | NL | Visa/MC, Crypto | 2.60 $ |
| [Prohoster](https://accsly.io/en/vps/hosting/prohoster) | VPS-512-1-SSD | 2 | 2 GB | 20 GB SSD | NL | Visa/MC, Crypto | 2.60 $ (when paying for year: 2.22 $/mo) |
| [RuVDS](https://accsly.io/en/vps/hosting/ruvds) | Старт SSD | 1 | 512 MB | 10 GB SSD | RU | Visa/MC, MIR, SBP, YooMoney | 2.65 $ |
| [Спринтхост](https://accsly.io/en/vps/hosting/sprinthost) | Джун | 1 | 600 MB | 10 GB NVMe | RU | MIR, Visa/MC, SBP, YooMoney, Invoice | 2.67 $ |
| [FreakHosting.com](https://accsly.io/en/vps/hosting/freakhosting) | BVPS-1 | 1 | 1 GB | 25 GB NVMe | DE, US | PayPal, Visa/MC, Crypto, Invoice | 2.79 $ |
| [Globalnet.com.ua](https://accsly.io/en/vps/hosting/globalnet-com) | VPS Міні | 1 × 1.8 GHz | 1 GB | 10 GB HDD | UA | WebMoney, Visa/MC | 2.86 $ |
| [Antihost](https://accsly.io/en/vps/hosting/antihost) | LITE S 1 | 1 | 2 GB | 30 GB NVMe | US, DE | Visa/MC, Invoice | 2.99 $ (when paying for 3 years: 2.54 $/mo) |
| [xost.su](https://accsly.io/en/vps/hosting/xost) | ECO VDS-2 | 1 | 1 GB | 20 GB NVMe | RU | SBP, Invoice, MIR, YooMoney, WebMoney | 3.02 $ |
| [HOST-FOOD](https://accsly.io/en/vps/hosting/host-food) | KVM1 | 1 × 2.5 GHz | 768 MB | 5 GB SSD | RU | MIR, SBP, YooMoney, Invoice, WebMoney | 3.02 $ |
| [Cloudavt.com](https://accsly.io/en/vps/hosting/cloudavt) | VDS-2 | 1 | 1 GB | 20 GB NVMe | RU | WebMoney, YooMoney, Invoice, MIR, Crypto | 3.02 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/free-trial?format=json

## How to make the most of a VPS trial period

A trial period is the most honest way to test a host: instead of promises on a website you get a real machine and measure for yourself what matters for your task. Trial days are short, and if you spend them installing a panel and getting to know the interface, you won't have time to check the important things. Below is a plan that fits into a couple of hours.

### What a trial usually gives you

Most often it's a full virtual server for a few days: free, for a token amount, or with a refund if the service doesn't suit you. There are also cut-down versions — an entry-level plan instead of the one you chose, limited traffic, port 25 blocked. Every host has its own terms, so before ordering, read what will be available and what happens to the server when the period ends. If you're given a smaller configuration than the one you need, you'll have to scale the CPU and disk results in your head — or better, ask for a trial of exactly the plan you intend to buy.

### A test plan for the first hours

1. **Ping and route.** Run `mtr` from your computer and, if you can, from your users' network. A steady ping without packet loss matters more than the lowest value.
2. **CPU.** Check the model with `lscpu` and watch the steal value in `top`. If it's noticeably above zero under load, the cores are shared with neighbours too densely.
3. **Disk.** An `fio` test of random 4K reads and writes shows real IOPS. For databases this matters more than linear speed; more about disks on the [NVMe VPS](https://accsly.io/en/vps/nvme) page.
4. **Network.** `iperf3` or downloading a large file from a public mirror will show whether the port matches what's advertised.
5. **Support.** Ask a specific technical question in a ticket and time the response. That's how fast you'll get help when the server goes down at night.

While you're at it, test the panel: OS reinstall, VNC console, snapshots, reverse DNS. If [KVM](https://accsly.io/en/vps/kvm) is advertised, the `systemd-detect-virt` command will confirm it in a second. For email, check the IP against public blacklists.

### Restrictions and identity checks

A free server attracts spammers and miners, so hosts protect themselves. They almost always ask you to verify a phone number or link a card, and some enable the trial only after a conversation with support. Usually the rule is "one trial per person", and repeat sign-ups are blocked. The trial server's data may be deleted irrecoverably once the period ends.

### What to do after the test

If everything suits you, ask whether you can keep the server with its data when moving to a paid plan — then you won't have to set everything up again. If not, compare the alternatives in the table above: prices are shown in your currency, and the "Payment" column shows which methods each host accepts. For one-off experiments with no commitment, plans with [hourly billing](https://accsly.io/en/vps/hourly-billing) also work: a few hours of use cost little.

## FAQ

### How long does a VPS trial period last?

Most often from one day to a few days, longer with some hosts. The exact period and extension terms are stated in the offer description.

### Why do hosts ask for a phone number or card for a VPS trial?

It's how hosts weed out spammers and miners who sign up for free servers en masse. Money is usually not charged to a linked card without your consent, but it's better to read the auto-renewal terms in advance.

### Will my data be kept after the trial period ends?

It depends on the host: some move the server to a paid plan with its data, others delete it as soon as the period ends. If you need the data, clarify this before starting the trial.

### How do I test disk speed on a VPS?

Use fio with a random 4K read and write test: it shows the IOPS that database performance depends on. A dd test measures only linear speed and says little about real-world load.

### What is steal time on a VPS?

It's the share of time your virtual machine waits for a CPU busy with other customers on the same server. You can see it in top in the st column; consistently high steal means an overloaded node.

### Can I send email from a trial VPS?

Most often not: on trial servers outgoing port 25 is usually blocked to prevent spam. Many hosts open it on request only after payment.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# Cheap VPS/VDS under 4 $ a month

Plans under 4 $ a month — for a VPN, a bot, a test environment or a small website. Cheapest first; to avoid seeing ten plans from the same provider in a row, turn on “One plan per provider”.

> Source: https://accsly.io/en/vps/cheap · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 586, hosts: 316
- Price: from 0.40 $, a quarter below 1.99 $, median 2.71 $
- NVMe: 43 %, unlimited traffic: 31 %, hourly billing: 12 %
- RAM → price from: 1 GB — 0.49 $, 2 GB — 0.80 $, 4 GB — 1.60 $, 8 GB — 3.19 $, 16 GB — 3.46 $
- Countries: USA (166), Germany (112), Russia (87), Netherlands (80), Turkey (45), United Kingdom (41)
- Cheapest hosts: [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 0.70 $, [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) — 0.71 $, [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 0.90 $, [V.PS](https://accsly.io/en/vps/hosting/v) — 0.93 $, [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) — 0.97 $

## Cheapest plans — 586 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-384 Low-Cost Special US | 1 × 3.0 GHz | 384 MB | 12 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.40 $ (total when paying for 6 mo (2.39 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-II 384 Europe | 1 × 3.1 GHz | 384 MB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 0.42 $ (total when paying for 6 mo (2.50 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ NL 256MB NAT | 1 | 256 MB | 5 GB SSD | NL | — | 0.42 $ (total when paying for year (4.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ Germany 256MB NAT | 1 | 256 MB | 5 GB SSD | DE | — | 0.44 $ (total when paying for year (5.31 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ Sweden 256MB NAT | 1 | 256 MB | 5 GB SSD | SE | — | 0.46 $ (total when paying for year (5.50 $)) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | STARDUST1-S | 1 × 2.1 GHz | 1 GB | — | FR, NL, PL | — | 0.49 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Pico | 1 | 128 MB | 5 GB SSD | US | Crypto | 0.50 $ |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM Canada NAT 256MB | 1 | 256 MB | 5 GB SSD | CA | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM India 256MB NAT | 1 | 256 MB | 5 GB SSD | IN | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM SG 400MB NAT | 1 | 400 MB | 5 GB NVMe | SG | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM Texas 300 MB NAT | 1 | 300 MB | 5 GB SSD | US | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM Turkey 256MB NAT | 1 | 256 MB | 5 GB SSD | TR | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM UK 256 MB NAT | 1 | 256 MB | 5 GB SSD | GB | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ HK 256MB NAT | 1 | 256 MB | 5 GB SSD | HK | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ Japan 256MB NAT | 1 | 256 MB | 5 GB SSD | JP | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ Pakistan 256MB NAT | 1 | 256 MB | 5 GB SSD | PK | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ SA 256MB NAT | 1 | 256 MB | 5 GB SSD | ZA | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ SG 400MB NAT (KVM) | 1 | 400 MB | 5 GB SSD | SG | — | 0.58 $ (total when paying for year (6.99 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-512-LXC | 1 | 512 MB | 6 GB SSD | SG, HK, TW, JP, DE, TR… | Crypto | 0.64 $ (total when paying for year (7.70 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ DE 512 MB NAT | 1 | 512 MB | 5 GB SSD | DE | — | 0.67 $ (total when paying for year (8.00 $)) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/cheap?format=json

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS with 1 GB RAM

Plans with 1 GB of RAM or more — a VPN, a bot, a small website.

> Source: https://accsly.io/en/vps/1-gb-ram · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 30,287, hosts: 2,247
- Price: from 0.49 $, a quarter below 19.02 $, median 45.88 $
- NVMe: 42 %, unlimited traffic: 31 %, hourly billing: 18 %
- RAM → price from: 1 GB — 0.49 $, 2 GB — 0.80 $, 4 GB — 1.60 $, 8 GB — 3.19 $, 16 GB — 3.46 $
- Countries: USA (8720), Germany (5837), Netherlands (5577), United Kingdom (4762), Singapore (3533), India (2837)
- Cheapest hosts: [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 0.70 $, [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) — 0.71 $, [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 0.90 $, [V.PS](https://accsly.io/en/vps/hosting/v) — 0.93 $, [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) — 0.97 $

## Cheapest plans — 30,287 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | STARDUST1-S | 1 × 2.1 GHz | 1 GB | — | FR, NL, PL | — | 0.49 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS1 Türkiye | 1 × 3.4 GHz | 1 GB | 15 GB SSD | TR | PayPal, Invoice | 0.70 $ |
| [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) | IaaS Lite 1 vCPU / 1 ГБ | 1 | 1 GB | 10 GB NVMe | RU | MIR, SBP, Crypto, WebMoney, Invoice | 0.71 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS1 Fransa | 1 × 4.0 GHz | 2 GB | 15 GB SSD | FR | PayPal, Invoice | 0.80 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS2 Türkiye | 2 × 3.4 GHz | 1 GB | 20 GB SSD | TR | PayPal, Invoice | 0.80 $ |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ NL 1024MB NAT | 1 | 1 GB | 5 GB SSD | NL | — | 0.86 $ (total when paying for year (10.30 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-1024 US | 2 × 3.0 GHz | 1 GB | 30 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.90 $ (total when paying for 3 mo (2.69 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS3 Türkiye | 2 × 3.4 GHz | 2 GB | 25 GB SSD | TR | PayPal, Invoice | 0.90 $ |
| [V.PS](https://accsly.io/en/vps/hosting/v) | Nano | 1 | 1 GB | 15 GB SSD | NL, DE | PayPal, Visa/MC, Invoice | 0.93 $ (total when paying for year (11.13 $)) |
| [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) | Промо SSD 2026 | 1 | 1 GB | 6 GB SSD | RU | Invoice, MIR, SBP, YooMoney | 0.97 $ |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 1 | 1 | 1 GB | 10 GB NVMe | US, HK | Visa/MC, Crypto | 0.99 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Dedicated Server 4 Cheolistic | 4 × 1.8 GHz | 1 GB | 32 GB SSD | US | Crypto | 1.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Dedicated Server 5 Pennam | 4 × 1.8 GHz | 1 GB | 16 GB SSD | US | Crypto | 1.00 $ |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-1024-LXC | 2 | 1 GB | 8 GB SSD | SG, HK, TW, JP, DE, TR… | Crypto | 1.00 $ (total when paying for year (12.01 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ SA 1024 MB NAT | 1 | 1 GB | 8 GB SSD | ZA | — | 1.00 $ (total when paying for year (11.99 $)) |
| [h2 NEXUS](https://accsly.io/en/vps/hosting/h2) | RED-PROMO | 1 × 3.3 GHz | 1 GB | 10 GB NVMe | DE, FI, PL | — | 1.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | VDS 1 Vaporia | 2 × 1.5 GHz | 1 GB | 16 GB SSD | US | Crypto | 1.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | VDS 6 Corket | 4 × 1.1 GHz | 1 GB | 8 GB SSD | US | Crypto | 1.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | VDS 8 Emi | 4 × 1.2 GHz | 1 GB | 16 GB SSD | US | Crypto | 1.00 $ |
| [TierHive](https://accsly.io/en/vps/hosting/tierhive) | Калькулятор (конфигурация по умолчанию) | 1 | 1 GB | 20 GB NVMe | NL, CA, DE, FR, US, GB… | — | 1.01 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/1-gb-ram?format=json

## VPS with 1 GB RAM: what fits and how not to run out of memory

One gigabyte of RAM is the floor at which a modern Linux server still runs without a constant fight for resources. It is enough for one task, not for "everything at once": a bot, a small site without a heavy CMS, an internal service for a team. If you know in advance how much each process takes, a VPS with 1 GB RAM can run for months without reboots. If you install everything in sight, the first sign of trouble will be a crashed database.

### What really fits in 1 GB

A clean system without a GUI takes 120–250 MB: least for Alpine and minimal Debian, more for Ubuntu with snapd and cloud agents. The rest is divided like this:

- **A Python or Node.js bot**: 50–200 MB per process. Two or three bots with SQLite fit comfortably; more in the [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot) section.
- **A static site or landing page on Nginx**: tens of megabytes, leaving plenty of memory to spare.
- **A corporate VPN** for staff remote access to the office: WireGuard itself runs in the kernel and uses almost no memory, while a management panel adds 100–150 MB. See [VPS for WireGuard](https://accsly.io/en/vps/for-wireguard).
- **A PHP site with a small database**: possible, but tight. MariaDB with a trimmed buffer takes 150–250 MB, leaving room for 3–5 PHP-FPM processes.
- **Monitoring agents, a DNS server, a backup MX, cron jobs**: the typical "utility" load for a server like this.

What won't fit: Docker with a database, cache and application together, Windows Server, Java applications with a heap over 256 MB, Minecraft, GitLab, Elasticsearch, and also front-end builds via npm or compiling large packages. For such tasks take a [VPS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram) or more. The opposite happens too: for a single bot or a VPN for a couple of staff members a gigabyte is overkill, and a 512 MB plan will do just as well.

### Swap and the OOM killer: insurance, not extra capacity

When processes run out of memory, the kernel starts the OOM killer and terminates the "heaviest" of them, usually the database or the application's interpreter. On 1 GB this most often happens during package updates, backups or traffic spikes.

1. Create a 1–2 GB swap file: `fallocate -l 1G /swapfile`, `chmod 600`, `mkswap`, `swapon` and a line in `/etc/fstab`.
2. Set `vm.swappiness=10` so the kernel only uses swap when memory is genuinely short.
3. An alternative is zram: compressed swap right in memory. On a slow disk it works faster than an ordinary swap file.
4. To find out which process the kernel killed, use `journalctl -k | grep -i "killed process"`.

Swap is no substitute for memory: if the server is constantly swapping, the site will take seconds to respond. That is a signal to move to a bigger plan, not to enlarge the swap file.

### Guaranteed memory and container virtualisation

On KVM the whole gigabyte is allocated to the virtual machine, and the kernel inside sees exactly that. On OpenVZ and LXC, plans often list two figures: the guaranteed amount and burst, memory the container can borrow temporarily if it is free on the node. Burst is not promised to anyone: at peak hours the neighbours take it, and processes crash even though your monitoring showed headroom. Use only the guaranteed figure for planning. On top of that, in a container you can't create your own swap or change kernel parameters, which matters more on 1 GB than on bigger plans.

### How to check memory after buying

- `free -h`: look at the available column, which is the amount programs can get without evicting the cache. Near-zero free with a large available is normal.
- `cat /proc/meminfo | head -5`: on KVM, MemTotal is usually 50–100 MB below the advertised figure, because the kernel takes part of it. If the gap is hundreds of megabytes, ask support.
- `systemd-detect-virt`: shows kvm, openvz or lxc and confirms which virtualisation you actually have.
- `ps aux --sort=-rss | head`: a list of the most memory-hungry processes. Unneeded services such as snapd, cloud-init or ModemManager can be disabled after the first boot.

### Cores and disk on 1 GB plans

Such a plan usually comes with one virtual core and a 10–25 GB disk. The CPU is enough for a bot or VPN, but check the disk: logs and the package cache quickly eat up 10 GB. If the choice is between 1 GB on NVMe and 1 GB on HDD, take NVMe, as the difference in responsiveness is noticeable when swap is active. And for a system with minimal memory use, consider a [VPS with Alpine Linux](https://accsly.io/en/vps/alpine): it boots in about 50 MB.

## FAQ

### Is 1 GB of RAM enough for WordPress?

For a small site with page caching, yes, if you limit PHP-FPM to three to five processes and reduce the MariaDB buffer. With page-builder plugins and a shop, it is better to take 2 GB from the start.

### Can I run Docker on a VPS with 1 GB?

Docker itself takes about 100 MB, so one or two light containers will run. An application, database and cache together won't fit in 1 GB without constant swapping.

### How much swap should a server with 1 GB RAM have?

Usually 1–2 GB. More isn't needed: if the server is actively using a large swap, it is already running too slowly.

### How is 512 MB worse than 1 GB?

With 512 MB, 250–350 MB remains after the system boots, enough for one VPN or a small bot. 1 GB lets you run a small database and a web server at the same time.

### Why does free -h show less memory than the plan?

The kernel reserves part of the memory, and on KVM that is 50–100 MB of the advertised amount. A large gap may mean the plan counts a gigabyte as 1000 MB or includes reserved areas.

### What is burst memory in a VPS plan?

It is memory a container on OpenVZ or LXC can take beyond the guaranteed amount while it is free on the server. You can't count on it: when neighbours are under load, it is taken away.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS with 2 GB RAM

Plans with 2 GB of RAM or more — a CMS website, several services in Docker.

> Source: https://accsly.io/en/vps/2-gb-ram · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 28,199, hosts: 2,222
- Price: from 0.80 $, a quarter below 22.37 $, median 50.48 $
- NVMe: 42 %, unlimited traffic: 31 %, hourly billing: 19 %
- RAM → price from: 1 GB — 0.80 $, 2 GB — 0.80 $, 4 GB — 1.60 $, 8 GB — 3.19 $, 16 GB — 3.46 $
- Countries: USA (8165), Germany (5534), Netherlands (5188), United Kingdom (4515), Singapore (3344), India (2743)
- Cheapest hosts: [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 0.80 $, [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) — 1.20 $, [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) — 1.33 $, [V.PS](https://accsly.io/en/vps/hosting/v) — 1.87 $, [HostVDS](https://accsly.io/en/vps/hosting/hostvds) — 1.99 $

## Cheapest plans — 28,199 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS1 Fransa | 1 × 4.0 GHz | 2 GB | 15 GB SSD | FR | PayPal, Invoice | 0.80 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS3 Türkiye | 2 × 3.4 GHz | 2 GB | 25 GB SSD | TR | PayPal, Invoice | 0.90 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-01 | 1 | 2 GB | 40 GB NVMe | DE, FI | PayPal, Invoice | 1.19 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS4 Türkiye | 3 × 3.4 GHz | 2 GB | 30 GB SSD | TR | PayPal, Invoice | 1.20 $ |
| [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) | IaaS Lite 1 vCPU / 2 ГБ | 1 | 2 GB | 20 GB NVMe | RU | MIR, SBP, Crypto, WebMoney, Invoice | 1.20 $ |
| [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) | Старт0 SSD 2026 | 1 | 2 GB | 10 GB SSD | RU | Invoice, MIR, SBP, YooMoney | 1.33 $ (when paying for 2 years: 1.00 $/mo) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS2 Fransa | 1 × 4.0 GHz | 4 GB | 25 GB SSD | FR | PayPal, Invoice | 1.60 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-02 | 2 | 4 GB | 70 GB NVMe | DE, FI | PayPal, Invoice | 1.70 $ |
| [TierHive](https://accsly.io/en/vps/hosting/tierhive) | STANDARD | 1 | 2 GB | 25 GB NVMe | NL, CA, DE, FR, US, GB… | — | 1.71 $ |
| [V.PS](https://accsly.io/en/vps/hosting/v) | Nano Pro | 1 | 2 GB | 30 GB SSD | NL, DE | PayPal, Visa/MC, Invoice | 1.87 $ (total when paying for year (22.33 $)) |
| [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) | Старт1 SSD 2026 | 2 | 3 GB | 15 GB SSD | RU | Invoice, MIR, SBP, YooMoney | 1.94 $ (when paying for 2 years: 1.45 $/mo) |
| [SmokyHosts](https://accsly.io/en/vps/hosting/smokyhosts) | IPv6-only VPS | 1 | 2 GB | 10 GB SSD |  | PayPal | 1.95 $ |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 2 | 1 | 2 GB | 20 GB NVMe | US, HK | Visa/MC, Crypto | 1.99 $ |
| [TNA Hosting](https://accsly.io/en/vps/hosting/tnahosting) | SSD KVM 2GB | 2 | 2 GB | 50 GB SSD | US | — | 2.00 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS5 Türkiye | 3 × 4.2 GHz | 3 GB | 45 GB SSD | TR | PayPal, Invoice | 2.00 $ |
| [EVL Gaming, LLC](https://accsly.io/en/vps/hosting/evlbox) | General Purpose 2GB | 1 | 2 GB | 25 GB NVMe | US | Visa/MC | 2.08 $ (total when paying for year (25.00 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | VPS-2048-KVM-TR | 2 | 2 GB | 24 GB SSD | TR | Crypto | 2.08 $ (total when paying for year (25.00 $)) |
| [Hostablanca.com](https://accsly.io/en/vps/hosting/hostablanca) | VPS RAM 2 GB | 1 | 2 GB | 10 GB NVMe | ES, DE | Crypto, Visa/MC | 2.13 $ (when paying for year: 1.93 $/mo) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | ExtraVPS-4096 | 3 × 3.1 GHz | 4 GB | 60 GB NVMe | FI | Visa/MC, PayPal, Crypto | 2.17 $ (total when paying for 3 mo (6.49 $)) |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-1 | 1 × 3.3 GHz | 4 GB | 50 GB NVMe |  | PayPal, Visa/MC, Crypto | 2.18 $ (total when paying for year (26.19 $)) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/2-gb-ram?format=json

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS with 4 GB RAM

Plans with 4 GB of RAM or more — an online store, a database, a game server.

> Source: https://accsly.io/en/vps/4-gb-ram · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 24,133, hosts: 2,162
- Price: from 1.60 $, a quarter below 29.99 $, median 63.80 $
- NVMe: 43 %, unlimited traffic: 31 %, hourly billing: 20 %
- RAM → price from: 1 GB — 1.60 $, 2 GB — 1.60 $, 4 GB — 1.60 $, 8 GB — 3.19 $, 16 GB — 3.46 $
- Countries: USA (7118), Germany (4922), Netherlands (4518), United Kingdom (4041), Singapore (2983), India (2540)
- Cheapest hosts: [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 1.60 $, [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 2.17 $, [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) — 2.18 $, [Aeza](https://accsly.io/en/vps/hosting/aeza) — 2.23 $, [ByteHosting](https://accsly.io/en/vps/hosting/bytehosting) — 2.24 $

## Cheapest plans — 24,133 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS2 Fransa | 1 × 4.0 GHz | 4 GB | 25 GB SSD | FR | PayPal, Invoice | 1.60 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-02 | 2 | 4 GB | 70 GB NVMe | DE, FI | PayPal, Invoice | 1.70 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | ExtraVPS-4096 | 3 × 3.1 GHz | 4 GB | 60 GB NVMe | FI | Visa/MC, PayPal, Crypto | 2.17 $ (total when paying for 3 mo (6.49 $)) |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-1 | 1 × 3.3 GHz | 4 GB | 50 GB NVMe |  | PayPal, Visa/MC, Crypto | 2.18 $ (total when paying for year (26.19 $)) |
| [Server Hosh](https://accsly.io/en/vps/hosting/serverhosh) | 10yrs Special Package | 4 | 10 GB | 100 GB SSD | US | Visa/MC, PayPal, Crypto, Invoice | 2.20 $ (total when paying for 10 years (265 $)) |
| [Aeza](https://accsly.io/en/vps/hosting/aeza) | SWE-PROMO | 1 | 4 GB | 10 GB NVMe | SE | Visa/MC | 2.23 $ |
| [ByteHosting](https://accsly.io/en/vps/hosting/bytehosting) | Xeon - 4GB | 1 | 4 GB | 30 GB NVMe | DE | PayPal, Crypto | 2.24 $ (total when paying for year (26.87 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS3 Fransa | 2 × 4.0 GHz | 6 GB | 35 GB SSD | FR | PayPal, Invoice | 2.39 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS6 Türkiye | 4 × 4.2 GHz | 4 GB | 50 GB SSD | TR | PayPal, Invoice | 2.40 $ |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | VPS-1 (Xeon) | 2 | 4 GB | 40 GB NVMe | TR | Invoice | 2.59 $ |
| [Zentyx Limited](https://accsly.io/en/vps/hosting/zentyx) | Budget VPS 1 | 1 × 2.3 GHz | 6 GB | 40 GB SSD | GB | Visa/MC, PayPal | 2.67 $ |
| [Rabisu.com](https://accsly.io/en/vps/hosting/rabisu) | Aydın VPS x4 | 2 | 4 GB | 40 GB NVMe | AU, BG, CA, DE, GB, HK… | Visa/MC, PayPal, Crypto, Invoice | 2.99 $ (when paying for year: 2.46 $/mo) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-03 | 3 | 6 GB | 125 GB NVMe | DE, FI | PayPal, Invoice | 2.99 $ |
| [Brnchost internet ve bilişim hizmetleri](https://accsly.io/en/vps/hosting/brnchost) | VDS Kirala 2 | 2 | 4 GB | 35 GB SSD | TR | Visa/MC | 2.99 $ |
| [Server 4 You](https://accsly.io/en/vps/hosting/server4you) | VPS Basic (SSD) | 1 | 4 GB | 100 GB SSD | FR, US | — | 2.99 $ (when paying for 2 years: 2.57 $/mo) |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | VPS-2 (Xeon) | 4 | 6 GB | 60 GB NVMe | TR | Invoice | 2.99 $ |
| [TNA Hosting](https://accsly.io/en/vps/hosting/tnahosting) | Hybrid 4GB | 2 | 4 GB | 150 GB HDD | US | — | 3.00 $ |
| [ServerCheap](https://accsly.io/en/vps/hosting/servercheap) | NVMe-KVM-4GB-New | 2 × 3.1 GHz | 4 GB | 40 GB NVMe | US | PayPal | 3.00 $ (total when paying for 3 mo (9.00 $)) |
| [No Ack Hosting](https://accsly.io/en/vps/hosting/noackhosting) | KVM VPS Cheap | 4 | 4 GB | 50 GB SSD | SE | Visa/MC, PayPal, Invoice, Crypto | 3.05 $ (total when paying for 3 mo (9.16 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS4 Fransa | 2 × 4.0 GHz | 8 GB | 45 GB SSD | FR | PayPal, Invoice | 3.19 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/4-gb-ram?format=json

## VPS with 4 GB RAM: Windows, an online shop, a Docker stack and Java without compromises

Four gigabytes is the point at which a server stops being "single-task". It fits a full online shop with a database and cache, Windows Server for remote work, a small game server or a stack of several Docker containers. Yet 4 GB is still easy to waste: one misconfigured Java VM or an oversized database buffer eats half of it.

### Typical tasks and their memory budget

- **Windows Server with RDP.** The system itself takes 1.5–2 GB after boot, and a browser with a few tabs plus an office suite add another gigabyte. For one or two users this is the working minimum; more on the [VPS with Windows](https://accsly.io/en/vps/windows) page.
- **An online shop on a CMS.** Nginx, PHP-FPM with 10–15 processes, MySQL with a 1 GB buffer and Redis for sessions fit in 3–3.5 GB. For 1C-Bitrix with composite caching this is a sensible minimum; see VPS for Bitrix.
- **Docker Compose with 5–8 services**: an application, PostgreSQL, Redis, a reverse proxy, monitoring. A typical example is an automation platform with its own database, as in the [VPS for n8n](https://accsly.io/en/vps/for-n8n) section.
- **A vanilla Minecraft server** for 10–20 players: 2.5–3 GB goes to the Java heap, the rest to the system. With modpacks this is no longer enough.
- **A test environment** with a Java or .NET application and a database.

For a single bot, landing page or small blog, 4 GB is overpaying: such projects use less than a gigabyte, and the rest sits idle.

### Java and Windows: where people most often go wrong

A Java application without an explicit limit takes a quarter of the machine's memory for its heap and may try to grow further under load. On 4 GB, set `-Xmx` manually and leave 20–30% on top of it for metaspace, thread stacks and buffers: with `-Xmx3G` the process actually takes 3.5–3.8 GB, and on a server with a database that is a sure path to the OOM killer. The same rule applies to Minecraft servers: a 3 GB heap out of 4 is the maximum, and only if nothing else runs on the server.

Windows has its own quirk: the page file is system-managed and grows by default, so a memory shortage shows up not as crashing processes but as sluggishness and RDP freezes. Look at the Committed line in Task Manager: if it is consistently above the physical amount, you are short of memory, no matter what Available shows.

### How 4 GB pairs with cores and disk

On most plans 4 GB comes with 2 virtual cores and a 40–80 GB disk; options with 1 core or with 4 are less common. For a shop and Windows the second core matters more: PHP and the Windows interface hit single-thread CPU limits before they run out of memory. For a Docker stack with a database the disk matters more: take NVMe and check that there is enough space for images, since each layer takes hundreds of megabytes and nobody runs `docker system prune` just in case. If your scenario fits the budget, good-value plans of this size are collected in the [cheap VPS with 4 GB](https://accsly.io/en/vps/cheap-4-gb) selection.

### Guaranteed memory or burst

On KVM, all 4 GB are allocated to the virtual machine. On OpenVZ and LXC, a "4 GB" plan is often made up of 2 GB of guaranteed memory and 2 GB of burst, which the node hands out only when resources are free. Container virtualisation doesn't suit Windows at all, and for Java and databases burst is dangerous: the application grows into the "bonus" memory and then hits OOM when the neighbours take their share. Look for the words "guaranteed" or "dedicated" memory and the virtualisation type in the plan description.

### Checks after buying

1. `systemd-detect-virt`: make sure the virtualisation is the one you paid for.
2. `free -h` and `cat /proc/meminfo`: MemTotal should be about 3.8 GB. If you see 2 GB with "the rest on demand", you are looking at burst.
3. On a container, look at `/proc/user_beancounters` (OpenVZ) or `/sys/fs/cgroup/memory.max` (LXC with cgroup v2): they show the real limits.
4. A load test: `stress-ng --vm 1 --vm-bytes 3G --timeout 60s`. On an honest 4 GB it completes without killed processes and without a sharp rise in steal in `top`.
5. On Windows, open System Information and Resource Monitor: installed memory should match the plan.

If, once set up, the server consistently uses more than 3 GB excluding cache and swap keeps growing, the project has outgrown the plan: move to 8 GB before an OOM happens during working hours.

## FAQ

### Is 4 GB RAM enough for Windows Server?

For one or two users with a browser and office programs, yes. For a terminal server for several staff members or 1C on Windows you need 8 GB or more.

### How much should I give Minecraft on a 4 GB server?

About 2.5–3 GB via the -Xmx parameter, if nothing else runs on the server. The rest is needed by the system and by the Java VM itself on top of the heap.

### Is a VPS with 4 GB suitable for an online shop?

Yes, for a shop with a catalogue of several thousand products and moderate traffic this is a normal amount. It is important to enable caching and limit the number of PHP-FPM processes.

### What matters more with 4 GB: a second core or more disk?

For websites and Windows, usually the second core; for Docker and databases, a fast NVMe disk with room to spare. Memory is used the same way in either case.

### How can I tell that the memory in a plan is not guaranteed?

Check the virtualisation type with systemd-detect-virt and the limits in /proc/user_beancounters or cgroup. On KVM, MemTotal is almost equal to the plan; on containers the guaranteed part may be half as much.

### How many Docker containers will run on 4 GB?

Usually 5–8 services, including one database. Give each a memory limit in the compose file so that a leak in one container doesn't bring down the others.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS with 8 GB RAM

Plans with 8 GB of RAM or more — high-load projects and multiple websites.

> Source: https://accsly.io/en/vps/8-gb-ram · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 18,279, hosts: 1,987
- Price: from 2.20 $, a quarter below 43.65 $, median 88.42 $
- NVMe: 43 %, unlimited traffic: 30 %, hourly billing: 23 %
- RAM → price from: 1 GB — 3.19 $, 2 GB — 3.19 $, 4 GB — 3.19 $, 8 GB — 3.19 $, 16 GB — 3.46 $
- Countries: USA (5646), Germany (3980), Netherlands (3584), United Kingdom (3344), Singapore (2499), India (2227)
- Cheapest hosts: [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 3.19 $, [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) — 3.46 $, [BalHost](https://accsly.io/en/vps/hosting/balhost-net) — 4.19 $, [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) — 4.42 $, [ByteHosting](https://accsly.io/en/vps/hosting/bytehosting) — 4.47 $

## Cheapest plans — 18,279 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Server Hosh](https://accsly.io/en/vps/hosting/serverhosh) | 10yrs Special Package | 4 | 10 GB | 100 GB SSD | US | Visa/MC, PayPal, Crypto, Invoice | 2.20 $ (total when paying for 10 years (265 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS4 Fransa | 2 × 4.0 GHz | 8 GB | 45 GB SSD | FR | PayPal, Invoice | 3.19 $ |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | General Basic | 2 | 16 GB | 200 GB SSD | IN | Invoice | 3.46 $ |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | VPS-3 (Xeon) | 4 | 8 GB | 80 GB NVMe | TR | Invoice | 4.19 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS5 Fransa | 3 × 4.0 GHz | 12 GB | 65 GB SSD | FR | PayPal, Invoice | 4.39 $ |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-2 | 4 × 3.3 GHz | 10 GB | 100 GB NVMe |  | PayPal, Visa/MC, Crypto | 4.42 $ (yearly: 4.42 $/mo) |
| [ByteHosting](https://accsly.io/en/vps/hosting/bytehosting) | Xeon Gold – 8GB | 2 | 8 GB | 75 GB NVMe | DE | PayPal, Crypto | 4.47 $ |
| [Zentyx Limited](https://accsly.io/en/vps/hosting/zentyx) | Budget VPS 2 | 2 × 2.3 GHz | 8 GB | 50 GB SSD | GB | Visa/MC, PayPal | 4.55 $ |
| [Brnchost internet ve bilişim hizmetleri](https://accsly.io/en/vps/hosting/brnchost) | VDS Kirala 4 | 4 | 8 GB | 45 GB SSD | TR | Visa/MC | 4.59 $ |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | VDS-5 | 4 | 8 GB | 75 GB NVMe | TR | Invoice | 4.79 $ |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | Gold 4C/8GB/100GB | 4 | 8 GB | 100 GB SSD | IN | Invoice | 4.88 $ |
| [Time4VPS](https://accsly.io/en/vps/hosting/time4vps) | C8 Plan | 3 | 8 GB | 100 GB SSD | LT | PayPal, Visa/MC, Invoice, Crypto | 4.91 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-04 | 4 | 12 GB | 250 GB NVMe | DE, FI | PayPal, Invoice | 4.98 $ |
| [TNA Hosting](https://accsly.io/en/vps/hosting/tnahosting) | Hybrid 8GB | 3 | 8 GB | 300 GB HDD | US | — | 5.00 $ |
| [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | VDS L-TR 8GB | 4 | 8 GB | 60 GB NVMe | TR | Visa/MC | 5.09 $ |
| [Rabisu.com](https://accsly.io/en/vps/hosting/rabisu) | Aydın VPS x8 | 4 | 8 GB | 60 GB NVMe | AU, BG, CA, DE, GB, HK… | Visa/MC, PayPal, Crypto, Invoice | 5.25 $ (when paying for year: 4.20 $/mo) |
| [Mag Host](https://accsly.io/en/vps/hosting/maghost) | hyb.v3-80-8 | 3 | 8 GB | 80 GB SSD | RO | Visa/MC, PayPal, Crypto | 5.31 $ |
| [Webyne](https://accsly.io/en/vps/hosting/webyne) | Speed VPS1 | 4 | 8 GB | 200 GB SSD | IN | Visa/MC, Invoice | 5.32 $ |
| [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) | Старт3 SSD 2026 | 5 | 10 GB | 60 GB SSD | RU | Invoice, MIR, SBP, YooMoney | 5.45 $ (when paying for 2 years: 4.09 $/mo) |
| [Linveo](https://accsly.io/en/vps/hosting/linveo) | Intel KVM VPS 8GB | 4 | 8 GB | 50 GB NVMe | US | Visa/MC | 5.50 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/8-gb-ram?format=json

## VPS with 8 GB RAM: several projects, 1C and game servers on one machine

People usually go for eight gigabytes when they have too many small servers and want to merge them into one, or when a single task needs memory in earnest: 1C with a database for several users, a modded game server, GitLab, CI runners. At this size the main question is no longer "will it fit" but "how do I split memory between services so that one doesn't starve the rest".

### What runs on 8 GB

- **Consolidation.** Five to ten websites on a shared Nginx and a single MySQL, plus bots and cron jobs that used to live on separate 1–2 GB VPSes. One database with a 2–3 GB buffer works more efficiently than five small ones.
- **1C:Enterprise.** A file-based database with web publishing, or the client-server version with PostgreSQL for 5–10 users: the 1C cluster takes 2–4 GB and the database another 2–3. Details on licences and platform versions are in the VPS for 1C section.
- **GitLab** for a small team: the official minimum is 4 GB, but with a runner, container registry and Prometheus it becomes comfortable from 8 GB. See [VPS for GitLab](https://accsly.io/en/vps/for-gitlab).
- **Game servers**: Minecraft with a modpack for 20–40 players, a Rust or ARK server for a small community, or a couple of CS2 servers at once. Choosing by game is covered on the [VPS for a game server](https://accsly.io/en/vps/for-game-server) page.
- **Windows Server** as a terminal server for 3–5 staff members with office software.

8 GB is overkill for a single CMS website, a single bot or a corporate VPN: such tasks live for years on 2 GB, and the extra memory will simply go to the file cache. It becomes too little when the database outgrows 10–15 GB and no longer fits in the buffer, when Elasticsearch appears on the server, or when the number of 1C users goes above fifteen. The tell-tale sign is swap that stays in use and response times that grow at peak hours while the CPU is not loaded.

### How to split memory between services

The most common mistake at 8 GB is having every service tuned "for the whole server". MySQL with the "buffer at 70% of memory" advice, Java with its default heap and PHP-FPM with a hundred processes each look reasonable on their own, but together they guarantee an OOM. Plan the budget in advance:

1. Leave 1 GB for the system and the file cache.
2. Give the database a fixed share: size `innodb_buffer_pool_size` or `shared_buffers` by the amount of hot data, not by a formula based on total memory.
3. Set `-Xmx` for Java applications and game servers, leaving 25% headroom for off-heap memory.
4. Set `mem_limit` for Docker containers and `MemoryMax=` in the unit file for systemd services. Then, if something leaks, the kernel kills the culprit rather than the database.

A 2–4 GB swap is still needed as a safety net, but keep `vm.swappiness` low: a game server that has gone into swap starts lagging for every player at once.

### Cores, disk and an honest plan

The typical combination is 8 GB with 4 virtual cores and an 80–160 GB disk. Game servers and 1C care more about single-core clock speed than about core count, while GitLab and CI, on the contrary, love parallelism. This is the size at which the difference between plans of the same spec first becomes really noticeable: the cheapest 8 GB plans are often sold on oversold nodes, where the memory is formally yours but the CPU and disk are shared with dozens of neighbours. The sign is a high `steal` in `top` while your own workload is idle.

### Guaranteed memory versus burst

8 GB OpenVZ and LXC container plans are sometimes put together as 4 GB guaranteed plus 4 GB burst. For a set of websites that is tolerable; for 1C, a database or a game server it is not: they need memory that won't be taken away during the evening peak. For such tasks choose a [KVM VPS](https://accsly.io/en/vps/kvm), where the whole amount is allocated to the virtual machine. But even on KVM the host may use a balloon driver: check `lsmod | grep virtio_balloon`. The module itself is nothing to worry about, but if MemTotal shrinks over time, memory is being taken from the machine.

### How to check the server after purchase

- `free -h`: a MemTotal of about 7.7–7.8 GB is normal for KVM.
- `stress-ng --vm 2 --vm-bytes 6G --timeout 120s`: allocating the full amount should not lead to killed processes or a frozen SSH session.
- `sysbench memory run` measures memory speed. A result much lower than on other plans is a reason to suspect an overloaded node.
- After a day of operation, look at `sar -r` or your monitoring graphs: they show how much memory your services really use and whether it's time to trim the excess.

## FAQ

### Is 8 GB RAM enough for 1C?

Yes, for a file-based database with web access or the client-server version with PostgreSQL for 5–10 users. For 20 or more users and several databases you need 16 GB.

### How many players can Minecraft handle on 8 GB?

A vanilla or Paper server handles 50 or more players, a modded build 20–40, depending on the modpack and view distance. Give 6 GB to the Java heap and leave the rest to the system.

### Which is better: one 8 GB VPS or four 2 GB ones?

One big server is cheaper to maintain and uses memory more efficiently for a shared database and cache. Separate machines isolate projects more reliably: if one goes down, the others are not affected.

### Is 8 GB enough for GitLab?

Yes, for a team of up to 20–30 people. If a CI runner building Docker images runs on the same machine, limit its memory and the number of parallel jobs.

### Why is my 8 GB server slow even though memory is free?

Most often the cause is CPU or disk use by neighbours on the node. Check the steal value in top and iowait: high values mean an overloaded host, not a shortage of memory.

### Do I need swap on an 8 GB VPS?

A small one, 2–4 GB, as protection against the OOM killer during peaks. Constantly running in swap means you need to cut service limits or get more memory.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS with 16 GB RAM

Plans with 16 GB of RAM or more — databases, CI, heavy applications.

> Source: https://accsly.io/en/vps/16-gb-ram · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 11,954, hosts: 1,581
- Price: from 3.46 $, a quarter below 68.00 $, median 140 $
- NVMe: 42 %, unlimited traffic: 27 %, hourly billing: 29 %
- RAM → price from: 1 GB — 3.46 $, 2 GB — 3.46 $, 4 GB — 3.46 $, 8 GB — 3.46 $, 16 GB — 3.46 $
- Countries: USA (3939), Germany (2855), Netherlands (2533), United Kingdom (2477), Singapore (1895), India (1772)
- Cheapest hosts: [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) — 3.46 $, [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 6.38 $, [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) — 6.66 $, [Time4VPS](https://accsly.io/en/vps/hosting/time4vps) — 7.85 $, [SpeedHost247.com](https://accsly.io/en/vps/hosting/speedhost247) — 7.95 $

## Cheapest plans — 11,954 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | General Basic | 2 | 16 GB | 200 GB SSD | IN | Invoice | 3.46 $ |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | General Essentials | 4 | 32 GB | 500 GB SSD | IN | Invoice | 6.30 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS6 Fransa | 4 × 4.0 GHz | 16 GB | 85 GB SSD | FR | PayPal, Invoice | 6.38 $ |
| [WeHaveServers](https://accsly.io/en/vps/hosting/wehaveservers) | VPS-3 | 6 × 3.3 GHz | 16 GB | 200 GB NVMe |  | PayPal, Visa/MC, Crypto | 6.66 $ |
| [Time4VPS](https://accsly.io/en/vps/hosting/time4vps) | C16 Plan | 4 | 16 GB | 200 GB SSD | LT | PayPal, Visa/MC, Invoice, Crypto | 7.85 $ |
| [SpeedHost247.com](https://accsly.io/en/vps/hosting/speedhost247) | Premium VPS | 12 | 48 GB | 250 GB NVMe | GB, SG, IN | — | 7.95 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-05 | 6 | 24 GB | 500 GB NVMe | DE, FI | PayPal, Invoice | 7.97 $ |
| [Zentyx Limited](https://accsly.io/en/vps/hosting/zentyx) | Budget VPS 4 | 4 × 2.3 GHz | 16 GB | 150 GB SSD | GB | Visa/MC, PayPal | 8.03 $ |
| [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | VDS L-TR 16GB | 4 | 16 GB | 90 GB NVMe | TR | Visa/MC | 8.27 $ |
| [Prohoster](https://accsly.io/en/vps/hosting/prohoster) | VPS-4-1-SSD | 2 | 16 GB | 80 GB SSD | NL | Visa/MC, Crypto | 8.40 $ |
| [TNA Hosting](https://accsly.io/en/vps/hosting/tnahosting) | Hybrid 16GB | 4 | 16 GB | 650 GB HDD | US | — | 8.50 $ |
| [Square Brothers](https://accsly.io/en/vps/hosting/squarebrothers) | Premium | 4 | 16 GB | 150 GB NVMe | IN | Visa/MC, PayPal | 8.52 $ |
| [almas.host](https://accsly.io/en/vps/hosting/almas) | vpsx-70 | 4 | 16 GB | 100 GB NVMe | IR | — | 8.53 $ |
| [ByteHosting](https://accsly.io/en/vps/hosting/bytehosting) | Xeon Gold – 16GB | 4 | 16 GB | 150 GB NVMe | DE | PayPal, Crypto | 8.94 $ |
| [LeaseWeb](https://accsly.io/en/vps/hosting/leaseweb) | Leaseweb VPS 2 | 6 | 16 GB | 200 GB NVMe |  | Visa/MC, Invoice, PayPal | 9.05 $ |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | Forex 6C/16GB/300GB | 6 | 16 GB | 300 GB SSD | IN | Invoice | 9.13 $ |
| [SSD Nodes](https://accsly.io/en/vps/hosting/ssdnodes) | Standard KVM / MEDIUM | 4 | 16 GB | 320 GB SSD | US, GB, NL, DE, IN, SG… | — | 9.41 $ (total when paying for 3 years (339 $)) |
| [Keyubu](https://accsly.io/en/vps/hosting/keyubu) | VPS L-TR 16GB | 8 | 16 GB | 100 GB NVMe | TR | Visa/MC | 9.78 $ (yearly: 9.77 $/mo) |
| [Rabisu.com](https://accsly.io/en/vps/hosting/rabisu) | Aydın VPS x16 | 6 | 16 GB | 120 GB NVMe | AU, BG, CA, DE, GB, HK… | Visa/MC, PayPal, Crypto, Invoice | 9.81 $ (when paying for year: 7.86 $/mo) |
| [dashserv](https://accsly.io/en/vps/hosting/dashserv) | XEON GOLD CEPH Super | 4 × 3.9 GHz | 16 GB | 150 GB SSD | DE | PayPal, Invoice | 10.02 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/16-gb-ram?format=json

## VPS with 16 GB RAM: in-memory databases, search and local AI models

Sixteen gigabytes is the size at which memory starts working as an accelerator rather than a constraint. The main reason to take it is data: a database that fits entirely in cache, a search index, analytics, a language model. If on 8 GB you were splitting memory between services, on 16 GB you decide which one gets the lion's share.

### Workloads that call for 16 GB

- **PostgreSQL or MySQL with a 10–30 GB database.** The hot part of the data (active orders, users, indexes) fits in memory, and queries stop waiting on the disk. How to tune a server for a database is covered in the [VPS for PostgreSQL](https://accsly.io/en/vps/for-postgresql) section.
- **Elasticsearch or OpenSearch** on a single node: 8 GB goes to the heap, and Lucene needs the rest for the file cache. Indexes of up to several tens of gigabytes run at acceptable speed; see [VPS for Elasticsearch](https://accsly.io/en/vps/for-elasticsearch).
- **Language models on the CPU.** A 7–8 billion parameter model in 4-bit quantisation takes 5–6 GB, a 13–14 billion one 9–10 GB. Both fit in 16 GB together with a web interface. Response speed will be limited by the CPU, not memory; details are in the [VPS for Ollama](https://accsly.io/en/vps/for-ollama) section.
- **1C in client-server mode** for 15–30 users: the 1C cluster and PostgreSQL on one machine.
- **A Kubernetes node** or a k3s test environment with a dozen microservices, monitoring and logging.
- **A CI server** that builds several Node.js, Java or Go projects in parallel.

16 GB becomes overpaying if the server hosts a set of small websites and bots: they don't need that much cache, and an 8 GB plan with the same number of cores will cope just as well. Before adding memory, look at where the current memory goes: the "shortage" often turns out to be a single leaking process or a database without indexes that reads whole tables. If the working data set really is growing faster than the buffer can hold, the next step is 32 GB or a separate database server.

### How to allocate 16 GB for a database

For a dedicated database server the classic guidelines are: in PostgreSQL, `shared_buffers` around 4 GB (25%) and `effective_cache_size` 11–12 GB, because the kernel uses the rest for the file cache, which Postgres also reads from. `work_mem` is multiplied by the number of concurrent sort operations, so 64 MB across a hundred connections can easily eat all the memory: keep a connection pool via PgBouncer. For MySQL with InnoDB the buffer can be raised to 10–11 GB if there are no other heavy services on the server.

For Elasticsearch the rule is the opposite: the heap gets no more than half of memory, and the other half must stay free for the operating system cache. Setting the heap to 14 GB out of 16 is a common mistake that makes search slower, not faster.

### Disk and cores at 16 GB

16 GB usually comes with 4–8 virtual cores and a 160–320 GB disk. For databases and search, choose only an [NVMe VPS](https://accsly.io/en/vps/nvme): memory speeds up reads, but writing the transaction log and merging index segments still hit the disk. For AI models the cores and their generation matter more: AVX2 or AVX-512 support speeds up model inference several times over, and you can check for it with `grep -o 'avx[^ ]*' /proc/cpuinfo | sort -u`.

### Guaranteed memory, OOM and swap

The tasks people take 16 GB for cope badly with both container burst memory and swap. A database that has grown into non-guaranteed memory gets an OOM at the busiest moment when that memory is reclaimed; Elasticsearch, once its heap lands in swap, starts pausing for garbage collection for tens of seconds. So:

- take KVM with fully dedicated memory, not OpenVZ or LXC with burst;
- for Elasticsearch enable `bootstrap.memory_lock`, and for Postgres set `vm.overcommit_memory=2` as the documentation recommends;
- keep swap small, 2–4 GB, and make sure it doesn't grow.

### Checks after purchase

1. `free -h` and `nproc`: about 15.6 GB of memory and the number of cores stated in the plan.
2. `stress-ng --vm 2 --vm-bytes 14G --timeout 120s`: the server should survive filling its memory without freezing.
3. `fio` with random 4 KB block writes: for a database this matters more than sequential read speed.
4. After a week of operation, compare the size of the hot data with the buffers: if the cache hit ratio in `pg_stat_database` is below 99%, there isn't enough memory for the data.

## FAQ

### What AI model can I run on a VPS with 16 GB RAM?

Models with 7–14 billion parameters in 4-bit quantisation. They will run on the CPU, so answers are generated at a few words per second.

### What shared_buffers value should I set in PostgreSQL on 16 GB?

Usually around 4 GB, with effective_cache_size at 11–12 GB. PostgreSQL uses the rest of the memory through the operating system's file cache.

### Is 16 GB enough for Elasticsearch?

Yes, for a single node with indexes of up to several tens of gigabytes. Give the heap 8 GB and leave the other half for the file system cache.

### How many 1C users can a 16 GB server handle?

The client-server version with PostgreSQL on one machine is usually sized for 15–30 active users. A lot depends on the configuration and heavy reports.

### Do I need NVMe if the database fits in memory?

Yes. More reads will come from memory, but writing the transaction log, checkpoints and recovery after a restart still depend on disk speed.

### Can I use a 16 GB OpenVZ plan for a database?

Only if all the memory in the plan is guaranteed. Burst memory is dangerous for a database: when the node is under load it gets reclaimed, and the process hits an OOM.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# NVMe VPS/VDS

Plans on NVMe drives only — several times faster than SATA SSD at reads and writes.

> Source: https://accsly.io/en/vps/nvme · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 12,681, hosts: 1,165
- Price: from 0.40 $, a quarter below 16.17 $, median 38.66 $
- NVMe: 100 %, unlimited traffic: 35 %, hourly billing: 12 %
- RAM → price from: 1 GB — 0.71 $, 2 GB — 1.19 $, 4 GB — 1.70 $, 8 GB — 4.19 $, 16 GB — 6.66 $
- Countries: USA (3372), Germany (2593), Netherlands (2117), United Kingdom (1841), Singapore (979), Russia (977)
- Cheapest hosts: [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) — 0.71 $, [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 0.90 $, [HostVDS](https://accsly.io/en/vps/hosting/hostvds) — 0.99 $, [h2 NEXUS](https://accsly.io/en/vps/hosting/h2) — 1.00 $, [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 1.19 $

## Cheapest plans — 12,681 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-384 Low-Cost Special US | 1 × 3.0 GHz | 384 MB | 12 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.40 $ (total when paying for 6 mo (2.39 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-II 384 Europe | 1 × 3.1 GHz | 384 MB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 0.42 $ (total when paying for 6 mo (2.50 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM SG 400MB NAT | 1 | 400 MB | 5 GB NVMe | SG | — | 0.58 $ (total when paying for year (6.99 $)) |
| [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) | IaaS Lite 1 vCPU / 1 ГБ | 1 | 1 GB | 10 GB NVMe | RU | MIR, SBP, Crypto, WebMoney, Invoice | 0.71 $ |
| [EUGameHost](https://accsly.io/en/vps/hosting/eugamehost) | Nano Edge | 1 | 512 MB | 5 GB NVMe | GB | PayPal, Visa/MC | 0.86 $ (when paying for year: 0.67 $/mo) |
| [uaVPS](https://accsly.io/en/vps/hosting/uavps) | VPS-PROMO | 1 | 512 MB | 10 GB NVMe | UA, PL, FR, DE, NL | — | 0.90 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-1024 US | 2 × 3.0 GHz | 1 GB | 30 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.90 $ (total when paying for 3 mo (2.69 $)) |
| [RuVPS](https://accsly.io/en/vps/hosting/ruvps) | VPS-0 | 1 | 768 MB | 7 GB NVMe | NL, PL, UA | Visa/MC, Crypto | 0.95 $ |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 1 | 1 | 1 GB | 10 GB NVMe | US, HK | Visa/MC, Crypto | 0.99 $ |
| [Jink Host](https://accsly.io/en/vps/hosting/jink) | Dirt | 1 | 512 MB | 20 GB NVMe | US, NL | Visa/MC, PayPal, Crypto | 1.00 $ (total when paying for 3 mo (3.00 $)) |
| [h2 NEXUS](https://accsly.io/en/vps/hosting/h2) | RED-PROMO | 1 × 3.3 GHz | 1 GB | 10 GB NVMe | DE, FI, PL | — | 1.00 $ |
| [Hostablanca.com](https://accsly.io/en/vps/hosting/hostablanca) | Cheap VPS (слайдер, по умолчанию) | 1 | 512 MB | 10 GB NVMe | ES, DE | Crypto, Visa/MC | 1.01 $ (when paying for year: 0.93 $/mo) |
| [TierHive](https://accsly.io/en/vps/hosting/tierhive) | Калькулятор (конфигурация по умолчанию) | 1 | 1 GB | 20 GB NVMe | NL, CA, DE, FR, US, GB… | — | 1.01 $ |
| [ReconV](https://accsly.io/en/vps/hosting/reconv) | LXC 512 MB | 1 | 512 MB | 6 GB NVMe | PL, FR | PayPal | 1.02 $ |
| [myPrepaid-Server](https://accsly.io/en/vps/hosting/myprepaid-server) | 1 Euro Server | 1 × 3.5 GHz | 512 MB | 20 GB NVMe | DE | Visa/MC, PayPal, Invoice | 1.12 $ |
| [DeinServerHost](https://accsly.io/en/vps/hosting/deinserverhost) | KVM vServer FLEX | 1 | 1 GB | 10 GB NVMe | DE | PayPal, Invoice, Visa/MC, Crypto | 1.12 $ |
| [Hostablanca.com](https://accsly.io/en/vps/hosting/hostablanca) | VPS 11 | 1 | 600 MB | 11 GB NVMe | ES, DE | Crypto, Visa/MC | 1.12 $ (when paying for year: 1.02 $/mo) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-01 | 1 | 2 GB | 40 GB NVMe | DE, FI | PayPal, Invoice | 1.19 $ |
| [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) | IaaS Lite 1 vCPU / 2 ГБ | 1 | 2 GB | 20 GB NVMe | RU | MIR, SBP, Crypto, WebMoney, Invoice | 1.20 $ |
| [Hostablanca.com](https://accsly.io/en/vps/hosting/hostablanca) | VPS 12 | 1 | 700 MB | 12 GB NVMe | ES, DE | Crypto, Visa/MC | 1.24 $ (when paying for year: 1.12 $/mo) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/nvme?format=json

## NVMe, SSD or HDD: when you really need an NVMe VPS

The word NVMe has become almost mandatory in plan descriptions, but the difference between disks isn't felt in every task. To avoid overpaying — or making the opposite mistake — it helps to understand how the three types of storage differ and which numbers actually matter.

### How NVMe, SATA SSD and HDD differ

- **HDD** — a mechanical disk. Sequential reads of 150–250 MB/s, but random access is slow: on the order of one or two hundred operations per second. Suitable for archives and backups; see [HDD VPS](https://accsly.io/en/vps/hdd) and [Storage VPS](https://accsly.io/en/vps/storage).
- **SATA SSD** — flash memory on an older interface. It hits the SATA bus ceiling at about 550 MB/s, but random operations already reach tens of thousands per second.
- **NVMe** — flash on the PCIe bus. A single drive delivers gigabytes per second and hundreds of thousands of IOPS, and most importantly, noticeably lower latency per operation and deep request queues.

On a VPS you don't get the whole disk, but your share of it: the host sets IOPS and throughput limits for each virtual machine. So "NVMe" on a plan doesn't mean 7 GB/s; it means the shared array is fast and your server has to wait for its neighbours less.

### Where NVMe gives a real gain

- **Databases.** PostgreSQL and MySQL constantly do small random reads and write their log with fsync. What matters here is IOPS and latency, not megabytes per second. If the database doesn't fit entirely into RAM, NVMe speeds up queries several times over. More on this: [VPS for PostgreSQL](https://accsly.io/en/vps/for-postgresql).
- **Game servers.** Minecraft, Rust and ARK write the world to disk in chunks and save it on a schedule. On a slow disk this causes lag when new areas are generated and during autosaves.
- **Builds and CI.** `npm install`, `composer install`, compilation and Docker layers mean thousands of small files. On NVMe the build finishes noticeably faster.
- **Online stores and CMSs** with a large catalogue and no full caching.

### Where there's almost no difference

Your own VPN, a proxy, a Telegram bot, a static site behind nginx — all of these live in RAM and are limited by the network or the CPU. There's no need to overpay for NVMe for these tasks, although these days it often costs the same as SATA SSD. For backups and file archives capacity matters more than speed: HDD is better value there.

### How to check that the disk really is fast

The label on the plan guarantees nothing: there are NVMe plans with strict limits, and SSD arrays that perform better. After the server starts, test random operations, not just linear speed:

`fio --name=rand --rw=randrw --bs=4k --size=1G --iodepth=32 --direct=1 --runtime=30 --time_based`

As a guideline: on a good NVMe plan, 4K random reads give tens of thousands of IOPS or more; on an overloaded SATA SSD, a few thousand. A `dd` test shows only sequential writes and almost always looks good, so you can't judge by it.

The table above collects plans whose disk type is listed as NVMe on the host's website. If your budget is tight, start with the selection of [cheap NVMe VPS](https://accsly.io/en/vps/cheap-nvme) and sort by price.

## FAQ

### What are IOPS and why do they matter more than speed in MB/s?

IOPS is the number of input/output operations per second. Databases and websites make many small random disk accesses, so their speed depends on IOPS and latency, not on the linear read speed of large files.

### Does a WordPress site need NVMe?

For a small cached site the difference is barely noticeable. For a WooCommerce store with a large catalogue and no full cache, NVMe speeds up the database and the admin panel.

### Why does a dd test show 1 GB/s while the site is still slow?

dd measures sequential writes, which are almost always fast. The bottleneck is usually random operations in small blocks — test them with fio using a 4k block size.

### Can an NVMe VPS be worse than an SSD one?

Yes. If the host strictly limits IOPS per virtual machine or overloads the array, an NVMe plan can run slower than a good SATA SSD. That's why it's worth testing the speed after purchase.

### What should I prioritise for a game server: NVMe or more memory?

Memory and CPU clock speed first, then the disk. But if the world is large and players actively explore the map, NVMe noticeably reduces lag during chunk generation and autosaves.

### Is NVMe suitable for storing backups?

It is, but usually not cost-effective: a gigabyte on NVMe costs more. For archives and backups it's better to take plans with a large HDD.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# KVM VPS/VDS

Full KVM virtualization: your own kernel, Docker, VPN, any OS and your own ISO image.

> Source: https://accsly.io/en/vps/kvm · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 28,789, hosts: 2,094
- Price: from 0.40 $, a quarter below 18.90 $, median 46.02 $
- NVMe: 42 %, unlimited traffic: 31 %, hourly billing: 19 %
- RAM → price from: 1 GB — 0.49 $, 2 GB — 1.20 $, 4 GB — 2.17 $, 8 GB — 3.46 $, 16 GB — 3.46 $
- Countries: USA (8486), Germany (5685), Netherlands (5380), United Kingdom (4639), Singapore (3505), India (2725)
- Cheapest hosts: [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) — 0.71 $, [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 0.90 $, [V.PS](https://accsly.io/en/vps/hosting/v) — 0.93 $, [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) — 0.97 $, [HostVDS](https://accsly.io/en/vps/hosting/hostvds) — 0.99 $

## Cheapest plans — 28,789 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-384 Low-Cost Special US | 1 × 3.0 GHz | 384 MB | 12 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.40 $ (total when paying for 6 mo (2.39 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-II 384 Europe | 1 × 3.1 GHz | 384 MB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 0.42 $ (total when paying for 6 mo (2.50 $)) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | STARDUST1-S | 1 × 2.1 GHz | 1 GB | — | FR, NL, PL | — | 0.49 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Pico | 1 | 128 MB | 5 GB SSD | US | Crypto | 0.50 $ |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM Canada NAT 256MB | 1 | 256 MB | 5 GB SSD | CA | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM India 256MB NAT | 1 | 256 MB | 5 GB SSD | IN | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM SG 400MB NAT | 1 | 400 MB | 5 GB NVMe | SG | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM Texas 300 MB NAT | 1 | 300 MB | 5 GB SSD | US | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM Turkey 256MB NAT | 1 | 256 MB | 5 GB SSD | TR | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM UK 256 MB NAT | 1 | 256 MB | 5 GB SSD | GB | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ SG 400MB NAT (KVM) | 1 | 400 MB | 5 GB SSD | SG | — | 0.58 $ (total when paying for year (6.99 $)) |
| [RocketCloud](https://accsly.io/en/vps/hosting/rocketcloud) | IaaS Lite 1 vCPU / 1 ГБ | 1 | 1 GB | 10 GB NVMe | RU | MIR, SBP, Crypto, WebMoney, Invoice | 0.71 $ |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-512-KVM | 1 | 512 MB | 6 GB SSD | SG, HK, JP, TW, DE, TR… | Crypto | 0.73 $ (total when paying for year (8.79 $)) |
| [EUGameHost](https://accsly.io/en/vps/hosting/eugamehost) | Nano Edge | 1 | 512 MB | 5 GB NVMe | GB | PayPal, Visa/MC | 0.86 $ (when paying for year: 0.67 $/mo) |
| [uaVPS](https://accsly.io/en/vps/hosting/uavps) | VPS-PROMO | 1 | 512 MB | 10 GB NVMe | UA, PL, FR, DE, NL | — | 0.90 $ |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-1024 US | 2 × 3.0 GHz | 1 GB | 30 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.90 $ (total when paying for 3 mo (2.69 $)) |
| [V.PS](https://accsly.io/en/vps/hosting/v) | Nano | 1 | 1 GB | 15 GB SSD | NL, DE | PayPal, Visa/MC, Invoice | 0.93 $ (total when paying for year (11.13 $)) |
| [RuVPS](https://accsly.io/en/vps/hosting/ruvps) | VPS-0 | 1 | 768 MB | 7 GB NVMe | NL, PL, UA | Visa/MC, Crypto | 0.95 $ |
| [ЕЛЕНАХОСТ](https://accsly.io/en/vps/hosting/elenahost) | Промо SSD 2026 | 1 | 1 GB | 6 GB SSD | RU | Invoice, MIR, SBP, YooMoney | 0.97 $ |
| [HostVDS](https://accsly.io/en/vps/hosting/hostvds) | HostVDS 1 | 1 | 1 GB | 10 GB NVMe | US, HK | Visa/MC, Crypto | 0.99 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/kvm?format=json

## KVM, OpenVZ or LXC: what a KVM VPS gives you

Almost all the plans in the table above run on KVM: in recent years hosts have largely moved to it from container virtualization. The "KVM" label has become the norm, but it's still useful to understand the difference — it explains why some programs start on a cheap server and others don't.

### How KVM differs from OpenVZ and LXC

KVM is hardware virtualization. Each virtual machine gets emulated "hardware" and boots its own operating system kernel, like an ordinary computer. To the system inside, it's a separate server.

OpenVZ and LXC are containers. All customers on a physical server run on one shared host kernel, and isolation is provided by the kernel itself. The overhead is lower, so containers are cheaper, but the host, not you, chooses the kernel version and its settings. More about these options on the [OpenVZ VPS](https://accsly.io/en/vps/openvz) and [LXC VPS](https://accsly.io/en/vps/lxc) pages.

### What your own kernel gives you

- **Docker and containers** work without caveats, whereas in OpenVZ and LXC their support depends on the host's settings. There's a selection for this task: [VPS for Docker](https://accsly.io/en/vps/for-docker).
- **Kernel-level VPN.** [WireGuard](https://accsly.io/en/vps/for-wireguard) is built into the Linux kernel and installs with one command on KVM; in a container you're left with a userspace implementation, if the host has opened the TUN device at all.
- **Any OS.** Windows, FreeBSD, your own image via ISO in the panel, disk encryption.
- **Network and memory tuning.** Your own swap, sysctl parameters, the BBR algorithm, nftables rules without restrictions.

That said, for a static site, a small bot or a scheduled script the difference is barely noticeable. If the program doesn't need its own kernel modules or Docker, a container will cope just as well and sometimes costs less. Problems start when the project grows and gets things a container can't do: moving to a new server mid-project is more awkward than taking KVM from the start.

### Does KVM guarantee dedicated resources

Only partly. On KVM the system sees memory as ordinary RAM of the given size, with no "burst" memory above the guaranteed amount that was often sold on OpenVZ. But CPU cores are almost always virtual and shared with neighbours, and KVM doesn't change that. If you need stable CPU performance, look for "dedicated cores" or "dedicated vCPU" in the description and check steal time in `top` after purchase. The disk can also be overloaded by neighbours, so the drive type and IOPS limits matter more than the word KVM in the name.

### How to check the virtualization

Log in to the server via SSH and run `systemd-detect-virt`: on KVM the command prints `kvm`, in a container `openvz` or `lxc`. If one thing is advertised and the system shows another, that's a reason to contact support or ask for a refund. On accsly the KVM filter is already applied, and each plan's card shows the price in your currency and the payment methods taken from the host's website.

## FAQ

### Which is better for a VPS: KVM or OpenVZ?

KVM for most tasks: your own kernel, Docker, WireGuard and any OS without restrictions. OpenVZ makes sense only if you need the cheapest possible server for a simple site or script.

### Does Docker work on OpenVZ and LXC?

Sometimes it does, if the host has enabled the necessary kernel features, but with network and storage limitations. On KVM Docker works just as on an ordinary server.

### Is OpenVZ suitable for a VPN?

OpenVPN will run in a container if the host has opened the TUN device, while WireGuard will only work in its userspace version. For your own VPN, KVM is more reliable.

### Can I install Windows on a KVM VPS?

Yes, KVM lets you install any OS, including Windows from your own ISO. Keep in mind that Windows Server needs a licence, and many hosts include it in their Windows plans.

### Is nested virtualization available on a KVM VPS?

Usually not: most hosts disable it. You can run your own virtual machines or an Android emulator inside a VPS only where nested virtualization support is explicitly stated.

### Why is an OpenVZ VPS cheaper than a KVM one?

Containers are lighter: no separate kernel is started for each customer, so more customers fit on one physical server. The price of the savings is less freedom in configuring the system.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS with unlimited traffic

Traffic is not metered — only the port speed is limited. Check the bandwidth on the plan card.

> Source: https://accsly.io/en/vps/unlimited-traffic · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 9,551, hosts: 947
- Price: from 0.49 $, a quarter below 16.79 $, median 38.15 $
- NVMe: 46 %, unlimited traffic: 100 %, hourly billing: 10 %
- RAM → price from: 1 GB — 0.49 $, 2 GB — 0.80 $, 4 GB — 1.60 $, 8 GB — 3.19 $, 16 GB — 6.38 $
- Countries: USA (1839), Germany (1341), Netherlands (1228), Russia (907), United Kingdom (822), France (725)
- Cheapest hosts: [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 0.70 $, [Inoventica](https://accsly.io/en/vps/hosting/invs) — 1.20 $, [OnlineVDS](https://accsly.io/en/vps/hosting/onlinevds) — 1.56 $, [Sindad](https://accsly.io/en/vps/hosting/sindad) — 1.71 $, [Servera](https://accsly.io/en/vps/hosting/servera) — 2.12 $

## Cheapest plans — 9,551 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | STARDUST1-S | 1 × 2.1 GHz | 1 GB | — | FR, NL, PL | — | 0.49 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Pico | 1 | 128 MB | 5 GB SSD | US | Crypto | 0.50 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS1 Türkiye | 1 × 3.4 GHz | 1 GB | 15 GB SSD | TR | PayPal, Invoice | 0.70 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS1 Fransa | 1 × 4.0 GHz | 2 GB | 15 GB SSD | FR | PayPal, Invoice | 0.80 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS2 Türkiye | 2 × 3.4 GHz | 1 GB | 20 GB SSD | TR | PayPal, Invoice | 0.80 $ |
| [uaVPS](https://accsly.io/en/vps/hosting/uavps) | VPS-PROMO | 1 | 512 MB | 10 GB NVMe | UA, PL, FR, DE, NL | — | 0.90 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS3 Türkiye | 2 × 3.4 GHz | 2 GB | 25 GB SSD | TR | PayPal, Invoice | 0.90 $ |
| [RuVPS](https://accsly.io/en/vps/hosting/ruvps) | VPS-0 | 1 | 768 MB | 7 GB NVMe | NL, PL, UA | Visa/MC, Crypto | 0.95 $ |
| [Jink Host](https://accsly.io/en/vps/hosting/jink) | Dirt | 1 | 512 MB | 20 GB NVMe | US, NL | Visa/MC, PayPal, Crypto | 1.00 $ (total when paying for 3 mo (3.00 $)) |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Nano | 1 | 256 MB | 10 GB SSD | US | Crypto | 1.00 $ |
| [Host Media Ltd](https://accsly.io/en/vps/hosting/hostmedia) | Developer VPS 512MB IPv6-only | 1 | 512 MB | 10 GB SSD | GB | Visa/MC | 1.01 $ (total when paying for year (12.07 $)) |
| [ReconV](https://accsly.io/en/vps/hosting/reconv) | LXC 512 MB | 1 | 512 MB | 6 GB NVMe | PL, FR | PayPal | 1.02 $ |
| [myPrepaid-Server](https://accsly.io/en/vps/hosting/myprepaid-server) | 1 Euro Server | 1 × 3.5 GHz | 512 MB | 20 GB NVMe | DE | Visa/MC, PayPal, Invoice | 1.12 $ |
| [myPrepaid-Server](https://accsly.io/en/vps/hosting/myprepaid-server) | ONLY IPv6 | 1 | 512 MB | 15 GB SSD | DE | Visa/MC, PayPal, Invoice | 1.12 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS4 Türkiye | 3 × 3.4 GHz | 2 GB | 30 GB SSD | TR | PayPal, Invoice | 1.20 $ |
| [eServer RU](https://accsly.io/en/vps/hosting/eserver-ru) | KVM VPS Econom Bronze-1 | 1 | 512 MB | 10 GB SSD | RU | WebMoney, MIR, Crypto, Invoice | 1.20 $ (when paying for year: 1.00 $/mo) |
| [Inoventica](https://accsly.io/en/vps/hosting/invs) | LUNA PROMO | 1 | 1 GB | 20 GB SSD | RU | YooMoney | 1.20 $ |
| [VDS4YOU](https://accsly.io/en/vps/hosting/vds4you) | Гибрид VDS MINI | 1 | 512 MB | 20 GB HDD | RU | MIR, Visa/MC, WebMoney, YooMoney, PayPal, Invoice, Crypto | 1.20 $ |
| [WebHosting24](https://accsly.io/en/vps/hosting/webhosting24) | Munich NVMe KVM 512MB | 1 × 2.4 GHz | 512 MB | 10 GB NVMe | DE | Visa/MC, PayPal, Crypto, Invoice | 1.39 $ (total when paying for year (16.79 $)) |
| [1hs](https://accsly.io/en/vps/hosting/1hs) | SSD-VPS-1 | 1 | 512 MB | 10 GB SSD | RU | Visa/MC, YooMoney, WebMoney, PayPal, Invoice | 1.44 $ (when paying for year: 1.30 $/mo) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/unlimited-traffic?format=json

## What a VPS with unlimited traffic really means

"Unlimited traffic" on a plan almost never means "as much as you like". It means the host doesn't count gigabytes but limits you through port speed and fair-use rules. Once you understand these two limits, it's easy to tell genuine unlimited from the marketing kind.

### Port speed is your real limit

Physically, you can't push more through a port in a month than its bandwidth allows. Simple arithmetic at 24/7 load:

- a 100 Mbps port — about 32 TB a month;
- a 1 Gbps port — about 320 TB a month;
- a 10 Gbps port — petabytes in theory, but nobody loads it like that.

That's why unlimited at 100 Mbps is more honest than "1 Gbps and 1 TB of traffic": in the first case you know the ceiling, in the second, once you hit the cap, the speed may be cut to 10 Mbps or you'll be billed for every gigabyte. Also check whether the speed is guaranteed or "up to": on a shared port several customers split the channel, and in the evening the real speed is lower. Plans with a wide channel are collected on the [1 Gbps VPS](https://accsly.io/en/vps/1-gbit) and [10 Gbps VPS](https://accsly.io/en/vps/10-gbit) pages.

### Fair use

Almost every unlimited contract has a fair-use clause. The wording varies, but the meaning is the same: if the server keeps the port 100% loaded for months, the host has the right to lower the speed, move you to another plan or ask you to leave. Read the terms before paying and look for specifics:

- whether there's an average-load threshold beyond which the speed is cut;
- whether only outgoing traffic is counted or incoming too (usually only outgoing);
- which kinds of load are prohibited: torrents, public proxies, file distribution, streaming.

### When traffic really matters

1. **A corporate VPN.** Video calls, file exchange and backups through the tunnel add up to many gigabytes per employee. A small team easily uses 1–3 TB a month, so for a [VPN VPS](https://accsly.io/en/vps/for-vpn) unlimited or a large allowance is almost a must.
2. **File and media distribution.** A video site, a file-sharing service, a distribution mirror, an update server for an app.
3. **Backups.** The first full upload and regular copies of large volumes eat traffic faster than you'd think. For a [backup server](https://accsly.io/en/vps/for-backups), unlimited removes the question of overage charges.
4. **Scraping and crawlers** that download millions of pages.

An ordinary website, bot or database, on the other hand, will be fine with 1 TB: even a busy project rarely serves more than a few hundred gigabytes a month.

### How to check the channel after purchase

Run `iperf3` against a public server or download a large test file at different times of day. See whether the speed holds in the evening. To track traffic, install `vnstat` — it shows actual usage and helps you understand whether you need unlimited at all. The table above marks plans where unlimited traffic is stated on the host's website; check the port speed in the specifications of the particular plan.

## FAQ

### How much traffic does a corporate VPN use per employee?

With email, documents and messengers, tens of gigabytes a month. Video calls and large file transfers through the tunnel raise usage to 100–300 GB or more.

### Is incoming traffic counted too?

Most hosts count only outgoing traffic; incoming is free. But this isn't a rule, so check the condition in the contract or ask support.

### Can a server with unlimited traffic be shut down?

Yes, if the load breaks fair-use rules or falls under prohibited uses, such as public torrent seeding. Usually the speed is reduced first or a warning is sent.

### Which is better: unlimited at 100 Mbps or 1 Gbps with a 2 TB cap?

It depends on the load profile. For a VPN and file distribution with a constant stream, unlimited is more reliable; for a site with occasional peaks, a gigabit port with an allowance will be faster.

### How do I find out how much traffic my server uses?

Install vnstat: it keeps statistics by day and month. Many hosts also show a traffic graph in the customer area.

### What happens when the traffic allowance runs out?

Usually the speed is reduced to 10 Mbps or lower until the end of the billing period, or you are charged for every extra gigabyte. Less often the server is suspended until payment.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS with DDoS protection

Plans with attack filtering included in the price.

> Source: https://accsly.io/en/vps/ddos-protection · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 16,004, hosts: 1,133
- Price: from 0.40 $, a quarter below 16.73 $, median 37.99 $
- NVMe: 49 %, unlimited traffic: 36 %, hourly billing: 11 %
- RAM → price from: 1 GB — 0.70 $, 2 GB — 0.80 $, 4 GB — 1.60 $, 8 GB — 3.19 $, 16 GB — 3.46 $
- Countries: USA (4820), Germany (3223), Netherlands (2550), United Kingdom (2344), Singapore (1574), India (1366)
- Cheapest hosts: [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) — 0.70 $, [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 0.90 $, [h2 NEXUS](https://accsly.io/en/vps/hosting/h2) — 1.00 $, [Inoventica](https://accsly.io/en/vps/hosting/invs) — 1.20 $, [Sive Host](https://accsly.io/en/vps/hosting/sive) — 1.22 $

## Cheapest plans — 16,004 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-384 Low-Cost Special US | 1 × 3.0 GHz | 384 MB | 12 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.40 $ (total when paying for 6 mo (2.39 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-II 384 Europe | 1 × 3.1 GHz | 384 MB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 0.42 $ (total when paying for 6 mo (2.50 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS1 Türkiye | 1 × 3.4 GHz | 1 GB | 15 GB SSD | TR | PayPal, Invoice | 0.70 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS1 Fransa | 1 × 4.0 GHz | 2 GB | 15 GB SSD | FR | PayPal, Invoice | 0.80 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS2 Türkiye | 2 × 3.4 GHz | 1 GB | 20 GB SSD | TR | PayPal, Invoice | 0.80 $ |
| [EUGameHost](https://accsly.io/en/vps/hosting/eugamehost) | Nano Edge | 1 | 512 MB | 5 GB NVMe | GB | PayPal, Visa/MC | 0.86 $ (when paying for year: 0.67 $/mo) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-1024 US | 2 × 3.0 GHz | 1 GB | 30 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.90 $ (total when paying for 3 mo (2.69 $)) |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS3 Türkiye | 2 × 3.4 GHz | 2 GB | 25 GB SSD | TR | PayPal, Invoice | 0.90 $ |
| [RuVPS](https://accsly.io/en/vps/hosting/ruvps) | VPS-0 | 1 | 768 MB | 7 GB NVMe | NL, PL, UA | Visa/MC, Crypto | 0.95 $ |
| [Jink Host](https://accsly.io/en/vps/hosting/jink) | Dirt | 1 | 512 MB | 20 GB NVMe | US, NL | Visa/MC, PayPal, Crypto | 1.00 $ (total when paying for 3 mo (3.00 $)) |
| [hostEONS.com](https://accsly.io/en/vps/hosting/hosteons) | OVZ256 | 1 | 256 MB | 5 GB SSD | US | PayPal, Visa/MC, Crypto, Invoice | 1.00 $ |
| [h2 NEXUS](https://accsly.io/en/vps/hosting/h2) | RED-PROMO | 1 × 3.3 GHz | 1 GB | 10 GB NVMe | DE, FI, PL | — | 1.00 $ |
| [Host Media Ltd](https://accsly.io/en/vps/hosting/hostmedia) | Developer VPS 512MB IPv6-only | 1 | 512 MB | 10 GB SSD | GB | Visa/MC | 1.01 $ (total when paying for year (12.07 $)) |
| [ReconV](https://accsly.io/en/vps/hosting/reconv) | LXC 512 MB | 1 | 512 MB | 6 GB NVMe | PL, FR | PayPal | 1.02 $ |
| [myPrepaid-Server](https://accsly.io/en/vps/hosting/myprepaid-server) | 1 Euro Server | 1 × 3.5 GHz | 512 MB | 20 GB NVMe | DE | Visa/MC, PayPal, Invoice | 1.12 $ |
| [DeinServerHost](https://accsly.io/en/vps/hosting/deinserverhost) | KVM vServer FLEX | 1 | 1 GB | 10 GB NVMe | DE | PayPal, Invoice, Visa/MC, Crypto | 1.12 $ |
| [myPrepaid-Server](https://accsly.io/en/vps/hosting/myprepaid-server) | ONLY IPv6 | 1 | 512 MB | 15 GB SSD | DE | Visa/MC, PayPal, Invoice | 1.12 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | DE-AMD-01 | 1 | 2 GB | 40 GB NVMe | DE, FI | PayPal, Invoice | 1.19 $ |
| [Çelen Hosting Information Tech.](https://accsly.io/en/vps/hosting/celenhosting) | VDS4 Türkiye | 3 × 3.4 GHz | 2 GB | 30 GB SSD | TR | PayPal, Invoice | 1.20 $ |
| [eServer RU](https://accsly.io/en/vps/hosting/eserver-ru) | KVM VPS Econom Bronze-1 | 1 | 512 MB | 10 GB SSD | RU | WebMoney, MIR, Crypto, Invoice | 1.20 $ (when paying for year: 1.00 $/mo) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/ddos-protection?format=json

## What VPS DDoS protection really includes

More than half the plans in the catalogue carry a "DDoS protection" label, including the cheapest ones. Behind the same words are different services: from basic filtering at the edge of the data centre network to a separate protected IP with application-level traffic scrubbing. Before renting a VDS for a game, a store or an API, work out exactly what you're being protected from.

### L3/L4 and L7 are two different problems

Most attacks are volumetric, at the network and transport layers (L3/L4): UDP floods, SYN floods, amplification via DNS, NTP or memcached. The goal is to clog the channel or the connection table. Filtering at the provider works against them: traffic passes through scrubbing equipment before it reaches the server. This is what's usually called basic protection.

Application-layer (L7) attacks look like ordinary HTTP requests: thousands of bots open search, the cart, the login form. Their volume is small, and the network filter doesn't notice them. Different tools are needed here: a protective proxy or CDN in front of the site, request limits in nginx, a captcha, caching of heavy pages. For a website or an [online store](https://accsly.io/en/vps/for-online-store), the host's L3/L4 protection covers only half the risks.

### What's included in the plan and what costs extra

- **Basic protection included in the price.** Automatic filtering of known flood types with limited capacity. If the attack is stronger, the host may send your IP to a blackhole: the server keeps running but is unreachable from the internet until the attack ends.
- **Advanced protection.** A separate protected IP or a plan with higher filtering capacity, sometimes with rules for specific protocols.
- **L7 protection.** Usually a standalone service: the domain is proxied through a filtering network, and the server's real IP is hidden.

### What to ask the host before paying

1. What the filtering capacity is and what happens when an attack exceeds it.
2. Whether protection runs constantly (always-on) or kicks in after an attack is detected. In the second case the server may be unreachable for the first few minutes.
3. How UDP is filtered. Game and voice protocols suffer from crude rules: real players drop off along with the flood.
4. Whether incoming attack traffic counts towards the plan's limit, and what happens with repeated attacks.
5. Whether you get notified of attacks and whether they're visible in the panel.

### Who needs protection most

Game projects are attacked most often: [Minecraft](https://accsly.io/en/vps/for-minecraft) and [Rust](https://accsly.io/en/vps/for-rust) servers, RP projects on [RAGE MP and FiveM](https://accsly.io/en/vps/for-gta5-rp). Ordering a flood is cheap, so fine-tuned rules for game protocols matter more here than CPU power. The second risk is stores and services during sales. For a small corporate VPN gateway or a test environment, the basic protection that most plans already have is enough.

The table above collects plans where the host itself claims DDoS protection; prices are converted into your currency, and the "Payment" column shows whether you can pay by card, PayPal or cryptocurrency. Hosts describe protection capacity and terms in different ways, so check them with support.

## FAQ

### Does a host's basic protection protect a website from DDoS?

Usually only from volumetric network-level attacks: UDP and SYN floods, amplification. Against HTTP bots that imitate visitors you need separate L7 protection: a proxy or CDN, request limits and caching.

### What is a blackhole during a DDoS attack?

It's switching off routing to your IP when an attack exceeds the filter's capacity. The server keeps running, but it can't be reached from the internet until the attack ends and the host lifts the block.

### Can I protect a VPS from DDoS myself?

Not from a volumetric attack: the channel gets clogged before traffic even reaches the server, and iptables rules won't help. Against small L7 attacks, request limits in nginx, fail2ban, caching and proxying through a CDN work.

### How does always-on protection differ from on-demand protection?

Always-on passes all traffic through the filter constantly, so an attack is mitigated immediately. On-demand protection kicks in after an attack is detected, so the server may be unreachable for the first few minutes.

### Do I need DDoS protection for a corporate VPN gateway?

A VPN gateway for a small team is rarely attacked: its address is known only to employees. The basic filtering that most plans have is enough.

### Does a CDN hide the server's real IP?

It does, unless the IP has leaked earlier: through old DNS records, subdomains or email headers. After connecting a CDN, allow incoming HTTP connections only from its addresses, and change the server's IP if necessary.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# VPS/VDS with IPv6

Plans with an IPv6 address in addition to IPv4.

> Source: https://accsly.io/en/vps/ipv6 · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 11,721, hosts: 696
- Price: from 0.40 $, a quarter below 16.31 $, median 40.00 $
- NVMe: 46 %, unlimited traffic: 35 %, hourly billing: 17 %
- RAM → price from: 1 GB — 0.49 $, 2 GB — 1.71 $, 4 GB — 2.17 $, 8 GB — 4.47 $, 16 GB — 7.85 $
- Countries: USA (3821), Germany (2766), Netherlands (2550), United Kingdom (2047), Singapore (1532), France (1325)
- Cheapest hosts: [CServers](https://accsly.io/en/vps/hosting/c-servers-co) — 0.90 $, [V.PS](https://accsly.io/en/vps/hosting/v) — 0.93 $, [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) — 1.00 $, [h2 NEXUS](https://accsly.io/en/vps/hosting/h2) — 1.00 $, [Inoventica](https://accsly.io/en/vps/hosting/invs) — 1.20 $

## Cheapest plans — 11,721 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-384 Low-Cost Special US | 1 × 3.0 GHz | 384 MB | 12 GB NVMe | US | Visa/MC, PayPal, Crypto | 0.40 $ (total when paying for 6 mo (2.39 $)) |
| [CServers](https://accsly.io/en/vps/hosting/c-servers-co) | NanoVPS-II 384 Europe | 1 × 3.1 GHz | 384 MB | 20 GB NVMe | FI | Visa/MC, PayPal, Crypto | 0.42 $ (total when paying for 6 mo (2.50 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ NL 256MB NAT | 1 | 256 MB | 5 GB SSD | NL | — | 0.42 $ (total when paying for year (4.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ Germany 256MB NAT | 1 | 256 MB | 5 GB SSD | DE | — | 0.44 $ (total when paying for year (5.31 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ Sweden 256MB NAT | 1 | 256 MB | 5 GB SSD | SE | — | 0.46 $ (total when paying for year (5.50 $)) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | STARDUST1-S | 1 × 2.1 GHz | 1 GB | — | FR, NL, PL | — | 0.49 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Pico | 1 | 128 MB | 5 GB SSD | US | Crypto | 0.50 $ |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM Canada NAT 256MB | 1 | 256 MB | 5 GB SSD | CA | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM India 256MB NAT | 1 | 256 MB | 5 GB SSD | IN | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM SG 400MB NAT | 1 | 400 MB | 5 GB NVMe | SG | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM Texas 300 MB NAT | 1 | 300 MB | 5 GB SSD | US | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM Turkey 256MB NAT | 1 | 256 MB | 5 GB SSD | TR | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | KVM UK 256 MB NAT | 1 | 256 MB | 5 GB SSD | GB | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ HK 256MB NAT | 1 | 256 MB | 5 GB SSD | HK | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ Japan 256MB NAT | 1 | 256 MB | 5 GB SSD | JP | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ Pakistan 256MB NAT | 1 | 256 MB | 5 GB SSD | PK | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ SA 256MB NAT | 1 | 256 MB | 5 GB SSD | ZA | — | 0.58 $ (total when paying for year (6.99 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ SG 400MB NAT (KVM) | 1 | 400 MB | 5 GB SSD | SG | — | 0.58 $ (total when paying for year (6.99 $)) |
| [ByteVirt](https://accsly.io/en/vps/hosting/bytevirt) | NAT-512-LXC | 1 | 512 MB | 6 GB SSD | SG, HK, TW, JP, DE, TR… | Crypto | 0.64 $ (total when paying for year (7.70 $)) |
| [KhanWebHost.com](https://accsly.io/en/vps/hosting/khanwebhost) | OVZ DE 512 MB NAT | 1 | 512 MB | 5 GB SSD | DE | — | 0.67 $ (total when paying for year (8.00 $)) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/vps/ipv6?format=json

## VPS with IPv6: what the second protocol gives you and why you still need IPv4

Free IPv4 addresses ran out long ago, and hosts buy them on the secondary market: hence the surcharge for every additional address and cheap plans with no IPv4 at all. IPv6 addresses are available in enormous quantity, so they are usually given out free and in blocks. The selection above contains plans where IPv6 is offered in addition to ordinary IPv4.

### What you get with IPv6

- **Many addresses per server.** A typical allocation is a /64 subnet, which is 18 quintillion addresses. Less often the host gives a single /128 address or, on the contrary, a large /56 or /48 block. A separate address can be assigned to every site, container or virtual machine inside the server at no extra cost.
- **Direct addressing without NAT.** Docker containers and guest machines get public addresses, and port forwarding is not needed.
- **Reachability for mobile networks.** Many mobile operators around the world have a sizeable share of IPv6 subscribers, and some connections to a site with an AAAA record go directly, bypassing their address translation gateways.
- **Future-proofing.** The share of IPv6 worldwide grows every year, and a service that already answers on both protocols will not need to be reconfigured in a hurry.

A separate topic is a proxy with many outgoing addresses from one subnet. It is covered on the [VPS for a proxy server](https://accsly.io/en/vps/for-proxy) page.

### Why IPv4 is still needed

Most home internet providers in Russia do not give subscribers IPv6, and a server reachable only over IPv6 simply will not open for such visitors. In other countries IPv6 coverage varies a lot, so check the figures for your audience. The same goes for outgoing connections: some popular services, code repositories and payment APIs still work over IPv4 only. A server without IPv4 cannot download an update from such an address unless the host provides a NAT64 and DNS64 gateway.

So for a website, a bot or an API take a plan with both protocols (dual stack): IPv4 ensures reachability for everyone, while IPv6 adds addresses and direct connectivity. IPv6-only plans make sense in three cases:

- internal network nodes that talk to each other and reach the outside world through a single server with IPv4;
- a site behind a CDN or reverse proxy that accepts visitors over IPv4 and connects to the server over IPv6;
- study environments and tests, where price matters more than reachability.

### Firewall: v6 rules are written separately

The most common mistake is closing ports in iptables and forgetting about ip6tables. These are two different rule tables, and a database closed over IPv4 can remain open to the whole internet over IPv6. Applications listening on the `::` address accept connections on both protocols by default.

- **nftables**: use a table of the `inet` family, so that one rule applies to both IPv4 and IPv6.
- **ufw**: check that `/etc/default/ufw` has `IPV6=yes`; then rules are created for both protocols.
- **Do not block ICMPv6 entirely.** Neighbour discovery (the replacement for ARP) and Packet Too Big messages work through it. Without them the server loses its gateway or "hangs" on large packets. Allow at least the neighbor solicitation and advertisement, router advertisement and packet too big types.
- **Docker** publishes ports bypassing ufw rules, and with IPv6 enabled it does so over v6 as well. Check open ports from outside, from another machine, on both addresses.

If the plan has no firewall in the host's panel, the rules in the system are the only protection. [KVM](https://accsly.io/en/vps/kvm) virtualization gives full control over the kernel and nftables; in OpenVZ and LXC containers working with IPv6 and rules is limited by the host machine's settings.

### How to check IPv6 after ordering

1. See how the address is assigned: statically in the panel, via SLAAC or via DHCPv6. On many plans you have to configure an address from the subnet in the system yourself, because it is not set up by default.
2. Check outgoing connectivity: `ping -6` to any large host and `curl -6` to a service that returns your address.
3. Add an AAAA record to DNS only after that: if v6 does not work on the server, some visitors will get an error instead of the site.
4. Request a PTR (reverse) record for the IPv6 address if the server sends mail. Large mail services check PTR and SPF separately for each protocol and calculate reputation for the whole /64 subnet. More about mail is on the [VPS for a mail server](https://accsly.io/en/vps/for-mail-server) page.

IPv6 and IPv4 routes at the same host can differ, so the ping from Russia, or from wherever your users are, to the server's two addresses may not be the same. If latency matters, measure both.

## FAQ

### How many IPv6 addresses come with a VPS?

Most often a /64 subnet, which is a practically unlimited number of addresses. Some hosts give a single /128 address, or a /56 or /48 block on request.

### Can I manage with an IPv6-only VPS?

Not for a public website: many users, for example in Russia, have no IPv6, and the site will not open for them. Such plans suit internal nodes, servers behind a CDN or reverse proxy, and tests.

### Why can't an IPv6-only server download packages from some sites?

Some services and repositories work over IPv4 only. You need a NAT64 gateway with DNS64, from the host or your own, or a plan with IPv4.

### Do iptables rules protect IPv6 addresses?

No, IPv6 needs separate ip6tables rules. It is simpler to switch to nftables with an inet table, where one rule works for both protocols.

### Can I block all ICMPv6?

No: neighbour and router discovery and packet-too-big messages depend on it. Without them the server loses connectivity or works with dropouts.

### Does a mail server need a PTR record for IPv6?

Yes. If the server sends mail over IPv6 without a reverse record, large mail services reject the messages or put them in spam. Ask the host for a PTR or disable sending over v6.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection)

# GPU servers

Rent a server with a graphics card for AI, rendering and compute: cloud and VPS plans with a GPU. Compare the card, cores, memory and price; cheapest first.

> Source: https://accsly.io/en/gpu · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 295, hosts: 34
- Price: from 11.17 $, a quarter below 464 $, median 1,088 $
- NVMe: 23 %, unlimited traffic: 14 %, hourly billing: 63 %
- RAM → price from: 1 GB — 11.17 $, 2 GB — 11.17 $, 4 GB — 11.17 $, 8 GB — 25.00 $, 16 GB — 25.00 $
- Countries: USA (120), India (97), Germany (72), United Kingdom (72), France (71), Netherlands (63)
- Cheapest hosts: [BalHost](https://accsly.io/en/vps/hosting/balhost-net) — 11.17 $, [Temok.com](https://accsly.io/en/vps/hosting/temok) — 25.00 $, [BitHost](https://accsly.io/en/vps/hosting/bithost) — 44.00 $, [Ownwebservers.com](https://accsly.io/en/vps/hosting/ownwebservers) — 45.00 $, [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) — 57.29 $

## Cheapest plans — 295 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [BalHost](https://accsly.io/en/vps/hosting/balhost-net) | GPU VPS-1 · GPU GPU | 4 | 6 GB | 50 GB NVMe | TR | Invoice | 11.17 $ |
| [Temok.com](https://accsly.io/en/vps/hosting/temok) | GPU VPS 8-Core, 1x NVIDIA GeForce GT 730 2GB · GPU NVIDIA GeForce GT 730, 2 GB | 8 | 16 GB | 120 GB SSD | US | Visa/MC, PayPal, Invoice | 25.00 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Vultr GPU NVIDIA A16 · 2 vCPU / 4 GB / 50 GB · GPU NVIDIA A16, 1 GB | 2 | 4 GB | 50 GB SSD |  | Crypto | 44.00 $ |
| [Ownwebservers.com](https://accsly.io/en/vps/hosting/ownwebservers) | Express GPU VPS · GPU GPU, 2 GB | 8 | 16 GB | 120 GB SSD | US | PayPal, Visa/MC | 45.00 $ (yearly: 45.00 $/mo) |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | GPU P1000 12vCPU/64GB/480GB · GPU NVIDIA Quadro P1000, 4 GB | 12 | 64 GB | 480 GB SSD | IN | Invoice | 57.29 $ |
| [VDSina](https://accsly.io/en/vps/hosting/vdsina-ru) | GPU 8 core / 8 Gb / 2 Gb VRAM · GPU NVIDIA L4, 2 GB | 8 × 3.6 GHz | 8 GB | 150 GB NVMe | RU, NL | Crypto, Invoice | 57.78 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Vultr GPU NVIDIA A40 · 1 vCPU / 3 GB / 40 GB · GPU NVIDIA A40, 1 GB | 1 | 3 GB | 40 GB SSD |  | Crypto | 60.00 $ |
| [Grav Hosting](https://accsly.io/en/vps/hosting/gravhosting) | A2000 GPU · GPU NVIDIA RTX A2000, 12 GB | 4 | 12 GB | 100 GB NVMe | NL | Crypto | 70.00 $ (when paying for year: 56.00 $/mo) |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | GPU A16 8vCPU/64GB/250GB · GPU NVIDIA A16, 16 GB | 8 | 64 GB | 250 GB NVMe | IN | Invoice | 80.64 $ |
| [Hosthink](https://accsly.io/en/vps/hosting/hosthink) | HT-C-012 Cloud GPU · GPU NVIDIA A16, 2 GB | 2 | 8 GB | 50 GB SSD | DE, GB, IN, JP, SG, US | Visa/MC, Invoice | 86.00 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Vultr GPU NVIDIA A16 · 2 vCPU / 8 GB / 50 GB · GPU NVIDIA A16, 2 GB | 2 | 8 GB | 50 GB SSD |  | Crypto | 86.00 $ |
| [Initech](https://accsly.io/en/vps/hosting/initech) | Vultr Cloud GPU — A16 1/8 GPU, 2GB GPU Memory, 2 vCPU, 8 GB RAM, 50 GB NVMe, Cloud GPU, 1.00 TB Transfer (Chicago) · GPU NVIDIA A16, 2 GB | 2 | 8 GB | 50 GB NVMe | DE, JP, SG, US | PayPal, Crypto | 90.00 $ (when paying for year: 71.99 $/mo) |
| [Hosthink](https://accsly.io/en/vps/hosting/hosthink) | HT-C-013 Cloud GPU · GPU NVIDIA A40, 2 GB | 1 | 5 GB | 90 GB SSD | DE, GB, IN, JP, US | Visa/MC, Invoice | 110 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Vultr GPU NVIDIA A40 · 1 vCPU / 5 GB / 90 GB · GPU NVIDIA A40, 2 GB | 1 | 5 GB | 90 GB SSD |  | Crypto | 110 $ |
| [FirstVDS](https://accsly.io/en/vps/hosting/firstvds) | vGPU 4 (L40S-4Q) · GPU NVIDIA L40S-4Q, 4 GB | 2 × 3.9 GHz | 4 GB | 30 GB NVMe | RU | Invoice, MIR, Visa/MC, SBP, YooMoney | 112 $ (yearly: 112 $/mo) |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | GPU V100 16vCPU/128GB/500GB · GPU NVIDIA V100, 16 GB | 16 | 128 GB | 500 GB SSD | IN | Invoice | 115 $ |
| [Temok.com](https://accsly.io/en/vps/hosting/temok) | GPU VPS 16-Core, 1x NVIDIA GeForce RTX 5060 8GB · GPU NVIDIA GeForce RTX 5060, 8 GB | 16 | 28 GB | 240 GB SSD | US | Visa/MC, PayPal, Invoice | 115 $ |
| [VDSina](https://accsly.io/en/vps/hosting/vdsina-ru) | GPU 16 core / 16 Gb / 4 Gb VRAM · GPU L4, 4 GB | 16 × 3.6 GHz | 16 GB | 500 GB NVMe | RU, NL | Crypto, Invoice | 127 $ |
| [Ownwebservers.com](https://accsly.io/en/vps/hosting/ownwebservers) | Basic GPU VPS · GPU NVIDIA RTX 5060, 8 GB | 16 | 28 GB | 240 GB SSD | US | PayPal, Visa/MC | 139 $ (yearly: 139 $/mo) |
| [ServaRica](https://accsly.io/en/vps/hosting/servarica) | P40 GPU Slice 1 - 1xP40 (24GB VRAM) · GPU NVIDIA Tesla P40, 24 GB | 10 | 40 GB | 500 GB NVMe | CA | PayPal, Visa/MC, Crypto, Invoice | 139 $ (when paying for year: 127 $/mo) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/gpu?format=json

## GPU server rental: which tasks need one and how to choose the card

A server with a graphics card makes sense when the work splits into thousands of parallel threads: the matrix operations of neural networks, rendering frames, encoding video. A CPU handles this kind of job many times slower, while buying your own data-centre card costs as much as a car and leaves it idle between jobs. The table above lists cloud and VPS plans with a GPU from hosts in Europe, the USA and Asia; the switch above it also shows [dedicated servers with a graphics card](https://accsly.io/en/gpu/dedicated).

### Why people rent a GPU and when a CPU is enough

- **Neural network inference.** A language model with 7–70 billion parameters, speech recognition, embeddings for document search. On a GPU an answer arrives in seconds, and one server can serve many users at once.
- **Fine-tuning.** Fine-tuning and LoRA adapters on your own data need noticeably more video memory than running the same model: besides the weights, gradients and optimizer state also live in memory.
- **Image generation.** Stable Diffusion, Flux and similar models produce an image in seconds on an RTX-class card and in minutes on a CPU.
- **Rendering.** Blender Cycles, Redshift, Octane: renting for a few hours before a deadline is cheaper than buying a workstation for one project.
- **Video transcoding.** The NVENC/NVDEC hardware codecs encode a stream into several qualities at once and take the load off the processor.
- **Scientific computing.** Molecular dynamics, simulations, image processing: anything written for CUDA or OpenCL.

You do not always need a graphics card. Small language models in compressed form run on an ordinary processor too: slower, but at the flat price of a regular VPS. For an internal bot or document processing without strict speed requirements, start with the [VPS for Ollama](https://accsly.io/en/vps/for-ollama) selection and move to a GPU once response time becomes the bottleneck.

### Cloud GPU or a dedicated server with a card

A cloud GPU or GPU VPS suits short and unpredictable jobs. Many plans are billed by the hour: start the server, run the training or the render, delete it, and pay only for the time used. In such plans the card is either passed through to the virtual machine whole (passthrough) or shared between customers via vGPU, where you get a slice of memory and compute units. Check which one you get: a slice is fine for inference of small models, but not for training.

A dedicated server with a graphics card belongs to one customer: no virtualization between you and the card, consistent performance and usually more disk and memory. It pays off under steady load, when a model answers users around the clock or the render queue never empties. If you need a powerful machine but not a GPU, see the general catalog of [dedicated servers](https://accsly.io/en/dedicated).

### How to read a GPU plan

- **Card model and generation.** Consumer RTX 3090 and 4090 cards give a lot of compute for the money and are good for image generation and inference. Professional A2000 and L4-class cards are power-efficient and fit inference and video. A100 and H100 are for training large models: more memory, a fast link between cards and support for formats such as BF16 and FP8.
- **Video memory.** This is the main limit: a model that does not fit into VRAM either will not start or runs several times slower. A rough rule: at full FP16 precision a billion parameters takes about 2 GB, with 4-bit quantization several times less, plus headroom for context. For training, multiply by several times again.
- **Number of cards.** Two cards are not one card with double the memory: the model has to be split between them, and the link speed between cards (NVLink or PCIe) affects the result.
- **CPU and RAM next to the card.** A weak CPU cannot feed data fast enough, and an expensive card sits idle. System memory should ideally be at least as large as video memory.
- **NVMe disk.** Datasets, checkpoints and model weights take tens to hundreds of gigabytes; a slow disk stretches every load.
- **Bandwidth and traffic.** Weights of a large model are downloaded in gigabytes. Check port speed and the traffic limit so the first download does not eat the monthly quota.
- **Ready images.** An image with the NVIDIA driver, CUDA, PyTorch or GPU-enabled Docker saves an hour of setup. Check the versions: an old driver will not run a recent framework.
- **Hourly or monthly price.** Compare by real usage: a few hours a day favours an hourly plan, round-the-clock work favours a monthly one.

### What to check before paying

1. **A test hour.** Rent the server for an hour, run your own job and look at the nvidia-smi output: card model, memory size, driver version and utilization under load.
2. **Card availability.** Popular models are often sold out, and a plan in the list does not guarantee a free card in the location you want. Ask how long delivery takes and whether a server can be reserved.
3. **Data location.** If the model processes personal data of people in the EU, GDPR applies to you as the controller, and a data centre inside the EU makes transfers easier to document. Otherwise location mostly affects how fast datasets download.
4. **Persistent storage.** Deleting an hourly server usually wipes its disk. Check whether there is a persistent volume or snapshots so you do not download the weights again on every start.
5. **Payment.** Hourly plans charge a prepaid balance, and the server is stopped when the balance hits zero. Most hosts accept cards, many take PayPal and business customers can usually pay by invoice; the table shows the methods for each plan.

If the card is needed for only part of a project, move the rest to a regular server from the [VPS catalog](https://accsly.io/en/vps): the web interface and the database live there, and the GPU server is switched on only for compute.

## FAQ

### Which graphics card do I need for neural networks?

For inference and image generation an RTX 3090 or 4090 with 24 GB of memory is usually enough. For training large models people take an A100 or H100, which have more video memory and a fast link between cards.

### How much VRAM does a language model need?

A rough guide is about 2 GB per billion parameters in FP16 and several times less with 4-bit quantization, plus headroom for context. Fine-tuning needs several times more memory than inference.

### How is a cloud GPU different from a dedicated GPU server?

A cloud GPU is a virtual machine with a passed-through card or a slice of one, often billed hourly. A dedicated server is entirely yours, with no virtualization, and pays off under steady load.

### What is vGPU?

It is a technology that splits one physical card between several virtual machines. Each gets a share of video memory and compute units, so for training a plan with a whole card is the better choice.

### Can I rent a GPU server for a few hours?

Yes, many cloud plans are billed by the hour. Keep in mind that deleting the server usually wipes its disk, so keep important data on a persistent volume.

### Is a GPU server good for Stable Diffusion?

Yes, it is one of the most common tasks. RTX-class cards with 12–24 GB of memory generate images in seconds, and more memory is needed for high resolutions and training your own LoRA.

### Do I have to install drivers and CUDA myself?

Not always: many hosts offer images with the NVIDIA driver, CUDA and PyTorch. Check the versions in the image so they match your framework.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# Dedicated GPU servers

A dedicated server with a graphics card: the whole physical server and the card are yours alone. Compare the card, processor, memory and price; cheapest first.

> Source: https://accsly.io/en/gpu/dedicated · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 251, hosts: 35
- Price: from 52.99 $, a quarter below 373 $, median 598 $
- NVMe: 56 %, unlimited traffic: 44 %, hourly billing: 40 %
- RAM → price from: 1 GB — 52.99 $, 2 GB — 52.99 $, 4 GB — 52.99 $, 8 GB — 52.99 $, 16 GB — 52.99 $
- Countries: Russia (74), USA (51), Finland (35), Netherlands (32), Germany (17), France (9)
- Cheapest hosts: [Temok.com](https://accsly.io/en/vps/hosting/temok) — 52.99 $, [HostingSource](https://accsly.io/en/vps/hosting/hostingsource) — 74.00 $, [Ownwebservers.com](https://accsly.io/en/vps/hosting/ownwebservers) — 109 $, [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) — 146 $, [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) — 149 $

## Cheapest plans — 251 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Temok.com](https://accsly.io/en/vps/hosting/temok) | GPU Dedicated Server, Intel Xeon E5-2690, 1× NVIDIA Quadro P1000 4GB · GPU NVIDIA Quadro P1000, 4 GB | 8 | 32 GB | 1080 GB SSD | US | Visa/MC, PayPal, Invoice | 52.99 $ |
| [HostingSource](https://accsly.io/en/vps/hosting/hostingsource) | M1-Basic - 8 Core CPU + 8 Core GPU - 3.2GHz · GPU GPU | 8 | 8 GB | 256 GB SSD | US | Visa/MC, PayPal | 74.00 $ (when paying for 2 years: 59.21 $/mo) |
| [Ownwebservers.com](https://accsly.io/en/vps/hosting/ownwebservers) | Express – P1000 · GPU NVIDIA RTX A4000, 16 GB | 24 | 28 GB | 320 GB SSD | US | PayPal, Visa/MC | 109 $ (yearly: 109 $/mo) |
| [HostingSource](https://accsly.io/en/vps/hosting/hostingsource) | M2-Professional - 8 Core CPU + 10 Core GPU - 3.5GHz · GPU GPU | 8 | 16 GB | 256 GB SSD | US | Visa/MC, PayPal | 109 $ (when paying for 2 years: 87.21 $/mo) |
| [HostingSource](https://accsly.io/en/vps/hosting/hostingsource) | M4-Basic - 10 Core CPU + 10 Core GPU - 4.5GHz · GPU GPU | 10 | 16 GB | 256 GB SSD | US | Visa/MC, PayPal | 129 $ (when paying for 2 years: 103 $/mo) |
| [HostingSource](https://accsly.io/en/vps/hosting/hostingsource) | M2-Advanced - 8 Core CPU + 16 Core GPU - 3.5GHz · GPU GPU | 8 | 24 GB | 512 GB SSD | US | Visa/MC, PayPal | 139 $ (when paying for 2 years: 111 $/mo) |
| [Temok.com](https://accsly.io/en/vps/hosting/temok) | GPU Dedicated Server, Intel Xeon E5-2690, 1× NVIDIA Tesla K80 24GB · GPU NVIDIA Tesla K80, 24 GB | 8 | 64 GB | 1080 GB SSD | US | Visa/MC, PayPal, Invoice | 145 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Rise RISE-GPU-1 · GPU AMD Radeon RX 6700 XT, 12 GB | 8 × 3.8 GHz | 64 GB | 1920 GB NVMe | FR | PayPal, Visa/MC | 146 $ (when paying for 2 years: 138 $/mo) |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Vectora · GPU NVIDIA GTX 1660, 6 GB | 16 | 64 GB | 960 GB SSD | US | Visa/MC, Invoice | 149 $ |
| [PebbleHost](https://accsly.io/en/vps/hosting/pebblehost) | Power-02 Gen2 + NVIDIA RTX A1000 · GPU NVIDIA RTX A1000, 8 GB | 12 | 32 GB | 512 GB NVMe | GB | PayPal, Visa/MC | 150 $ (when paying for year: 130 $/mo) |
| [Veeble](https://accsly.io/en/vps/hosting/veeble) | GPU: Ryzen 9 / 64 GB / 2×480 GB NVMe / NVIDIA NVS 315 (NL) · GPU NVIDIA NVS 315 | 12 | 64 GB | 960 GB NVMe | NL | Visa/MC, PayPal, Crypto | 160 $ (when paying for 2 years: 145 $/mo) |
| [Timeweb Cloud](https://accsly.io/en/vps/hosting/timeweb-cloud) | Intel Core i3-14100 (4 ядра, 3.5-4.7 ГГц, 8 потоков) / 32 DDR5 / 2 x 1 Тб NVMe + GPU RTX A2000 6GB · GPU NVIDIA RTX A2000, 6 GB | 4 × 3.5 GHz | 32 GB | 2 TB NVMe | RU | MIR, Visa/MC, SBP, YooMoney, Invoice | 169 $ |
| [Timeweb](https://accsly.io/en/vps/hosting/timeweb) | i3-14100 / 32 / 2N + RTX A2000 · GPU NVIDIA RTX A2000, 6 GB | 4 × 3.5 GHz | 32 GB | 2 TB NVMe | RU | MIR, Visa/MC, YooMoney, SBP, Invoice | 169 $ |
| [HostingSource](https://accsly.io/en/vps/hosting/hostingsource) | M2-Expert - 8 Core CPU + 16 Core GPU - 3.5GHz · GPU GPU | 8 | 32 GB | 512 GB SSD | US | Visa/MC, PayPal | 179 $ (when paying for 2 years: 143 $/mo) |
| [Aluy](https://accsly.io/en/vps/hosting/aluy) | Hetzner auction #3103978 — Intel Core i7-7700, 64 GB, 2× 512 GB SATA SSD · GPU NVIDIA GTX 1080, 8 GB | 4 | 64 GB | 1024 GB SSD | DE | PayPal, Visa/MC, Crypto | 185 $ |
| [HostingSource](https://accsly.io/en/vps/hosting/hostingsource) | M4-Professional - 10 Core CPU + 10 Core GPU - 4.5GHz · GPU GPU | 10 | 16 GB | 512 GB SSD | US | Visa/MC, PayPal | 189 $ (when paying for 2 years: 151 $/mo) |
| [PebbleHost](https://accsly.io/en/vps/hosting/pebblehost) | Power-03 Gen2 + NVIDIA RTX A1000 · GPU NVIDIA RTX A1000, 8 GB | 16 | 64 GB | 512 GB NVMe | GB | PayPal, Visa/MC | 190 $ (when paying for year: 162 $/mo) |
| [PebbleHost](https://accsly.io/en/vps/hosting/pebblehost) | Power-03 Gen3 + NVIDIA RTX A1000 · GPU NVIDIA RTX A1000, 8 GB | 12 | 64 GB | 512 GB NVMe | GB | PayPal, Visa/MC | 190 $ (when paying for year: 162 $/mo) |
| [Grav Hosting](https://accsly.io/en/vps/hosting/gravhosting) | AI Ready AMD Ryzen 9 9950X NVIDIA RTX A2000 12GB GPU · GPU NVIDIA RTX A2000, 12 GB | 16 | 128 GB | 4 TB SSD | US | Crypto | 200 $ (yearly: 200 $/mo) |
| [Dimofinf](https://accsly.io/en/vps/hosting/dimofinf) | GPU 5 · GPU NVIDIA Tesla T4, 16 GB | 20 | 32 GB | 960 GB SSD | SA | Visa/MC, Invoice, PayPal | 200 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/gpu/dedicated?format=json

## Dedicated GPU server: when your own machine beats the cloud and how to read the configuration

A dedicated server with a graphics card is a physical machine with one or more cards installed, and all of that hardware works for you alone. There is no hypervisor between your model and the GPU, no neighbours share the PCIe bus, the disks or the uplink with you, and the BIOS, driver and operating system settings stay in your hands. The table above lists such configurations, from a single workstation card to builds with several accelerators. If your job is short and you want hourly billing, compare the cloud plans in the main [GPU servers](https://accsly.io/en/gpu) section.

### When a dedicated GPU server pays off over a cloud GPU

- **The card is busy almost around the clock.** An hourly cloud GPU is great while you switch it on for an evening. When a service answers users without a break, a monthly dedicated GPU server rental usually costs less than the same load billed by the hour.
- **Training runs for weeks.** A long training or fine-tuning run does not like interruptions. On your own machine it will not be stopped because the provider ran short of capacity, and checkpoints sit on a local disk instead of paid external storage.
- **Data must not leave the machine.** Medical scans, customer conversations, internal company documents: on a dedicated server the disks are not shared with other customers, and it is easier to show an auditor where the data physically lives and who can reach it.
- **Licences are tied to the hardware.** Some professional software for rendering, CAD and simulation is licensed per machine or per physical card. A permanent server with the same GPUs saves you from reactivating after every virtual machine restart.
- **You need several cards with a known topology.** For distributed training it matters exactly how the cards are linked. In the cloud the interconnect is often hidden, while for a dedicated server you can ask in advance and verify it after delivery.

If you do not need GPU computing and simply want a powerful physical machine for databases or virtualization, the general catalog of [dedicated servers](https://accsly.io/en/dedicated) is a better place to look: more configurations and lower prices.

### Card, video memory and the link between cards

The first thing to read in a plan line is the card model and its memory size. The RTX A4000 and A5000 workstation cards are built for long rack-mounted workloads and run quieter, the RTX 3090 and 4090 give a lot of compute for the money, and the A100 and H100 are needed when a model does not fit into 24 GB or training uses large batches. Older Tesla K80 and P40 cards show up in budget configurations: they have plenty of memory, but they do not support recent CUDA versions or modern number formats, so they suit experiments rather than production. Also watch out for low-end cards such as NVS or entry-level Quadro: in servers they are often installed only for display output and are almost useless for neural networks.

A "2×" or "8×" in the name is the number of cards, not the memory of a single card. Two 24 GB cards are not the same as one 48 GB card: the model has to be split, and the speed of exchange between the cards starts to decide the outcome. Cards joined by an NVLink bridge exchange data several times faster than over the PCIe bus, and in HGX-class multi-GPU platforms all accelerators are connected to each other directly. Ask the host how many PCIe lanes each card gets and whether they all hang off one processor: if half of the cards are attached through the second socket, traffic between them is slower.

### Processor, disks, power and network

- **CPU and RAM.** The processor prepares the data, decodes images and tokenizes text. Plan several physical cores per card and at least as much RAM as the total video memory, otherwise the accelerators wait for data.
- **NVMe for datasets.** A large dataset is read from disk on every epoch. Local NVMe noticeably shortens training compared with SATA disks and network volumes.
- **Power and cooling.** One powerful card draws hundreds of watts, and an eight-accelerator server draws as much as a small rack. Not every data centre can supply that much power to a single unit, so multi-card servers come in small batches and often show up in the table as "out of stock".
- **Port and traffic.** Model weights and datasets weigh hundreds of gigabytes. A gigabit port without a tight traffic cap spares you the wait on the first download and on regular checkpoint uploads.
- **Setup fee and minimum term.** GPU servers more often than regular ones come with a setup fee and a minimum rental term from one month to a year. Count the cost over the whole period, not just the monthly line.
- **Delivery time.** Servers in stock are handed over within hours; configurations with scarce cards are built to order, and the wait stretches to days or weeks.

### What to check before you pay

1. **Image with the driver.** Ask whether the host installs a system with the NVIDIA driver and CUDA or hands over a clean OS. Match the driver version against what your framework and containers require.
2. **Remote console.** KVM or IPMI lets you reinstall the system and fix the boot after a failed driver update without waiting for support. On a GPU server this matters even more: a driver failure sometimes leaves the machine without network.
3. **Replacement of a failed card.** Graphics cards under constant load fail more often than disks. Find out how quickly a card is replaced, whether spares are kept on site and whether the rental is extended for the downtime.
4. **Data location.** Check the data centre country and storage terms if the server will process personal data or trade secrets. For customers in the EU this decides whether GDPR rules on transfers outside the Union apply; location also affects how fast datasets download.
5. **Test after delivery.** In the first hours run a real job at full load and watch card temperatures and clocks: overheating and throttling show up right away, and a complaint is easier to make at the start of the term.

If you are still choosing between server classes, start with the [guide to choosing a VPS](https://accsly.io/en/vps/guide/how-to-choose-vps). And for a small local model without strict speed requirements, a regular server without a graphics card from the [VPS for Ollama](https://accsly.io/en/vps/for-ollama) selection is sometimes enough.

## FAQ

### How is a dedicated GPU server different from a cloud GPU?

A cloud GPU is a virtual machine with a passed-through card, often billed by the hour. A dedicated server with a graphics card is a whole physical machine for one customer, with no hypervisor, monthly rental and full control over the hardware.

### Which GPU server should I choose for neural networks?

For inference and image generation one card with 24 GB of memory, such as an RTX 4090 or A5000, is usually enough. For training large models people take an A100 or H100, or several cards linked via NVLink.

### What is NVLink and do I need it?

NVLink is a direct high-speed connection between graphics cards that is faster than the PCIe bus. It matters for training when a model is split across cards; for independent inference on each card you can do without it.

### Why are multi-GPU servers so often out of stock?

They draw a lot of power and need strong cooling, so data centres install only a limited number. Powerful cards also sell out quickly, and new configurations are often built to order.

### Are old Tesla K80 and P40 cards any good for AI?

For experiments and small models, yes: they have enough memory. But recent CUDA and framework versions no longer support them, and they are much slower than current cards.

### Who replaces the graphics card if it fails?

With a rental the host replaces it within the time stated in the terms. Check that time before paying and ask whether downtime is compensated.

### Can I rent a dedicated GPU server for just one month?

Often yes, but some offers have a minimum term or a one-off setup fee. On a short rental that fee can noticeably raise the total price.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# GPU servers with NVIDIA T4

Servers with NVIDIA T4 (16 GB, 70 W): an affordable card for small-model inference, speech recognition and video transcoding. Compare CPU, RAM and price; cheapest first.

> Source: https://accsly.io/en/gpu/t4 · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 48, hosts: 11
- Price: from 200 $, a quarter below 442 $, median 686 $
- NVMe: 19 %, unlimited traffic: 10 %, hourly billing: 46 %
- RAM → price from: 1 GB — 200 $, 2 GB — 200 $, 4 GB — 200 $, 8 GB — 200 $, 16 GB — 200 $
- Countries: Finland (17), Russia (10), USA (8), Netherlands (6), Canada (5), Australia (4)
- Cheapest hosts: [Dimofinf](https://accsly.io/en/vps/hosting/dimofinf) — 200 $, [Timeweb Cloud](https://accsly.io/en/vps/hosting/timeweb-cloud) — 204 $, [Timeweb](https://accsly.io/en/vps/hosting/timeweb) — 204 $, [Beget](https://accsly.io/en/vps/hosting/beget) — 331 $, [4vps](https://accsly.io/en/vps/hosting/4vps) — 345 $

## Cheapest plans — 48 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Dimofinf](https://accsly.io/en/vps/hosting/dimofinf) | GPU 5 · GPU NVIDIA Tesla T4, 16 GB | 20 | 32 GB | 960 GB SSD | SA | Visa/MC, Invoice, PayPal | 200 $ |
| [Timeweb Cloud](https://accsly.io/en/vps/hosting/timeweb-cloud) | Intel Core i3-14100 (4 ядра, 3.5-4.7 ГГц, 8 потоков) / 32 DDR5 / 2 x 1 Тб NVMe + GPU Tesla T4 16GB · GPU NVIDIA Tesla T4, 16 GB | 4 × 3.5 GHz | 32 GB | 2 TB NVMe | RU | MIR, Visa/MC, SBP, YooMoney, Invoice | 204 $ |
| [Timeweb](https://accsly.io/en/vps/hosting/timeweb) | Intel Core i3-14100 (4 ядра, 3.5-4.7 ГГц, 8 потоков) / 32 DDR5 / 2 x 1 Тб NVMe + GPU Tesla T4 16GB · GPU NVIDIA Tesla T4, 16 GB | 4 × 3.5 GHz | 32 GB | 2 TB NVMe | RU | MIR, Visa/MC, YooMoney, SBP, Invoice | 204 $ |
| [Dimofinf](https://accsly.io/en/vps/hosting/dimofinf) | GPU 6 · GPU NVIDIA Tesla T4, 16 GB | 48 | 128 GB | 1920 GB SSD | SA | Visa/MC, Invoice, PayPal | 250 $ |
| [Beget](https://accsly.io/en/vps/hosting/beget) | Tesla №1 · GPU NVIDIA Tesla T4, 16 GB | 6 × 3.4 GHz | 32 GB | 960 GB SSD | RU | MIR, SBP, Invoice, YooMoney | 331 $ |
| [4vps](https://accsly.io/en/vps/hosting/4vps) | E5-2450L / 64 GB / 2x250 GB SSD / 1 Gbit/s / NVIDIA Tesla T4 16GB GDDR6 · GPU NVIDIA Tesla T4, 16 GB | 8 × 2.3 GHz | 64 GB | 500 GB SSD | FI | MIR, Visa/MC, SBP, WebMoney, Crypto | 345 $ |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC4as T4 v3 · GPU NVIDIA T4, 16 GB | 4 | 28 GB | — | AU, BR, CA, DE, ES, FR… | Visa/MC | 384 $ (when paying for 3 years: 144 $/mo) |
| [PrivateAlps](https://accsly.io/en/vps/hosting/privatealps) | GPU Server V1 · GPU NVIDIA Tesla P4 / T4 | 28 | 64 GB | 1 TB SSD | CH | Crypto, Visa/MC | 395 $ (yearly: 395 $/mo) |
| [Dimofinf](https://accsly.io/en/vps/hosting/dimofinf) | GPU 1 · GPU NVIDIA Tesla T4, 16 GB | 32 | 128 GB | 960 GB SSD | SA | Visa/MC, Invoice, PayPal | 400 $ |
| [Timeweb Cloud](https://accsly.io/en/vps/hosting/timeweb-cloud) | Intel Xeon E-2236 (6 ядер, 3.4-4.8 ГГц, 12 потоков) / 16 DDR4 / 2 x 240 Гб SSD + GPU Tesla T4 16GB · GPU NVIDIA Tesla T4, 16 GB | 6 × 3.4 GHz | 16 GB | 480 GB SSD | RU | MIR, Visa/MC, SBP, YooMoney, Invoice | 406 $ |
| [Timeweb Cloud](https://accsly.io/en/vps/hosting/timeweb-cloud) | Intel Xeon E-2456 (6 ядер, 3.3-5.1 ГГц, 12 потоков) / 32 DDR5 / 2 x 960 Гб SSD + GPU Tesla T4 16GB · GPU NVIDIA Tesla T4, 16 GB | 6 × 3.3 GHz | 32 GB | 1920 GB SSD | RU | MIR, Visa/MC, SBP, YooMoney, Invoice | 436 $ |
| [4vps](https://accsly.io/en/vps/hosting/4vps) | 2xE5-2450L / 64 GB / 2x250 GB SSD / 1 Gbit/s / 2xNVIDIA Tesla T4 16GB GDDR6 · GPU NVIDIA Tesla T4 ×2, 16 GB | 16 × 2.3 GHz | 64 GB | 500 GB SSD | FI | MIR, Visa/MC, SBP, WebMoney, Crypto | 442 $ |
| [4vps](https://accsly.io/en/vps/hosting/4vps) | E5-2450L / 64 GB / 2x250 GB SSD / 1 Gbit/s / 2xNVIDIA Tesla T4 16GB GDDR6 · GPU NVIDIA Tesla T4 ×2, 16 GB | 8 × 2.3 GHz | 64 GB | 500 GB SSD | FI | MIR, Visa/MC, SBP, WebMoney, Crypto | 454 $ |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC4as T4 v3 (West Europe) · GPU NVIDIA T4, 16 GB | 4 | 28 GB | — | NL | Visa/MC | 480 $ (when paying for 3 years: 182 $/mo) |
| [4vps](https://accsly.io/en/vps/hosting/4vps) | 2xE5-2680v4 / 128 GB / 2x500 GB SSD / 1 Gbit/s / 2xNVIDIA Tesla T4 16GB GDDR6 · GPU NVIDIA Tesla T4 ×2, 16 GB | 28 × 3.3 GHz | 128 GB | 1 TB SSD | FI | MIR, Visa/MC, SBP, WebMoney, Crypto | 503 $ |
| [Timeweb Cloud](https://accsly.io/en/vps/hosting/timeweb-cloud) | AMD EPYC 7402P (24 ядра, 2.8-3.35 ГГц, 48 потоков) / 64 DDR4 / 960 Гб SSD + GPU Tesla T4 16GB · GPU NVIDIA Tesla T4, 16 GB | 24 × 2.8 GHz | 64 GB | 960 GB SSD | RU | MIR, Visa/MC, SBP, YooMoney, Invoice | 515 $ |
| [Justhost](https://accsly.io/en/vps/hosting/justhost) | GPU Altair T4 · GPU NVIDIA T4, 16 GB | 16 | 32 GB | 200 GB NVMe | US | MIR, Visa/MC, PayPal, YooMoney, Invoice | 522 $ (when paying for 3 years: 313 $/mo) |
| [4vps](https://accsly.io/en/vps/hosting/4vps) | 2xE5-2450L / 64 GB / 2x250 GB SSD / 1 Gbit/s / NVIDIA Tesla T4 16GB GDDR6 · GPU NVIDIA Tesla T4, 16 GB | 16 × 2.3 GHz | 64 GB | 500 GB SSD | FI | MIR, Visa/MC, SBP, WebMoney, Crypto | 539 $ |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC8as T4 v3 · GPU NVIDIA T4, 16 GB | 8 | 56 GB | — | AU, BR, CA, DE, ES, FR… | Visa/MC | 549 $ (when paying for 3 years: 206 $/mo) |
| [SeiMaxim](https://accsly.io/en/vps/hosting/seimaxim) | 1x Tesla T4 ATX / Xeon E-2288G 3.7GHz (8 cores) / Netherlands · GPU NVIDIA Tesla T4, 16 GB | 8 × 3.7 GHz | 32 GB | 960 GB SSD | NL | Crypto, PayPal, Visa/MC, WebMoney, Invoice | 550 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/gpu/t4?format=json

## NVIDIA T4: the budget card for inference and video, what it handles and where it stops

The NVIDIA T4 came out in 2018 on the Turing architecture and is still the most affordable data-centre card for AI work. It has 16 GB of GDDR6 memory, draws only 70 W, fits a low-profile single slot and is passively cooled: the server fans push air through it, so data centres can put it into almost any machine. That is why renting a server with a T4 usually costs much less than any plan with a newer card. The table above lists cloud VPS plans with a T4 and dedicated servers, from a single card up to builds with four.

### What fits into 16 GB

A rule of thumb: in FP16 a model takes about 2 GB per billion parameters, in 8-bit about 1 GB, in 4-bit 0.5–0.6 GB. On top of that you need headroom for the KV cache, which grows with context length and the number of concurrent requests.

- **Language models.** A 7–8B model runs in 8-bit or 4-bit quantisation, a 3–4B model in full FP16. That is enough for a support chatbot, ticket classification or answers over a document base. Anything above 13B will not fit on one card with a usable context.
- **Speech recognition.** Whisper and similar models are one of the best jobs for a T4: transcribing calls and podcasts runs many times faster than real time.
- **Embeddings, OCR and computer vision.** Vectorising documents for search, reading text from scans, object detection and image classification fit into memory with plenty to spare.
- **Image generation.** Stable Diffusion runs, but each image takes noticeably longer than on RTX-class cards; for large models such as Flux, 16 GB is too little without heavy compression.
- **Training.** Small models and LoRA or QLoRA fine-tuning up to 7B are possible, but slow. The T4 is not a card for serious training.

### What the T4 cannot do and what to check in the image

The T4 tensor cores handle FP16, INT8 and INT4, but not BF16 or FP8. Many recent models are published in BF16, and on a T4 you have to run them in FP16, which sometimes takes extra configuration. The card has compute capability 7.5, while some newer inference engines and attention kernels, FlashAttention 2 for example, require 8.0 or higher, meaning Ampere or later. Before renting, check that your stack supports Turing.

Drivers are not a problem: current CUDA 12.x still supports Turing and needs a driver from the 525 branch or newer. In the image, check the driver version, the CUDA version and whether the NVIDIA Container Toolkit is installed if you work with Docker.

A separate advantage is the hardware NVENC and NVDEC codecs. A GPU server with a T4 transcodes several video streams to H.264 and HEVC at once while barely loading the CPU. Turing has no AV1 encoding.

### One card, a share of a card or several

Some cloud plans give you not a whole T4 but a share of it through vGPU: the virtual machine gets part of the video memory, for example 4 or 8 GB, and part of the compute. That is enough for embeddings or a small speech model, but for a 7B language model take a full card. The T4 has no MIG, the technology that splits A100 and H100 cards into isolated parts.

Plans marked "×2" and "×4" mean two or four separate 16 GB cards. The T4 has no NVLink, the cards talk over PCIe 3.0, so splitting one model across them is slow. A multi-card server pays off when each card runs its own copy of the model or its own job queue: that way it is easier to serve many parallel requests.

### Prices, billing and what to pick instead

In the catalogue, T4 plans cost roughly $210 to $4,000 a month; the low end is a cloud VPS with one card, the high end is dedicated servers with four cards, lots of RAM and a many-core CPU. Most plans are billed by the hour. If you need the card a few hours a day for batch transcription or overnight processing, hourly billing is cheaper; for a service running around the clock, compare the monthly plan or a dedicated server. The section on [hourly billing](https://accsly.io/en/vps/hourly-billing) explains how to calculate it. Most plans accept card payment; for EU customers, the data centre location also decides GDPR questions and latency to your users.

If you hit the limits of the T4, look at the neighbouring cards:

- [NVIDIA L4](https://accsly.io/en/gpu/l4) is the direct successor on the Ada architecture: 24 GB, 72 W, BF16 and FP8 support, AV1 encoding and noticeably higher speed. It costs more but removes almost all T4 limitations.
- [NVIDIA A2](https://accsly.io/en/gpu/a2) also has 16 GB and draws even less power, with the Ampere architecture and BF16, but it has less compute than the T4. It suits light workloads where compatibility with newer engines matters.

If you are not sure yet which card you need, start with the overview of [GPU servers](https://accsly.io/en/gpu). A T4 for rent is a sensible first step: it is a cheap way to find out how many resources your model really needs before paying for higher-end cards.

## FAQ

### Is a T4 enough for a 7B language model?

Yes, in 8-bit or 4-bit quantisation a 7–8B model fits into 16 GB together with the context cache. In full FP16 precision a single T4 comfortably runs models up to 3–4B parameters.

### Why do some models not run on a T4?

The T4 has compute capability 7.5 and no BF16 or FP8 support. Some recent inference engines and kernels, FlashAttention 2 for example, require 8.0 or higher, so check what your stack needs in advance.

### How is the T4 different from the L4?

The L4 is the T4 successor on the Ada architecture: 24 GB of memory instead of 16, BF16 and FP8 support, AV1 encoding and noticeably higher speed at almost the same power draw. The T4 is cheaper and fits when you do not need those features.

### Is the T4 good for video transcoding?

Yes, the hardware NVENC and NVDEC transcode several H.264 and HEVC streams at once and take the load off the CPU. The T4 has no AV1 encoding.

### Can I train models on a T4?

Small models and LoRA or QLoRA fine-tuning, yes, but slowly and only in FP16. For training large models people use cards with more memory and BF16 support.

### Does a server with two or four T4 cards make sense?

Yes, if each card runs its own copy of the model or its own job queue. The T4 has no NVLink, so splitting one large model across cards over PCIe is slow.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# GPU servers with NVIDIA RTX PRO 6000

Servers with NVIDIA RTX PRO 6000 (Blackwell, 96 GB): cloud, VPS and dedicated. Compare GPU count, VRAM, CPU and price; cheapest first.

> Source: https://accsly.io/en/gpu/rtx-pro-6000 · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 37, hosts: 11
- Price: from 249 $, a quarter below 1,118 $, median 1,505 $
- NVMe: 30 %, unlimited traffic: 24 %, hourly billing: 81 %
- RAM → price from: 1 GB — 249 $, 2 GB — 249 $, 4 GB — 249 $, 8 GB — 249 $, 16 GB — 249 $
- Countries: USA (16), Germany (12), India (12), Netherlands (10), Spain (9), France (9)
- Cheapest hosts: [MojoHost](https://accsly.io/en/vps/hosting/mojohost) — 249 $, [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) — 825 $, [Alpenhost e.U.](https://accsly.io/en/vps/hosting/alpenhost) — 895 $, [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) — 1,097 $, [Contabo.com](https://accsly.io/en/vps/hosting/contabo) — 1,118 $

## Cheapest plans — 37 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [MojoHost](https://accsly.io/en/vps/hosting/mojohost) | MOJOGPU RTX PRO 6000 Max Q 24GB · GPU NVIDIA RTX PRO 6000 Max Q, 24 GB | 14 | 60 GB | — | US | Visa/MC | 249 $ |
| [MojoHost](https://accsly.io/en/vps/hosting/mojohost) | MOJOGPU RTX PRO 6000 Max Q 48GB · GPU NVIDIA RTX PRO 6000 Max Q, 48 GB | 20 | 120 GB | — | US | Visa/MC | 499 $ |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC24ldsxlRTX6K v6 · GPU NVIDIA RTX PRO 6000 Blackwell Server Edition | 24 | 72 GB | — | AE, AU, CH, DE, ES, FR… | Visa/MC | 825 $ (when paying for 3 years: 363 $/mo) |
| [Alpenhost e.U.](https://accsly.io/en/vps/hosting/alpenhost) | GPU-vServer Platin · GPU NVIDIA RTX Pro 6000 Blackwell, 96 GB | 16 | 64 GB | — | AT | Invoice, PayPal | 895 $ |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC36ldsxlRTX6K v6 · GPU NVIDIA RTX PRO 6000 Blackwell Server Edition | 36 | 72 GB | — | AE, AU, CH, DE, ES, FR… | Visa/MC | 907 $ (when paying for 3 years: 399 $/mo) |
| [MojoHost](https://accsly.io/en/vps/hosting/mojohost) | MOJOGPU RTX PRO 6000 Max Q 96GB · GPU NVIDIA RTX PRO 6000 Max Q, 96 GB | 20 | 240 GB | — | US, NL | Visa/MC | 999 $ |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC36dsxlRTX6K v6 · GPU NVIDIA RTX PRO 6000 Blackwell Server Edition | 36 | 132 GB | — | AE, AU, CH, DE, ES, FR… | Visa/MC | 1,053 $ (when paying for 3 years: 463 $/mo) |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Surge · GPU NVIDIA RTX PRO 6000, 96 GB | 24 | 256 GB | 960 GB NVMe | DE | Visa/MC, Invoice | 1,097 $ |
| [Hetzner](https://accsly.io/en/vps/hosting/hetzner) | GEX63 · GPU NVIDIA RTX PRO 6000 Blackwell Max-Q, 96 GB | 20 × 2.4 GHz | 128 GB | 3840 GB NVMe | FI | Visa/MC, PayPal, Invoice | 1,118 $ |
| [Contabo.com](https://accsly.io/en/vps/hosting/contabo) | GPU VPS · GPU NVIDIA RTX PRO 6000 Blackwell Server Edition, 96 GB | 18 | 96 GB | 900 GB NVMe | DE | Visa/MC, PayPal, Invoice | 1,118 $ |
| [Contabo.com](https://accsly.io/en/vps/hosting/contabo) | GPU VPS — US Central · GPU NVIDIA RTX PRO 6000 Blackwell Server Edition, 96 GB | 18 | 96 GB | 900 GB NVMe | US | Visa/MC, PayPal, Invoice | 1,144 $ |
| [Zeno Cloud](https://accsly.io/en/vps/hosting/zenocloud) | NVIDIA RTX PRO 6000 96GB, 16 vCPU / 128 GB · GPU NVIDIA RTX PRO 6000, 96 GB | 16 | 128 GB | — | IN | Visa/MC | 1,172 $ |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC24ldsxlRTX6K v6 (West Europe) · GPU NVIDIA RTX PRO 6000 Blackwell Server Edition | 24 | 72 GB | — | NL | Visa/MC | 1,180 $ (when paying for 3 years: 519 $/mo) |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC36ldsxlRTX6K v6 (West Europe) · GPU NVIDIA RTX PRO 6000 Blackwell Server Edition | 36 | 72 GB | — | NL | Visa/MC | 1,297 $ (when paying for 3 years: 571 $/mo) |
| [Zeno Cloud](https://accsly.io/en/vps/hosting/zenocloud) | NVIDIA RTX PRO 6000 96GB, 24 vCPU / 192 GB · GPU NVIDIA RTX PRO 6000, 96 GB | 24 | 192 GB | — | IN | Visa/MC | 1,321 $ |
| [Zeno Cloud](https://accsly.io/en/vps/hosting/zenocloud) | NVIDIA RTX PRO 6000 96GB, 32 vCPU / 256 GB · GPU NVIDIA RTX PRO 6000, 96 GB | 32 | 256 GB | — | IN | Visa/MC | 1,492 $ |
| [MojoHost](https://accsly.io/en/vps/hosting/mojohost) | RTX Pro 6000 96GB MICHIGAN · GPU NVIDIA RTX Pro 6000, 96 GB | 20 | 240 GB | — | US | Visa/MC | 1,499 $ |
| [MojoHost](https://accsly.io/en/vps/hosting/mojohost) | RTX Pro 6000 96GB NETHERLANDS · GPU NVIDIA RTX Pro 6000, 96 GB | 20 | 240 GB | — | NL | Visa/MC | 1,499 $ |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC36dsxlRTX6K v6 (West Europe) · GPU NVIDIA RTX PRO 6000 Blackwell Server Edition | 36 | 132 GB | — | NL | Visa/MC | 1,505 $ (when paying for 3 years: 662 $/mo) |
| [Hetzner](https://accsly.io/en/vps/hosting/hetzner) | GEX131 · GPU NVIDIA RTX PRO 6000 Blackwell Max-Q, 96 GB | 24 × 2.1 GHz | 256 GB | — | FI, DE | Visa/MC, PayPal, Invoice | 1,678 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/gpu/rtx-pro-6000?format=json

## RTX PRO 6000 for rent: 96 GB on a single card for large models and rendering

The NVIDIA RTX PRO 6000 is a professional Blackwell-generation card with 96 GB of GDDR7 memory with error correction (ECC). That is more than the 80 GB of an H100 PCIe and twice as much as an RTX 6000 Ada. The main reason to pick a GPU server with RTX PRO 6000 is to run a model on one card that used to need two, without splitting the weights across accelerators. It is still a full graphics card, too: it has RT cores for ray tracing and hardware NVENC encoders, so people rent it for rendering and video as well.

### Three cards with similar names

Catalogs make it easy to mix up three different generations, and their prices differ several times over:

- **Quadro RTX 6000** — Turing architecture, 24 GB. An old graphics card with too little memory and compute for current neural networks.
- **RTX 6000 Ada** — 48 GB, the previous generation. Close in design to the [L40S](https://accsly.io/en/gpu/l40s).
- **RTX PRO 6000 Blackwell** — 96 GB of GDDR7, fifth-generation tensor cores with FP4, FP6 and FP8 formats. This is the card collected on this page.

Blackwell comes in variants as well. The Server Edition is built for racks: passive cooling, up to 600 W, with airflow from the server fans. Max-Q is a 300 W workstation version with a blower fan; it is easier to fit several in one chassis, but under sustained load it runs at lower clocks. If the plan line just says "RTX PRO 6000", ask the host which variant it is: speed depends on it, and so does MIG availability.

### What fits into 96 GB

A rough estimate: in FP16 a model takes about 2 GB per billion parameters, with 8-bit quantization about 1 GB, with 4-bit 0.5–0.6 GB. On top of that you need headroom for the KV cache, which grows with context length and the number of concurrent requests.

- **FP16 without quantization** — models up to roughly 30–40 billion parameters with moderate context.
- **8-bit** — a 70-billion-parameter model entirely on one card, with room left for the cache.
- **4-bit** — models in the 100–120 billion class. FP4 support in the tensor cores speeds up this kind of inference if your engine handles the format.
- **Fine-tuning** — LoRA for 13–30B models in 16-bit and QLoRA for 70B. Full training of large models is not a job for this card.
- **Images and video** — image generation in large batches, heavy video generation models that feel cramped in 24–48 GB.
- **Rendering and 3D** — scenes with huge textures that do not fit in gaming cards, offline rendering, video transcoding on NVENC.

### MIG, multiple cards and when an H100 is better

The Server Edition supports MIG: the card can be split into four isolated instances of about 24 GB each, every one with its own memory and compute units. That is handy when several small models or several users share one server. If a plan lists a share of the card with part of its memory, it is a vGPU or MIG slice, not a whole card: compare the memory size, not the model name.

The "×2" and "×4" plans give 192 and 384 GB in total, but the RTX PRO 6000 has no NVLink, so the cards talk over PCIe 5.0. For inference this usually does not get in the way: each card can run its own copy of the model, and splitting one model across two cards over PCIe works acceptably. For training, where cards constantly synchronize gradients, the slower link eats up the gain. If you plan multi-GPU training, look at [H100 servers](https://accsly.io/en/gpu/h100) with NVLink.

### Driver, CUDA and the image

The card has compute capability 12.0. It needs the R570 driver branch or newer and CUDA 12.8 or later. In older images with CUDA 12.4 the card either will not be detected or the framework will find no kernels for it. Once the server is delivered, check the `nvidia-smi` output, the CUDA version inside the container, and that PyTorch or your inference engine is built with support for this architecture.

### Hourly billing or a month

Renting a server with RTX PRO 6000 in the catalog costs roughly $830 to $5,700 a month, with a typical plan around $1,800. The low end is a single cloud card, the high end is dedicated machines with four cards. Most plans are billed by the hour, which pays off for a trial run, a one-off data processing job or a render against a deadline: you pay only for the hours the machine runs. If the card will be busy more than two thirds of the month, compare with the monthly price and with the [dedicated GPU servers](https://accsly.io/en/gpu/dedicated) section. Before paying, check that the host accepts your card in your currency; if you process personal data of EU residents, also check the data centre country for GDPR purposes and its latency to your users.

## FAQ

### How much video memory does the RTX PRO 6000 have?

96 GB of GDDR7 with ECC error correction. That is more than the H100 PCIe (80 GB) and twice the RTX 6000 Ada.

### Will a 70-billion-parameter model fit on one RTX PRO 6000?

With 8-bit or 4-bit quantization, yes, with room for context. In FP16 such a model takes about 140 GB and needs two cards.

### How is the RTX PRO 6000 different from the RTX 6000 Ada and Quadro RTX 6000?

They are three generations: Quadro RTX 6000 (Turing, 24 GB), RTX 6000 Ada (48 GB) and RTX PRO 6000 Blackwell (96 GB, FP4 support). For neural networks the gap in memory and speed is very large.

### Does the RTX PRO 6000 have NVLink?

No, in multi-GPU servers the cards are linked over PCIe 5.0. That is usually enough for inference; for training across several cards H100s with NVLink are a better fit.

### Which CUDA version does the RTX PRO 6000 need?

CUDA 12.8 or newer and a driver from the R570 branch or later. In images with an older CUDA the framework may not recognise the card.

### What does Max-Q mean in a plan name?

It is a 300 W variant of the card instead of the 600 W Server Edition. It has the same 96 GB of memory, but runs slower under sustained load.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# GPU servers with NVIDIA L4

Servers with NVIDIA L4 (24 GB, 72 W), an efficient card for inference, speech recognition and video. Compare card count, CPU, RAM and price; cheapest first.

> Source: https://accsly.io/en/gpu/l4 · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 33, hosts: 10
- Price: from 57.78 $, a quarter below 447 $, median 655 $
- NVMe: 58 %, unlimited traffic: 45 %, hourly billing: 48 %
- RAM → price from: 1 GB — 57.78 $, 2 GB — 57.78 $, 4 GB — 57.78 $, 8 GB — 57.78 $, 16 GB — 127 $
- Countries: France (11), Poland (10), United Kingdom (9), Canada (6), Germany (6), USA (6)
- Cheapest hosts: [VDSina](https://accsly.io/en/vps/hosting/vdsina-ru) — 57.78 $, [CloudTechtiq](https://accsly.io/en/vps/hosting/cloudtechtiq) — 320 $, [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) — 327 $, [Dimofinf](https://accsly.io/en/vps/hosting/dimofinf) — 450 $, [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) — 604 $

## Cheapest plans — 33 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [VDSina](https://accsly.io/en/vps/hosting/vdsina-ru) | GPU 8 core / 8 Gb / 2 Gb VRAM · GPU NVIDIA L4, 2 GB | 8 × 3.6 GHz | 8 GB | 150 GB NVMe | RU, NL | Crypto, Invoice | 57.78 $ |
| [VDSina](https://accsly.io/en/vps/hosting/vdsina-ru) | GPU 16 core / 16 Gb / 4 Gb VRAM · GPU L4, 4 GB | 16 × 3.6 GHz | 16 GB | 500 GB NVMe | RU, NL | Crypto, Invoice | 127 $ |
| [CloudTechtiq](https://accsly.io/en/vps/hosting/cloudtechtiq) | NVIDIA L4 AMD EPYC 9015 AI Server · GPU NVIDIA L4, 24 GB | 8 | 64 GB | 480 GB SSD | IN | Invoice | 320 $ |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Vajra · GPU NVIDIA L4, 24 GB | 25 | 110 GB | 250 GB SSD | IN | Visa/MC, Invoice | 327 $ |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Apex · GPU NVIDIA L4, 24 GB | 12 | 32 GB | 480 GB SSD | SE | Visa/MC, Invoice | 447 $ |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Celtic · GPU NVIDIA L4, 24 GB | 12 | 32 GB | 480 GB SSD | IE | Visa/MC, Invoice | 447 $ |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Crown · GPU NVIDIA L4, 24 GB | 12 | 32 GB | 480 GB SSD | NL | Visa/MC, Invoice | 447 $ |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Emerald · GPU NVIDIA L4, 24 GB | 12 | 32 GB | 480 GB SSD | FR | Visa/MC, Invoice | 447 $ |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Forge · GPU NVIDIA L4, 24 GB | 12 | 32 GB | 480 GB SSD | CH | Visa/MC, Invoice | 447 $ |
| [Dimofinf](https://accsly.io/en/vps/hosting/dimofinf) | GPU 2 · GPU NVIDIA L4, 24 GB | 48 | 128 GB | 1920 GB SSD | SA | Visa/MC, Invoice, PayPal | 450 $ |
| [CloudTechtiq](https://accsly.io/en/vps/hosting/cloudtechtiq) | Titanium Cloud GPU · GPU NVIDIA L4 ×2, 24 GB | 16 | 128 GB | 1 TB NVMe | IN | Invoice | 479 $ |
| [Dimofinf](https://accsly.io/en/vps/hosting/dimofinf) | GPU 3 · GPU NVIDIA L4, 24 GB | 48 | 128 GB | 1920 GB SSD | SA | Visa/MC, Invoice, PayPal | 520 $ |
| [VDSina](https://accsly.io/en/vps/hosting/vdsina-ru) | Конструктор GPU NVIDIA L4 24GB VRAM · GPU NVIDIA L4, 24 GB | 8 × 3.6 GHz | 16 GB | 5 GB NVMe | RU, NL | Crypto, Invoice | 548 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Public Cloud GPU l4-90 · GPU NVIDIA L4, 24 GB | 22 × 2.8 GHz | 90 GB | 400 GB NVMe | CA, DE, FR, GB, PL, US | PayPal, Visa/MC | 604 $ |
| [CloudTechtiq](https://accsly.io/en/vps/hosting/cloudtechtiq) | NVIDIA Dual L4 AMD EPYC 9015 AI · GPU NVIDIA L4 ×2, 24 GB | 16 | 128 GB | 960 GB NVMe | IN | Invoice | 639 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | L4-1-24G · GPU NVIDIA L4, 24 GB | 8 × 2.7 GHz | 48 GB | — | FR, PL | — | 643 $ |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Astra · GPU NVIDIA L4 ×2, 24 GB | 50 | 220 GB | 250 GB SSD | IN | Visa/MC, Invoice | 655 $ |
| [Timeweb Cloud](https://accsly.io/en/vps/hosting/timeweb-cloud) | Intel Xeon E-2488 (8 ядер, 3.2-5.6 ГГц, 16 потоков) / 64 DDR5 / 2 x 2 Тб NVMe + 2 x 960 Гб SSD + GPU L4 24GB · GPU NVIDIA L4, 24 GB | 8 × 3.2 GHz | 64 GB | 5920 GB NVMe | RU | MIR, Visa/MC, SBP, YooMoney, Invoice | 850 $ |
| [Timeweb](https://accsly.io/en/vps/hosting/timeweb) | Intel Xeon E-2488 (8 ядер, 3.2-5.6 ГГц, 16 потоков) / 64 DDR5 / 2 x 2 Тб NVMe + 2 x 960 Гб SSD + GPU L4 24GB · GPU NVIDIA L4, 24 GB | 8 × 3.2 GHz | 64 GB | 5920 GB NVMe | RU | MIR, Visa/MC, YooMoney, SBP, Invoice | 850 $ |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Vector · GPU NVIDIA L4, 24 GB | 24 | 256 GB | 1 TB NVMe | GB | Visa/MC, Invoice | 874 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/gpu/l4?format=json

## Renting a server with NVIDIA L4: what fits in 24 GB and where the card beats its neighbours

The NVIDIA L4 is an Ada Lovelace card built for servers that care about power draw: 72 W, a low-profile single-slot passive design, powered straight from its PCIe 4.0 x16 slot. Where a chassis takes one big card, it can take several L4s. That defines its role: people rent a GPU server with L4 not to train large models but for round-the-clock inference, speech recognition and video processing, where the hourly price and the number of parallel streams matter most. It is the successor of the [T4](https://accsly.io/en/gpu/t4) and noticeably faster at the same jobs.

### What fits in 24 GB of video memory

The L4 has 24 GB of GDDR6. For language models, a rule of thumb: FP16 needs about 2 GB per billion parameters, 8-bit about 1 GB, 4-bit 0.5–0.6 GB, plus the KV cache, which grows with context length and the number of concurrent requests.

- **7–8B parameters in FP16** fit, but with a long context and several users at once the headroom runs out fast.
- **13B in 8-bit** fits with room for context.
- **Around 30B in 4-bit** is the limit for one card, with a short context.
- **Whisper, embeddings, rerankers** are the L4's core work: the models are small, and one card can host several such services.
- **Image generation** with Stable Diffusion or Flux runs at moderate speed; for a heavy stream of images a stronger card is more comfortable.

Fine-tuning works as LoRA or QLoRA for models up to 7–8B, but full training is not what this card is for. FP8 support (compute capability 8.9) helps inference: in FP8 a model takes half the memory of FP16 and usually loses less quality than 4-bit formats, provided your inference engine supports FP8.

### Where the L4 hits its limit and what to compare it with

The main limit is memory bandwidth, about 300 GB/s. Token generation speed in a language model depends on it first of all, so a chatbot on an L4 answers more slowly than on a card with the same capacity but faster memory.

- [A10](https://accsly.io/en/gpu/a10): also 24 GB, but about 600 GB/s at 150 W. Usually faster for chat with live users; for video and small models the extra cost is not always justified.
- [L40S](https://accsly.io/en/gpu/l40s): 48 GB and far more compute. Needed when a model does not fit in 24 GB or a large model gets many concurrent requests.

Video is where the L4 shines. Its hardware NVENC and NVDEC support AV1, and one card transcodes many streams at once: live-stream transcoding, clip cutting, camera footage analysis with object detection on the same card.

### A slice, one card or several

The cheapest rows in the table are not whole cards but vGPU slices with 2 or 4 GB of video memory. The L4 has no MIG; it is shared through vGPU profiles. A slice suits video, remote desktops and light recognition models, but not language models: even a small LLM with a usable context will not fit in 2–4 GB. The other plans give you whole cards, one, two or four.

The L4 has no NVLink either, so cards talk only over PCIe. A server with L4 ×2 or ×4 therefore pays off not for one big model split into parts but for several independent workers: each card runs its own copy of the model and a load balancer spreads the requests. If you need a single 40–70B model, one card with more memory is the better choice.

### Drivers, prices and billing

The L4 needs an NVIDIA driver from the 525 branch or newer and CUDA 11.8+; FP8 needs CUDA 12 and recent builds of PyTorch, vLLM or TensorRT-LLM. In a ready-made image check the nvidia-smi output: card model, memory (24 GB or the slice size) and driver version. On vGPU slices the guest driver has to match the host side, so it usually comes from the host's image rather than from the NVIDIA website.

Renting a server with L4 in the catalogue costs roughly from $60 a month for a slice to about $5,000 for a dedicated machine with four cards, with the middle of the range around $870. Most plans bill by the hour, which pays off for tests, batch video jobs and services needed only during working hours. If the card is busy around the clock, compare the hourly price with the monthly one; see the page on [hourly billing](https://accsly.io/en/vps/hourly-billing). Plans are spread across several regions: for personal data of EU residents pick an EU data centre to keep GDPR compliance simple, and for live inference choose a location close to your users to keep latency low. Most hosts accept international bank cards.

## FAQ

### Which language model can I run on an NVIDIA L4?

Its 24 GB hold a 7–8B model in FP16, a 13B model in 8-bit and roughly a 30B model in 4-bit. With a long context and many concurrent requests the memory headroom shrinks quickly.

### How is the L4 different from the A10?

Both have 24 GB, but the A10 has roughly twice the memory bandwidth, about 600 GB/s, and draws 150 W versus 72 W for the L4. The A10 usually generates text faster; the L4 is more efficient and stronger at video thanks to its AV1 codecs.

### Is a 2–4 GB slice of an L4 enough for AI?

Not for language models: even a small LLM with context will not fit. A slice suits video, remote desktops and light recognition models.

### Does the L4 support NVLink or MIG?

No. Cards in one server are linked only over PCIe, and a card is shared between customers through vGPU profiles. Several L4s work best as independent workers, each with its own model.

### Which driver and CUDA version does the L4 need?

An NVIDIA driver from the 525 branch or newer and CUDA 11.8 or later; FP8 needs CUDA 12 and recent framework versions. The card's compute capability is 8.9.

### Is hourly or monthly billing better for an L4?

Hourly suits tests, batch jobs and services that run a few hours a day. Under round-the-clock load a monthly plan or a dedicated server is usually cheaper.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# GPU servers with NVIDIA A16

Servers with NVIDIA A16 (four 16 GB GPUs on one board) for virtual desktops, video encoding and light inference. Compare CPU, memory and price; cheapest first.

> Source: https://accsly.io/en/gpu/a16 · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 28, hosts: 7
- Price: from 44.00 $, a quarter below 172 $, median 360 $
- NVMe: 29 %, unlimited traffic: 0 %, hourly billing: 36 %
- RAM → price from: 1 GB — 44.00 $, 2 GB — 44.00 $, 4 GB — 44.00 $, 8 GB — 80.64 $, 16 GB — 80.64 $
- Countries: USA (15), India (14), Germany (13), Singapore (13), Japan (12), United Kingdom (8)
- Cheapest hosts: [BitHost](https://accsly.io/en/vps/hosting/bithost) — 44.00 $, [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) — 80.64 $, [Hosthink](https://accsly.io/en/vps/hosting/hosthink) — 86.00 $, [Initech](https://accsly.io/en/vps/hosting/initech) — 90.00 $, [Vultr](https://accsly.io/en/vps/hosting/vultr) — 344 $

## Cheapest plans — 28 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Vultr GPU NVIDIA A16 · 2 vCPU / 4 GB / 50 GB · GPU NVIDIA A16, 1 GB | 2 | 4 GB | 50 GB SSD |  | Crypto | 44.00 $ |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | GPU A16 8vCPU/64GB/250GB · GPU NVIDIA A16, 16 GB | 8 | 64 GB | 250 GB NVMe | IN | Invoice | 80.64 $ |
| [Hosthink](https://accsly.io/en/vps/hosting/hosthink) | HT-C-012 Cloud GPU · GPU NVIDIA A16, 2 GB | 2 | 8 GB | 50 GB SSD | DE, GB, IN, JP, SG, US | Visa/MC, Invoice | 86.00 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Vultr GPU NVIDIA A16 · 2 vCPU / 8 GB / 50 GB · GPU NVIDIA A16, 2 GB | 2 | 8 GB | 50 GB SSD |  | Crypto | 86.00 $ |
| [Initech](https://accsly.io/en/vps/hosting/initech) | Vultr Cloud GPU — A16 1/8 GPU, 2GB GPU Memory, 2 vCPU, 8 GB RAM, 50 GB NVMe, Cloud GPU, 1.00 TB Transfer (Chicago) · GPU NVIDIA A16, 2 GB | 2 | 8 GB | 50 GB NVMe | DE, JP, SG, US | PayPal, Crypto | 90.00 $ (when paying for year: 71.99 $/mo) |
| [Hosthink](https://accsly.io/en/vps/hosting/hosthink) | HT-C-014 Cloud GPU · GPU NVIDIA A16, 4 GB | 2 | 16 GB | 80 GB SSD | DE, GB, IN, JP, SG, US | Visa/MC, Invoice | 172 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Vultr GPU NVIDIA A16 · 2 vCPU / 16 GB / 80 GB · GPU NVIDIA A16, 4 GB | 2 | 16 GB | 80 GB SSD |  | Crypto | 172 $ |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | GPU A16 16vCPU/64GB/768GB · GPU NVIDIA A16, 16 GB | 16 | 64 GB | 768 GB SSD | IN | Invoice | 173 $ |
| [Initech](https://accsly.io/en/vps/hosting/initech) | Vultr Cloud GPU — A16 1/4 GPU, 4GB GPU Memory, 2 vCPU, 16 GB RAM, 80 GB NVMe, Cloud GPU, 2.00 TB Transfer (Chicago) · GPU NVIDIA A16, 4 GB | 2 | 16 GB | 80 GB NVMe | DE, JP, SG, US | PayPal, Crypto | 180 $ (when paying for year: 144 $/mo) |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | GPU A16 32vCPU/256GB/1800GB · GPU NVIDIA A16 | 32 | 256 GB | 1800 GB SSD | IN | Invoice | 287 $ |
| [Vultr](https://accsly.io/en/vps/hosting/vultr) | Cloud GPU 1× NVIDIA A16 6 vCPU / 60 GB (vcg-a16-6c-60g-16vram) · GPU NVIDIA A16, 16 GB | 6 | 60 GB | 350 GB SSD | DE, GB, IN, JP, SG, US | Visa/MC, PayPal, Crypto | 344 $ |
| [Hosthink](https://accsly.io/en/vps/hosting/hosthink) | HT-C-016 Cloud GPU · GPU NVIDIA A16, 8 GB | 3 | 32 GB | 170 GB SSD | DE, GB, IN, JP, SG, US | Visa/MC, Invoice | 344 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Vultr GPU NVIDIA A16 · 3 vCPU / 32 GB / 170 GB · GPU NVIDIA A16, 8 GB | 3 | 32 GB | 170 GB SSD |  | Crypto | 344 $ |
| [Initech](https://accsly.io/en/vps/hosting/initech) | Vultr Cloud GPU — A16 1/2 GPU, 8GB GPU Memory, 3 vCPU, 32 GB RAM, 170 GB NVMe, Cloud GPU, 3.00 TB Transfer (Chicago) · GPU NVIDIA A16, 8 GB | 3 | 32 GB | 170 GB NVMe | DE, JP, SG, US | PayPal, Crypto | 360 $ (when paying for year: 288 $/mo) |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | GPU A16 64vCPU/512GB/6400GB · GPU NVIDIA A16 | 64 | 512 GB | 6400 GB NVMe | IN | Invoice | 391 $ |
| [0xcloud](https://accsly.io/en/vps/hosting/0xcloud) | vcg-a16-6c-64g-16vram · GPU NVIDIA A16, 16 GB | 6 | 64 GB | 350 GB SSD | US, IN, DE, GB, SG, JP | Crypto | 465 $ |
| [Justhost](https://accsly.io/en/vps/hosting/justhost) | GPU Rigel A16 · GPU NVIDIA A16, 16 GB | 16 | 32 GB | 200 GB NVMe | US | MIR, Visa/MC, PayPal, YooMoney, Invoice | 576 $ (when paying for 3 years: 346 $/mo) |
| [Vultr](https://accsly.io/en/vps/hosting/vultr) | Cloud GPU 2× NVIDIA A16 12 vCPU / 120 GB (vcg-a16-12c-120g-32vram) · GPU NVIDIA A16 ×2, 16 GB | 12 | 120 GB | 700 GB SSD | DE, GB, IN, JP, SG, US | Visa/MC, PayPal, Crypto | 688 $ |
| [Hosthink](https://accsly.io/en/vps/hosting/hosthink) | HT-C-018 Cloud GPU · GPU NVIDIA A16, 16 GB | 6 | 64 GB | 350 GB SSD | DE, GB, IN, JP, SG, US | Visa/MC, Invoice | 688 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Vultr GPU NVIDIA A16 · 6 vCPU / 64 GB / 350 GB · GPU NVIDIA A16, 16 GB | 6 | 64 GB | 350 GB SSD |  | Crypto | 688 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/gpu/a16?format=json

## NVIDIA A16 for rent: four GPUs on one board and what your machine actually gets

The NVIDIA A16 is built differently from most server cards. One PCIe board carries four separate Ampere-generation GPUs, each with its own 16 GB of GDDR6, for 64 GB per board at about 250 W. The card was designed for virtual desktops and video: one board is shared among many users, and it has enough hardware codecs for dozens of video streams. Each of the four GPUs, however, is modest in compute, well below an [A10](https://accsly.io/en/gpu/a10) or an [L4](https://accsly.io/en/gpu/l4). Renting an A16 server makes sense when the number of users and streams matters more than the speed of one large model.

### What "A16" means in a plan

The main trap: "A16" in a plan name almost never means the whole 64 GB board. A virtual machine usually gets one of the four GPUs with its 16 GB, or a vGPU slice of one GPU with part of its memory. That is why video memory in the catalog starts at 2 GB: these are small vGPU profiles meant for a desktop, not for neural networks.

- **vGPU slice (2 to 8 GB).** A share of one GPU; the compute units are time-shared with neighbours. Good for a remote desktop, viewing drawings and light graphics.
- **One full GPU (16 GB).** The most a single model or application can get on an A16. The option for small-model inference and video encoding.
- **Several GPUs (32, 64 or 128 GB).** Two, four or eight separate processors, that is, up to two boards. There is no shared memory pool: the A16 has no NVLink and no MIG partitioning. Splitting a model across GPUs over PCIe works, but slowly. These plans pay off when you run several independent copies of a service or serve many workstations.

### AI workloads: what fits into 16 GB on one GPU

Memory rule of thumb: about 2 GB per billion parameters in FP16, about 1 GB in 8-bit, 0.5–0.6 GB in 4-bit, plus the context cache (KV cache), which grows with conversation length. On one A16 GPU this means:

- 3–4B models run in FP16 with room for a long context;
- 7–8B models are comfortable in 8-bit or 4-bit; in FP16 the weights take almost all the memory and leave no room for context;
- 13–14B models fit only in 4-bit and with a short context;
- OCR, embeddings for document search, classifiers and small speech-recognition models are a comfortable load;
- Stable Diffusion image generation works, but noticeably slower than on RTX-class cards.

Memory bandwidth per GPU is low, so token generation is unhurried even on a small model. Training on an A16 makes little sense: QLoRA for a 7B model technically fits into 16 GB but takes many times longer than on an A100. For a chatbot that has to answer fast, or a model above 14B, pick a card with more memory and compute.

### Virtual desktops, CAD and video

The A16's strength is VDI. With NVIDIA vGPU one board serves many remote workstations: office applications with hardware-accelerated graphics, CAD model and drawing viewers, light 3D. A GPU server with an A16 fits a team that needs remote workstations when buying a powerful computer for everyone is too expensive. For heavy rendering and complex scenes one small GPU is not enough.

For video, what matters is that each of the four GPUs has its own NVENC encoders and NVDEC decoders. A server with several GPUs transcodes many streams at once to H.264 and HEVC while barely loading the CPU. AV1 decoding is supported, but the Ampere generation has no hardware AV1 encoding.

### Drivers, vGPU licence, billing and prices

- **CUDA.** The A16 has compute capability 8.6: you need CUDA 11.1 or newer and a driver that supports it. Current PyTorch builds and CUDA 12 containers work; BF16 and TF32 are supported, FP8 is not.
- **Driver inside vGPU.** A vGPU machine uses a guest driver whose version must match the driver on the provider's host. The standard driver from the NVIDIA website may not work, so ask which image or package to use.
- **vGPU licence.** NVIDIA vGPU software is licensed separately. The provider may or may not include the licence in the price: check before paying, and ask whether CUDA compute is allowed in your profile, since that depends on the licence type.
- **Hourly or monthly.** Only a small share of A16 plans in the catalog bill by the hour; the rest are monthly. Desktops and transcoding usually run non-stop, so a monthly plan is cheaper for them. Hourly is handy for a test: run your model or video pipeline, check nvidia-smi output, then decide. More in the [hourly billing VPS](https://accsly.io/en/vps/hourly-billing) selection.

All A16 plans in the catalog are cloud or VPS plans. Prices run from roughly $85 to $5,500 a month, with the middle of the range around $690. At the bottom are vGPU slices with a couple of vCPUs; at the top, servers with several GPUs, dozens of vCPUs and hundreds of gigabytes of RAM. If the desktops or data belong to EU users, check the data centre country for GDPR and for latency to your team or audience in the EU or US. Compare not just the total price but how much video memory and how many full GPUs you get for it.

## FAQ

### How much video memory do I get with an A16 plan?

Usually one GPU with 16 GB or a vGPU slice from 2 GB. The 64 GB board is four separate GPUs, and a single model can use at most 16 GB on one of them.

### Can the memory of the four A16 GPUs be combined?

No: there is no shared memory pool and the A16 has no NVLink. A model can be split across GPUs over PCIe, but slowly, so people usually run a separate copy of the service on each GPU.

### Which language models run on an A16?

On one GPU, 3–8B models in 8-bit or 4-bit, and models up to 13–14B only in 4-bit with a short context. Responses come slower than on an A10 or L4.

### Is the A16 suitable for training neural networks?

No. Each GPU has little compute, and even fine-tuning a small model drags on. For training people use an A100 or H100.

### Do I need an NVIDIA vGPU licence?

vGPU profiles need a licence, but the provider often includes it in the price. Check before paying and ask whether CUDA compute is allowed in the profile.

### How is the A16 different from the A10 and L4?

The A16 is built for many users and video streams on one board; the A10 and L4 give you one fast GPU for inference and graphics. For a single model that needs quick answers, an A10 or L4 is the better buy.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# GPU servers with NVIDIA L40S

Servers with NVIDIA L40S (48 GB, Ada Lovelace) for LLM inference, image generation and rendering, as a full card or a vGPU slice. Compare VRAM, CPU and price; cheapest first.

> Source: https://accsly.io/en/gpu/l40s · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 27, hosts: 10
- Price: from 112 $, a quarter below 610 $, median 1,201 $
- NVMe: 63 %, unlimited traffic: 37 %, hourly billing: 56 %
- RAM → price from: 1 GB — 112 $, 2 GB — 112 $, 4 GB — 112 $, 8 GB — 300 $, 16 GB — 309 $
- Countries: Russia (8), France (8), Netherlands (6), Germany (6), Poland (6), Canada (4)
- Cheapest hosts: [FirstVDS](https://accsly.io/en/vps/hosting/firstvds) — 112 $, [VDSina](https://accsly.io/en/vps/hosting/vdsina-ru) — 309 $, [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) — 575 $, [Fornex](https://accsly.io/en/vps/hosting/fornex) — 610 $, [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) — 1,128 $

## Cheapest plans — 27 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [FirstVDS](https://accsly.io/en/vps/hosting/firstvds) | vGPU 4 (L40S-4Q) · GPU NVIDIA L40S-4Q, 4 GB | 2 × 3.9 GHz | 4 GB | 30 GB NVMe | RU | Invoice, MIR, Visa/MC, SBP, YooMoney | 112 $ (yearly: 112 $/mo) |
| [FirstVDS](https://accsly.io/en/vps/hosting/firstvds) | vGPU 8 (L40S-8Q) · GPU NVIDIA L40S-8Q, 8 GB | 4 × 3.9 GHz | 6 GB | 50 GB NVMe | RU | Invoice, MIR, Visa/MC, SBP, YooMoney | 207 $ (yearly: 207 $/mo) |
| [FirstVDS](https://accsly.io/en/vps/hosting/firstvds) | vGPU 12 (L40S-12Q) · GPU NVIDIA L40S-12Q, 12 GB | 6 × 3.9 GHz | 8 GB | 100 GB NVMe | RU | Invoice, MIR, Visa/MC, SBP, YooMoney | 300 $ (yearly: 300 $/mo) |
| [VDSina](https://accsly.io/en/vps/hosting/vdsina-ru) | GPU 32 core / 32 Gb / 8 Gb VRAM · GPU NVIDIA L40S, 8 GB | 32 × 3.6 GHz | 32 GB | 500 GB NVMe | RU, NL | Crypto, Invoice | 309 $ |
| [FirstVDS](https://accsly.io/en/vps/hosting/firstvds) | vGPU 16 (L40S-16Q) · GPU NVIDIA L40S-16Q, 16 GB | 8 × 3.9 GHz | 12 GB | 150 GB NVMe | RU | Invoice, MIR, Visa/MC, SBP, YooMoney | 356 $ (yearly: 356 $/mo) |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Agni · GPU NVIDIA L40S, 48 GB | 60 | 220 GB | 250 GB SSD | IN | Visa/MC, Invoice | 575 $ |
| [Fornex](https://accsly.io/en/vps/hosting/fornex) | GPU: L40SMIN · GPU NVIDIA L40S, 48 GB | 16 × 3.0 GHz | 64 GB | 1920 GB NVMe | DE, SE, NL | Visa/MC, Crypto, MIR, SBP | 610 $ |
| [Fornex](https://accsly.io/en/vps/hosting/fornex) | GPU: L40SMED · GPU NVIDIA L40S, 48 GB | 32 × 3.3 GHz | 128 GB | 3840 GB NVMe | DE, SE, NL | Visa/MC, Crypto, MIR, SBP | 756 $ |
| [Fornex](https://accsly.io/en/vps/hosting/fornex) | GPU: L40SMAX · GPU NVIDIA L40S, 48 GB | 32 × 3.3 GHz | 256 GB | 8160 GB NVMe | DE, SE, NL | Visa/MC, Crypto, MIR, SBP | 861 $ |
| [FirstVDS](https://accsly.io/en/vps/hosting/firstvds) | GPU L40S · GPU NVIDIA L40S, 48 GB | 16 | 32 GB | 500 GB NVMe | RU | Invoice, MIR, Visa/MC, SBP, YooMoney | 934 $ (yearly: 934 $/mo) |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Public Cloud GPU l40s-90 · GPU NVIDIA L40S, 48 GB | 15 × 2.8 GHz | 90 GB | 400 GB NVMe | CA, DE, FR, GB, PL, US | PayPal, Visa/MC | 1,128 $ |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Tejas · GPU NVIDIA L40S ×2, 48 GB | 120 | 440 GB | 250 GB SSD | IN | Visa/MC, Invoice | 1,140 $ |
| [DigitalOcean](https://accsly.io/en/vps/hosting/digitalocean) | GPU Droplet NVIDIA L40S · GPU NVIDIA L40S, 48 GB | 8 | 64 GB | 500 GB NVMe | US, CA, NL | Visa/MC, PayPal, Invoice | 1,146 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | L40S-1-48G · GPU NVIDIA L40S, 48 GB | 8 × 2.7 GHz | 96 GB | — | FR, PL | — | 1,201 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox GPU-10-L40S · GPU NVIDIA L40S ×2, 48 GB | 32 × 2.7 GHz | 256 GB | 7680 GB NVMe | FR | — | 1,679 $ (when paying for 3 years: 1,427 $/mo) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | EM-T220E-L40S · GPU NVIDIA L40S ×2 | 32 × 2.7 GHz | 256 GB | 7680 GB NVMe | FR | — | 1,679 $ |
| [VDSina](https://accsly.io/en/vps/hosting/vdsina-ru) | Конструктор GPU NVIDIA L40S 48GB VRAM · GPU NVIDIA L40S, 48 GB | 8 × 3.6 GHz | 16 GB | 5 GB NVMe | RU, NL | Crypto, Invoice | 1,820 $ |
| [Aruba Cloud](https://accsly.io/en/vps/hosting/arubacloud) | AI - A110.2 · GPU NVIDIA L40S, 48 GB | 32 × 3.0 GHz | 128 GB | 960 GB SSD | IT | — | 2,046 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Public Cloud GPU l40s-180 · GPU NVIDIA L40S ×2, 48 GB | 30 × 2.8 GHz | 180 GB | 400 GB NVMe | CA, DE, FR, GB, PL, US | PayPal, Visa/MC | 2,257 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | L40S-2-48G · GPU NVIDIA L40S ×2, 48 GB | 16 × 2.7 GHz | 192 GB | — | FR, PL | — | 2,402 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/gpu/l40s?format=json

## Renting an L40S server: what fits in 48 GB and how a vGPU slice differs from a full card

The NVIDIA L40S is a data-centre card built on the Ada Lovelace architecture: 48 GB of GDDR6 memory with ECC, tensor cores with FP8 support, RT cores for ray tracing and hardware codecs with AV1. It sits between low-power inference cards and training accelerators: twice the memory of 24 GB cards, at a noticeably lower price than an H100. The table above lists cloud plans and dedicated servers with this card, from a vGPU slice with a few gigabytes of memory to four-card builds. If you are looking at an L40S server rental, first check what you actually get: the whole card or a part of it.

### What fits in 48 GB of video memory

Memory is the main reason to pick the L40S. A rule of thumb for language models: about 2 GB per billion parameters in FP16, about 1 GB in 8-bit quantization and 0.5–0.6 GB in 4-bit. On top of that you need headroom for the KV cache: the longer the context and the more parallel requests, the more memory it takes.

- **7–13B models in FP16** fit with room to spare: a 13B model takes about 26 GB, leaving space for long context and batched requests.
- **30–34B models in 8-bit** need about 34–36 GB for weights. That is a workable setup for one card with moderate context.
- **70B models** fit only in 4-bit quantization: the weights take about 40 GB, leaving a few gigabytes for context. Enough for a single user and short conversations; for a service under load, two cards are better.
- **Fine-tuning.** LoRA on 7–13B models and QLoRA up to roughly 30B fit on one card. Full training of even a 7B model with the Adam optimizer needs more than 48 GB.

If your model is under 8B parameters and needs up to 24 GB, compare prices for [L4 servers](https://accsly.io/en/gpu/l4): they are more economical for that load. For training large models from scratch, the [H100](https://accsly.io/en/gpu/h100) and A100 are a better fit: their HBM memory has far higher bandwidth and the cards are linked through NVLink.

### Images, rendering and video

This is where the L40S is stronger than in training. Stable Diffusion and Flux generate images on it in seconds, and 48 GB lets you work at high resolution, keep several models in memory at once and train your own LoRAs without offloading weights. RT cores speed up rendering in Blender Cycles via OptiX and in other GPU renderers, and the large memory holds heavy scenes with high-resolution textures. Hardware NVENC and NVDEC with AV1 support handle video transcoding without loading the CPU.

### vGPU slice, full card and ×2, ×4 builds

The cheapest rows in the table are not full cards. Plans named "L40S-4Q", "-8Q", "-12Q", "-16Q" give you a share of one card through NVIDIA vGPU: the virtual machine gets 4, 8, 12 or 16 GB of video memory and a portion of compute time. The letter Q stands for the virtual workstation profile.

- **A 4–8 GB slice** suits a remote workstation: CAD, 3D modelling, hardware-accelerated editing. You will not run a language model of useful size in 4 GB.
- **A 12–16 GB slice** handles image generation and small 4-bit models, but compute units are shared with neighbours and speed is not guaranteed.
- **A full 48 GB card** is what you need for inference of large models, fine-tuning and steady performance.
- **×2 and ×4 builds** give 96 and 192 GB in total. The L40S has no NVLink, so cards talk over PCIe 4.0, and splitting one model across cards is slower than on NVLink accelerators. Several independent model copies, one per card, scale almost linearly though.

The L40S does not support MIG: the card is shared only through vGPU profiles.

### Driver, CUDA and what to check in the image

- **Compute capability 8.9.** You need CUDA 11.8 or newer; for FP8 and current PyTorch releases pick an image with CUDA 12.
- **On vGPU slices the driver** is installed by the host: the machine runs a vGPU guest driver, and you should not install a regular driver over it. Ask for its version in advance.
- **nvidia-smi output** after first boot shows the model, the allocated memory and the CUDA version; compare them with the plan.

### Hourly or monthly billing and price range

In the catalogue a GPU server with the L40S costs roughly $115 a month for a vGPU slice up to about $4,500 for the most powerful multi-card configurations; the median is around $960. Fewer than half of the plans bill by the hour. Hourly billing pays off for one-off jobs: a fine-tuning run, rendering a project, testing a model before launch. If the card is busy most of the month, a monthly plan or a [dedicated GPU server](https://accsly.io/en/gpu/dedicated) is usually cheaper. How to compare such plans is covered on the [hourly billing](https://accsly.io/en/vps/hourly-billing) page. Check the data centre location too: for personal data of EU residents a data centre in the EU keeps GDPR compliance simple, and a nearby location cuts latency for interactive use and speeds up dataset downloads. Payment methods per plan are listed in the table; most international hosts take regular bank cards.

## FAQ

### Which language model can I run on an L40S?

Models up to 13B parameters run in FP16 with headroom, and 30–34B fit in 8-bit. A 70B model runs only in 4-bit quantization with short context.

### What does L40S-4Q or L40S-16Q mean in a plan name?

It is a share of one card through vGPU with 4 or 16 GB of video memory; Q is the virtual workstation profile. Compute units are shared with other customers, and language models need a bigger slice or a full card.

### Is the L40S good for training neural networks?

For LoRA and QLoRA fine-tuning of mid-size models, yes. For full training of large models an H100 or A100 with HBM memory and NVLink is better.

### Does the L40S have NVLink or MIG?

No. In multi-card servers the cards are linked over PCIe 4.0, and a single card is shared only through vGPU profiles.

### Which CUDA version does the L40S need?

The card has compute capability 8.9 and works with CUDA 11.8 and newer. For FP8 and current PyTorch releases an image with CUDA 12 is the better choice.

### How is the L40S different from the L4?

The L40S has 48 GB of memory and several times the compute at 350 W. The L4 with 24 GB and low power draw is cheaper and fits inference of small models and video processing.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# GPU servers with NVIDIA A100

Cloud, VPS and dedicated servers with NVIDIA A100. Compare the number of cards, video memory, processor and price; cheapest first.

> Source: https://accsly.io/en/gpu/a100 · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 26, hosts: 10
- Price: from 180 $, a quarter below 1,065 $, median 2,131 $
- NVMe: 35 %, unlimited traffic: 8 %, hourly billing: 50 %
- RAM → price from: 1 GB — 180 $, 2 GB — 180 $, 4 GB — 180 $, 8 GB — 360 $, 16 GB — 720 $
- Countries: India (11), USA (8), Canada (5), Germany (5), France (5), United Kingdom (5)
- Cheapest hosts: [BitHost](https://accsly.io/en/vps/hosting/bithost) — 180 $, [Dimofinf](https://accsly.io/en/vps/hosting/dimofinf) — 720 $, [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) — 863 $, [Hapih Host](https://accsly.io/en/vps/hosting/hapihhost) — 1,071 $, [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) — 1,143 $

## Cheapest plans — 26 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Vultr GPU NVIDIA A100 · 1 vCPU / 6 GB / 70 GB · GPU NVIDIA A100, 4 GB | 1 | 6 GB | 70 GB SSD |  | Crypto | 180 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Vultr GPU NVIDIA A100 · 1 vCPU / 12 GB / 140 GB · GPU NVIDIA A100, 8 GB | 1 | 12 GB | 140 GB SSD |  | Crypto | 360 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Vultr GPU NVIDIA A100 · 2 vCPU / 15 GB / 170 GB · GPU NVIDIA A100, 10 GB | 2 | 15 GB | 170 GB SSD |  | Crypto | 500 $ |
| [Dimofinf](https://accsly.io/en/vps/hosting/dimofinf) | GPU 4 · GPU NVIDIA A100 | 48 | 128 GB | 1920 GB SSD | SA | Visa/MC, Invoice, PayPal | 720 $ |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Pinnacle · GPU NVIDIA A100, 40 GB | 36 | 256 GB | 2 TB NVMe | US | Visa/MC, Invoice | 863 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Vultr GPU NVIDIA A100 · 3 vCPU / 30 GB / 350 GB · GPU NVIDIA A100, 20 GB | 3 | 30 GB | 350 GB SSD |  | Crypto | 900 $ |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Prithvi · GPU NVIDIA A100, 80 GB | 16 | 115 GB | 250 GB SSD | IN | Visa/MC, Invoice | 1,065 $ |
| [Hapih Host](https://accsly.io/en/vps/hosting/hapihhost) | 1xA100 · GPU NVIDIA A100, 80 GB | 8 | 32 GB | 500 GB SSD | IN | Visa/MC | 1,071 $ (when paying for year: 943 $/mo) |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | GPU A100-80GB 16vCPU/115GB/1500GB · GPU NVIDIA A100 80GB, 80 GB | 16 | 115 GB | 1500 GB NVMe | IN | Invoice | 1,143 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Public Cloud GPU a100-180 · GPU NVIDIA A100, 80 GB | 15 × 3.0 GHz | 180 GB | 300 GB NVMe | CA, DE, FR, GB, PL, US | PayPal, Visa/MC | 1,231 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Vultr GPU NVIDIA A100 · 6 vCPU / 60 GB / 700 GB · GPU NVIDIA A100, 40 GB | 6 | 60 GB | 700 GB SSD |  | Crypto | 1,750 $ |
| [Hapih Host](https://accsly.io/en/vps/hosting/hapihhost) | 2xA100 · GPU NVIDIA A100 ×2, 80 GB | 16 | 64 GB | 1 TB SSD | IN | Visa/MC | 2,002 $ (when paying for year: 1,874 $/mo) |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Akash · GPU NVIDIA A100 ×2, 80 GB | 32 | 230 GB | 250 GB SSD | IN | Visa/MC, Invoice | 2,131 $ |
| [Temok.com](https://accsly.io/en/vps/hosting/temok) | GPU Dedicated Server, Dual Intel E5-2697v4, 1× NVIDIA A100 80GB · GPU NVIDIA A100 80GB, 80 GB | 36 × 2.3 GHz | 256 GB | 10240 GB NVMe | US | Visa/MC, PayPal, Invoice | 2,199 $ |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | GPU 2xA100-80GB 32vCPU/230GB/3000GB · GPU NVIDIA A100 80GB ×2, 80 GB | 32 | 230 GB | 3 TB NVMe | IN | Invoice | 2,287 $ |
| [0xcloud](https://accsly.io/en/vps/hosting/0xcloud) | vcg-a100-12c-120g-80vram · GPU NVIDIA A100, 80 GB | 12 | 120 GB | 1400 GB SSD | US, JP | Crypto | 2,363 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Public Cloud GPU a100-360 · GPU NVIDIA A100 ×2, 80 GB | 30 × 3.0 GHz | 360 GB | 500 GB NVMe | CA, DE, FR, GB, PL, US | PayPal, Visa/MC | 2,462 $ |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC24ads A100 v4 · GPU NVIDIA A100 80GB PCIe, 80 GB | 24 | 220 GB | — | AU, BR, CA, CH, DE, ES… | Visa/MC | 2,681 $ (when paying for 3 years: 995 $/mo) |
| [Hapih Host](https://accsly.io/en/vps/hosting/hapihhost) | 3xA100 · GPU NVIDIA A100 ×3, 80 GB | 24 | 96 GB | 1500 GB SSD | IN | Visa/MC | 2,935 $ (when paying for year: 2,807 $/mo) |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC24ads A100 v4 (West Europe) · GPU NVIDIA A100 80GB PCIe, 80 GB | 24 | 220 GB | — | NL | Visa/MC | 3,486 $ (when paying for 3 years: 1,294 $/mo) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/gpu/a100?format=json

## Renting a server with an NVIDIA A100: 40 or 80 GB, PCIe or SXM, and which models to train on it

The NVIDIA A100 is an Ampere-generation accelerator for training and inference, the card on which most language models of the early 2020s were built. It has HBM memory, Tensor Cores with TF32, BF16 and FP16, full FP64 for scientific work, partitioning into isolated instances through MIG, and card-to-card links through NVLink. As of 3 November 2026 the catalog lists 17 A100 plans from six providers: 14 cloud plans and 3 dedicated servers, seven of them with hourly billing. Monthly prices start at about $850, with a median around $2,450. Configurations carry one, two or four cards; 13 plans have 80 GB cards, mostly the PCIe version, and 4 plans have 40 GB cards.

### Four A100 versions and how they differ

The compute side is the same on every A100: 9.7 TFLOPS FP64 (19.5 on the Tensor Cores), 19.5 FP32, 156 TF32, 312 TFLOPS FP16 and BF16, 624 TOPS INT8; with structured sparsity the Tensor Core figures double. What differs is memory, power and how the card is attached.

- **A100 40GB PCIe**: HBM2, 1555 GB/s, 250 W.
- **A100 80GB PCIe**: HBM2e, 1935 GB/s, 300 W. This is the one you will see most often in the table above.
- **A100 40GB SXM**: 1555 GB/s, 400 W.
- **A100 80GB SXM**: HBM2e, 2039 GB/s, 400 W.

The 80 GB version wins twice: it has double the memory and it is about a quarter faster. For text generation, where speed is bound by reading weights from memory, that is a direct gain; for training it means a larger batch without splitting. The 40 GB version makes sense when the model and data clearly fit and the price is noticeably lower.

SXM modules sit on HGX boards, where all cards are connected through NVLink at up to 600 GB/s. PCIe cards attach to the 64 GB/s PCIe Gen4 bus, and NVLink between them is possible only with a bridge and only for a pair. So four A100 PCIe cards without bridges exchange gradients over the bus, and for training with a split model that is noticeably slower than the same four cards on HGX.

### What to train and fine-tune on an A100

Memory guidelines: for FP16 inference a model takes about 2 GB per billion parameters. Full mixed-precision training with the Adam optimizer needs roughly 16 bytes per parameter for weights, gradients and optimizer states, plus activations.

- **Full fine-tuning.** A 1–3B model trains in full on one 80 GB card. For 7–8B one card is not enough: you need two to four A100s with optimizer states sharded across them (ZeRO, FSDP), and here NVLink speeds things up noticeably.
- **LoRA and QLoRA.** LoRA for 7–13B models and QLoRA for models around 70B fit on a single 80 GB card. This is the most common reason to rent an A100: fine-tune an open model on your own data in a few hours or days.
- **Inference.** A 30–34B model in FP16 fits on one 80 GB card with a moderate context; 70B in FP16 needs two cards, in 8-bit one card with a small margin.
- **Scientific computing.** Up to 19.5 TFLOPS of FP64 on the Tensor Cores makes the A100 a good fit for simulation and double-precision linear algebra, where inference cards are close to useless.

For ×2 and ×4 plans, ask in advance how the cards are linked. Two A100 PCIe cards with an NVLink bridge handle distributed fine-tuning of 7–13B models well, while four cards without bridges are better used differently: a separate experiment, hyperparameter set or inference copy of the model on each. Plan for disk as well: a checkpoint of a 7B model with optimizer states weighs around a hundred gigabytes, so local NVMe with room for several saves spares hours of waiting.

### MIG: one A100 as seven small ones

MIG splits the card into up to seven isolated instances. Each has its own memory and compute units, and neighbours do not affect each other's latency. On a 40 GB A100 the smallest instance gets 5 GB, on an 80 GB card 10 GB. This is handy when you need to host several small models on one card or give a team separate isolated GPUs for experiments. If a plan shows less than 40 GB of video memory, it is most likely a MIG instance rather than a whole card: nvidia-smi shows its profile, for example 1g.10gb. For training and large models, take a plan with a full card.

### When to pick an H100, and when an A10 or L4 is enough

The [H100](https://accsly.io/en/gpu/h100) is justified when training time costs more than rental: it has HBM3 at up to 3.35 TB/s in the SXM5 version, FP8 support and NVLink at up to 900 GB/s. If you train large models for weeks or serve many users with one big model, the speed-up often pays for the price difference. If the workload is LoRA fine-tuning, inference of a mid-size model or scientific code without FP8, an A100 80GB delivers most of the result for noticeably less.

In the other direction, an A100 is overkill for inference of quantized 7–13B models, speech recognition and embeddings. 24 GB cards, the [A10](https://accsly.io/en/gpu/a10) or [L4](https://accsly.io/en/gpu/l4), handle such loads at a fraction of the price. Renting an A100 for these jobs makes sense only as a MIG instance.

Hourly plans suit one-off training runs: train, save a checkpoint, delete the server. The details are in our note on [hourly billing](https://accsly.io/en/vps/hourly-billing). After delivery, check in nvidia-smi which version you have (PCIe or SXM, 40 or 80 GB) and run nvidia-smi topo -m to see whether the cards share NVLink. The A100 has compute capability 8.0, supported by current CUDA 12 and 13. If your training data contains personal information of EU residents, choose the data centre country with GDPR in mind.

## FAQ

### How does the A100 40GB differ from the 80GB?

In memory size and speed: the 40GB has HBM2 at 1555 GB/s, the 80GB has HBM2e at 1935 GB/s in the PCIe version and 2039 GB/s in SXM. Compute performance is the same.

### Which model can I fine-tune on one A100 80GB?

With LoRA, 7–13B models; with QLoRA, up to about 70B. Full training fits for 1–3B models; 7B and larger need several cards.

### How many instances does MIG give on an A100?

Up to seven isolated instances. On a 40 GB card the smallest instance gets 5 GB of memory, on an 80 GB card 10 GB.

### Does the A100 PCIe have NVLink?

Only through an NVLink bridge and only between two cards. Full NVLink connectivity of all cards at up to 600 GB/s comes with the SXM version on HGX boards.

### A100 or H100 for training?

The H100 is faster thanks to HBM3, FP8 and NVLink at up to 900 GB/s, and pays off on long training of large models. For LoRA fine-tuning and inference of mid-size models, the A100 80GB is usually better value.

### Which CUDA version does the A100 need?

The A100 has compute capability 8.0, supported by both CUDA 12 and CUDA 13, along with BF16 and TF32. Before starting, match the driver version in the image against your framework's requirements.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# GPU servers with NVIDIA H100

Servers with NVIDIA H100 (80 GB HBM, Hopper) for training and serving large models, cloud and dedicated. Compare card count, CPU, memory and price; cheapest first.

> Source: https://accsly.io/en/gpu/h100 · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 21, hosts: 13
- Price: from 1,361 $, a quarter below 2,397 $, median 3,219 $
- NVMe: 57 %, unlimited traffic: 24 %, hourly billing: 81 %
- RAM → price from: 1 GB — 1,361 $, 2 GB — 1,361 $, 4 GB — 1,361 $, 8 GB — 1,361 $, 16 GB — 1,361 $
- Countries: France (7), USA (7), India (4), Germany (4), Canada (4), Poland (4)
- Cheapest hosts: [Hostnetindia.com](https://accsly.io/en/vps/hosting/hostnetindia) — 1,361 $, [Fornex](https://accsly.io/en/vps/hosting/fornex) — 1,890 $, [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) — 2,171 $, [Gcorelabs](https://accsly.io/en/vps/hosting/gcore) — 2,304 $, [Scaleway](https://accsly.io/en/vps/hosting/scaleway) — 2,342 $

## Cheapest plans — 21 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Hostnetindia.com](https://accsly.io/en/vps/hosting/hostnetindia) | GPU 1xH100 · GPU NVIDIA H100, 80 GB | 26 | 250 GB | 3 TB SSD | IN | — | 1,361 $ |
| [Fornex](https://accsly.io/en/vps/hosting/fornex) | GPU: H100 · GPU NVIDIA H100 | 32 × 3.3 GHz | 256 GB | 1920 GB NVMe | DE, NL, SE | Visa/MC, Crypto, MIR, SBP | 1,890 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Public Cloud GPU h100-380 · GPU NVIDIA H100, 80 GB | 30 × 3.0 GHz | 380 GB | 4040 GB NVMe | CA, DE, FR, GB, PL, US | PayPal, Visa/MC | 2,171 $ |
| [Gcorelabs](https://accsly.io/en/vps/hosting/gcore) | Virtual GPU 1×H100 · GPU NVIDIA H100 80GB, 80 GB | 24 | 232 GB | 1250 GB SSD |  | Visa/MC, PayPal, Invoice | 2,304 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | H100-1-80G · GPU NVIDIA H100 PCIe, 80 GB | 24 × 2.7 GHz | 240 GB | — | FR, PL | — | 2,342 $ |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU Overlord · GPU NVIDIA H100, 80 GB | 36 | 256 GB | 2 TB NVMe | US | Visa/MC, Invoice | 2,397 $ |
| [Hosthink](https://accsly.io/en/vps/hosting/hosthink) | GPU-3 H100 80GB (Keflavik) · GPU NVIDIA H100 80GB, 80 GB | 32 × 2.4 GHz | 160 GB | 1 TB NVMe | IS | Visa/MC, Invoice | 2,535 $ |
| [Hostnetindia.com](https://accsly.io/en/vps/hosting/hostnetindia) | GPU 2×H100 · GPU NVIDIA H100 ×2, 80 GB | 52 | 500 GB | 6 TB SSD | IN | — | 2,722 $ |
| [Temok.com](https://accsly.io/en/vps/hosting/temok) | GPU Dedicated Server, Dual Intel E5-2697v4, 1× NVIDIA H100 80GB · GPU NVIDIA H100 80GB, 80 GB | 36 | 256 GB | 10240 GB NVMe | US | Visa/MC, PayPal, Invoice | 2,729 $ |
| [server.ir](https://accsly.io/en/vps/hosting/server-ir) | OGS H100 · GPU NVIDIA H100 NVL, 94 GB | 64 × 3.1 GHz | 256 GB | 960 GB NVMe | US | Invoice | 2,955 $ |
| [DigitalOcean](https://accsly.io/en/vps/hosting/digitalocean) | GPU Droplet NVIDIA HGX H100 ×1 · GPU NVIDIA H100, 80 GB | 20 | 240 GB | 720 GB NVMe | US, CA, NL | Visa/MC, PayPal, Invoice | 3,219 $ |
| [Timeweb Cloud](https://accsly.io/en/vps/hosting/timeweb-cloud) | AMD Ryzen 9 9950X (16 ядер, 4.3-5.7 ГГц, 32 потока) / 192 DDR5 / 2 x 2 Тб NVMe + GPU H100 80GB · GPU NVIDIA H100, 80 GB | 16 × 4.3 GHz | 192 GB | 4 TB NVMe | RU | MIR, Visa/MC, SBP, YooMoney, Invoice | 3,562 $ |
| [Timeweb](https://accsly.io/en/vps/hosting/timeweb) | AMD Ryzen 9 9950X (16 ядер, 4.3-5.7 ГГц, 32 потока) / 192 DDR5 / 2 x 2 Тб NVMe + GPU H100 80GB · GPU NVIDIA H100 80GB, 80 GB | 16 × 4.3 GHz | 192 GB | 4 TB NVMe | RU | MIR, Visa/MC, YooMoney, SBP, Invoice | 3,562 $ |
| [Gcorelabs](https://accsly.io/en/vps/hosting/gcore) | Virtual GPU 2×H100 · GPU NVIDIA H100 80GB ×2, 80 GB | 48 | 464 GB | 2500 GB SSD |  | Visa/MC, PayPal, Invoice | 3,865 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox GPU-10-H100 · GPU NVIDIA H100 ×2, 80 GB | 32 × 2.7 GHz | 512 GB | 15360 GB NVMe | FR | — | 3,918 $ (when paying for 3 years: 3,330 $/mo) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | EM-T620E-H100 · GPU NVIDIA H100 ×2 | 32 × 2.7 GHz | 512 GB | 15362 GB NVMe | FR | — | 3,918 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Public Cloud GPU h100-760 · GPU NVIDIA H100 ×2, 80 GB | 60 × 3.0 GHz | 760 GB | 7880 GB NVMe | CA, DE, FR, GB, PL, US | PayPal, Visa/MC | 4,343 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | H100-2-80G · GPU NVIDIA H100 PCIe ×2, 80 GB | 48 × 2.7 GHz | 480 GB | — | FR, PL | — | 4,684 $ |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC40ads H100 v5 · GPU NVIDIA H100 NVL, 94 GB | 40 | 320 GB | — | AE, AU, CA, CH, DE, ES… | Visa/MC | 5,095 $ (when paying for 3 years: 2,802 $/mo) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | H100-SXM-2-80G · GPU NVIDIA H100 SXM ×2, 80 GB | 32 × 2.0 GHz | 240 GB | — | FR | — | 5,409 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/gpu/h100?format=json

## Renting an H100 server: SXM or PCIe, what fits in 80 GB and how not to overpay

NVIDIA H100 is the Hopper-generation accelerator for training and serving large models. People rent an H100 server when an A100 is no longer fast enough and the model or dataset needs 80 GB of fast memory per card. The table above lists cloud plans and dedicated servers with one, two or four cards; monthly prices in the catalogue run from roughly $1,350 to $5,400, with the middle around $3,000. Most plans can be billed by the hour.

### SXM, PCIe and NVL: three different H100s under one name

Quite different cards are sold as H100, and plans often just say "H100 80GB".

- **H100 SXM5, 80 GB HBM3.** About 3.35 TB/s of memory bandwidth and up to 700 W. It sits on HGX boards where the cards are linked by NVLink at up to 900 GB/s. This is the fastest option for multi-GPU training.
- **H100 PCIe, 80 GB HBM2e.** About 2 TB/s and 350 W, a regular card in a PCIe slot. A pair can be joined with an NVLink bridge, but that is optional, not the rule. Slower than SXM, but cheaper and more common in the cloud.
- **H100 NVL, 94 GB HBM3.** A PCIe card with extra memory, designed to work in pairs over NVLink bridges. The additional 14 GB per card helps with long context in inference.

How to tell which one a plan has: look for SXM, PCIe or NVL in the name; a 700 W power figure points to SXM, 350–400 W to the PCIe version. For multi-card setups ask whether NVLink is present and between which cards: four PCIe cards without bridges exchange data only over the bus, which noticeably slows training with a split model. Once the server is up, check the card with `nvidia-smi` (name and power limit) and the links between cards with `nvidia-smi topo -m`.

### What fits in 80 GB

Rule of thumb: in FP16 a model takes about 2 GB per billion parameters, in 8-bit about 1 GB, in 4-bit 0.5–0.6 GB, plus headroom for the KV cache, which grows with context length and the number of concurrent requests.

- **70B models in FP8** fit on a single 80 GB card with moderate context. For long context and many users an H100 NVL or two cards is more comfortable.
- **The same 70B in FP16** takes about 140 GB and needs two cards with the model split between them (tensor parallel).
- **In 4-bit** a single card leaves plenty of room for context and parallel requests on models up to 70B.
- **Full fine-tuning** of 7–13B models fits on one or two cards; gradients and optimizer state take several times more memory than the weights.
- **LoRA and QLoRA on 70B** run on several cards, QLoRA with a small batch sometimes on one.

The main step up from the previous generation is the Transformer Engine with FP8: with frameworks that support it, transformer inference and training run noticeably faster than in FP16, and the model takes half the memory. For image generation and rendering the H100 is overkill: those jobs are cheaper on an [L40S](https://accsly.io/en/gpu/l40s) or RTX-class cards.

### MIG, drivers and CUDA

The H100 supports MIG: the card can be split into up to seven isolated instances, each with its own share of memory and compute. Clouds sell fractional GPUs this way. That is economical for serving a small model, but training and large models need a full card, so check the VRAM figure in the plan, not just the name.

The H100 has compute capability 9.0. It needs CUDA 11.8 or newer, 12.x recommended, and a matching NVIDIA datacenter driver. In the image, check the driver, CUDA version and PyTorch build: old images made for A100 or V100 will start but without FP8 and with lost speed.

### Hourly or monthly

The card is expensive, so the billing model affects the total more than with smaller GPUs. Hourly plans suit experiments, hyperparameter searches and one-off runs: start the server, train, save the checkpoint to external storage, delete the server. More on that in the [hourly billing](https://accsly.io/en/vps/hourly-billing) section. If you need an H100 for a service that answers users around the clock, or for training that lasts weeks, a monthly plan or a [dedicated GPU server](https://accsly.io/en/gpu/dedicated) usually works out cheaper.

Training across several servers needs InfiniBand or another fast network between nodes. The catalogue does not always state it, so ask before paying. Also check the data centre location: for personal data of EU users, GDPR terms matter, and for interactive services latency to your users in Europe or the US does too.

If you do not need FP8 and the budget is tight, compare with the [A100](https://accsly.io/en/gpu/a100): it is cheaper and also has 80 GB, but it is slower and lacks FP8. The newer H200 offers 141 GB and makes sense when a model does not fit in 80–94 GB.

## FAQ

### What is the difference between H100 SXM and H100 PCIe?

SXM5 runs on HGX boards with NVLink at up to 900 GB/s, has HBM3 at about 3.35 TB/s and draws up to 700 W. The PCIe version is slower: HBM2e at about 2 TB/s, 350 W and NVLink only via a bridge between a pair of cards.

### Will a 70B model fit on one H100?

In FP8 or 4-bit quantization, yes, with moderate context. In FP16 the model needs about 140 GB, so two cards.

### Which CUDA version does the H100 need?

At least CUDA 11.8, 12.x recommended, plus an NVIDIA datacenter driver. The card's compute capability is 9.0.

### What is the H100 NVL?

It is a PCIe version of the H100 with 94 GB of HBM3, installed in pairs joined by NVLink bridges. It is handy for serving large models with long context.

### Can I rent part of an H100?

Yes, if the plan uses MIG: the card is split into up to seven isolated instances, each with its own memory. For training and large models, choose a plan with a full card.

### Is an H100 cheaper by the hour or by the month?

By the hour for experiments and one-off training runs. Under round-the-clock load a monthly plan or a dedicated server is usually cheaper.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# GPU servers with NVIDIA RTX 4000 Ada

Servers with NVIDIA RTX 4000 Ada (20 GB) for rendering, image generation and small-model inference. Compare card count, CPU and price, cheapest first.

> Source: https://accsly.io/en/gpu/rtx-4000-ada · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 19, hosts: 5
- Price: from 346 $, a quarter below 555 $, median 978 $
- NVMe: 16 %, unlimited traffic: 53 %, hourly billing: 89 %
- RAM → price from: 1 GB — 346 $, 2 GB — 346 $, 4 GB — 346 $, 8 GB — 346 $, 16 GB — 346 $
- Countries: USA (10), Germany (9), France (9), India (9), Singapore (7), Japan (4)
- Cheapest hosts: [KODU.CLOUD](https://accsly.io/en/vps/hosting/kodu) — 346 $, [Akamai (Linode)](https://accsly.io/en/vps/hosting/linode) — 380 $, [Aluy](https://accsly.io/en/vps/hosting/aluy) — 458 $, [DigitalOcean](https://accsly.io/en/vps/hosting/digitalocean) — 555 $, [BitHost](https://accsly.io/en/vps/hosting/bithost) — 700 $

## Cheapest plans — 19 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [KODU.CLOUD](https://accsly.io/en/vps/hosting/kodu) | GX-234-1 · GPU NVIDIA RTX 4000 SFF Ada Generation, 20 GB | 14 | 64 GB | 3932 GB NVMe | DE | Visa/MC | 346 $ |
| [Akamai (Linode)](https://accsly.io/en/vps/hosting/linode) | RTX 4000 Ada GPU x1 Small · GPU NVIDIA RTX 4000 Ada, 20 GB | 4 | 16 GB | 500 GB SSD | US, DE, FR, IN, SG, JP | Visa/MC, PayPal, Invoice | 380 $ |
| [Aluy](https://accsly.io/en/vps/hosting/aluy) | Hetzner auction #3093155 — Intel Core i5-13500, 64 GB, 2× 1920 GB NVMe · GPU NVIDIA RTX 4000 SFF Ada, 20 GB | 14 | 64 GB | 3840 GB NVMe | DE | PayPal, Visa/MC, Crypto | 458 $ |
| [Akamai (Linode)](https://accsly.io/en/vps/hosting/linode) | RTX 4000 Ada GPU x1 Medium · GPU NVIDIA RTX 4000 Ada, 20 GB | 8 | 32 GB | 500 GB SSD | US, DE, FR, IN, SG, JP | Visa/MC, PayPal, Invoice | 489 $ |
| [DigitalOcean](https://accsly.io/en/vps/hosting/digitalocean) | GPU Droplet NVIDIA RTX 4000 Ada · GPU NVIDIA RTX 4000 Ada Generation, 20 GB | 8 | 32 GB | 500 GB NVMe | US, CA, NL | Visa/MC, PayPal, Invoice | 555 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Linode GPU NVIDIA RTX 4000 Ada · 4 vCPU / 16 GB / 512 GB · GPU NVIDIA RTX 4000 Ada, 20 GB | 4 | 16 GB | 512 GB SSD |  | Crypto | 700 $ |
| [Akamai (Linode)](https://accsly.io/en/vps/hosting/linode) | RTX 4000 Ada GPU x1 Large · GPU NVIDIA RTX 4000 Ada, 20 GB | 16 | 64 GB | 500 GB SSD | US, DE, FR, IN, SG, JP | Visa/MC, PayPal, Invoice | 701 $ |
| [Akamai (Linode)](https://accsly.io/en/vps/hosting/linode) | RTX 4000 Ada GPU x2 Small · GPU NVIDIA RTX 4000 Ada ×2, 20 GB | 8 | 32 GB | 1 TB SSD | US, DE, FR, IN, SG | Visa/MC, PayPal, Invoice | 767 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Linode GPU NVIDIA RTX 4000 Ada · 8 vCPU / 32 GB / 512 GB · GPU NVIDIA RTX 4000 Ada, 20 GB | 8 | 32 GB | 512 GB SSD |  | Crypto | 892 $ |
| [Akamai (Linode)](https://accsly.io/en/vps/hosting/linode) | RTX 4000 Ada GPU x2 Medium · GPU NVIDIA RTX 4000 Ada ×2, 20 GB | 16 | 64 GB | 1 TB SSD | US, DE, FR, IN, SG | Visa/MC, PayPal, Invoice | 978 $ |
| [Akamai (Linode)](https://accsly.io/en/vps/hosting/linode) | RTX 4000 Ada GPU x2 Medium High Storage · GPU NVIDIA RTX 4000 Ada ×2, 20 GB | 16 | 64 GB | 2 TB SSD | US, DE, FR, IN, SG | Visa/MC, PayPal, Invoice | 1,088 $ |
| [Akamai (Linode)](https://accsly.io/en/vps/hosting/linode) | RTX 4000 Ada GPU x1 X-Large · GPU NVIDIA RTX 4000 Ada, 20 GB | 32 | 128 GB | 500 GB SSD | US, DE, FR, IN, SG, JP | Visa/MC, PayPal, Invoice | 1,117 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Linode GPU NVIDIA RTX 4000 Ada · 16 vCPU / 64 GB / 512 GB · GPU NVIDIA RTX 4000 Ada, 20 GB | 16 | 64 GB | 512 GB SSD |  | Crypto | 1,276 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Linode GPU NVIDIA RTX 4000 Ada · 16 vCPU / 64 GB / 2048 GB · GPU NVIDIA RTX 4000 Ada ×2, 20 GB | 16 | 64 GB | 2048 GB SSD |  | Crypto | 1,984 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Linode GPU NVIDIA RTX 4000 Ada · 32 vCPU / 128 GB / 512 GB · GPU NVIDIA RTX 4000 Ada, 20 GB | 32 | 128 GB | 512 GB SSD |  | Crypto | 2,041 $ |
| [Akamai (Linode)](https://accsly.io/en/vps/hosting/linode) | RTX 4000 Ada GPU x4 Small · GPU NVIDIA RTX 4000 Ada ×4, 20 GB | 32 | 128 GB | 2 TB SSD | US, FR, IN | Visa/MC, PayPal, Invoice | 2,161 $ |
| [Akamai (Linode)](https://accsly.io/en/vps/hosting/linode) | RTX 4000 Ada GPU x4 Medium · GPU NVIDIA RTX 4000 Ada ×4, 20 GB | 48 | 196 GB | 2 TB SSD | US, FR, IN | Visa/MC, PayPal, Invoice | 2,606 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Linode GPU NVIDIA RTX 4000 Ada · 32 vCPU / 128 GB / 2048 GB · GPU NVIDIA RTX 4000 Ada ×4, 20 GB | 32 | 128 GB | 2048 GB SSD |  | Crypto | 3,952 $ |
| [BitHost](https://accsly.io/en/vps/hosting/bithost) | Linode GPU NVIDIA RTX 4000 Ada · 48 vCPU / 196 GB / 2048 GB · GPU NVIDIA RTX 4000 Ada ×4, 20 GB | 48 | 196 GB | 2048 GB SSD |  | Crypto | 4,768 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/gpu/rtx-4000-ada?format=json

## Renting an NVIDIA RTX 4000 Ada server: what fits in 20 GB and when one card is enough

The RTX 4000 Ada Generation is NVIDIA's professional workstation card on the Ada Lovelace architecture, with 20 GB of GDDR6 memory and ECC error correction. It has the same FP8-capable tensor cores, third-generation RT cores and AV1-capable NVENC encoder as the bigger cards in the line, at a modest power draw. Renting an RTX 4000 Ada server makes sense when you want a current architecture and certified drivers, and the 24–48 GB of the larger cards would be more than the job needs.

### Two versions of the card, and what not to confuse it with

- **RTX 4000 Ada Generation**: a single-slot card with an active fan and a power draw of up to 130 W.
- **RTX 4000 SFF Ada**: a 70 W low-profile version with the same 20 GB of memory but lower clocks. It goes into compact servers and is noticeably slower than the full-size card on long compute jobs.
- **Quadro RTX 4000**: an older Turing card with 8 GB of memory. The name is similar, the class is not: if a plan does not say "Ada", ask the host which model it is.

Compared with the [NVIDIA L4](https://accsly.io/en/gpu/l4), the RTX 4000 Ada has slightly less memory (20 GB versus 24 GB), but it has its own cooling and drivers for graphics applications, while the L4 is a passively cooled data-centre accelerator built mainly for inference and video. The [L40S](https://accsly.io/en/gpu/l40s) on the same architecture offers 48 GB and far more compute, at several times the price.

### What fits in 20 GB of video memory

Rule of thumb for language models: about 2 GB per billion parameters in FP16, about 1 GB in 8-bit quantization and 0.5–0.6 GB in 4-bit. On top of that comes the KV cache, which grows with context length and the number of concurrent requests.

- **7–8B parameters in FP16**: they fit, but only with a short context, since the weights alone take 14–16 GB.
- **13B in 8-bit**: comfortable, with room for context and several parallel requests.
- **Around 30B in 4-bit**: a tight fit with a small context; a 24–48 GB card is more convenient for models this size.
- **Image generation.** SDXL runs on one card with room to spare. Full-precision Flux does not fit in 20 GB, so people use FP8 or quantized versions, and Ada tensor cores handle FP8 in hardware.
- **Rendering and video.** Blender Cycles with OptiX, Unreal Engine, CAD packages, editing and encoding to H.264, HEVC and AV1 with NVENC.

For fine-tuning, 20 GB is enough for LoRA and QLoRA on models up to 7–8B parameters. Full training of even small language models needs cards with more memory.

### One card, ×2 and ×4

The catalogue has plans with one, two and four cards. The RTX 4000 Ada has neither NVLink nor MIG: cards talk only over the PCIe 4.0 bus, and each one sees its own 20 GB. A ×4 server is not 80 GB of shared memory but four separate 20 GB pools. A large model can be split across cards (tensor or pipeline parallelism in vLLM, layer splitting in llama.cpp), but the traffic over PCIe slows generation down.

Multi-card plans pay off best on independent work: four copies of a model serve parallel requests, or a render job draws different frames on different cards. In cloud plans the card is usually passed through to the virtual machine whole; if a plan lists a share of a card, check how much memory you actually get.

### Drivers and CUDA

The RTX 4000 Ada has compute capability 8.9. It needs CUDA 11.8 or newer, and FP8 needs CUDA 12 with recent libraries; the R535 driver branch and later supports both versions of the card. In the image, check the nvidia-smi output and the CUDA and PyTorch versions: framework builds for older CUDA may not know this architecture. For Blender, Unreal and CAD, where certification matters, the professional RTX Enterprise or Studio driver is used, so ask which driver the host installs and whether the image includes the OpenGL and Vulkan graphics stack.

### Prices, hourly and monthly billing

As of 24 October 2026, an RTX 4000 Ada GPU server in the catalogue costs roughly $350 to $2,600 a month: single-card plans with 4 vCPUs at the bottom, four-card builds with dozens of cores and almost 200 GB of RAM at the top. A typical plan comes to around $750–800 a month. Almost all plans are billed by the hour, which suits a render on a deadline, model tests and one-off generation runs, where the server lives for a few hours and is then deleted. If the card is busy more than half of every day for the whole month, compare the hourly bill with the monthly price. How to count such plans is covered in the [hourly-billed VPS](https://accsly.io/en/vps/hourly-billing) selection. Most hosts take payment by card; if you process personal data of EU residents, also check the data-centre country, as it decides how GDPR applies and what latency your users in Europe or the US will see.

## FAQ

### How much video memory does the RTX 4000 Ada have?

20 GB of GDDR6 with ECC on both versions: the full-size 130 W card and the low-profile 70 W RTX 4000 SFF Ada. The SFF version runs at lower clocks, so it computes more slowly.

### Which language model can I run on an RTX 4000 Ada?

A 7–8B model in FP16 with a short context, 13B in 8-bit quantization and around 30B in 4-bit, though that is a tight fit. For long contexts, leave spare memory for the KV cache.

### How is the RTX 4000 Ada different from the Quadro RTX 4000?

The Quadro RTX 4000 is a Turing card with 8 GB of memory. The RTX 4000 Ada is two generations newer and has 20 GB, FP8 support and AV1 encoding.

### Is memory pooled in the ×2 and ×4 plans?

No. This card has no NVLink, each card sees only its own 20 GB, and a model split across cards exchanges data over PCIe 4.0, which is slower than one card with more memory.

### Does the RTX 4000 Ada support MIG?

No, hardware MIG partitioning is only on data-centre accelerators such as the A100 and H100. Several models on one RTX 4000 Ada run as separate processes that share the 20 GB.

### Is the RTX 4000 Ada good for rendering in Blender?

Yes: third-generation RT cores speed up Cycles through OptiX, and the professional driver is certified for Blender, Unreal and CAD. The limit is 20 GB of memory for very heavy scenes.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# GPU servers with NVIDIA V100

Cloud, VPS and dedicated servers with NVIDIA V100. Compare the number of cards, video memory, processor and price; cheapest first.

> Source: https://accsly.io/en/gpu/v100 · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 16, hosts: 6
- Price: from 115 $, a quarter below 358 $, median 1,128 $
- NVMe: 56 %, unlimited traffic: 0 %, hourly billing: 69 %
- RAM → price from: 1 GB — 115 $, 2 GB — 115 $, 4 GB — 115 $, 8 GB — 115 $, 16 GB — 115 $
- Countries: Canada (11), USA (9), France (8), United Kingdom (8), Germany (6), Poland (6)
- Cheapest hosts: [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) — 115 $, [ServaRica](https://accsly.io/en/vps/hosting/servarica) — 179 $, [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) — 352 $, [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) — 564 $, [Timeweb Cloud](https://accsly.io/en/vps/hosting/timeweb-cloud) — 1,218 $

## Cheapest plans — 16 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Cloudy4 Web Services](https://accsly.io/en/vps/hosting/cloudy4) | GPU V100 16vCPU/128GB/500GB · GPU NVIDIA V100, 16 GB | 16 | 128 GB | 500 GB SSD | IN | Invoice | 115 $ |
| [ServaRica](https://accsly.io/en/vps/hosting/servarica) | V100 GPU Slice 1 - 1xV100 (32GB VRAM) · GPU NVIDIA Tesla V100, 32 GB | 8 | 35 GB | 400 GB NVMe | CA | PayPal, Visa/MC, Crypto, Invoice | 179 $ (when paying for year: 164 $/mo) |
| [Infinitive Host](https://accsly.io/en/vps/hosting/infinitivehost) | GPU MatrixX · GPU NVIDIA V100, 16 GB | 24 | 128 GB | 2 TB SSD | US | Visa/MC, Invoice | 352 $ |
| [ServaRica](https://accsly.io/en/vps/hosting/servarica) | V100 GPU Slice 2 - 2xV100 (64GB VRAM) · GPU NVIDIA Tesla V100 ×2, 32 GB | 16 | 70 GB | 800 GB NVMe | CA | PayPal, Visa/MC, Crypto, Invoice | 358 $ (when paying for year: 328 $/mo) |
| [ServaRica](https://accsly.io/en/vps/hosting/servarica) | V100 GPU Slice 3 - 3xV100 (96GB VRAM) · GPU NVIDIA Tesla V100 ×3, 32 GB | 24 | 105 GB | 1200 GB NVMe | CA | PayPal, Visa/MC, Crypto, Invoice | 537 $ (when paying for year: 492 $/mo) |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Public Cloud GPU t1-le-45 · GPU NVIDIA Tesla V100, 16 GB | 8 × 3.0 GHz | 45 GB | 300 GB NVMe | CA, DE, FR, GB, PL, US | PayPal, Visa/MC | 564 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Public Cloud GPU t2-le-45 · GPU NVIDIA Tesla V100S, 32 GB | 15 × 2.9 GHz | 45 GB | 300 GB NVMe | CA, DE, FR, GB, PL, US | PayPal, Visa/MC | 645 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Public Cloud GPU t1-le-90 · GPU NVIDIA Tesla V100 ×2, 16 GB | 16 × 3.0 GHz | 90 GB | 400 GB NVMe | CA, DE, FR, GB, PL, US | PayPal, Visa/MC | 1,128 $ |
| [Timeweb Cloud](https://accsly.io/en/vps/hosting/timeweb-cloud) | 2 x Intel Xeon Silver 4214 (24 ядра, 2.2-3.2 ГГц, 48 потоков) / 32 DDR4 / 960 Гб SSD + GPU Tesla V100 32GB · GPU NVIDIA Tesla V100, 32 GB | 24 × 2.2 GHz | 32 GB | 960 GB SSD | RU | MIR, Visa/MC, SBP, YooMoney, Invoice | 1,218 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Public Cloud GPU t2-le-90 · GPU NVIDIA Tesla V100S ×2, 32 GB | 30 × 2.9 GHz | 90 GB | 500 GB NVMe | CA, DE, FR, GB, PL, US | PayPal, Visa/MC | 1,289 $ |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC6s v3 · GPU NVIDIA Tesla V100 | 6 | 112 GB | — | AU, BR, CA, CH, FR, GB… | Visa/MC | 2,234 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Public Cloud GPU t1-le-180 · GPU NVIDIA Tesla V100 ×4, 16 GB | 32 × 3.0 GHz | 180 GB | 400 GB NVMe | CA, DE, FR, GB, PL, US | PayPal, Visa/MC | 2,257 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Public Cloud GPU t2-le-180 · GPU NVIDIA Tesla V100S ×4, 32 GB | 60 × 2.9 GHz | 180 GB | 500 GB NVMe | CA, DE, FR, GB, PL, US | PayPal, Visa/MC | 2,579 $ |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC6s v3 (West Europe) · GPU NVIDIA Tesla V100 | 6 | 112 GB | — | NL | Visa/MC | 2,791 $ |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC12s v3 · GPU NVIDIA Tesla V100 ×2 | 12 | 224 GB | — | AU, BR, CA, CH, FR, GB… | Visa/MC | 4,468 $ |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC12s v3 (West Europe) · GPU NVIDIA Tesla V100 ×2 | 12 | 224 GB | — | NL | Visa/MC | 5,582 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/gpu/v100?format=json

## Renting a server with an NVIDIA V100: when Volta still makes sense and which CUDA version to stay on

The NVIDIA V100 is a Volta-generation accelerator and NVIDIA's first data-centre card with Tensor Cores (640 of them). Its memory is HBM2 with 900 GB/s of bandwidth, in 16 or 32 GB. By 2026 standards it is a previous generation: it lacks the newer number formats and the latest CUDA releases no longer support it, yet in FP64 and in FP16 mixed precision the card still posts decent figures at a moderate price. As of 3 November 2026 the catalog lists 12 plans with the V100 and V100S from four providers: 10 cloud plans and 2 dedicated servers, almost all billed by the hour. Monthly prices start at about $350, with a median around $1,760. Configurations carry one, two or four cards; four plans state 16 GB per card, four state 32 GB and four do not state the size.

### What Volta lacks: BF16, TF32 and CUDA 13

Before renting a V100, check that your code does not depend on features that arrived later.

- **No BF16.** Many recent models are published in BF16. On a V100 you have to convert them to FP16 or FP32, and FP16 training needs loss scaling, otherwise gradients underflow to zero or overflow.
- **No TF32.** On Ampere and newer, ordinary FP32 matrix operations are automatically accelerated by Tensor Cores in TF32. The V100 has no such speed-up: FP32 runs on the regular cores at about 14–16 TFLOPS.
- **Compute capability 7.0.** Some current attention kernels and inference engines require 8.0 or higher, meaning Ampere. Check your libraries' documentation for the minimum architecture.
- **CUDA 13 no longer supports Volta.** In CUDA 13.0 NVIDIA removed support for Volta along with Maxwell and Pascal: the new toolkit cannot build code for these cards.

Hence the practical rule: on a V100, stay on CUDA 12.x. Use base Docker images with CUDA 12 and PyTorch builds made for CUDA 12, not 13. If the provider ships an image with a newer driver, that is fine, since the driver is backward compatible, but the toolkit inside the container and the framework version must come from the 12 branch. Pin versions in requirements or the Dockerfile so that the next dependency update does not pull in a build that will not start on Volta.

### When a V100 is a sensible choice

1. **Double-precision scientific calculations.** The V100 delivers about 7–8 TFLOPS of FP64, a legacy of the HPC line. Molecular dynamics, computational fluid dynamics and double-precision linear algebra run well on it, while most inference and graphics cards have FP64 cut down by a factor of dozens.
2. **Legacy training code.** A project written for CUDA 10–12 and FP16 mixed precision runs on a V100 as is. Porting it to new cards for a one-off retraining is not always worth it.
3. **Affordable mixed precision.** The Tensor Cores give 112–130 TFLOPS in FP16. That is enough to train convolutional networks, speech recognition models and small transformers, provided the code already works in FP16.
4. **Inference of models up to 32 GB.** Fast 900 GB/s HBM2 helps text generation: a 32 GB card holds a model of about 13B parameters in FP16.

When a V100 is the wrong fit: if you need BF16, FP8, current inference engines or CUDA 13, go straight to the [A100](https://accsly.io/en/gpu/a100), which also has HBM and NVLink but brings the Ampere generation with all its formats. For inference of mid-size models with no FP64 requirement, the [L4](https://accsly.io/en/gpu/l4) is often cheaper.

### PCIe, SXM2 or V100S: which card the plan has

The V100 name covers three variants, and plans label them in different ways.

- **V100 PCIe.** A regular card in a PCIe Gen3 slot (32 GB/s), 250 W. About 7 TFLOPS FP64, 14 FP32, 112 on the Tensor Cores. In a multi-card server the cards exchange data over the bus.
- **V100 SXM2.** A module on a dedicated board, 300 W, slightly higher clocks: 7.8 FP64, 15.7 FP32, 125 TFLOPS on the Tensor Cores. The main difference is NVLink at up to 300 GB/s between cards, almost ten times faster than the PCIe Gen3 bus. For four-card training with gradient exchange, that is the deciding advantage.
- **V100S PCIe.** The refreshed version: 32 GB HBM2 at 1134 GB/s, 8.2 FP64, 16.4 FP32 and 130 TFLOPS on the Tensor Cores at the same 250 W. The fastest single V100.

16 or 32 GB is the second key question. 16 GB is enough for convolutional networks, speech recognition and models of a few billion parameters. For larger transformers, long sequences and big training batches, take 32 GB: the price gap is usually smaller than the time lost to splitting batches.

### How to check what you got

A third of the plans in the catalog do not state the memory size, so verify the configuration right after the server is delivered:

- **nvidia-smi** shows the card name: it contains PCIE or SXM2, and the refreshed version reads V100S. It also shows the memory size (16 or 32 GB) and the power limit: 300 W points to SXM2, 250 W to PCIe.
- **nvidia-smi topo -m** prints the matrix of links between cards. Entries such as NV1 or NV2 mean NVLink, while PIX, PHB or SYS mean traffic goes over PCIe and the CPU.
- **Versions.** Check the driver and CUDA versions, then confirm in Python that torch.cuda sees all cards and that the framework build targets CUDA 12.

Almost all V100 plans are billed by the hour, which makes it easy to run these checks and a short performance test before a multi-day training run. How to calculate such costs is covered in our note on [hourly billing](https://accsly.io/en/vps/hourly-billing). If a calculation runs for weeks without a break, compare the total with monthly rental in the [dedicated GPU servers](https://accsly.io/en/gpu/dedicated) section. When the data includes personal information of EU residents, keep GDPR in mind when picking the data centre country.

## FAQ

### Does the V100 support CUDA 13?

No. In CUDA 13.0 NVIDIA removed support for the Volta architecture. On a V100, use CUDA 12.x and framework builds for CUDA 12.

### Does the V100 have BF16 and TF32?

No, these formats arrived with the Ampere generation. On a V100, training runs in FP16 mixed precision with loss scaling, or in plain FP32.

### How does the V100 SXM2 differ from the PCIe version?

The SXM2 draws 300 W, runs slightly faster and links cards through NVLink at up to 300 GB/s. The PCIe version is rated at 250 W, and cards exchange data over the 32 GB/s PCIe Gen3 bus.

### What is the V100S?

A refreshed PCIe version of the V100 with 32 GB of HBM2 and 1134 GB/s of memory bandwidth instead of 900. It is slightly faster in FP64, FP32 and on the Tensor Cores at the same 250 W.

### How do I find out how much memory the V100 in a plan has?

If the table does not state it, ask the provider before paying. After delivery, nvidia-smi shows the card name with its size, for example V100-PCIE-16GB or V100-SXM2-32GB.

### What is a V100 good for in 2026?

FP64 scientific calculations, legacy training code on CUDA 12 and FP16 mixed-precision training. For new BF16 models and current inference engines, an A100 or newer is the better choice.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# GPU servers with NVIDIA A10

Servers with NVIDIA A10 (24 GB) for inference of models up to 13B parameters, graphics and virtual desktops. Compare card count, CPU and price; cheapest first.

> Source: https://accsly.io/en/gpu/a10 · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 14, hosts: 1
- Price: from 331 $, a quarter below 803 $, median 1,518 $
- NVMe: 0 %, unlimited traffic: 0 %, hourly billing: 100 %
- RAM → price from: 1 GB — 331 $, 2 GB — 331 $, 4 GB — 331 $, 8 GB — 331 $, 16 GB — 331 $
- Countries: USA (9), Netherlands (8), UAE (6), Australia (6), Brazil (6), Canada (6)
- Cheapest hosts: [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) — 331 $

## Cheapest plans — 14 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NV6adsv5 · GPU NVIDIA A10 | 6 | 55 GB | — | AE, AU, BR, CA, CH, DE… | Visa/MC | 331 $ (when paying for 3 years: 146 $/mo) |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NV6adsv5 (West Europe) · GPU NVIDIA A10 | 6 | 55 GB | — | NL | Visa/MC | 431 $ (when paying for 3 years: 190 $/mo) |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NV12ads A10 v5 · GPU NVIDIA A10 | 12 | 110 GB | — | AE, AU, BR, CA, CH, DE… | Visa/MC | 663 $ (when paying for 3 years: 292 $/mo) |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC8ads A10 v4 · GPU NVIDIA A10 | 8 | 110 GB | — | NL, US | Visa/MC | 803 $ (when paying for 3 years: 321 $/mo) |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NV12ads A10 v5 (West Europe) · GPU NVIDIA A10 | 12 | 110 GB | — | NL | Visa/MC | 861 $ (when paying for 3 years: 379 $/mo) |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NV18ads A10 v5 · GPU NVIDIA A10 | 18 | 220 GB | — | AE, AU, BR, CA, CH, DE… | Visa/MC | 1,168 $ (when paying for 3 years: 514 $/mo) |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NV18ads A10 v5 (West Europe) · GPU NVIDIA A10 | 18 | 220 GB | — | NL | Visa/MC | 1,518 $ (when paying for 3 years: 668 $/mo) |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC16ads A10 v4 · GPU NVIDIA A10, 24 GB | 16 | 220 GB | — | NL, US | Visa/MC | 1,606 $ (when paying for 3 years: 642 $/mo) |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NV36ads A10 v5 · GPU NVIDIA A10, 24 GB | 36 | 440 GB | — | AE, AU, BR, CA, CH, DE… | Visa/MC | 2,336 $ (when paying for 3 years: 1,028 $/mo) |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NV36ads A10 v5 (West Europe) · GPU NVIDIA A10, 24 GB | 36 | 440 GB | — | NL | Visa/MC | 3,037 $ (when paying for 3 years: 1,336 $/mo) |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NC32ads A10 v4 · GPU NVIDIA A10 ×2, 24 GB | 32 | 440 GB | — | NL, US | Visa/MC | 3,212 $ (when paying for 3 years: 1,285 $/mo) |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NV36adms A10 v5 · GPU NVIDIA A10, 24 GB | 36 | 880 GB | — | AE, AU, BR, CA, CH, DE… | Visa/MC | 3,300 $ (when paying for 3 years: 1,452 $/mo) |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NV36adms A10 v5 (West Europe) · GPU NVIDIA A10, 24 GB | 36 | 880 GB | — | NL | Visa/MC | 4,289 $ (when paying for 3 years: 1,887 $/mo) |
| [Microsoft Azure](https://accsly.io/en/vps/hosting/azure-microsoft) | NV72ads A10 v5 · GPU NVIDIA A10 ×2, 24 GB | 72 | 880 GB | — | AE, AU, BR, CA, CH, DE… | Visa/MC | 4,760 $ (when paying for 3 years: 2,094 $/mo) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/gpu/a10?format=json

## Renting a server with an NVIDIA A10: what fits in 24 GB and how to tell a slice from a full card

The NVIDIA A10 is an Ampere-generation card with 24 GB of GDDR6 memory and a 150 W power draw. It takes a single PCIe 4.0 slot, so cloud platforms pack it densely and like to share it between virtual machines. The A10 is built for inference, graphics and video rather than training large models: it has Tensor Cores with BF16 and TF32 support, RT cores for ray tracing and hardware NVENC/NVDEC codecs. The table above holds only cloud plans billed by the hour, from a single card up to ×4 builds; the monthly price runs from roughly $330 to $6,200, with a median around $1,600.

### What fits in 24 GB

Use the rule of thumb: in FP16 a model takes about 2 GB per billion parameters, in 8-bit quantization about 1 GB, in 4-bit 0.5–0.6 GB. On top of that you need headroom for the KV cache, which grows with context length and the number of concurrent requests.

- **7–8B parameters in FP16.** The weights take 14–16 GB, leaving room for context and several parallel requests. This is the main reason people rent an A10: a chatbot, ticket classification, data extraction from documents.
- **13B in 8-bit.** About 13–14 GB for the weights, with quality close to full precision.
- **Around 30B in 4-bit.** It fits, but only with a short context and one or two users: little memory is left for the KV cache.
- **Fine-tuning.** Full fine-tuning of even a 7B model will not fit on one card, but QLoRA for a 7B model runs fine. The A10 is not meant for training from scratch.
- **Images, graphics, video.** SDXL runs with memory to spare. RT cores make the A10 a good fit for remote graphics workstations, CAD and rendering with streamed output, and NVENC/NVDEC for transcoding video into several qualities at once.

### A slice of the card or a full A10

Some cloud plans give you not the whole card but a share of it through NVIDIA virtual GPU software: 1/6, 1/3 or 1/2 with the matching part of the memory, that is 4, 8 or 12 GB. The A10 has no MIG, so the compute units are time-shared with neighbours while the memory is hard-assigned to each virtual machine. Such slices are most likely the rows at the top of the table. They are easy to spot:

- the video memory column shows less than 24 GB;
- the plan has few vCPUs and little RAM, a handful of cores instead of the dozens that come with a full card;
- on the server, nvidia-smi names the card with a profile suffix such as A10-4Q rather than just A10.

A slice is enough for a virtual desktop with 3D applications, light inference (embeddings, speech recognition, a 7B model in 4-bit on 8 GB) and a trial run before renting a full card. You need the whole A10 when the model takes more than 12 GB, when response latency must stay steady regardless of neighbours, or when you fine-tune.

### Multiple cards, drivers and CUDA

The A10 has no NVLink: in ×2 and ×4 plans the cards exchange data over PCIe 4.0. For inference that is acceptable. vLLM and similar engines split a model across cards, so a ×2 plan (48 GB) holds a model of about 30B parameters in 8-bit and a ×4 plan (96 GB) holds a 70B model in 4-bit with room for context. Another mode often pays off better: run a separate copy of a 7–8B model on each card and balance requests between them. For training large models across several cards without NVLink, the A10 falls behind.

The A10 has compute capability 8.6. The architecture is supported from CUDA 11.1 onward, and CUDA 12 and current PyTorch builds need a driver from the 525 branch or newer. On card slices the virtual machine runs a vGPU guest driver that must match the branch of the host driver: a regular driver from the NVIDIA website may not work there, so use the provider's image and do not update the driver yourself. Right after delivery, check nvidia-smi: card model and profile, memory size, driver and CUDA versions.

### Hourly billing and how the A10 compares with the L4 and A100

Every A10 plan in the catalog is billed by the hour. The median plan works out to roughly $2.20 per hour of uptime, the cheapest slice to about $0.45. Hourly A10 server rental pays off when you need the card for an evening, a batch job or a test week: delete the server and charges stop. The pitfalls are covered in our note on [hourly billing](https://accsly.io/en/vps/hourly-billing). If a GPU server with an A10 stays busy around the clock for months, compare the total with a monthly physical machine in the [dedicated GPU servers](https://accsly.io/en/gpu/dedicated) section. For data about people in the EU, also check the data centre country because of GDPR, and pick a location close to your users to keep latency low.

The closest alternative is the [NVIDIA L4](https://accsly.io/en/gpu/l4): the same 24 GB, Ada generation, about 72 W and FP8 support. The A10 has twice the memory bandwidth (600 GB/s versus 300), so in text generation, where speed is bound by memory, the A10 is usually faster while the L4 is more power-efficient. The [A100](https://accsly.io/en/gpu/a100), with 40 or 80 GB of fast memory, NVLink and MIG, is the choice when a model does not fit into 24 GB or you run full training; it costs noticeably more.

## FAQ

### Which language models can run on an A10?

A single 24 GB card handles 7–8B models in FP16, 13B in 8-bit quantization and about 30B in 4-bit with a short context. A 70B model needs a ×4 plan or a card with more memory.

### How can I tell that a plan offers a slice of an A10 rather than the whole card?

The video memory column shows less than 24 GB (usually 4, 8 or 12 GB), and the plan has far fewer vCPUs and less RAM than full-card plans. On the server itself nvidia-smi shows a vGPU profile such as A10-8Q.

### Does the A10 support MIG and NVLink?

No. The card is shared between virtual machines with NVIDIA vGPU software, and in ×2 and ×4 plans the cards are linked only through the PCIe 4.0 bus.

### Can I fine-tune models on an A10?

Yes, QLoRA for a 7B model runs fine on a single card. Full training of large models is better done on an A100 or H100.

### A10 or L4 for inference?

Both have 24 GB. The A10 usually generates text faster thanks to twice the memory bandwidth, while the L4 draws less power and supports FP8.

### Which CUDA version does the A10 need?

The A10 has compute capability 8.6, supported from CUDA 11.1 onward; CUDA 12 needs a driver from the 525 branch or newer. On card slices use the driver from the provider's image, since it must match the host driver.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# Dedicated servers

Rent a whole physical server: the CPU, memory and disks are yours alone, shared with no one. Compare the processor, cores, memory, disks and port speed; cheapest first.

> Source: https://accsly.io/en/dedicated · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 7,016, hosts: 199
- Price: from 4.00 $, a quarter below 149 $, median 249 $
- NVMe: 25 %, unlimited traffic: 31 %, hourly billing: 14 %
- RAM → price from: 1 GB — 4.00 $, 2 GB — 4.00 $, 4 GB — 4.00 $, 8 GB — 5.58 $, 16 GB — 16.00 $
- Countries: USA (1452), Germany (1024), Netherlands (758), Russia (694), France (570), United Kingdom (504)
- Cheapest hosts: [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) — 4.00 $, [Scaleway](https://accsly.io/en/vps/hosting/scaleway) — 5.58 $, [it4int](https://accsly.io/en/vps/hosting/it4int) — 16.00 $, [DigitalBerg.com](https://accsly.io/en/vps/hosting/digitalberg) — 17.41 $, [PebbleHost](https://accsly.io/en/vps/hosting/pebblehost) — 19.99 $

## Cheapest plans — 7,016 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Dedicated Server 11 Duckney | 2 × 2.2 GHz | 4 GB | 32 GB SSD | US | Crypto | 4.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Dedicated Server 2 Goze | 2 × 2.5 GHz | 4 GB | 16 GB SSD | US | Crypto | 4.00 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-1-M-SATA | 8 × 2.4 GHz | 8 GB | 1 TB HDD | FR | — | 5.58 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-2-S-SATA | 2 × 1.7 GHz | 4 GB | 1 TB HDD | NL, FR | — | 5.58 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-2-S-SSD | 2 × 1.7 GHz | 4 GB | 120 GB SSD | NL, FR | — | 5.58 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-3-S-SSD | 2 × 1.7 GHz | 4 GB | 250 GB SSD | FR | — | 5.58 $ (when paying for year: 5.31 $/mo) |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Dedicated Server 3 Crossport | 2 × 2.4 GHz | 4 GB | 64 GB SSD | US | Crypto | 6.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Dedicated Server 10 Resativa | 4 × 1.9 GHz | 4 GB | 64 GB SSD | US | Crypto | 6.51 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Dedicated Server 13 Resativa | 2 × 2.8 GHz | 4 GB | 256 GB SSD | US | Crypto | 8.00 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-1-M-SSD | 8 × 2.4 GHz | 8 GB | 120 GB SSD | FR | — | 15.66 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-1-M-SSD-160G | 8 × 2.4 GHz | 8 GB | 160 GB SSD | FR | — | 15.66 $ |
| [it4int](https://accsly.io/en/vps/hosting/it4int) | Popular Plan Category — E3-1230 v5 - 3.40 GHz | 4 | 32 GB | 250 GB SSD | US | PayPal, Crypto | 16.00 $ |
| [DigitalBerg.com](https://accsly.io/en/vps/hosting/digitalberg) | Intel Core2Duo Preconfigured | 2 × 1.6 GHz | 4 GB | 250 GB SSD | US | PayPal, Visa/MC | 17.41 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-2-M-SATA | 8 × 2.4 GHz | 16 GB | 1 TB HDD | NL, FR | — | 17.89 $ (when paying for year: 17.01 $/mo) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-2-M-SSD | 8 × 2.4 GHz | 16 GB | 250 GB SSD | NL, FR | — | 17.89 $ (when paying for year: 17.01 $/mo) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | EM-RV1-C4M16S128-A | 4 × 1.9 GHz | 16 GB | 128 GB SSD | FR | — | 17.89 $ |
| [PebbleHost](https://accsly.io/en/vps/hosting/pebblehost) | Value-01 | 2 | 8 GB | 240 GB SSD | GB | PayPal, Visa/MC | 19.99 $ (when paying for year: 15.99 $/mo) |
| [Gen X Web Hosting](https://accsly.io/en/vps/hosting/genxwhosting) | Linux Dedicated Starter 1 | 2 × 1.7 GHz | 4 GB | 1 TB HDD | IN, US, SG, GB, AU, DE | — | 20.91 $ (yearly: 20.91 $/mo) |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Kimsufi KS-3 | 4 × 3.5 GHz | 32 GB | 4 TB HDD | AU, CA, DE, FR, GB, PL… | PayPal, Visa/MC | 21.26 $ (when paying for 2 years: 20.19 $/mo) |
| [DigitalBerg.com](https://accsly.io/en/vps/hosting/digitalberg) | Mercury | 2 × 1.6 GHz | 4 GB | 250 GB SSD |  | PayPal, Visa/MC | 21.44 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/dedicated?format=json

## Renting a dedicated server: when you need one and how to read a plan

A dedicated server is a whole physical machine that a host gives to a single customer. The processor, memory, disks and network port are not shared with neighbours, and you get full access to the hardware: you can install any operating system or hypervisor, or build your own RAID. The table above lists plans with the exact CPU model, core count, memory, disks and port speed, so configurations from different hosts can be compared directly.

### When a dedicated server beats a VPS

A virtual server is cheaper and more flexible, but it has a ceiling: the resources of the physical host are shared between customers, and when neighbours are busy your server slows down too. Dedicated server hosting pays off in a few cases.

- **Steady heavy load.** If the processor runs above half capacity around the clock, a large VPS usually costs about as much as a physical machine, while the machine performs more consistently.
- **Databases and disk-heavy work.** A large PostgreSQL, MySQL or ClickHouse instance is limited by disk latency, and local NVMe without a virtualization layer gives predictable response times. Plans for this task are collected on the [VPS for databases](https://accsly.io/en/vps/for-database) page.
- **Licences per physical CPU.** Some server software is licensed per socket or per physical core, and counting them is simpler and often cheaper on your own hardware.
- **Isolation and compliance.** When a security team or an auditor requires that data does not sit on a shared hypervisor, a dedicated server settles the question. Under GDPR it also makes it easier to document where personal data is stored and who has access to the hardware.

### Processor, memory and disks

The CPU model in a plan matters more than the core count. Older Xeon E3 and E5 chips appear in the cheapest offers: the E5 has many cores, but clock speed and per-core performance are noticeably lower than on current chips. AMD EPYC is built for multi-threaded load and large amounts of memory, while Ryzen offers high clock speeds and suits game servers and single-threaded tasks. You can compare them on the [AMD EPYC VPS](https://accsly.io/en/vps/epyc) and [Ryzen VPS](https://accsly.io/en/vps/ryzen) pages; game hosting configurations are on the [game server](https://accsly.io/en/vps/for-game-server) page.

Check whether a plan lists cores or threads: eight cores with Hyper-Threading give sixteen threads, but do not double performance. A server that holds data needs ECC memory, which corrects single-bit errors that on ordinary memory silently corrupt files and databases. Ryzen in budget plans often comes without ECC, so it is worth asking.

"2×1 TB NVMe" means two separate disks, not one 2 TB disk. In a RAID 1 mirror 1 TB stays usable, but the failure of one disk does not stop the server. NVMe is several times faster than SATA SSD on random operations, while HDD remains an option for backups and archives where capacity matters most.

### Network, traffic and hidden terms

- **Port speed vs guaranteed bandwidth.** A 1 Gbps port does not always mean a gigabit at any time: some hosts guarantee less and provide the rest on a best-effort basis.
- **Traffic limits.** Unlimited traffic on a 100 Mbps port and 20 TB on a gigabit port are different terms. Check what happens when you exceed the limit: a charge per terabyte or a speed cap.
- **Extra IP addresses** usually cost extra, and a subnet sometimes requires a justification.
- **Setup fee.** Some hosts charge a one-off fee to prepare the server, especially with monthly billing. Compare the total for the first year, not just the monthly price.
- **Delivery time.** Ready configurations are handed over within a few hours; custom builds take from one to several days.
- **KVM or IPMI.** A remote console lets you reinstall the system and fix boot problems without contacting support. Without it, any mistake in the network settings turns into a ticket.
- **Hardware replacement.** Ask how many hours it takes to replace a failed disk or power supply and whether that is included in the price.

### Renting vs colocation

With colocation you buy the server yourself and pay the data centre for rack space, power and bandwidth. It pays off over several years and with non-standard hardware, but repairs, spare parts and shipping are on you. Renting removes these questions: the hardware belongs to the host, and the host is responsible for replacing components. For one or two servers, renting is almost always simpler.

### Location and payment

Put the server close to your users. Within Europe, Germany and the Netherlands reach most capitals in 10–30 ms; between the US east coast and Western Europe expect around 80 ms, and Asia adds 150–250 ms from either side. That gap is noticeable in games and interactive services, but does not matter for backups and batch computing. Before renting, ask the host for a test IP and check latency and download speed from your side. If a share of a machine is enough, compare configurations in the [VPS catalog](https://accsly.io/en/vps), and for a simple website without server administration look at [shared hosting](https://accsly.io/en/hosting). Payment methods depend on the host: most accept cards, many take PayPal, business customers can usually pay by invoice, and some also accept cryptocurrency. The "Payment" column in the table shows the methods for each plan.

## FAQ

### How is a dedicated server different from a VPS?

A VPS is a virtual machine on a shared physical server whose resources are split between customers. A dedicated server belongs entirely to one customer, so its performance does not depend on neighbours.

### Which is better for a server: EPYC, Ryzen or Xeon?

EPYC suits multi-threaded load and large amounts of memory, Ryzen suits tasks where high per-core clock speed matters. Older Xeon E3 and E5 chips are cheaper but slower per core and fit undemanding workloads.

### Do I need ECC memory?

For databases, file storage and anything where data integrity matters, yes. ECC corrects single-bit memory errors that would otherwise silently damage files.

### How quickly is a dedicated server delivered?

Ready configurations are usually handed over within a few hours of payment. If the server is built to order, it can take several days.

### What is IPMI and why do I need it?

IPMI is a hardware-level remote management interface: console, reboot, mounting an image to install a system. It lets you regain access to the server without visiting the data centre or opening a support ticket.

### Who replaces a disk if it fails?

When you rent, the host is responsible for the replacement, usually free of charge and within the time stated in the terms. With colocation, the server owner buys and installs the parts.

### Is a dedicated server in the EU subject to GDPR?

The host in the EU operates under GDPR, and if you process personal data of people in the EU, the regulation applies to you as the controller wherever the server stands. Hosting inside the EU simply makes data transfers easier to document.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# Dedicated servers with Windows

Physical servers on which the host installs Windows Server, for RDP, business applications, MS SQL and Hyper-V. Hosts charge for the licence by processor core count, so check the total price with Windows before ordering. Cheapest first.

> Source: https://accsly.io/en/dedicated/windows · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 6,097, hosts: 145
- Price: from 4.00 $, a quarter below 151 $, median 251 $
- NVMe: 26 %, unlimited traffic: 32 %, hourly billing: 15 %
- RAM → price from: 1 GB — 4.00 $, 2 GB — 4.00 $, 4 GB — 4.00 $, 8 GB — 16.00 $, 16 GB — 16.00 $
- Countries: USA (1169), Germany (919), Russia (626), Netherlands (606), France (499), Canada (447)
- Cheapest hosts: [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) — 4.00 $, [it4int](https://accsly.io/en/vps/hosting/it4int) — 16.00 $, [PebbleHost](https://accsly.io/en/vps/hosting/pebblehost) — 19.99 $, [Gen X Web Hosting](https://accsly.io/en/vps/hosting/genxwhosting) — 20.91 $, [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) — 21.26 $

## Cheapest plans — 6,097 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Dedicated Server 2 Goze | 2 × 2.5 GHz | 4 GB | 16 GB SSD | US | Crypto | 4.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Dedicated Server 3 Crossport | 2 × 2.4 GHz | 4 GB | 64 GB SSD | US | Crypto | 6.00 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Dedicated Server 10 Resativa | 4 × 1.9 GHz | 4 GB | 64 GB SSD | US | Crypto | 6.51 $ |
| [ELECTROHAXZ Hosting](https://accsly.io/en/vps/hosting/electrohaxz) | Dedicated Server 13 Resativa | 2 × 2.8 GHz | 4 GB | 256 GB SSD | US | Crypto | 8.00 $ |
| [it4int](https://accsly.io/en/vps/hosting/it4int) | Popular Plan Category — E3-1230 v5 - 3.40 GHz | 4 | 32 GB | 250 GB SSD | US | PayPal, Crypto | 16.00 $ |
| [PebbleHost](https://accsly.io/en/vps/hosting/pebblehost) | Value-01 | 2 | 8 GB | 240 GB SSD | GB | PayPal, Visa/MC | 19.99 $ (when paying for year: 15.99 $/mo) |
| [Gen X Web Hosting](https://accsly.io/en/vps/hosting/genxwhosting) | Linux Dedicated Starter 1 | 2 × 1.7 GHz | 4 GB | 1 TB HDD | IN, US, SG, GB, AU, DE | — | 20.91 $ (yearly: 20.91 $/mo) |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Kimsufi KS-3 | 4 × 3.5 GHz | 32 GB | 4 TB HDD | AU, CA, DE, FR, GB, PL… | PayPal, Visa/MC | 21.26 $ (when paying for 2 years: 20.19 $/mo) |
| [DigitalBerg.com](https://accsly.io/en/vps/hosting/digitalberg) | Mercury | 2 × 1.6 GHz | 4 GB | 250 GB SSD |  | PayPal, Visa/MC | 21.44 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Kimsufi KS-4 | 4 × 3.5 GHz | 32 GB | 4 TB HDD | AU, CA, DE, FR, GB, PL… | PayPal, Visa/MC | 23.49 $ (when paying for 2 years: 22.31 $/mo) |
| [Premiumtechs.uk](https://accsly.io/en/vps/hosting/premiumtechs) | Dedicated Plan-I | 2 × 3.4 GHz | 8 GB | 2 TB HDD | DE, RU, FR, NL, BG, CA… | Visa/MC, PayPal, Invoice | 24.00 $ |
| [PebbleHost](https://accsly.io/en/vps/hosting/pebblehost) | Essential-01 | 4 | 16 GB | 240 GB SSD | GB | PayPal, Visa/MC | 24.99 $ (when paying for year: 19.99 $/mo) |
| [DigitalBerg.com](https://accsly.io/en/vps/hosting/digitalberg) | Dual Xeon 5150 Hybrid Storage Dedicated Server USA | 4 × 2.7 GHz | 16 GB | 1120 GB SSD | US | PayPal, Visa/MC | 25.45 $ |
| [server.ir](https://accsly.io/en/vps/hosting/server-ir) | ODS B2350SD1 | 2 × 1.7 GHz | 4 GB | 128 GB SSD | NL | Invoice | 27.58 $ (yearly: 27.58 $/mo) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-2-L | 6 × 2.2 GHz | 32 GB | 500 GB SSD | FR | — | 27.97 $ (when paying for year: 26.57 $/mo) |
| [SteadyHost](https://accsly.io/en/vps/hosting/steadyhost) | Xeon E3-1220 8GB 1x1000GB (NL-AMS) | 4 × 3.1 GHz | 8 GB | 1 TB HDD | NL | Visa/MC, PayPal, WebMoney, Crypto | 29.00 $ |
| [SteadyHost](https://accsly.io/en/vps/hosting/steadyhost) | Xeon G530 2GB 2x500GB (DE-FRA) | 2 × 2.4 GHz | 2 GB | 1 TB HDD | DE | Visa/MC, PayPal, WebMoney, Crypto | 29.00 $ |
| [DigitalBerg.com](https://accsly.io/en/vps/hosting/digitalberg) | I3-3220 2TB Preconfigured | 2 × 3.3 GHz | 16 GB | 2 TB SSD | US | PayPal, Visa/MC | 29.47 $ |
| [DigitalBerg.com](https://accsly.io/en/vps/hosting/digitalberg) | Intel i5-750 Dedicated Server USA | 4 × 2.7 GHz | 16 GB | 500 GB SSD | US | PayPal, Visa/MC | 32.15 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Kimsufi KS-GAME | 4 × 4.2 GHz | 32 GB | 900 GB NVMe | AU, CA, DE, FR, GB, PL… | PayPal, Visa/MC | 32.45 $ (when paying for 2 years: 30.83 $/mo) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/dedicated/windows?format=json

## A dedicated server with Windows: the host’s licence or your own, and what to check before ordering

Most hosts allow Windows Server on a dedicated server, so the real question is not "where is it allowed" but how the licence is billed and how much it adds to the price. As of 7 November 2026 the selection holds 4,457 plans from 102 hosts, 86 % of all dedicated servers in stock. The median is about $252 a month, a quarter of the plans cost less than $158, and a quarter more than $458. Most offers are in the US, Germany and Russia, followed by Canada and France.

### The licence is counted by cores

Windows Server is licensed by the physical cores of the server. A host provides Windows under Microsoft's Services Provider License Agreement (SPLA) and pays for it monthly: every core of the machine has to be licensed, with a minimum of eight per processor. That is why the cost of Windows grows with the processor: on a server with 32 cores it is several times higher than on one with eight.

For a sense of scale, here is the published price list of one of the large European hosts (excluding VAT): Windows Server Standard costs about €28 a month for a server with up to 8 cores, about €56 for 16 cores and about €112 for 32 cores. Datacenter costs six times as much: about €173 for 8 cores and €347 for 16. Other hosts charge a fixed amount for the first 8 cores plus a surcharge for every additional two.

In the catalog, no dedicated plan has the licence marked as included in the price. Among VPS such plans exist, and the "Windows included" toggle in the [Windows VPS](https://accsly.io/en/vps/windows) selection shows them. For a dedicated server, assume that a Windows fee will be added to the price in the table unless the host explicitly states otherwise.

### Standard, Datacenter or your own licence

- **Standard from the host** allows, under SPLA terms, one virtual machine on top of a server running the Hyper-V role. For RDP, 1C (a popular Russian accounting suite), MS SQL and software that runs directly on the server, that is enough.
- **Datacenter** allows any number of Windows virtual machines on that server. You need it if you split the server into Hyper-V machines: on 16 cores the licence can cost more than the server itself, so do the maths in advance. Hardware requirements for virtualization are covered in the [servers for virtualization](https://accsly.io/en/dedicated/for-virtualization) selection.
- **Your own licence.** Microsoft's 2019 restrictions apply to dedicated servers from Amazon, Google, Alibaba and Microsoft itself. With other hosts, a licence bought by your company can be installed on a dedicated server rented by you alone. All physical cores must be licensed, with a minimum of 16 per server and 8 per processor. Ask the host whether you can install Windows with your own key and whether their licence will still be charged on top.

### RDP, 1C and MS SQL

Without additional licences, Windows Server allows two administrators to connect over RDP at the same time. If employees work on the server, each user needs a Remote Desktop Services (RDS) licence: from the host it is rented monthly, or you buy your own separately. Without licences a terminal server runs for a 120-day grace period, after which new connections are refused. For small tasks without an office full of users, see [RDP servers on VPS](https://accsly.io/en/vps/rdp).

MS SQL Server is also licensed by cores, with a minimum of four per processor; hosts provide it under SPLA in two-core packs. The free SQL Server Express is limited to a 10 GB database (50 GB in the 2025 version), 1.4 GB of memory for the buffer pool and four cores. Standard 2025 uses up to 32 cores and 256 GB of buffer pool memory, the 2022 version up to 24 cores and 128 GB. If nothing else runs on the server, there is no point taking a bigger machine for SQL Standard.

Because Windows, 1C and MS SQL are licensed per core, eight fast cores pay off better than 32 slow ones: licences for every extra core are paid each month, and a 1C server and database queries are more often limited by clock speed than by core count. Such processors are collected in the [servers with 4 GHz or more](https://accsly.io/en/dedicated/high-frequency) selection; for VPS options, see VPS for 1C.

### How many resources Windows Server needs

The system itself is undemanding: Microsoft specifies a 1.4 GHz processor, 2 GB of memory for the Desktop Experience installation (4 GB recommended for Windows Server 2025) and at least 32 GB of disk. On a dedicated server these minimums are covered with plenty to spare: the selection's median is 64 GB of memory and eight cores, and 58 % of the plans have no more than eight cores. Choose memory and cores for the load: the number of RDP users, the size of the database, the number of virtual machines. Take SSD or NVMe for the system and databases: on hard disks Windows boots and updates noticeably slower, and HDD is fitted in a third of the plans in the selection.

### What to check before ordering

- **What the licence costs on this server.** Ask for the total price with Windows for the specific processor model, not a "from" price.
- **Which version.** Specific versions are listed in the OS templates of roughly a quarter of the plans, most often 2022 and 2019. Extended support for Windows Server 2016 ends on 12 January 2027, for 2019 on 9 January 2029, and for 2022 on 14 October 2031. For a new server, 2022 or 2025 is the sensible choice.
- **Remote console.** If RDP stops responding after an update or a firewall misconfiguration, the only way back in is the server console (IPMI, iDRAC, iLO). Check whether the host gives customers access to it.
- **RDS and SQL licences.** How much they cost from the host and whether you can bring your own.

## FAQ

### Is the Windows licence included in the price of a dedicated server?

It depends on the host: it is often added as a separate line item and calculated by the number of cores. In the catalog no dedicated plan has the licence marked as included, so check the total price with Windows before ordering.

### Why does Windows cost more on a server with many cores?

The host licenses Windows Server by physical cores, with a minimum of eight per processor. The more cores, the more licences it pays for every month.

### What is the difference between Windows Server Standard and Datacenter?

The features are almost the same, and both include Hyper-V. The difference is the right to run virtual machines: Standard from the host allows one, Datacenter allows any number on that server.

### Can I install my own Windows licence on a rented server?

Yes, if the server is dedicated to you alone and the host is not Amazon, Google, Alibaba or Microsoft. All physical cores must be licensed, with a minimum of 16 per server; ask the host in advance whether it allows installation with your own key.

### How many people can work on the server over RDP?

Without additional licences, two simultaneous sessions for administration. Employees need an RDS licence for each user; without it a terminal server works for 120 days.

### Which version of Windows Server should I choose?

For a new server, 2022 or 2025. Extended support for Windows Server 2016 ends in January 2027, after which there will be no more security updates.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# Dedicated servers with Intel Xeon

Physical servers with Intel Xeon, from affordable older E3 and E5 chips to dual-socket Xeon Gold and Platinum; ECC memory. Compare the CPU model, cores, memory and disks; cheapest first.

> Source: https://accsly.io/en/dedicated/xeon · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 4,582, hosts: 158
- Price: from 19.99 $, a quarter below 148 $, median 242 $
- NVMe: 11 %, unlimited traffic: 26 %, hourly billing: 13 %
- RAM → price from: 1 GB — 19.99 $, 2 GB — 19.99 $, 4 GB — 19.99 $, 8 GB — 19.99 $, 16 GB — 21.26 $
- Countries: USA (1044), Russia (530), Netherlands (513), Germany (421), France (317), Canada (315)
- Cheapest hosts: [PebbleHost](https://accsly.io/en/vps/hosting/pebblehost) — 19.99 $, [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) — 21.26 $, [Scaleway](https://accsly.io/en/vps/hosting/scaleway) — 22.37 $, [DigitalBerg.com](https://accsly.io/en/vps/hosting/digitalberg) — 25.45 $, [SteadyHost](https://accsly.io/en/vps/hosting/steadyhost) — 29.00 $

## Cheapest plans — 4,582 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [PebbleHost](https://accsly.io/en/vps/hosting/pebblehost) | Value-01 | 2 | 8 GB | 240 GB SSD | GB | PayPal, Visa/MC | 19.99 $ (when paying for year: 15.99 $/mo) |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Kimsufi KS-3 | 4 × 3.5 GHz | 32 GB | 4 TB HDD | AU, CA, DE, FR, GB, PL… | PayPal, Visa/MC | 21.26 $ (when paying for 2 years: 20.19 $/mo) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-1-L | 4 × 3.1 GHz | 16 GB | 2 TB HDD | FR | — | 22.37 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Kimsufi KS-4 | 4 × 3.5 GHz | 32 GB | 4 TB HDD | AU, CA, DE, FR, GB, PL… | PayPal, Visa/MC | 23.49 $ (when paying for 2 years: 22.31 $/mo) |
| [PebbleHost](https://accsly.io/en/vps/hosting/pebblehost) | Essential-01 | 4 | 16 GB | 240 GB SSD | GB | PayPal, Visa/MC | 24.99 $ (when paying for year: 19.99 $/mo) |
| [DigitalBerg.com](https://accsly.io/en/vps/hosting/digitalberg) | Dual Xeon 5150 Hybrid Storage Dedicated Server USA | 4 × 2.7 GHz | 16 GB | 1120 GB SSD | US | PayPal, Visa/MC | 25.45 $ |
| [DigitalBerg.com](https://accsly.io/en/vps/hosting/digitalberg) | Dual Xeon 5420 Custom Dedicated Server USA | 8 × 2.5 GHz | 16 GB | 1 TB HDD | US | PayPal, Visa/MC | 26.80 $ |
| [DigitalBerg.com](https://accsly.io/en/vps/hosting/digitalberg) | Dual Xeon 5150 Dedicated Server USA | 4 × 2.7 GHz | 16 GB | 1 TB HDD | US | PayPal, Visa/MC | 26.81 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-2-L | 6 × 2.2 GHz | 32 GB | 500 GB SSD | FR | — | 27.97 $ (when paying for year: 26.57 $/mo) |
| [SteadyHost](https://accsly.io/en/vps/hosting/steadyhost) | Xeon E3-1220 8GB 1x1000GB (NL-AMS) | 4 × 3.1 GHz | 8 GB | 1 TB HDD | NL | Visa/MC, PayPal, WebMoney, Crypto | 29.00 $ |
| [SteadyHost](https://accsly.io/en/vps/hosting/steadyhost) | Xeon G530 2GB 2x500GB (DE-FRA) | 2 × 2.4 GHz | 2 GB | 1 TB HDD | DE | Visa/MC, PayPal, WebMoney, Crypto | 29.00 $ |
| [Dacentec](https://accsly.io/en/vps/hosting/dacentec) | Supermicro X3440 8GB 2x2TB Rent Only | 4 | 8 GB | 4 TB SSD | US | — | 29.99 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | EM-A116X-SSD | 4 × 3.1 GHz | 32 GB | 2048 GB SSD | FR, PL, NL | — | 31.33 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Store-1-S | 4 × 3.1 GHz | 32 GB | 8 TB HDD | FR | — | 33.57 $ |
| [DigitalBerg.com](https://accsly.io/en/vps/hosting/digitalberg) | Dual Xeon 5420 Hybrid Storage Dedicated Server USA | 8 × 2.5 GHz | 24 GB | 2240 GB SSD | US | PayPal, Visa/MC | 34.84 $ |
| [QuickHostUK](https://accsly.io/en/vps/hosting/quickhost) | Dell PowerEdge R210 II · E3-1230 V2 · 8 GB · 1× 240GB SSD | 4 × 3.3 GHz | 8 GB | 240 GB SSD | GB | — | 38.73 $ |
| [QuickHostUK](https://accsly.io/en/vps/hosting/quickhost) | Dell PowerEdge R210 II · E3-1230 V2 · 8 GB · 1× 250GB SSD | 4 × 3.3 GHz | 8 GB | 250 GB SSD | GB | — | 38.73 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Pro-4-S | 4 × 3.5 GHz | 32 GB | 750 GB SSD | FR | — | 39.16 $ (when paying for 3 years: 33.29 $/mo) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-3-L | 6 × 2.2 GHz | 32 GB | 1 TB SSD | NL, FR | — | 39.16 $ (when paying for year: 37.20 $/mo) |
| [Ihor](https://accsly.io/en/vps/hosting/ihor) | Xeon E5620 / 4 GB / 500 GB HDD (конфигуратор) | 4 × 2.4 GHz | 4 GB | 500 GB HDD | RU | Visa/MC, MIR, WebMoney, YooMoney, Invoice, PayPal, Crypto | 39.98 $ (when paying for year: 35.98 $/mo) |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/dedicated/xeon?format=json

## Dedicated server on Intel Xeon: from a decade-old E3 to Xeon 6

The word Xeon in the catalogue covers machines more than ten years apart. A quad-core E3 from 2013, a dual-processor E5 v4 platform and a fresh Xeon 6 with dozens of cores on DDR5 sit side by side. Their price and performance differ by an order of magnitude, so a dedicated server on Xeon is chosen by model number, not by brand.

### Generations by model number

- **E3-1200 v2–v6** (roughly 2013–2017). Four cores, eight threads, up to 32–64 GB of memory. Found in the cheapest plans, good for small websites, mail and monitoring.
- **E5-2600 v2–v4** (2013–2016). Up to 14–22 cores per socket, four memory channels, often on dual-processor boards. Russian data centres still have even older E5620 and L5640 from around 2010; take them only for very light tasks.
- **E-2100 and E-2200** (2018–2019). Successors to the E3: six to eight high-clock cores, but only two memory channels and a 128 GB ceiling.
- **Xeon D**. A low-power system on a chip: D-1520 and D-1540 are often put in compact servers for storage and backups.
- **Scalable Silver, Gold, Platinum** (since 2017). The second digit of the number indicates the generation: 4114 and 6138 are first, 4216 and 6230 second, 6348 third, 5515+ and 6542Y fifth. More on the difference between the lines on the [VPS on Xeon Gold](https://accsly.io/en/vps/xeon-gold) page.
- **Xeon 6** (since 2024, models such as 6517P and 6527P). A new naming scheme, DDR5 and PCIe 5.0; priced closer to modern EPYC.

### Why an old E5 is so cheap

Servers on E5 v3 and v4 paid for themselves long ago, and parts for them are sold in bulk after being decommissioned from corporate racks. Hence the low rent for a solid configuration: 2×E5-2680 v4 gives 28 cores and up to hundreds of gigabytes of memory. The downsides are a low per-core clock, DDR4 at 2133–2400 MHz, high power consumption and SATA instead of NVMe on many boards. For tasks that parallelise well and do not need fast response this is a sensible saving; for a game server or a busy PHP site, a new processor with fewer cores will be faster.

"2×" in the model name means two physical processors. Cores and memory in such a server are doubled, but memory is split between sockets: an application that is not NUMA-aware sometimes runs worse on a dual-processor machine than expected.

### ECC, disks and storage

All server Xeons work with ECC memory, usually registered, which sets them apart from desktop processors for rent. For file storage on ZFS or a database that runs for months without a reboot, this matters more than extra cores. A noticeable share of Xeon plans come with hard drives: old platforms with many HDD bays are an inexpensive way to get dozens of terabytes for archives or [backups](https://accsly.io/en/vps/for-backups). Check whether there is a hardware RAID controller or the array has to be built in software, and how many free bays will remain for expansion.

### Where Xeon is rented and what to check

Russia accounts for the most Xeon servers in the catalogue: Moscow and St Petersburg lead by number of plans, followed by London, Frankfurt, Paris and Toronto. Russian sites readily use Xeon because spare parts are easier to find, and payment there goes through Russian MIR cards, SBP or invoice; that selection is on the [dedicated servers in Russia](https://accsly.io/en/dedicated/russia) page. A setup fee is noticeably rarer for Xeon plans than for EPYC, and the port is gigabit in most cases.

Before ordering, ask for the exact model and the platform's build year, the memory type, whether IPMI or iDRAC is available, and the BIOS firmware: on old machines without microcode updates, performance drops noticeably after the patches for the Spectre and Meltdown vulnerabilities.

## FAQ

### Is it worth renting a server on Xeon E5 v2 in 2026?

Only for undemanding tasks: test benches, storage, background computation. For a website or application with live users, E5 v4 or E-2200 will give noticeably better response for almost the same money.

### What does 2× in the processor name mean?

The server has two physical processors on one board. There are twice as many cores and memory slots, but power consumption is higher too, and the application must be able to work with two NUMA nodes.

### How is the Xeon E-2136 different from the E3-1270 v3?

The E-2136 is five years newer, with six cores instead of four, support for faster memory and up to 128 GB of RAM. Per-core performance is also noticeably better on the E-2136.

### Why use Xeon D if it is weaker than regular Xeons?

Xeon D uses little power and integrates network controllers right into the chip, so such servers are cheap to rent. They are taken for file storage, backups and small services where the processor is not fully loaded.

### Can I install Windows Server on a rented Xeon?

On most plans yes, Windows installation is shown in the table. Windows Server licensing is per physical core, so on a dual-processor machine with dozens of cores it will cost noticeably more.

### Which Xeon to choose for 1C and a database?

For 1C (a popular Russian accounting suite) core clock matters, so E-2200, high-clock Xeon Gold or Xeon 6 fit better. Many-core, low-clock E5 are better value for parallel loads, not for a single-threaded accounting system.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# Dedicated servers in Europe

Physical servers in Germany, France, the Netherlands, the UK, Poland, Finland and other European countries. Compare the country, processor, memory, disks and setup fee; cheapest first.

> Source: https://accsly.io/en/dedicated/europe · accsly.io catalog data as of 2026-11-11. accsly.io compares prices and does not sell servers; orders are placed on the host's site.

## Figures

- Plans: 3,245, hosts: 119
- Price: from 5.58 $, a quarter below 146 $, median 229 $
- NVMe: 30 %, unlimited traffic: 34 %, hourly billing: 13 %
- RAM → price from: 1 GB — 5.58 $, 2 GB — 5.58 $, 4 GB — 5.58 $, 8 GB — 5.58 $, 16 GB — 17.89 $
- Countries: Germany (1024), Netherlands (758), France (570), United Kingdom (504), Poland (255), Canada (233)
- Cheapest hosts: [Scaleway](https://accsly.io/en/vps/hosting/scaleway) — 5.58 $, [PebbleHost](https://accsly.io/en/vps/hosting/pebblehost) — 19.99 $, [Gen X Web Hosting](https://accsly.io/en/vps/hosting/genxwhosting) — 20.91 $, [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) — 21.26 $, [Premiumtechs.uk](https://accsly.io/en/vps/hosting/premiumtechs) — 24.00 $

## Cheapest plans — 3,245 in all

| Host | Plan | Cores | RAM | Disk | Countries | Payment | Price/month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-1-M-SATA | 8 × 2.4 GHz | 8 GB | 1 TB HDD | FR | — | 5.58 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-2-S-SATA | 2 × 1.7 GHz | 4 GB | 1 TB HDD | NL, FR | — | 5.58 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-2-S-SSD | 2 × 1.7 GHz | 4 GB | 120 GB SSD | NL, FR | — | 5.58 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-3-S-SSD | 2 × 1.7 GHz | 4 GB | 250 GB SSD | FR | — | 5.58 $ (when paying for year: 5.31 $/mo) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-1-M-SSD | 8 × 2.4 GHz | 8 GB | 120 GB SSD | FR | — | 15.66 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-1-M-SSD-160G | 8 × 2.4 GHz | 8 GB | 160 GB SSD | FR | — | 15.66 $ |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-2-M-SATA | 8 × 2.4 GHz | 16 GB | 1 TB HDD | NL, FR | — | 17.89 $ (when paying for year: 17.01 $/mo) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-2-M-SSD | 8 × 2.4 GHz | 16 GB | 250 GB SSD | NL, FR | — | 17.89 $ (when paying for year: 17.01 $/mo) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | EM-RV1-C4M16S128-A | 4 × 1.9 GHz | 16 GB | 128 GB SSD | FR | — | 17.89 $ |
| [PebbleHost](https://accsly.io/en/vps/hosting/pebblehost) | Value-01 | 2 | 8 GB | 240 GB SSD | GB | PayPal, Visa/MC | 19.99 $ (when paying for year: 15.99 $/mo) |
| [Gen X Web Hosting](https://accsly.io/en/vps/hosting/genxwhosting) | Linux Dedicated Starter 1 | 2 × 1.7 GHz | 4 GB | 1 TB HDD | IN, US, SG, GB, AU, DE | — | 20.91 $ (yearly: 20.91 $/mo) |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Kimsufi KS-3 | 4 × 3.5 GHz | 32 GB | 4 TB HDD | AU, CA, DE, FR, GB, PL… | PayPal, Visa/MC | 21.26 $ (when paying for 2 years: 20.19 $/mo) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-1-L | 4 × 3.1 GHz | 16 GB | 2 TB HDD | FR | — | 22.37 $ |
| [OVHcloud](https://accsly.io/en/vps/hosting/ovhcloud) | Kimsufi KS-4 | 4 × 3.5 GHz | 32 GB | 4 TB HDD | AU, CA, DE, FR, GB, PL… | PayPal, Visa/MC | 23.49 $ (when paying for 2 years: 22.31 $/mo) |
| [Premiumtechs.uk](https://accsly.io/en/vps/hosting/premiumtechs) | Dedicated Plan-I | 2 × 3.4 GHz | 8 GB | 2 TB HDD | DE, RU, FR, NL, BG, CA… | Visa/MC, PayPal, Invoice | 24.00 $ |
| [PebbleHost](https://accsly.io/en/vps/hosting/pebblehost) | Essential-01 | 4 | 16 GB | 240 GB SSD | GB | PayPal, Visa/MC | 24.99 $ (when paying for year: 19.99 $/mo) |
| [server.ir](https://accsly.io/en/vps/hosting/server-ir) | ODS B2350SD1 | 2 × 1.7 GHz | 4 GB | 128 GB SSD | NL | Invoice | 27.58 $ (yearly: 27.58 $/mo) |
| [Scaleway](https://accsly.io/en/vps/hosting/scaleway) | Dedibox Start-2-L | 6 × 2.2 GHz | 32 GB | 500 GB SSD | FR | — | 27.97 $ (when paying for year: 26.57 $/mo) |
| [SteadyHost](https://accsly.io/en/vps/hosting/steadyhost) | Xeon E3-1220 8GB 1x1000GB (NL-AMS) | 4 × 3.1 GHz | 8 GB | 1 TB HDD | NL | Visa/MC, PayPal, WebMoney, Crypto | 29.00 $ |
| [SteadyHost](https://accsly.io/en/vps/hosting/steadyhost) | Xeon G530 2GB 2x500GB (DE-FRA) | 2 × 2.4 GHz | 2 GB | 1 TB HDD | DE | Visa/MC, PayPal, WebMoney, Crypto | 29.00 $ |

Every plan with filters is on the page; the same as JSON: https://accsly.io/en/dedicated/europe?format=json

## Dedicated server in Europe: pick the country first, then the hardware

As of 3 November 2026 the European selection of the catalogue holds 1,889 plans from 63 hosts. The cheapest machines cost about $20 a month and the median one about $219. Germany has the most offers (roughly a third), followed by France, the UK and the Netherlands, then Poland, Finland, Italy, Spain, Switzerland, Romania and Sweden. Many configurations are sold in several countries at once, so when ordering check that the cart shows the location you actually chose the plan for. When choosing a dedicated server in Europe, settle on the country first and then move on to its own selection.

### Whose latency matters

Start with where your users are. For an audience spread across the EU, Frankfurt and Amsterdam sit in the middle of the network and reach most European capitals over short paths. For users in the UK and Ireland, London is the natural choice; for Southern Europe, Milan or Madrid; for the Nordics and the Baltics, Helsinki or Stockholm. If you also serve North America, the western edge of Europe (London, Paris, Amsterdam) shaves a few milliseconds off the transatlantic leg.

The reason a few cities are so central is internet exchange points. Frankfurt hosts DE-CIX, one of the largest exchanges in the world by peak traffic, Amsterdam has AMS-IX and London has LINX. Hundreds of networks exchange traffic there directly instead of paying for transit through third parties. In the north the same role is played by Netnod in Stockholm. A server in a city with a large exchange gets more direct routes and more even latency to different countries. Popular destinations have their own pages: [dedicated servers in Germany](https://accsly.io/en/dedicated/germany), [in Finland](https://accsly.io/en/dedicated/finland) and [in Switzerland](https://accsly.io/en/dedicated/switzerland).

### Law: GDPR, the UK and Switzerland

Every EU country applies the same GDPR, supervised by the national authority where the data controller is established. For the owner of a server holding Europeans' data the obligations are the same in Berlin, Warsaw or Helsinki: a data processing agreement with the host, a clear retention period and a breach notification procedure. After Brexit the UK runs its own UK GDPR, and Switzerland, which is not in the EU, has its own data protection act, revised with effect from 1 September 2023. The EU recognises both as providing adequate protection, so transfers from the EU there need no extra contractual mechanisms. If you are a non-European company serving EU customers, an EU location does not remove your GDPR duties, but it keeps the data flow simple.

### Price spread and setup fees

The same class of machine costs noticeably different amounts depending on the country. Medians for several countries in the catalogue: Italy about $177, Finland about $236, Bulgaria about $253, Spain about $299, Romania about $335, Sweden about $369, Switzerland about $411. Part of the gap reflects the mix rather than the location: where there are more older Xeons and desktop chips, the median is lower.

About 13% of European plans charge a one-off setup fee, but it is unevenly spread. In Finland roughly a third of plans have one, while in Italy, Sweden and Switzerland the catalogue shows none at all. When comparing countries, add the setup fee to a year of rent rather than looking at the monthly price alone.

### Hardware and disks across Europe

More than half of European plans run on Intel Xeon of various generations. Ryzen and desktop Intel Core together account for about a quarter: inexpensive high-clock machines, usually without ECC memory. AMD EPYC appears in roughly one plan in ten, Xeon Gold and Platinum less often. The median server has 64 GB of memory, and half of the plans fall between 32 and 128 GB.

- **HDD**: about a third of plans, for archives, backups and file storage where the price per terabyte matters.
- **SATA SSD**: about 39% of plans, for websites, mail and small databases.
- **NVMe**: about a quarter of plans, for databases, virtualisation and build servers.

Most plans list a 1 Gbit/s port, about one in twenty a 10 Gbit/s port. Unmetered traffic comes with 63% of plans among those where the host states its traffic terms. DDoS filtering is included in about 70% of offers and IPv6 in two thirds. About 39% of machines are delivered right after payment; the rest take from a few hours to a couple of days.

### Paying for it

More than half of European plans can be paid by international card and almost half via PayPal. Bank invoices for companies are less common, roughly one offer in seven, so if your accounting needs an invoice in euros, filter for it before comparing prices. If a virtual machine is enough for the project, also compare [VPS in Europe](https://accsly.io/en/vps/europe).

## FAQ

### Which European city gives the best latency across the EU?

Frankfurt and Amsterdam, thanks to the DE-CIX and AMS-IX exchanges and their central position. For users concentrated in one region, a server in that region is better still.

### Does GDPR apply in Switzerland and the UK?

No, they have their own laws: UK GDPR in Britain and the revised Federal Act on Data Protection in Switzerland. The requirements are close to the EU ones, and the EU recognises their level of protection as adequate.

### Where in Europe are there no setup fees?

In the catalogue, plans in Italy, Sweden and Switzerland have none and Spain almost none. In Finland a one-off fee appears on roughly a third of plans.

### Frankfurt or Amsterdam for a European audience?

Both sit on the largest exchanges and give short routes across Europe. Decide on the hardware and price of the specific plan; the latency difference for users is usually small.

### Do I need an EU server to comply with GDPR?

No, GDPR follows the data, not the server. An EU location simply avoids the extra paperwork needed for transfers outside the EU and countries with adequacy decisions.

### Why is one plan listed in several countries?

Many hosts sell one configuration in different data centres. Price and delivery time can differ by location, so check the selected country before paying.

## More selections

- Tasks: [VPS for a corporate VPN](https://accsly.io/en/vps/for-vpn), [VPS for a website](https://accsly.io/en/vps/for-website), [VPS for a Telegram bot](https://accsly.io/en/vps/for-telegram-bot), [VPS for Docker](https://accsly.io/en/vps/for-docker), [VPS for a game server](https://accsly.io/en/vps/for-game-server), [Windows VPS/VDS](https://accsly.io/en/vps/windows), [VPS for a proxy server](https://accsly.io/en/vps/for-proxy), [VPS for web scraping](https://accsly.io/en/vps/for-parsing), [VPS for a database](https://accsly.io/en/vps/for-database), [VPS for a mail server](https://accsly.io/en/vps/for-mail-server), [VPS for CI/CD runners](https://accsly.io/en/vps/for-ci), [VPS for CPU-only AI models (Ollama)](https://accsly.io/en/vps/for-ollama)
- Countries: [VPS/VDS in Russia](https://accsly.io/en/vps/russia), [VPS/VDS in the Netherlands](https://accsly.io/en/vps/netherlands), [VPS/VDS in Germany](https://accsly.io/en/vps/germany), [VPS/VDS in Finland](https://accsly.io/en/vps/finland), [VPS/VDS in the USA](https://accsly.io/en/vps/usa), [VPS/VDS in Poland](https://accsly.io/en/vps/poland), [VPS/VDS in Kazakhstan](https://accsly.io/en/vps/kazakhstan), [VPS/VDS in Turkey](https://accsly.io/en/vps/turkey), [VPS/VDS in Latvia](https://accsly.io/en/vps/latvia), [VPS/VDS in Europe](https://accsly.io/en/vps/europe), [VPS/VDS in the CIS](https://accsly.io/en/vps/cis), [VPS/VDS in Asia](https://accsly.io/en/vps/asia)
- Payment: [VPS/VDS paid with cryptocurrency](https://accsly.io/en/vps/pay-with-crypto), [VPS/VDS paid with PayPal](https://accsly.io/en/vps/pay-with-paypal), [VPS/VDS with hourly billing](https://accsly.io/en/vps/hourly-billing), [VPS/VDS with a free trial](https://accsly.io/en/vps/free-trial)
- Specs: [Cheap VPS/VDS under 4 $ a month](https://accsly.io/en/vps/cheap), [VPS/VDS with 1 GB RAM](https://accsly.io/en/vps/1-gb-ram), [VPS/VDS with 2 GB RAM](https://accsly.io/en/vps/2-gb-ram), [VPS/VDS with 4 GB RAM](https://accsly.io/en/vps/4-gb-ram), [VPS/VDS with 8 GB RAM](https://accsly.io/en/vps/8-gb-ram), [VPS/VDS with 16 GB RAM](https://accsly.io/en/vps/16-gb-ram), [NVMe VPS/VDS](https://accsly.io/en/vps/nvme), [KVM VPS/VDS](https://accsly.io/en/vps/kvm), [VPS/VDS with unlimited traffic](https://accsly.io/en/vps/unlimited-traffic), [VPS/VDS with DDoS protection](https://accsly.io/en/vps/ddos-protection), [VPS/VDS with IPv6](https://accsly.io/en/vps/ipv6)

# Selections in Russian only

Payment methods and terms that matter only in Russia (MIR cards, SBP, Russian law).

- [Зарубежные VPS/VDS](https://accsly.io/ru/vps/abroad)
- [VPS/VDS с оплатой картой МИР](https://accsly.io/ru/vps/pay-with-mir)
- [VPS/VDS с оплатой через СБП](https://accsly.io/ru/vps/pay-with-sbp)
- [VPS/VDS с оплатой ЮMoney](https://accsly.io/ru/vps/pay-with-yoomoney)
- [Зарубежный VPS с оплатой российской картой](https://accsly.io/ru/vps/abroad-pay-with-mir)
- [Зарубежный VPS с оплатой через СБП](https://accsly.io/ru/vps/abroad-pay-with-sbp)
- [Зарубежные хостеры, которые работают с россиянами](https://accsly.io/ru/vps/abroad-for-russians)
- [VPS для бота ВКонтакте](https://accsly.io/ru/vps/for-vk-bot)
- [VPS по 152-ФЗ — серверы в России для юрлиц](https://accsly.io/ru/vps/for-152-fz)
- [VPS для 1С](https://accsly.io/ru/vps/for-1c)
- [Выделенный сервер для 1С](https://accsly.io/ru/dedicated/for-1c)
- [VPS для Key Collector](https://accsly.io/ru/vps/for-key-collector)
- [VPS для QUIK](https://accsly.io/ru/vps/for-quik)
- [VPS для 1С-Битрикс](https://accsly.io/ru/vps/for-bitrix)
- [VPS с Astra Linux](https://accsly.io/ru/vps/astra-linux)
- [VPS с низким пингом из России](https://accsly.io/ru/vps/low-ping)
- [VPS до 150 ₽ в месяц](https://accsly.io/ru/vps/under-150)
- [Хостинг с оплатой картой МИР](https://accsly.io/ru/hosting/pay-with-mir)