Neckrez

VPS for trading, paid in crypto

A server that keeps a trading bot or a trading terminal online around the clock. Hourly billing, a dedicated IPv4, no identity check.

In short

A trading bot has one job that a laptop cannot do: stay online, all day and all night, on a stable connection with a stable address. A VPS does that. On Neckrez you pick a city, get a server with full root and a dedicated IPv4 in about a minute, and pay by the hour from a crypto balance with no identity check. Run Linux for a Python, Node or Docker bot, or Windows for a terminal that only exists for Windows.

We sell servers, not trading advice. Nothing here says a bot will make money; the page is about the part we can speak to, which is the machine it runs on.

What a trading server actually needs

Most bots need far less than people expect. A bot that polls prices, applies rules and sends orders is light on CPU and memory, and what matters is closer to a short list of boring properties:

  • It stays up. A bot that runs on a home computer stops when the power, the router or the laptop does. A server in a data centre does not.
  • A stable IPv4 address. Exchanges let you restrict an API key to specific addresses, and a server with its own dedicated IPv4 makes that possible. A home connection changes its address.
  • A good route to the exchange. Distance adds latency. See below.
  • Enough memory for what you run. A single bot fits on a small plan. Running several, keeping a local database of candles or running a backtest in the same machine is when you need more.
  • Restart on its own. A crash at 3 am should not mean a missed day.

Pick the city by the exchange, not by where you live

You are not the one who needs to be close to the server; the bot needs to be close to the exchange. Order requests travel from the server to the exchange's API, so the shorter that route, the lower the delay on each call. Many exchanges run their API in a few well-known regions, and the quickest way to find out which is best for you is to measure it.

  • Look up where your exchange hosts its API, or deploy a small server in two or three candidate cities, which costs cents by the hour.
  • Measure with ping or a real API call from each server and keep the city with the lowest and steadiest times.
  • Destroy the ones you do not need. Billing stops the moment a server is deleted.

The Deploy page lists 49 locations across Europe, North and South America, Asia, Oceania and Africa, and shows the approximate delay from you to each. That is the distance to you, though, not to the exchange, so use it only as a tie-breaker.

Be honest about what a VPS is. If your strategy depends on being milliseconds ahead of other traders, a VPS in a shared data centre is not a colocation rack, and no ordinary hosting will win that race. For bots that trade on minutes, hours or days, a nearby VPS is more than enough.

Linux or Windows

  • Linux (Ubuntu, Debian) for bots written in Python, Node.js, Go or run in Docker, and for most open-source frameworks. It is lighter and cheaper: Windows adds a licence fee and needs at least 2 GB of RAM.
  • Windows Server (RDP) for terminals that only exist for Windows, such as MetaTrader. You connect over Remote Desktop and the terminal keeps running after you disconnect. See the Windows VPS page for versions and prices.

Sizing: start small

A single Python bot that talks to one exchange runs comfortably on one of the smallest plans, and you can deploy a bigger one later. The table below lists the live prices. Move up when you see memory or CPU running out, not before.

If you run something heavy that must not slow down, such as a large backtest that runs every night, look at Dedicated CPU: the cores are reserved for you rather than shared.

Keep the bot running

Whatever you run, let the operating system restart it. With a systemd unit the bot starts at boot and comes back five seconds after any crash. Replace the paths and names with your own:

[Unit]
Description=Trading bot
After=network-online.target

[Service]
User=bot
WorkingDirectory=/home/bot/app
EnvironmentFile=/home/bot/app/.env
ExecStart=/home/bot/app/venv/bin/python bot.py
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target

Save it as /etc/systemd/system/bot.service, then run systemctl enable --now bot. With Docker, the equivalent is --restart unless-stopped. Either way, read the logs the next morning at least once.

Keep the keys safe

An exchange API key is the most valuable thing on the machine, so treat it that way.

  • Create the key with only the rights the bot needs. Reading and trading are usually enough. Leave withdrawals off.
  • Whitelist the server's IPv4 on the exchange. Then a stolen key is useless from anywhere else.
  • Log in with an SSH key, not a password, and run the bot as a normal user rather than root.
  • Keep the keys in an environment file, outside the code and out of any repository.
  • Open only the ports you use. A bot that only makes outgoing calls needs nothing open except SSH.

Backups and recovery

The server keeps its disk, but disks fail and mistakes happen, so keep your own copy of the bot's code, config and any trade journal. You can also take an on-demand snapshot from the panel: it is kept 7 days and lets you start a copy of the server on a new machine if you need to move. The IP address of the new machine is different, so update the whitelist on the exchange afterwards. On Vultr you can instead swap the IP of the same server with one click.

What it costs

Billing is hourly from a prepaid balance, with no term and no contract. A small plan costs a few dollars a month. A server you test for an afternoon costs a few cents, and the table below shows the live prices for each size. Destroy the server and the charge stops.

How to start with crypto

  • 1. Sign up with an email. No KYC, no ID, no phone and no card.
  • 2. Top up the balance in crypto. Bitcoin, USDT, ETH or any of 300+ coins; the minimum top-up is $15.
  • 3. Pick a city and a plan, and Ubuntu or Windows as the system.
  • 4. Connect over SSH (or RDP on Windows), set up the bot and its restart rule, then add the server's IPv4 to your exchange key.
  • 5. Watch the balance page. It shows how many days your balance lasts at the current rate.

FAQ

What do I need for a crypto trading bot? A server that stays online, a stable IPv4 address to whitelist on the exchange, a city with a good route to the exchange, and a restart rule. Most single bots fit on one of the smallest plans.

Which city should I choose? The one closest, in network terms, to your exchange's API. Check where the exchange hosts it, or deploy a small server in two or three cities, measure, and keep the best.

Can I run MetaTrader on a VPS? Yes, on a Windows VPS. It runs on Vultr with a licence fee shown before you pay and at least 2 GB of RAM. See the Windows VPS page.

Will a VPS make my bot profitable? No. A VPS keeps the bot online and gives it a stable address. Whether the strategy makes money is down to the strategy, and we give no trading advice.

Is a VPS fast enough for high-frequency trading? Not for strategies that need to beat others by milliseconds. Those use colocation next to the exchange. A VPS suits bots that trade on minutes or longer.

Can I pay without a card and without identity checks? Yes. You sign up with an email and pay with Bitcoin, USDT, ETH or any of 300+ coins. See also VPS for bots for general bot hosting.