Control your server network.
Sign in with the owner access key configured on your control-plane server.
Your session stays in this tab's memory only. It is not saved to browser storage.Server command center
One owner. Every registered Linux and Oracle server.
Minimum free RAM before new work
This is the RAM that must remain available on a server before a new bot is assigned or started. It is not the server's total RAM. We use Linux MemAvailable, the same figure shown under the available column in free -h. The default is 256 MiB (about 0.25 GiB). Existing bots are not stopped when RAM drops below this limit.
Loading current policy…
Registered servers
Live telemetry from each server agent
Registered customers
Account details and assigned bot. Passwords and credentials are never displayed.
Assign bots to online servers
Only you can choose which registered server hosts each customer bot.
Connect another server to your network
You need a Linux server you control (for example, an Oracle Cloud VM). It must have a public HTTPS route to this control-plane API, Node.js 22+, SSH access and enough free RAM. This console does not rent or create cloud servers for you.
To look for a no-cost VM, check Oracle Cloud Free Tier. Oracle lists Always Free AMD micro VMs (1 GB RAM) and Ampere A1 resources (up to 2 OCPUs / 12 GB RAM total, subject to tenancy limits and capacity). Use only shapes explicitly marked Always Free. See the official Linux VM setup guide.
- Click Generate one-time ticket above and keep the ticket secret. It expires in 10 minutes.
- SSH into the new Linux VM. Clone the public repository over HTTPS with
git clone -b feature/hasa-bot-network-foundation https://github.com/coc338781-tech/Hasa_2_bot.gitand enter the repository directory. No GitHub token or private key is needed for this public repository. Never put a personal access token in the clone URL. Do not copy your production WhatsApp auth_info folder. - Run the telemetry agent installer:
cd network/agent && sudo bash install-systemd.sh. - Edit
/etc/hasa-agent/agent.envwithsudo nano /etc/hasa-agent/agent.env: set the real HTTPS API URL and paste the one-time ticket. Start it withsudo systemctl enable --now hasa-agent. Once enrolled, remove the ticket from that file and restart the service. - Confirm the new server appears as online here and its RAM / disk values are updating.
- Prepare and mount an encrypted volume at
/var/lib/hasa-worker/sessions. Install the separate worker only after verifying encryption:cd network/worker && sudo env HASA_CONFIRM_ENCRYPTED_VOLUME=true bash install-systemd.sh. Start it withsudo systemctl enable --now hasa-worker. Wait until the Worker column in this console says online and its session count is updating. - When the worker is healthy, choose the customer bot under Assign bots to online servers and select this server. Only the owner can do this.
Never paste SSH private keys, enrollment tickets, agent tokens, pairing codes or WhatsApp session files into this website or a chat. Do not enrol the production bot's existing auth_info directory as a customer instance.