Get the project ready to run
In Node.js, a start script in package.json. In Python, a requirements.txt and the main file. The bot token is not hardcoded: the code reads it from an environment variable.
Discord bots
Your Discord bot online 24 hours a day, without your PC.
Send the project as a zip or through GitHub. Vertra Cloud runs the bot in an isolated container, restarts it when it crashes and shows live logs in the dashboard.
The problem
A bot running on your PC goes down when your PC does.
Running the bot on your own machine works until the day the laptop closes, the power goes out or the system restarts itself to update.
The computer shuts down
A bot hosted at home goes offline together with the machine. In a cloud container, the process keeps running with your computer closed.
The process crashes
An unhandled error takes the bot down. Here the container is restarted on its own, with a longer wait after each attempt, and the reason shows up in the logs.
Updating becomes a ritual
Copying files, stopping the process and starting it again by hand is where things break. You send the zip or the repository, and the platform installs the dependencies and starts the bot.
What you get
Infrastructure built for bots, not for websites.
A bot is a background process that connects to Discord on its own. Vertra Cloud treats your application exactly that way.
Bot-type application
Runs in the background, with no HTTP port and no subdomain. If you later need an endpoint, such as a webhook, you can publish the application on the web.
Automatic restarts
When the bot crashes because of an error, the platform restarts it. If it crashes several times in a row within a few minutes, restarts are paused and the dashboard explains why.
Live logs
Follow the bot's console in real time, next to usage metrics, and see right away what happened after a deploy.
Isolated container
Each application runs in its own container, separate from the others, with the memory you choose.
Token out of the code
Environment variables live in the dashboard, encrypted at rest. The platform does not read a .env file, so the bot token goes in the variables.
A database next to it
Managed PostgreSQL, MongoDB, Redis and MySQL, with mandatory TLS, to store server settings, queues and whatever else the bot needs.
From code to a live bot
Five steps to get the bot online.
The path is the same for discord.js and discord.py. Only the main file and the way dependencies are installed change.
Send the project
Under New project, upload a .zip (up to 100 MB, and the dashboard already strips node_modules and venv first) or import a GitHub repository, private ones included. The CLI and the VS Code extension deploy too.
Set it up as a Bot
Check the main file, language, version and memory the platform detected. In the network step, leave web publishing off: that is what makes the application run as a bot.
Add the token
Under Environment variables, create DISCORD_TOKEN with the token from the Developer Portal. If the bot uses privileged intents, enable them in the Developer Portal as well.
Deploy and check the log
The platform installs the dependencies, starts the container and shows the live log. When your bot's login line appears, it is already online in your server.
FAQ
Frequently asked questions
Does my bot go down when I turn off my PC?
Not if it is hosted. On Vertra Cloud the bot runs in a cloud container, so closing the laptop, shutting down the computer or losing your home internet does not take it down. It keeps running until you stop the application or until an error takes it down, in which case automatic restart kicks in.
Do I need to open a port or have a website to host a bot?
No. The bot opens its own connection to Discord and does not need to receive traffic. A Bot-type application runs in the background, with no HTTP port and no subdomain.
What happens if the bot crashes or throws an error?
The platform restarts the container automatically, with a longer wait after each attempt. Errors that a restart cannot fix (a missing module, a syntax error, running out of memory) and a normal process exit are not restarted. If the bot crashes several times in a row within a few minutes, automatic restarts are paused and the dashboard shows the reason; starting the bot again by hand resets the count.
Where do I put the bot token?
In the project's environment variables, in the dashboard. They are encrypted at rest and reach the container at startup. The platform does not read a .env file, so the code must read the token from the environment: process.env in Node.js, os.environ in Python.
Which languages and libraries work?
The platform runs 13 languages, including JavaScript, TypeScript, Python, Go, Rust, Java, C# (.NET) and Elixir. For Discord the most common choices are discord.js on Node.js and discord.py on Python, but any library that runs on one of those languages works.
Do I need a plan to host the bot?
Creating applications requires an active plan on the account. Prices and what each plan includes are on the pricing page, which is always the up-to-date source.