Skip to content

Cloud VPS · Crypto trading bots

A VPS for crypto trading bots, next to the exchange.

Measured 28 October 2026 from our own servers: Binance, OKX, Bitget, Hyperliquid answer fastest from Tokyo (3.5-17 ms), Bybit from Singapore (7.6 ms). Put the bot in the city its exchange answers from. Linux VPS from $9.90 a month or $0.0136 an hour, each with a dedicated IPv4 address.

Latency measured 28 October 2026 from our own servers. Prices read from the catalogue the cart charges from.

Rendering of a network switch with three patch leads, one litTokyo · SingaporeMeasured

Step 01

Choose the city

Tokyo for Binance, OKX, Bitget and Hyperliquid; Singapore for Bybit. Each card shows the lowest price in that city.

Steps 02 to 05

Build your server in Tokyo.

The line and the size first, then the system, then the add-ons. Ubuntu 24.04 with Docker is selected for you; Windows appears on the sizes that carry it. The summary shows the price the cart charges.

Ordering in Tokyo, JapanChange city

Step 02

Pick a line

Every size we build, in more cities than any other line. Sizes are named for their shape, so come here knowing the cores, memory and disk you want; if you do not, Standard is the shorter answer to the same question.

Step 03

Choose a size

Sizes are fixed shapes, not sliders. Changing size later is a support request, and a smaller size usually means a new server because a disk cannot shrink.

Step 04

Choose an image

Clean vendor images, nothing preloaded that you did not ask for. You can rebuild onto any other image from the panel at any time.

Windows is not offered on C2-4-80 in Tokyo.

Every image is the vendor's own, unmodified. If you want the machine configured before you log in, add a start-up script below.

Start-up script · optional

Runs once as root while the server is being built, before it is handed to you. A shell script starting #!/bin/bash, or a #cloud-config. It cannot be changed after the machine is created, and its output is left in /root/startup-script.log.

0 / 32,768 characters

Step 05

Choose a term and add-ons

Terms are prepaid. Annual takes 5% off the same monthly rate — it is a discount for paying up front, not a different product.

Billing term

$37.90 charged every month. Switch to annual at any renewal.

How many

One machine. Each one you add is built separately, with its own address and root password.

1

A full disk image taken every night, stored off the host that runs your server; the last 2 are kept. Adds 20% to the plan price ($7.58/mo on C2-4-80).

The form shows the smaller sizes of each line. Every size in Tokyo

Our suggestion: 2 GB for a bot with its exchange library and a small database; 1 GB runs one light bot. Billed by the hour, you can measure from the server yourself and delete it if it does not suit you.

Measured

Every exchange, from Tokyo and from Singapore.

Lower is better; the faster city in each row is in colour. Binance in Tokyo and Bybit in Singapore match where a peer-reviewed study places them.

Round-trip time in milliseconds from our servers in Tokyo and Singapore to crypto exchange APIs
Exchange APIFrom TokyoFrom Singapore
BinanceSpot API6.7 msfastest75 ms
BinanceUSDⓈ-M futures API3.5 msfastest75 ms
BybitV5 API86 ms7.6 msfastest
OKXV5 API17 msfastest95 ms
BitgetV2 API17 msfastest75 ms
HyperliquidInfo API16 msfastest84 ms
  • Measured 28 October 2026 from our own servers in Tokyo and Singapore: the best of nine HTTPS requests to each exchange's public ping or time call, on one open connection, so the figure is the round trip to the exchange's API without the connection set-up. Every exchange answered with HTTP 200 from both cities.
  • A first connection showed about 2 ms everywhere: that is the content network's edge in the same city, not the exchange, so we do not print it as the exchange's latency.
  • We sell from two data centres in each city and measured both the same afternoon; each figure is the slower of the two, so it holds for any server on these pages. Your own bot adds its processing time, and routes change; measure from the server you order before you rely on a figure.

Source: The good, the bad, and latency: exploratory trading on Bybit and Binance (Quantitative Finance, 2025)

Setup

From order to a running bot.

