99.99%
Average observed uptime
<5s
From upload to bot online
1 ms
Latency to the database
What you can put online on WhatsApp
Support, sales and internal automations, with the number connected through WhatsApp Web or the official Cloud API.
Support
Chatbots that connect to your CRM, answer common questions and hand the conversation to a person when needed.
Sales and orders
Catalog, cart recovery and order tracking in the same conversation.
Internal automation
Scheduled reports, system alerts and webhooks for your company's events.
Customer relationship
Follow-ups, reminders and confirmations for contacts who agreed to receive messages.
Your WhatsApp libraries, no changes needed
Connect through WhatsApp Web or Meta's official Cloud API: deploy with the library you already use, in Node.js or Python.
Baileys
Connects through the WhatsApp Web WebSocket, no browser. Keep the auth folder on the application disk to keep the session across restarts.
$npm i @whiskeysockets/baileyswhatsapp-web.js
Automates WhatsApp Web with a headless browser (Puppeteer). Simpler to start with, uses more RAM than Baileys.
$npm i whatsapp-web.jsWPPConnect
Several sessions in one application, with an active Brazilian community.
$npm i @wppconnect-team/wppconnect
Venom-Bot and any HTTP client for the official Cloud API 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 WhatsApp bot hosting
Questions about Baileys, WhatsApp Web.js, multi-session and the official Cloud API.
Can I host a WhatsApp bot with Baileys or WhatsApp Web.js?
Yes. Both run normally on Node.js in our environment. WPPConnect, Venom-Bot and Meta's official Cloud API also work.
Does the WhatsApp session persist between restarts?
Yes, as long as you save the auth directory (auth_info_baileys, tokens/, etc.) on the application's persistent disk. Square Cloud doesn't wipe working-directory files between restarts.
Can I run multiple instances / multi-session WhatsApp?
Yes. Each session can be its own container or a single multi-tenant application managing sessions internally. The infrastructure imposes no per-app session limit.
Is there a ban risk using unofficial WhatsApp libraries?
The risk lies with Meta, not the infrastructure. For critical use cases, we recommend the official Cloud API. Square Cloud doesn't interfere with the protocol.
Can I connect a WhatsApp bot to a CRM or e-commerce platform?
Yes, via HTTP/webhooks. Set up a squareweb.app subdomain with HTTPS in the application's Domains tab and use that URL to integrate with your stack (Shopify, RD Station, HubSpot, etc.).
How much RAM does a Baileys session use?
On average 80–180 MB per active session, depending on volume. For multiple sessions, pick a plan with proportional RAM or split across containers.