Your bot.
A place to run.
Bot hosting for Node.js and Python projects. Keep process controls, logs and environment settings together in a separate application panel.
Compare bot plansPre-launch plans · one project per service
your community.
Give your project a home.
A public website or a background process? Start with what you’re running, then choose its resources.
For the bot your community relies on.
Pre-launch preview. Hardware, protection and backup specifications are proposed and will be confirmed before hosting goes live.
Help me chooseCompare every detailResources, access and what’s included in bots & workers.
| Your plan | |||
|---|---|---|---|
| CPU allocation | 1 shared vCPU | 1 shared vCPU | 2 shared vCPU |
| Memory | 1 GB DDR5 | 2 GB DDR5 | 4 GB DDR5 |
| NVMe storage | 5 GB | 10 GB | 20 GB |
| Monthly outbound transfer | 50 GB | 100 GB | 250 GB |
| Runtime | Node.js or Python background process | Node.js or Python background process | Node.js or Python background process |
| Projects per plan | 1 isolated project | 1 isolated project | 1 isolated project |
| Root access | No; project controls only | No; project controls only | No; project controls only |
| Backup slots | 3 | 3 | 3 |
| DDoS protection | Network-level filtering | Network-level filtering | Network-level filtering |
| Location | United States | United States | United States |
| Monthly price | $3.00 | $5.00 | $9.00 |
One bot or worker per plan. Public website endpoints and a custom domain are not included; use a Website plan for a public webhook endpoint. 1 Gbps shared uplink. Transfer is a proposed monthly outbound allowance; overage handling will be confirmed before launch. Protection covers L3 / L4 filtering by the infrastructure provider; no attack-capacity or uptime guarantee is specified.
Pre-launch preview · ordering opens when hosting is ready.
One bot or worker per plan. Public website endpoints and a custom domain are not included; use a Website plan for a public webhook endpoint.
Choose the right kind of process.
A bot usually waits for messages or runs background work. A website answers HTTP requests. Pick the hosting model your application actually needs.
What does a bot hosting plan run?
One isolated bot or background application per service. The planned runtimes are Node.js and Python. Choose resources for your own code, libraries and workload; a plan does not create or write the bot for you.
Can I host a Discord or Telegram bot?
The bot panel is designed for persistent processes, including Discord clients and Telegram bots using polling. You supply the application and its token. Customer workloads need an active service and a connected hosting node before they can run.
Does my bot get a public website address?
A background bot is different from an HTTP application. If your bot receives webhooks or needs a public API endpoint, compare website hosting or a self-managed VPS. Check networking requirements before ordering.
How should I store a bot token?
Keep tokens in the project's environment settings, not in source code or logs. If a token is exposed, revoke it with its provider and replace it in the panel. A restart does not undo a leaked credential.
Can I host more than one project?
Each bot hosting service covers one project. A saved draft does not include runtime resources, and access to the panel does not remove service limits. Additional independently hosted projects need their own eligible services.
Is bot hosting available now?
Bot hosting is in pre-launch preparation. The panel and proposed plans can be explored, but runtime operation depends on separate hosting nodes. Check current service availability before paying.