EchoAuthBothosting

Hosting for Discord bots that stay up.

Upload your bot or point us at a Git repository. It runs in an isolated container with a real console, SFTP access, and a process that restarts itself when it dies.

Create an account Sign in

No card required to start.

console — example-bot
$ python bot.py
20:01:18 INFO logging in with token
20:01:19 INFO gateway: shard 0 up
20:01:19 ready as example-bot#0000
20:01:19 synced 24 commands
20:04:52 WARN rate limited, retry 1.4s
20:04:54 INFO gateway: session resumed
uptime 9d 23h · mem 54.6 MiB

What you get

Everything below is part of every plan. There is no tier where we take the console away.

A console, not a log tail

Read stdout as it happens and type commands back into the process. Stack traces show up while you are still looking at them.

SFTP on port 2022

Connect VS Code, WinSCP, or plain sftp. Edit files in place instead of re-uploading a zip after every fix.

Git-based deploys

Give us a repository and a branch. Enable auto-update and the bot pulls the latest commit each time it boots.

Dependencies handled

A requirements.txt or package.json is installed before your entry point runs. Extra packages can be listed per server.

Restarts without you

If the process exits, it comes back. Scheduled restarts and backups run on a cron you control.

Honest resource limits

CPU, memory, disk, and network are metered and graphed. When a bot leaks memory you will see it before Discord does.

Runtimes

Pick a version when you create the server, change it later from the startup tab.

Node.js
22 LTS2426 — for discord.js and anything on npm
Python
3.103.113.123.133.14 — for discord.py, nextcord, hikari
Entry point
Any file you name — bot.py, index.js, or a bash script you provide
Storage
Persistent volume per bot. SQLite and flat files survive restarts and reinstalls

Deploying

Two paths in, both take about a minute.

  1. Create the server

    Choose Node.js or Python and a version. The container is provisioned and the image pulled before you reach the console.

  2. Get your code in

    Drag files into the file manager, connect over SFTP, or set a Git address and branch and let the install script clone it.

  3. Add the token and start

    Put your bot token in an environment variable or config file, hit start, and watch it connect in the console.

Put your bot somewhere it belongs.

Set up an account and have something running before your coffee gets cold.

Create an account Sign in