Skip to content
Tarisu Limited

Choosing between Node.js and Python for your bot

Updated: 7 November 2026 75 views

Bot hosting runs your bot in a container on the game panel, under one runtime chosen at the order screen. There are sixteen to choose from: Discord in Node.js, Python, Bun, Deno, Elixir, Go, Java, Lua, Ruby or Rust, and Telegram, Matrix and Slack in Python or Node.js. For most people the real question is still the first two, which is what the rest of this answers.

Which one

This is decided by the code you already have, not by preference. Look at the bot's source:

  • A package.json, and imports of discord.js. That is Node.js.
  • A requirements.txt or .py files, and imports of discord or nextcord. That is Python.

If you are writing from scratch and genuinely have no preference, pick the language you already know. Both run a Discord bot perfectly well on these plans, and the library ecosystems for each are mature. Neither is faster in any way you will notice for a bot that spends most of its life waiting on the gateway.

What to upload

Use the file manager in the game panel, or upload a zip and extract it there.

  • Node.js: your source, package.json and package-lock.json. Do not upload node_modules: the dependencies are installed on the container. Make sure the start script in package.json points at the right file.
  • Python: your source and a requirements.txt listing the packages you import. Set the startup file to the one that actually starts the bot.

Keep the bot token out of the files you upload. Put it in an environment variable on the container and read it from there. A token committed to a repository or left in a source file is the most common way a bot gets taken over.

Resources

The four plans differ in memory, CPU share and disk: 512 MB, 1 GB, 2 GB or 4 GB of memory, with 5, 8, 15 or 25 GB of disk and a CPU allowance of 50%, 75%, 100% or 200%, where 100% is one core. A typical command bot runs comfortably in the smallest; music and anything that processes audio or images is what pushes memory up. Watch the usage in the panel for a day or two before deciding you need more.

Changing the runtime later

You can switch to any of the sixteen runtimes from the service page in the client area. Be careful with it: changing the runtime rebuilds the container, and everything on it is deleted: your files, your settings and your logs. It cannot be recovered.

So decide before you upload, keep your source in version control, and if you do have to switch, take a backup and download it first.

We use strictly necessary cookies to keep you signed in and remember your preferences. We would also like to measure how the site is used, but only with your agreement. Read our privacy policy