Where can I host a Discord bot for free?

Does a free Discord bot really stay online 24/7?

Yes. The bot holds its connection to Discord's gateway from a process that never sleeps, and it starts again on its own if it crashes. No keep-alive pinger and no web server to fake traffic.

Do I need a credit card or to renew anything?

No to both. A verified email is all it takes. There is no button to press every few days, no ads to watch, no coins to earn and no expiry date. The bot does not sleep when nobody is using it, and a working bot is never stopped for being quiet, even if nobody uses it for months. The one exception is a bot that has stopped working and sent nothing at all for 7 days: we stop it, email you, and Start runs it again.

• No credit card
• No renewals
• No ads
• No coins
• No sleep timer

Can I host a bot without writing any code?

Yes. Ten ready-made bots deploy from the panel with a bot token and at most one more field, and each has a page of its own. We build and maintain all ten in the open.

How do I deploy my own bot?

Point us at the repository, public or private, put DISCORD_TOKEN in the environment table and deploy. Every push to the branch redeploys the bot, and you can upload your code instead of using GitHub.

1. 1

   Point us at the repository

   Public or private: a private one connects through the FadeHost GitHub App in one click, with nothing to paste. No repository yet? Pick a ready-made bot and fill in one field.

2. 2

   Put the token in the environment

   The bot token and any other secrets go in the environment table, never in the code. We read the repository, install the dependencies, run your build if there is one and start the bot.

3. 3

   Push to ship

   Every push to the branch redeploys the bot. Watch it log in on the live console, see which commit is running, and roll back to an earlier one when a push goes wrong.

DISCORD_TOKEN=the token from discord.com/developers
CLIENT_ID=your application id
GUILD_ID=the server you test in

The token goes in the bot's environment table, never in the code. Your code reads it the usual way: process.env.DISCORD_TOKEN in Node.js, os.environ["DISCORD_TOKEN"] in Python.

Which languages and libraries work?

discord.js and discord.py are what most bots use, and nextcord, py-cord, JDA, Discord4J, Javacord, discordgo and arikawa run as they are. Node.js, Python, Bun, Deno, Go, Java, PHP and Ruby are detected from the repository.

• discord.py Python, with nextcord and py-cord
• discord.js Node.js and TypeScript
• JDA Java, with Discord4J and Javacord
• discordgo Go, with arikawa and disgo
• Music bots FFmpeg and Opus included
• Any repository Deploy on every push

What comes with every bot?

The whole panel, on the free plan too: the live console, the crash doctor, deploy history with rollback, environment variables, scheduled commands, the usage chart and the file manager.

• Push to deploy

  Connect the GitHub App once and every push to the branch reinstalls and restarts the bot. Private repositories work through the App too.

• Live console

  Everything the bot prints lands on its page as it happens, from the install output to the line your command handler logged a second ago.

• Crash doctor

  When a bot dies in a loop we read the logs and name the cause in plain words, usually within a minute: an invalid token, a privileged intent you never turned on, a package that is not installed.

• Environment variables

  DISCORD_TOKEN and the rest live in a table in the panel with their values masked. Edit, save once, and the bot restarts with the new values.

• Deploy history and rollback

  Every deploy is listed with its commit. Roll back pins the bot to an older one and redeploys it; unpin when the fix is pushed.

• Eight runtimes

  Node.js, Python, Bun, Deno, Go, Java, PHP and Ruby. discord.js and discord.py are the common two; we pick the runtime from what is in the repository.

• Voice built in

  FFmpeg, libopus and libsodium are in the runtime, so a voice or music bot needs nothing installed by hand. The ready-made music bot plays in a voice channel on any plan, the free one included.

• Scheduled commands

  Run a command inside the bot's container on a cron schedule: a nightly cleanup, a stats dump, a reminder job. Ten per bot, with the output kept.

• Usage chart

  CPU and memory over the last 24 hours on the bot's page, so a bot sitting at its memory limit is obvious before it starts restarting.

• MySQL database

  Paid bots get a MySQL database at no extra cost. One click creates it and the connection details land in the bot's environment.

• Four regions, one private network

  Europe West (France), Canada East (Montreal), USA West (Oregon) or Asia Pacific (Singapore). From there the bot reaches your databases and your game servers by name on your own private network.

• A web address

  Give the bot a name and it answers at https://name.fadehost.app over HTTPS: a dashboard, an OAuth2 redirect URL, a webhook receiver. It comes with every plan. Free addresses sleep when idle, paid ones stay awake.

• Dockerfile and Railpack builds

  Paid bots can build into an image instead of running from source: your Dockerfile, or Railpack when there is none.

• Backups

  A daily backup for $1 a month per bot, kept seven days, restored in one click.

• File manager

  See what the bot keeps under /data and change it from the panel: upload a config or a data file, edit, download, extract a zip, bring a file back from a backup, or connect with SFTP. Files from your repository stay read only. Every plan; on the free plan, transfers count toward its daily traffic.

• Always on, locked down

  Non-root, hard memory and CPU limits, and an automatic restart if the bot falls over. No sleep timer, no coins, nothing to renew.

How is it different from other free hosts?

More disk for your bot, and nothing to do to keep it running.

Checked on each host's own page on November 1, 2026.

And against paid hosts

What does it cost when the bot outgrows free?

From $2 a month, on the same bill as your game servers and other apps. Starter carries one bot with 1 GB and a full vCPU, a MySQL database and no traffic limit. Yearly is ten months for twelve.

Bots sit on the same subscription as your game servers and other apps. See every plan

What happens when something breaks?

The bot starts again on its own, and the crash doctor names the cause in plain words, most often an invalid token or a privileged intent that was never turned on. A push that breaks the bot rolls back in one click from its deploy history.

More questions

What a bot may and may not do is in the terms.

Read on

• Bot hosting documentationCreate a bot, the token, build and start commands, auto-deploy, databases, the limits per tier.
• Minecraft server botPut your server's player count and its start and stop commands in Discord.
• App hostingThe same runtime for web apps, APIs, workers and static sites.
• Free bot hosting, explainedWhat free means elsewhere, coins and sleep timers included, and what it means here.
• Host a discord.py botrequirements.txt, intents and tokens, and why keep_alive hacks can go.
• Host a discord.js botThe package.json contract, slash command registration, a production checklist.
• 24/7, and what that takesWhy sleeping dynos and keep-alive pingers fail a bot.
• Music botsThe ready-made music bot, what it plays, and when a music bot wants a paid plan or Lavalink.