Linux over SSH, or Windows over Remote Desktop. Steps marked as our advice are ours; the rest is how the systems and exchanges work.

  1. Step 1

    Connect

    Your service page shows the address and the ssh command once the server is online.

    ssh root@YOUR_SERVER_IP
  2. Step 2 · our advice

    Keep the clock exact

    Signed API requests carry a timestamp the exchange checks, so a drifting clock gets requests refused. Check that time sync is on.

    timedatectl status | grep -i synchronized
  3. Step 3 · our advice

    Run the bot as a service

    A systemd service starts the bot at boot and restarts it if it stops; tmux is enough while you are testing.

    systemctl enable --now mybot.service journalctl -u mybot -f
  4. Step 4

    Lock the API key to this server

    Every server has its own IPv4 address that stays with it, so it can be the only address allowed to use your key. Binance asks for an IP access restriction on an API key before it may withdraw. Binance documentation. A Bybit API key with no IP address bound to it expires after 90 days. Bybit documentation. OKX recommends linking an API key to IP addresses. OKX documentation.

    curl -4 -s https://ifconfig.me

Bots

The bots people run on it.

Install commands from each project's own documentation. The form opens on Ubuntu 24.04 with Docker installed, which both open-source bots need. Bots sold as a website, where you only paste API keys, run on that company's servers and need no VPS.

  • Freqtrade

    Open-source strategy bot in Python, with backtesting and a web interface.

    mkdir ft_userdata && cd ft_userdata/ curl https://raw.githubusercontent.com/freqtrade/freqtrade/stable/docker-compose.yml -o docker-compose.yml docker compose pull docker compose run --rm freqtrade create-userdir --userdir user_data docker compose run --rm freqtrade new-config --config user_data/config.json docker compose up -dFreqtrade: Docker quick start
  • Hummingbot

    Open-source market-making and arbitrage bot, run from a terminal client.

    git clone https://github.com/hummingbot/hummingbot.git cd hummingbot make setup make deployHummingbot on GitHub
  • CCXT

    The library most self-written bots use to talk to exchanges, in Python, JavaScript and more.

    pip install ccxtCCXT on GitHub

Questions

What traders ask before they move a bot to a VPS.

Which VPS location is best for Binance?
Tokyo. Binance's futures API answered our Tokyo server in 3.5 ms and its spot API in 6.7 ms; from Singapore both took about 75 ms. A peer-reviewed study places Binance in Amazon's Tokyo region.
Which VPS location is best for Bybit?
Singapore: 7.6 ms to Bybit's API from our Singapore server, 86 ms from Tokyo. The same study places Bybit in Amazon's Singapore region.
And OKX, Bitget and Hyperliquid?
All three answered fastest from Tokyo, between 16 and 17 ms, and took 75 to 95 ms from Singapore. None of them has said where its matching engine runs, so this is our measurement, not their statement.
Why does a ping to the exchange show 1 or 2 ms from everywhere?
Exchanges sit behind content networks such as CloudFront and Cloudflare, and a ping or a first connection reaches the network's edge in your own city. The order still travels to the exchange. That is why we time a full API request instead.
Do exchanges block your servers?
None did on 28 October 2026: every request from Tokyo and Singapore was answered with HTTP 200. Each exchange decides who may trade from which country, so check its terms for where you live.
Can I lock my API keys to the server's address?
Yes. Every server has its own IPv4 address for as long as you keep it. Binance asks for an IP restriction before a key may withdraw, a Bybit key with no IP bound expires after 90 days, and OKX recommends binding keys to addresses.
Can I run my bot on Windows?
Yes. Windows Server with its licence included, on sizes from 2 vCPU and 4 GB, from $30.90 a month in Tokyo and Singapore. Choose it in the system step. For the same bot, Linux sizes cost less.
Can a server in Tokyo or Singapore let me use an exchange where it is restricted?
No. Exchanges decide who may trade by the account holder, not by the server, and using a server to get around that breaks their terms and can close the account. Use a server for speed, from a country where the exchange serves you.
Will my bot keep running when I close SSH or Remote Desktop?
Yes, if it runs as a service: on Linux a systemd unit or Docker keeps it going after you log out and starts it again after a reboot. On Windows, close the Remote Desktop window rather than signing out; signing out ends the programs you started.
Is my API key safe on a VPS?
The server is yours alone, with root or Administrator access only for you. Give the key trading rights without withdrawal, lock it to the server's IPv4 address, and keep it in a file only your bot's user can read, not in the code.
Does a closer server make my bot profitable?
No. It shortens the time an order takes to reach the exchange, which matters for bots that react to the market quickly. The strategy is still yours, and so is the risk.

Binance, Bybit, OKX, Bitget and Hyperliquid belong to their owners. PartVPS is an independent hosting company, not affiliated with any exchange; we sell the server, not trading services or advice. Each exchange decides who may use it from where: check its terms for your own country.

C2-4-80

$37.90 due today