Running a bot on your phone or PC vs hosting it

Almost every Discord bot starts on its author's computer. You run node index.js, the bot comes online, and the job looks done. Then you close the laptop, the power blinks, or Windows restarts to update, and the bot vanishes from your server.

That is not a bug in your code. A bot is a process that has to run all the time, and that process only exists while the machine running it is on. There are three common ways to keep it alive: your PC, your phone with Termux, and hosting.

Why does the bot go offline when the PC turns off?#

The bot opens a WebSocket connection to the Discord Gateway and keeps it alive with periodic messages called heartbeats. According to the Gateway documentation, if heartbeats are not acknowledged the connection is treated as dead, and the client should close it and try to reconnect.

When the PC shuts down, the process dies with it. When it sleeps, the CPU stops and the network often drops, so the connection closes. In both cases Discord shows the bot as offline, and no command gets an answer until it is back.

Reconnecting is automatic only when the process is still alive (a short network drop, for example). If the process was terminated, someone has to start it again. Other causes are covered in why a Discord bot goes offline.

What is it like to run the bot on a PC?#

It is the simplest option and the best for development. You get logs in the terminal, restart with Ctrl+C, and debug easily.

For continuous use it has clear limits:

• Power: the PC must stay on and be set to never sleep.
• Network: internet outages or an IP change drop the connection for a while.
• Restarts: system updates reboot the machine, and the bot does not come back unless you set up pm2 or a startup task.
• Shared use: the bot competes for CPU and memory with whatever else you do on the machine.

Even with pm2 and automatic startup, availability depends on your home, not on the bot. The power cost of this option is in how much it costs to host a Discord bot.

Can you run the bot on a phone with Termux?#

On Android, yes. Termux is a terminal emulator with a Linux environment, and you can install Node.js or Python in it. The basic flow:

pkg update
pkg install nodejs git
git clone https://github.com/your-user/your-bot.git
cd your-bot
npm install
node index.js

Keep the token in an environment variable or a .env file outside the repository, never in the code.

Three things matter:

1. Where to install from: the project README recommends the F-Droid or GitHub builds. The Google Play build is experimental, has missing functionality and bugs, and the Termux app and its plugins must be installed from the same source.
2. Android 12 or later: the project itself warns that Termux may be unstable, because Android kills "phantom" processes beyond 32 (the limit covers all apps combined) and processes using excessive CPU. The symptom is a Process completed (signal 9) message in the terminal.
3. Battery saving: the system may suspend the app in the background. Turning off battery optimization and using the Termux wake lock helps but does not guarantee anything: there is a user report on Android 15 of processes killed anyway. Results vary by device and Android version.

A phone also has a practical limit: it must stay charging, on Wi-Fi, and not be used for anything else. It suits testing or a throwaway bot, not a community that expects answers at any hour.

What changes when you host the bot?#

Hosting means running the same code on a machine that is not yours, powered on all the time, in a datacenter with redundant power and network. The process no longer depends on your PC, your phone or your internet.

In practice:

• The bot stays online when you shut down your computer.
• Automatic restart after a crash usually comes built in; at home you would have to set it up yourself.
• Logs are reachable from anywhere.
• You pick the process memory instead of sharing your device's.

In exchange there is a monthly fee, and you deploy instead of running node index.js locally. There are two families: a VPS, where you administer the operating system, and hosting platforms, where you only upload code. To compare what each includes, see how to keep a Discord bot online 24/7. Typical limits of no-cost tiers are in limits of no-cost bot hosting.

PC, phone or hosting: which one?#

There is no universal winner. Pick like this:

• Writing and testing the bot: use the PC.
• Just experimenting or learning away from the computer: a phone with Termux works, knowing it may drop.
• The bot serves people who expect answers at any hour: host it. Downtime usually costs more in complaints than the monthly fee.

How to do this on Square Cloud#

On Square Cloud the bot leaves your PC and your phone and runs in a container, in a Tier 3 datacenter with redundant power. Closing the laptop, a power cut at home or Android killing Termux no longer takes it down. The container stays on, with no sleep mode, and the application is never suspended for lack of traffic. If the process exits with an error, automatic restart, which is on by default for dashboard deploys, brings the bot back.

Swapping a local node index.js for a deploy is a short step. You upload the project as a ZIP in the dashboard, or use the CLI, GitHub or the VS Code extension, and the dashboard detects the main file and generates the configuration. The token goes in as an application environment variable, and the dashboard can import your .env. Your phone stays useful, now for following real-time logs in the mobile app instead of holding up the process.

A bot is a background application with a 256 MB RAM minimum, and it works with discord.js, discord.py, JDA, Discord.Net or any Gateway library. Hobby costs R$12.49 per month for 1 GB of RAM, paid by Pix or card. See what is included on Discord bot hosting and compare plans on pricing.