99.99%
Average observed uptime
<5s
From upload to bot online
1 ms
Latency to the database
What you can put online on Discord
From one server's moderation bot to a public bot in thousands of servers, the deploy is the same.
Games and economies
Economies, inventories, battles and quests, with the data in a database in the same datacenter.
Moderation
Spam filters, anti-raid, audit logs and warnings running all the time, without your computer switched on.
Community and tickets
Auto roles, welcome messages, support tickets and polls for servers of any size.
Music and voice
Audio bots in voice channels, with FFmpeg in the container and Lavalink as a separate application in the same account.
Your Discord libraries, no changes needed
Deploy the bot as it is. The most used Node.js and Python libraries run with no extra configuration.
discord.js
The most used Node.js library, with full API coverage, TypeScript types and voice through @discordjs/voice.
$npm i discord.jsSapphire
A framework on top of discord.js that organizes commands, listeners and preconditions in files. Good for large bots with several people on the code.
$npm i @sapphire/frameworkEris
A lean library used by large bots that need fine control over cache and memory.
$npm i eris
JDA, Discord.Net, DSharpPlus, Serenity, discordgo and any library that uses the Discord Gateway run too.
From code to a live bot in three steps
No Dockerfile and no server to configure. You choose where the code comes from.
- 1
Send the code
Connect a GitHub repository, use the CLI or upload a .zip in the dashboard.
- 2
Configure your way
The dashboard generates squarecloud.app from the runtime, memory and entry file you pick. Or write your own at the project root.
- 3
Bot online
The container starts in under 5 seconds. With GitHub connected, every push to the configured branch updates the files and restarts the bot.
Everything your bot needs to stay online
Included with every Discord, Telegram or WhatsApp bot. When a feature depends on the plan, the card says which one.
Always on
The bot's container runs nonstop: it never sleeps on inactivity and restarts automatically if the process exits.
- No sleep on inactivity
- Automatic process restart
- 99.99% average observed uptime
Isolated container
Each bot runs in its own container, with its own vCPU, RAM and disk. You pick the memory at deploy and change it when you need to.
- Its own vCPU, RAM and disk
- Memory you set
Live logs and status
Follow the bot's console in real time and see whether it is online, restarting or stopped.
- Console in the dashboard
- Logs in the CLI and VS Code
- Status and logs in the mobile app
Usage metrics
CPU, RAM and network for each bot, collected every 5 minutes and kept for 24 hours, so you know when it needs more memory.
- CPU, RAM and network per application
- 24-hour history
- On applications with 512 MB of RAM or more
Snapshots
Take a snapshot before a risky update and restore the bot if something goes wrong.
- Manual snapshots on every plan
- Daily snapshots from Pro, kept for 7 days
- The latest one stays available for up to 30 days
HTTPS for webhooks
Turn on web publishing and the bot gets a squareweb.app subdomain with TLS, ready for Telegram webhooks, the WhatsApp Cloud API or Discord interactions.
- squareweb.app subdomain with HTTPS
- TLS certificate issued and renewed automatically
- Custom domain from Standard
Keep your bot's data in the same datacenter
MongoDB, Redis, PostgreSQL and MySQL Hosting in the same dashboard as your applications, with 1 ms average connection latency. Available from the Standard plan.
A plan for every stage of your project
Start small and scale when you need to, with no loyalty contracts.
Hobby
To validate ideas, bots and personal projects
From R$12.49/mo ≈ $2.25
- 1 GB RAM
- 1 vCPU
- Up to 4 projects
- Scales up to 2 GB on the same plan
Standard
RecommendedFor production, with databases and custom domains
From R$44.99/mo ≈ $8.10
- 4 GB RAM
- 4 vCPU
- Up to 16 projects
- Scales up to 8 GB on the same plan
Pro
For high scale, with daily application snapshots and advanced analytics
From R$124.99/mo ≈ $22.50
- 12 GB RAM
- 6 vCPU
- Up to 48 projects
- Scales up to 24 GB on the same plan
4.9 out of 5 · 402 reviews on Google + TrustpilotTrustpilot
Frequently asked questions about Discord bot hosting
Get answers about discord.js, discord.py, sharding, intents and more.
Does Square Cloud support discord.js and discord.py?
Yes, both. We also support JDA, DSharpPlus, Serenity (Rust), discordgo (Go) and any official or community library that uses Discord's Gateway.
Can I host a music bot with FFmpeg and Lavalink?
Yes. FFmpeg comes pre-installed in the containers and you can run a Lavalink instance in the same account as a separate application.
How does sharding work for bots in many servers?
Set shardCount in your application and you can scale vertically (more RAM) or run shards in separate containers. From the Standard plan up, Redis Hosting can coordinate the shards.
Do slash commands have high latency?
No. The bot runs in an always-on container with no cold starts and a persistent Gateway connection. With a responsive handler, slash commands answer well within Discord's 3s timeout. The datacenter has a direct route to Discord's edges, with ~30 ms average latency to the Gateway.
Do I need to configure privileged intents in the Square Cloud panel?
No. Intents are configured in the Discord Developer Portal for your bot. Square Cloud only hosts the process, and nothing on our side blocks intents.
Can I use Voice Gateway / voice channels?
Yes. Outbound UDP and WebSocket are open. FFmpeg + @discordjs/voice or discord.py[voice] work without extra configuration.
How do I deploy a Discord bot to production?
Connect your repository via Personal Access Token + webhook in the dashboard. On every push to the configured branch, your application files are updated and the container restarts automatically. Live logs and metrics appear right in the panel.