Compare 182 VPS plans with starting rates of $1.74–$789.83/mo. The lowest rate is an estimated $1.74/mo at 720 hours of usage. Effective monthly rates are in USD; term totals and renewal prices are in RUB.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud EKB 15 — Yekaterinburg Linux (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud EKB 30 — Yekaterinburg Linux (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud NSK 30 — Novosibirsk Linux (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic CPU-50 MSK — Moscow Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic CPU-50 — Saint Petersburg Linux (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic CPU-50 — Saint Petersburg Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud EKB 40 — Yekaterinburg Linux (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud EKB 40 — Yekaterinburg Windows Server (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud KZN 40 — Kazan Windows Server (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud NSK 40 — Novosibirsk Linux (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud NSK 40 — Novosibirsk Windows Server (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud US-40 — New York State Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud EKB 50 — Yekaterinburg Linux (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud EKB 50 — Yekaterinburg Windows Server (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud KZN 50 — Kazan Windows Server (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud NSK 50 — Novosibirsk Linux (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud NSK 50 — Novosibirsk Windows Server (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud US-50 — New York State Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic High-40 — Moscow Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic CPU-80 MSK — Moscow Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic CPU-80 — Saint Petersburg Linux (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic CPU-80 — Saint Petersburg Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud EKB 80 — Yekaterinburg Linux (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud EKB 80 — Yekaterinburg Windows Server (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud KZN 80 — Kazan Windows Server (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud NSK 80 — Novosibirsk Linux (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud NSK 80 — Novosibirsk Windows Server (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud US-80 — New York State Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic High-60 — Moscow Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic CPU-100 MSK — Moscow Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic CPU-100 — Saint Petersburg Linux (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic CPU-100 — Saint Petersburg Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud-100 — Saint Petersburg Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud EKB 100 — Yekaterinburg Linux (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud EKB 100 — Yekaterinburg Windows Server (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud KZN 100 — Kazan Linux (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud KZN 100 — Kazan Windows Server (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud MSK Ultra 100 — Moscow Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud NSK 100 — Novosibirsk Linux (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud NSK 100 — Novosibirsk Windows Server (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud US-100 — New York State Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud-160 — Saint Petersburg Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud EKB 160 — Yekaterinburg Linux (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud EKB 160 — Yekaterinburg Windows Server (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud KZN 160 — Kazan Linux (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud KZN 160 — Kazan Windows Server (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud MSK Ultra 160 — Moscow Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud NSK 160 — Novosibirsk Linux (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud NSK 160 — Novosibirsk Windows Server (public IPv4 included)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud US-160 — New York State Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic High-100 — Moscow Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic CPU-120 MSK — Moscow Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic CPU-120 — Saint Petersburg Linux (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic CPU-120 — Saint Petersburg Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic High-120 — Moscow Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic CPU-140 MSK — Moscow Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic CPU-140 — Saint Petersburg Linux (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic CPU-140 — Saint Petersburg Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Cloud Dedic High-160 — Moscow Windows Server (IPv6)
Monthly usage estimates use 720 hours for hourly rates or 30 days for daily rates, plus any fixed commitment cost. Actual bills depend on usage, provider billing rules, and extras.
Provider deals
Current offers from Timeweb
7 offers pulled from the provider’s own promo pages. Check the final price, billing term, and renewal rate on the provider’s site before checkout.
Saint PetersburgMoscowNovosibirskFrankfurtAmsterdamLondonVelizyGdanskHelsinkiAlmatyIstanbul
Tier III certified datacenters in Russia, Europe, and Asia
Market context
Price is useful only when it has a baseline
Timeweb is compared with the median across the VPS plans currently tracked in our catalog.
Entry price
Timeweb$1.74
Catalog median$58.96
Its lowest tracked rate is below the catalog median.
Cost per GB of RAM
Timeweb$1.74
Catalog median$5.63
Its best RAM value beats the current catalog median.
Frequently asked questions
Timeweb VPS plans start at $1.74/mo (USD-normalized). It lists 182 plans.
Timeweb offers VPS in 5 locations: Germany, Kazakhstan, Netherlands, Russia, United States.
Timeweb is one of the VPS providers we track. Compare its plans and pricing above against the alternatives.
Evidence policy
This brief uses 2 source groups. Official provider pages are labeled as provider statements; independent sources are labeled verified. Unknown renewal terms and missing service details remain visible rather than being inferred.