Built in US East, close to Discord's API
Your bot has 3 seconds to respond to a slash command, so distance to Discord matters. Every plan runs in US East Ashburn, close to Discord's API, on AMD Ryzen 9 hardware.
Why it matters
The 3-second interaction deadline
When a user triggers a slash command, Discord sends an HTTP POST to your bot. You have exactly 3 seconds to respond with an HTTP 200 OK. If your bot needs to query a database, call an AI model, or process data, every millisecond of network latency eats into that window.
Network path
Your bot → Cloudflare Anycast Edge
WebSocket (Gateway)
Space-Node US East → Discord's REST API
HTTPS (REST API)
Running close to Discord's API keeps the network part of each REST call short, so more of your 3-second window is left for your bot's own logic.
Datacenter
US East, Ashburn, Virginia
One location, chosen because it is close to Discord's API. Every bot, every plan, same hardware.
US East
Ashburn, Virginia
Close to Discord's API
A bot hosted in Europe or Asia sits further from Discord's API, so every REST call travels further before your bot has done any work. Being close to Discord's API is the whole reason US East exists as a location.
DDoS protection
Attack traffic is filtered before it reaches your bot's container. On by default, no configuration needed.
Container isolation
Each bot runs in its own isolated container with its own CPU and RAM limits, separate from other customers' bots.
Automatic restart
On Growth and Pro, monitoring spots a crash and restarts your bot process automatically, without you logging in.
Feel the difference yourself
Deploy a bot on US East infrastructure. Growth starts at €0.50/mo.
Free Starter is not available right now