Prepare your Node.js or Python bot for hosting.

A useful bot-hosting request describes how the project runs, what it depends on and how many processes it needs. Prepare those details before choosing resources, and keep bot tokens out of the request.

Published by Sift Hosting ·

Server racks illuminated by green lights

Identify the runtime and startup command

Record whether the project uses Node.js or Python, the runtime version it has been tested with, and the command that starts it. “It is a Discord bot” is not enough information to reproduce the environment. Include the entry file or script name and any build step that must run first.

Different Discord applications also work differently. A Gateway-based bot maintains a connection and handles events; an application receiving interactions over HTTP has different requirements. Describe the architecture you have rather than assuming every bot needs the same hosting setup.

Make the dependencies reproducible

For Node.js, keep the package manifest and the project’s lockfile with the code. Explain which package-manager command you use and whether the project needs a separate build. For Python, identify the dependency file or packaging setup and recreate the environment from that information.

Python virtual environments isolate a project’s packages and are designed to be recreated, not copied between machines. Describe the environment in the request rather than sending a folder full of installed packages. Sift confirms the supported runtime and deployment details with the order; this guide does not imply a particular control panel or automatic install feature.

Keep the bot token out of public messages

Treat the Discord bot token as a secret. Do not paste it into Sift’s notes box, a public repository, a support screenshot or a copied plan request. Share public project requirements first and agree a suitable method for any private deployment details with Sift.

If a token has been exposed, replace it through the Discord Developer Portal and update the bot’s private configuration. Request only the application permissions and intents the bot needs. Hosting a bot does not grant it extra Discord permissions or remove Discord’s own requirements.

Compare processes as well as memory

Sift’s bot plans list memory, shared CPU, NVMe storage and a bot-process allowance. A separate worker or independently running bot can affect how many processes your project needs. Explain those components before choosing a tier, especially if the project includes more than one bot.

Describe any database, external API, persistent files or additional service the bot depends on. Do not assume those services are bundled into the hosting price. Sift can review the requirements and confirm what the accepted order includes.

  • Spark: 1 GB RAM; 1 shared vCPU; 10 GB NVMe storage; 1 bot process.
  • Orbit: 2 GB RAM; 2 shared vCPU; 20 GB NVMe storage; Up to 3 bot processes.
  • Fleet: 4 GB RAM; 4 shared vCPU; 40 GB NVMe storage; Up to 6 bot processes.

Your bot-hosting request checklist

Use the listed plan or request a custom quote, select the currency you want to be billed in, and choose a preferred region. The copied request captures the selected price and your notes; it does not deploy the bot or create an online payment.

  • Runtime version and public library/framework names
  • Entry file, startup command and any build step
  • Number of separately running bots or workers
  • Storage and external-service requirements
  • Preferred region and a public project link if available; no tokens or passwords

Documentation and further reading

For your Sift order, confirm the software, resources and region with us before paying.