How to host a Discord bot 24/7

What hosting a bot actually means

A Discord bot is just a program that has to keep running. Whatever host you pick, its only real job is to keep that process alive 24/7, restart it if it crashes, and not charge you a fortune for the privilege. You don't need root on a full server for that — you need somewhere that runs your bot's container and keeps it up. That's what Sinkron does: you hand it your bot as a container image, it runs it around the clock with automatic restarts, and you pay by the second of runtime instead of a flat monthly server bill.

Two kinds of Discord bot — it changes what you need

Worth knowing which one you have, because it changes how you run it:

• Gateway bots (most bots). Your bot opens a connection out to Discord and listens for events — messages, slash commands, reactions. It doesn't receive inbound web traffic, so you run a single always-on instance. On Sinkron that's one runner that never sleeps; the win is "no server to babysit" and "pay only while it's up," not horizontal scaling.
• HTTP-interaction bots and bots with a dashboard. If you use Discord's HTTP interactions endpoint, or your bot ships a web dashboard or admin panel, that part serves inbound traffic — and it benefits from Sinkron's load-balanced HTTPS URL across several machines, so the dashboard stays up even if one machine drops.

Host it in four steps

1. Put your bot in a container

Most bot frameworks containerise in a few lines — a small Dockerfile that installs your dependencies and runs your start command (python bot.py, node index.js, and so on). If you already build an image, point Sinkron at it; if you don't, the quickstart walks through it. Any language or library works — discord.py, discord.js, serenity, whatever you wrote it in.

2. Add a little funding

Top up a balance by card or USDC — no subscription, no minimum. You spend it down as the bot runs, and whatever you don't use stays yours.

3. Deploy it

Point Sinkron at your image, give it a small CPU/RAM footprint (a bot needs very little), and for a gateway bot set a single runner. It comes up within seconds — no server to provision, no reverse proxy, no certificates.

4. It stays up — you pay only while it runs

Sinkron keeps the bot running with health checks and automatic restarts if it crashes. Billing is per second; if your balance runs low we email you first, and if it hits zero the bot stops so you're never billed past your deposit. Stop it yourself any time and the cost drops to zero.

Is it free? What it costs

Honest answer: not literally free — anything that runs 24/7 costs something to keep online, and hosts advertising "free bot hosting" usually sleep your bot, throttle it, or quietly shut down. But a bot's footprint is tiny, so on Sinkron it runs for pennies an hour, you only pay while it's actually running, and it's free to sign up and look around. Because you pay for a small footprint by the second instead of a flat monthly box, it usually works out cheaper than the standard $5 VPS — which bills you around the clock whether the bot is busy or idle. See how that compares in Sinkron vs. a $5 VPS, or how pricing works.

When a plain VPS is still the better call

We'd rather be honest than oversell. Reach for a VPS instead if your bot writes a lot to persistent local disk and you don't want to use an external database, needs full OS-level control, or you're running a large sharded bot you manage as fixed infrastructure. Sinkron is the cheaper, lower-effort choice for the common case: a small-to-medium bot you just want online and don't want to babysit. For the wider picture, see how to host a small always-on app cheaply.