BOT MINI
- CPU
- E5v4
- Memory
- 512 MB
- Disk
- 5 GB SSD
- Backup
- Weekly
- Location
$0.99/mo
Choose ServerYour bot keeps running when your laptop does not. Discord, Telegram, Matrix and Slack, four plans in Istanbul (IST), 512 MB to 4 GB of RAM and 50% to 200% CPU, built in seconds when your payment clears and run from a web panel: console, file manager, restart.
Every package includes discord, Telegram, Matrix and Slack, web panel access, reserved CPU and memory.
$0.99/mo
Choose Server$1.75/mo
Choose Server$2.99/mo
Choose Server$5.49/mo
Choose ServerChoose the size, then which network you are writing for: Discord, Telegram, Matrix or Slack, and in which language. An invoice is created for the order.
Pay with one of the methods offered at checkout. Your order is accepted once the payment is recorded.
It arrives with the runtime you chose already installed, and the panel login is sent to the e-mail address on your account.
Put the files in through the panel file manager or over SFTP, enter your token or access key, set the start command and press start. The console shows the output live.
A bot on your laptop stops when the laptop closes, updates or drops its connection. Moving the process onto a machine in Istanbul that is always on is the whole purchase, and it is the same purchase whether the bot answers in a Discord guild, a Telegram group, a Matrix room or a Slack channel.
The container is built when your payment clears, in seconds, and everything after that happens in the web panel: upload the files, set the start command, watch the console, restart.
No shell, no root and no operating system of your own; that is the trade, and a VPS is where you go if you need the other side of it.
One question decides it: is the bot holding things in memory or chewing on audio.
Member caches for busy guilds and a database write on every message are memory problems, and they grow with how active the rooms are rather than with how many there are. Voice and music are processor problems, because the stream is decoded and re-encoded for as long as someone is listening, and they only arise on the Discord side.
The plans run 512 MB to 4 GB of RAM and 50% to 200% CPU, where 100% is one core, so pick the side you are on and read down that column.
Logging actions, handing out levels and roles, writing to a database on almost every message. The commonest job on the Discord and Telegram side, and a memory one.
Polling a feed or an API and posting into a Telegram or Slack channel costs little memory, just a process that stays connected.
Bridges, archivers and welcome bots connect to your homeserver. The default is matrix.org and you can point it at your own address.
Audio is bound by processor rather than memory, so size these on the CPU percentage. A Discord-side job.
Discord in Node.js, Python, Bun, Deno, Elixir, Go, Java, Lua, Ruby and Rust; Telegram, Matrix and Slack in Python and Node.js. All sixteen are rebuild targets on all four sizes, so the language is a decision you can change: rebuild from the panel and your files stay where they are, only the interpreter underneath is replaced.
One database per plan, created with the container. Levels, warnings, scores and seen-at timestamps belong in it rather than in a JSON file that a crash can truncate halfway through a write.
One allocation on every plan, which is what a webhook listener, an OAuth callback or a health endpoint needs. A bot that only opens outbound connections never touches it, and loses nothing by having it.
When the process exits the container starts it again, and the console keeps the output from before it went. A crash loop shows up in the panel as a crash loop, rather than as a quiet absence somebody reports to you hours later.
50% is half a Xeon E5v4 core, 100% is one and 200% is two. Text commands rarely reach the first of those; voice and audio encoding is the work that does, and it is the reason to read this line before the memory one.
One location, so there is no choice to get wrong. For a community that is mostly in Turkey, the round trip to the gateway and back is a local one, and the smallest plan costs less than the domain the bot is named after.
Could not find your answer? Write to us and we will route your question to the right team.
Still unansweredFour: Discord, Telegram, Matrix and Slack. They run in the same container, in the same panel, at the same price, and the only difference is the runtime you pick at the order screen. Telegram, Matrix and Slack come in Python and Node.js; Discord comes in ten languages.
A bot that answers a command and forgets it runs in tens of megabytes, so for that one the smallest plan is not a starter tier, it is the right tier. What moves a bot up this list is holding things: a member cache for busy guilds, a queue, an audio stream. Moving up later keeps your files and your runtime, so starting small costs nothing but the move.