Skip to main content
Botify uses MongoDB Atlas as its cloud backend for account storage, remote commands, logging, and multi-node coordination. The connection uses built-in credentials embedded in the application — no user configuration required.

​
Collections Overview

CollectionPurpose
botify_nodesPC registration, 30-second heartbeats, online/offline status, active accounts list
botify_cookies.ROBLOSECURITY cookies scoped per-user + per-PC (unique index)
botify_commandsRemote command queue — polled by each node every few seconds
botify_logsCloud log storage scoped per PC name and owner ID
botify_licensesLicense keys with plan types (standard / enterprise) and HWID bindings
botify_command_historyAudit trail for all executed remote commands
botify_enterprise_clustersEnterprise Cluster node registration and deployment tracking
botify_screenshotsRemote screenshot storage as Base64-encoded PNG
updatesAuto-update version manifest records
update_historyFull history of all published updates

​
Collection Details

​
botify_nodes

Registers each PC running Botify and tracks live status.
  • Document created or updated on every app launch
  • Heartbeat: last_seen field updated every 30 seconds
  • Nodes missing heartbeats for 90+ seconds are marked offline
FieldDescription
pc_nameMachine label from Settings
owner_idDiscord User ID of the account owner
statusonline or offline
active_accountsList of currently running bot usernames
command_token32-byte random hex token for remote command auth
last_seenTimestamp of most recent heartbeat

​
botify_cookies

Stores all .ROBLOSECURITY cookies with per-user and per-PC scoping.
  • Unique index: (owner_id, pc_name, username) — prevents cross-user cookie leakage
  • Fields include: cookie value, username, age timestamp, validation status

​
botify_commands

The remote command queue. Botify polls this collection every few seconds for commands addressed to its node.
  • Each command must include a valid auth_token matching the node’s command_token
  • Optionally verified against owner_id
  • Executed commands are moved to botify_command_history

​
botify_licenses

Stores license key records for legacy key activation.
FieldDescription
keyThe license key string
planstandard or enterprise
hwidHardware ID bound on first activation
expiryExpiration date (if applicable)

​
botify_enterprise_clusters

Tracks PCs registered under Enterprise Cluster deployments.
FieldDescription
cluster_idUnique identifier for the cluster
server_codeERLC private server code for this cluster
nodesList of PC names in this cluster
statusDeployment status

​
Data Flow Diagram

Botify App (your PC)
    │
    ├── Heartbeat every 30s ──────────► botify_nodes
    ├── Account CRUD ─────────────────► botify_cookies
    ├── Log writes ───────────────────► botify_logs
    ├── Polls for commands ◄──────────── botify_commands
    ├── Command results ──────────────► botify_command_history
    └── Screenshot uploads ───────────► botify_screenshots

​
Security Model

LayerImplementation
Database CredentialsEmbedded in the Botify binary — users never configure this
Command AuthPer-node 32-byte random command_token — commands without it are silently rejected
Cookie Scopingowner_id + pc_name unique index — nodes cannot read other users’ cookies
Local EncryptionOptional DPAPI encryption for account_store.json
Discord OAuthGuild role verification ("Client" role required) on every login