Hosting Coinbase Trading Bots After the Pro-to-Advanced-Trade Transition
If you search for Coinbase bot tutorials you will find a decade of material split across three APIs: the retired Coinbase Pro API, the institutional Exchange/Prime APIs, and the current Advanced Trade API. Sorting that out is half the setup work; the other half is giving the bot a home that does not depend on your laptop staying open. Here is both halves.
Which Coinbase API Your Bot Should Target
Coinbase retired the standalone Pro platform and moved retail professional trading into Advanced Trade, which lives under your main Coinbase account and exposes its own REST and websocket APIs with modern key management. New bots should target Advanced Trade; ccxt and the major bot frameworks already support it. Institutional accounts on Coinbase Exchange or Prime keep their own APIs — if that is you, the hosting picture below is identical, only the endpoints differ.
Older bots written against the Pro API need migrating, not just re-pointing: authentication, endpoint paths, and some order semantics changed. Budget an afternoon for the port and test against small orders first. The upside of doing it on the VPS from the start is that your tested environment is the production environment — no 'works on my machine' surprises when you cut over.
Server Placement and Connection Stability
Coinbase's matching infrastructure runs in US cloud regions, so our Chicago (427 S La Salle) and New York (Equinix NY7) servers are the natural homes for a Coinbase bot — short domestic round-trips for order placement and market data. Chicago doubles as the right choice if you also run CME Bitcoin or Ether futures on a platform like NinjaTrader, keeping both stacks on one machine.
Connection stability matters more than raw speed for most Coinbase strategies. A websocket feed that silently drops and resyncs can miss fills and duplicate signals; a datacenter-grade port holds subscriptions open for weeks. Combine that with a bot registered to auto-start on boot and NTP-locked server time (signature timestamps drift-fail otherwise) and the operational failure modes are mostly gone.
Security and Plan Sizing
Coinbase API keys support IP allowlisting, and on a fixed-IP server it is the control worth the most: keys locked to your VPS address cannot be used from anywhere else. Keep withdrawal permission off trading keys, use query-only keys for dashboards, and secure the server itself — MFA on remote access, renamed admin account, minimal open ports. Our security guides below cover the server-side checklist.
Sizing follows the standard crypto-bot curve: Swing ($45/mo, 4 cores, 10GB RAM) runs one or two Python bots with headroom; Momentum ($85/mo, 8 cores, 20GB) fits Docker stacks with databases and dashboards or research jobs beside live trading; Flow ($175/mo, 16 cores, 40GB, 300GB NVMe Gen5) is for multi-venue operations and large historical datasets. All plans upgrade in place.
