Aero BotsHOSTING
How the PM2 runtime, instances, logs and backups work.
PROCESS MODEL
Every product runs as its own PM2 process with an isolated instance directory containing config.json, messages.json, the bot database, transcripts and logs.
AUTOMATIC RECOVERY
The watchdog restarts crashed processes within seconds. Restart limits and a memory ceiling prevent restart loops from consuming the node.
LOGS & DIAGNOSIS
stdout and stderr are merged into the live log viewer. Known failure patterns are detected automatically and explained with a fix – invalid token, disallowed intents, missing permissions or an expired license.
BACKUPS
A snapshot of the configuration is taken before every save, restore and update. Backups can be inspected as raw JSON, restored or deleted.
UPDATES
Template updates are published as releases. Installing one backs up the configuration, merges new keys into your files, switches the version and restarts the process if it was running.
LICENSE ENFORCEMENT
When a runtime expires the process is stopped and the product is marked as expired. Redeeming another key extends it and the bot can be started again.