Team, domains, backup and RAM: how they work on MyBotCloud

Published on 5 min read

Moderators with permissions, subdomains and custom domains, code backup and import, RAM, name and avatar: how each feature works, in the terminal and in VS Code.

Besides deploying your bot, MyBotCloud's developer tools (the mybotcloud CLI and the VS Code extension) let you adjust the RAM, rename the app, change its avatar, download the code, invite moderators and point domains at it. This guide explains what each feature does, how to use it and where the limits are, so nothing surprises you.

If you have not set the tools up yet, start with Deploy your bot from the terminal, VS Code or AI (MCP). Everything below works in the CLI and in the extension; in the extension, right-click an app in the sidebar or use the command palette (Ctrl+Shift+P, type mybotcloud).

What the sidebar shows

The VS Code sidebar shows:

  • Account: plan, the plan's RAM (shared among your bots) and how many applications you use.
  • My applications: a green (up), gray (paused) or red (crashed) cloud. Expand it for state, memory, CPU, disk and network, uptime, restarts, language and avatar.
  • Team apps: only shown if someone invited you as a moderator. They show the owner and your permissions.
  • Domains: your subdomains and custom domains, with the state of each.

In the CLI, mybotcloud status shows the same numbers: state, memory, CPU, disk and network.

RAM

mybotcloud ram 80

Your plan's RAM is a pool shared by your bots (Start: 100 MB, Pulse: 1 GB, Orbit: 2 GB). You choose each bot's RAM between 64 MB and what is left of the pool (what your other bots already hold is not available). The server checks it again: a value outside that range is refused and nothing changes. The change applies to the container immediately and sticks across future deploys.

Two honest notes:

  • Lowering one bot's RAM frees RAM in the pool for your other bots; the plan's price does not change.
  • Below what your bot needs, the system stops it for lack of memory. If the bot crashes, raise it again.

mybotcloud.config is updated too (ram), and deploy stops warning that the value was ignored.

Name and avatar

mybotcloud rename "My New Bot"
mybotcloud avatar https://example.com/logo.png
mybotcloud avatar --clear

The name is 2 to 40 characters (letters, digits, space, _ and -). Since the folder is tied to the app by the id written in mybotcloud.config, renaming does not create another app.

The avatar is an https URL of up to 300 characters. The platform only stores the address: it never downloads the image.

Backup and import

mybotcloud backup my-backup.zip          # downloads the code now
mybotcloud backup create                  # stores a snapshot on the platform
mybotcloud backup list
mybotcloud backup get 12 my-backup.zip    # downloads snapshot #12 (without a number, the newest)
mybotcloud import my-folder --app my-bot

The backup is the app's code in a ZIP. It does not include dependencies (node_modules, venv; a deploy reinstalls them) or environment variables: they live outside the code folder and their values never leave the container.

The platform keeps the 3 newest backups of each app; creating a fourth deletes the oldest. Deleting the app deletes its backups.

Import downloads that ZIP into a folder and creates a mybotcloud.config already tied to the app (no key inside). It is for continuing your work on another machine: in an empty folder, all you need is the key in MYBOTCLOUD_KEY and the app name.

For safety:

  • import never writes outside the destination folder;
  • it does not overwrite files that already exist (use --force if you want to);
  • the backup's content is treated as untrusted: only regular files, no links, no absolute paths or .., with a size limit (20 MB).

If the app is paused, start it first: the code is read from inside the container.

Team (moderators)

mybotcloud team add [email protected] --perms control,env
mybotcloud team list
mybotcloud team set [email protected] --perms deploy
mybotcloud team remove [email protected]

The owner invites a person by their account e-mail (they must have signed in to mybotcloud at least once). Each app accepts up to 5 moderators. The permissions:

PermissionWhat it allows
viewSee status and logs (always included)
controlStart, stop and restart
deployUpdate the code and download the backup
envSee the names and change the variables

Only the owner can delete the app, rename it, change RAM and avatar, and manage the team and domains. If a moderator tries, they get a message saying they lack permission. Someone with no access at all gets "not found", as if the app did not exist.

The moderator sees the app under Team apps (in the extension) or in the API's app list, with the owner's e-mail and their permissions, and can leave the team whenever they want. A team app does not count toward their app quota. If the owner deletes the app, the access ends with it.

Domains

mybotcloud domains add --sub mybot --port 3000
mybotcloud domains add --host bot.example.com --port 3000
mybotcloud domains verify bot.example.com
mybotcloud domains list

There are two kinds:

  • Platform subdomain (mybot.<platform domain>): active right away. First come, first served. Use 3 to 30 letters, digits and hyphens; names such as admin, api and www are reserved.
  • Custom domain (bot.example.com): starts pending. To prove the domain is yours, create a DNS TXT record at _mybotcloud-challenge.bot.example.com with the value mbc-verify=... (the command shows the exact value) and run domains verify. DNS propagation can take a few minutes; if it was not found yet, try again.

The port is the one your app listens on, between 1024 and 65535. How many domains you can have depends on the plan (Start: 1; Pulse: 5; Orbit: 10).

Important: HTTP routing is not enabled yet. Today the platform registers and verifies domains, but it does not serve HTTP/HTTPS traffic for them yet. The list shows that notice. That step depends on infrastructure (a reverse proxy with HTTPS and wildcard DNS) that will be enabled separately. For Discord bots, which only make outbound connections, nothing changes.

In the VS Code extension

What to doCommand
Change RAMChange the RAM
Rename / avatarRename the app / Set the avatar
Store a backup on the platformBackup Application (the 3 newest are kept)
Download a backupDownload Backup
Bring it to a folderImport the app's code into a folder
ModeratorsManage team (moderators): add, change permissions, remove
DomainsAdd a domain, Verify domain (DNS), Remove domain

When you add a custom domain, the extension shows the TXT record you must create. Each app's context menu shows only what your role allows: team apps do not show the owner-only actions.

What does not exist (yet)

  • Remote terminal: there is none. Opening a shell inside the containers is a security decision the project has postponed. Not even the MCP server, which serves AI assistants, has a command-execution tool.
  • Serving HTTP on domains: see the notice above.
  • Team and domain screens in the web dashboard: for now they are CLI, extension and API only.

Still stuck? Open a ticket in Support in the dashboard.

  • team
  • domains
  • backup
  • vscode
  • cli

← Back to the blog