Frequently asked questions

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 workload may still be restarted or temporarily unavailable because of maintenance, a crash, a deployment, exhausted resources, a security response or an infrastructure incident.

Yes, the authenticated panel deploys enabled application, database and service profiles. Configure secrets in Environment and connect private repositories through the GitHub App. Domains supports aliases and DNS-verified custom domains with HTTPS. Paid plans are purchased through Stripe with single payments and manual renewal, not automatic subscriptions.

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 panel shows the observed process state and Console output. Check the startup command, environment and dependencies before starting again. Files and resource allocations remain reserved; an API acknowledgement alone does not mean your application is ready.

Redeploy reapplies managed configuration and startup dependencies to existing files, then restarts the server. It does not pull GitHub changes or reinstall the server. Use the GitHub tab to update source files. These operations can interrupt service; they are not zero-downtime deployments.

The underlying nodes are multi-tenant. Standard Free includes one server, 512 MB RAM, 50% CPU (0.5 vCore) and 1 GB storage. CPU is shared, not a dedicated core or a guarantee of constant peak performance. This offer is for new signups; existing accounts keep their assigned conditions.

Yes, within your assigned plan. A single workload can use the entire plan budget, or you can divide RAM, CPU and storage between workloads. Resources reserved for other workloads, including stopped workloads, count against the total. To reassign them, reduce an allocation or delete a workload. The API checks the shared budget before accepting a deployment or resource change.

Each database uses one normal server slot and shares the plan’s RAM, CPU and storage. There is no additional database-count limit: you can fill your available slots with databases within the shared resource budget. Small allocations may not suit every engine or workload. MariaDB (MySQL-compatible), MySQL, PostgreSQL and Redis are available; MongoDB is not enabled.

Create, download and restore backups from the panel, within your assigned plan limits. Stop databases before backing them up and stop any server before restoring. Only completed, successful backups are recovery points. Automatic deletion by age is not currently enabled. Keep an independent copy of important data.

Botkeep is for supported applications, workloads, websites, databases and services 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.

Server deletion removes its hosted files and configuration after infrastructure confirms removal. Export anything you need first: deleting browser storage does not delete your account or server. Backup expiry is not automatic at present. For account erasure and remaining retention obligations, contact support and consult the Privacy Policy.

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