Documentation
1. How BotVault works
Choose a bot, choose a duration, pay in BVC, fill in the configuration form, and deploy. BotVault selects healthy infrastructure, creates the application, applies your encrypted configuration and streams the build back to you.
2. app.json configuration
Every approved repository is analysed for app.json, Procfile, package.json, requirements.txt and Dockerfile. Detected environment variables become a form: required fields are enforced, defaults are pre-filled, and secret fields are masked after saving.
3. Coins and subscriptions
Deployments reserve BVC first. On success the reservation is spent; on failure it is released back to your wallet. Each deployment carries a subscription with expiry, renewal price, reminders at 7/3/1 days and an administrator-defined grace period.
4. Recovery and migration
BotVault stores its own deployment snapshot — repository, branch, version, runtime and encrypted configuration — so a bot can be rebuilt even if the original hosting account becomes unavailable. Where the underlying provider blocks access to an application, BotVault reports the limitation instead of promising recovery.