Direct questions.
Specific answers.

No. Botkeep’s Free plan is designed without a periodic manual renewal timer. You do not need to return to the dashboard just to keep an assigned slot alive. Capacity, security, fair-use and Terms enforcement still apply.

No scheduled idle sleep is part of the Botkeep runtime model. A bot may still be restarted or temporarily unavailable because of maintenance, a crash, a deployment, exhausted resources, a security response or an infrastructure incident.

Not yet. The current dashboard is a frontend prototype with local mock data. Do not enter a real Discord token, private repository or production file. Live Botkeep API, provisioning, authentication, database and payment integrations are not connected.

No. “24/7” describes continuous operation without a commercial sleep timer or manual renewal ritual. It is not a promise of uninterrupted 100% availability. The beta has no uptime SLA unless a separate written agreement expressly provides one.

The production design records the process exit, keeps the relevant logs visible and retries with backoff so a broken bot cannot restart in a tight loop forever. Repeated failures move the bot into a crashed state for diagnosis instead of hiding the problem. The current panel only simulates this flow.

The intended GitHub workflow builds a new immutable revision first and replaces the healthy deployment only after the build succeeds. A failed build should leave the previous deployment available. This production deployment pipeline is not connected in the current prototype.

The underlying nodes are multi-tenant. Each bot receives an enforced allocation or cap rather than dedicated physical hardware. On Free, the intended per-bot limits are 512 MB RAM, 0.5 vCore and 1 GB storage. CPU remains a shared scheduling resource, so a displayed maximum is not a dedicated core or a guarantee of constant peak performance.

Free uses a fixed per-bot profile. Plus and Pro are designed to let you allocate RAM, CPU and storage to each bot while staying inside both the per-bot maximum and the total plan budget. The current panel demonstrates this validation locally; real provisioning is not active yet.

The published plan model includes one database on Free, two on Plus and three on Pro. Exact production database engines, regions, connection limits and backup behaviour will be documented before live database provisioning opens.

The plan model includes one backup per bot on Free, three on Plus and five on Pro, with intended retention of 7, 30 and 45 days respectively. A backup is a recovery aid, not permanent archival storage. Keep an independent copy of important code and data. The production restore workflow must be tested before these limits are represented as operational.

Botkeep is for supported Discord bot workloads that coexist safely on shared infrastructure. Fair use prevents one account or process from degrading the service for everyone else.

• No cryptocurrency mining, proof-of-work, proxies, VPN endpoints or unrelated distributed workloads.
• No spam, mass messaging, credential tools, malware, scanning, denial-of-service activity or platform abuse.
• Do not evade account, slot, resource, security, suspension or billing restrictions.
• Sustained abusive CPU, memory, network, build, process, disk or log usage may be limited or suspended.

Deletion may permanently remove the bot’s files, configuration, deployments and logs after the applicable retention window. The exact production grace period and backup-expiry schedule have not yet been approved and must be published before live hosting opens. In the current prototype, workspace data remains only in your browser until you reset it or delete the site’s local storage.

There is no periodic renewal requirement, but Botkeep may eventually apply a separately published inactivity policy to recover abandoned capacity. No production inactivity interval is currently approved. It will not be silently presented as a renewal timer, and any deletion mechanics must match the Terms and retention policy before launch.