- A project you want to run
- A resource budget within your plan
- A verified Botkeep account
1. Applications and bots
The catalog covers Node.js, Python, Java, PHP, Go, Rust, C++, Lua/Luvit and Bun. Node.js with Nodemon is a tooling profile, not a separate language. Choose a blank workspace, GitHub repository or ZIP; set a start command appropriate to your project.
Discord remains a supported use case alongside web applications, APIs and workers. A Discord token is not required for a general application.
2. Databases
Choose Redis, PostgreSQL or MySQL from the available profiles. Each database occupies one server slot, with no separate database quota. Allocated RAM, CPU and storage draw from the same account pool as other servers.
The Database tab provides connection details and TLS settings. The Data tab lets you browse and edit data. The creation form checks your allocation against the remaining plan budget. Small allocations may be insufficient for your data or queries. MongoDB is not enabled.
3. Websites and services
Static sites serve HTML, CSS and JavaScript. PHP sites need a managed web runtime. Lavalink is an audio service for bot clients; Uptime Kuma is a monitoring application.
A service profile is not a guarantee that every application fits in the smallest allocation. Use Domains for HTTPS routing, Network for the assigned port and the service instructions for its required configuration.
4. One shared resource pool
A single workload can use the entire plan, or you can divide it between several workloads. Stopped instances keep their allocation. Reduce an allocation or remove an instance to free resources.
Compare current resource budgets in the plan catalogue. Your assigned limits and remaining capacity are shown in Plans and billing in the panel. The API validates your assigned plan before accepting changes.
5. Before going online
- Select an enabled runtime version and review your startup command.
- For HTTP access, listen on 0.0.0.0 and SERVER_PORT, then configure Domains.
- Create backups in the panel and keep an independent copy of important data. Stop databases before backup or restore.
- Store secrets in Environment, never in public repositories or logs.