Limits and fair use

Plan resources

• Free: 256 MB memory, 1 GB disk, 0.25 vCPU
• Starter: 512 MB memory, 2 GB disk, 0.5 vCPU
• Pro: 1 GB memory, 4 GB disk, 1 vCPU
• Plus: 2 GB memory, 8 GB disk, 1.5 vCPU

Disk covers your code, installed dependencies, and anything the bot writes. CPU is a share of a core, and at the limit the bot is throttled. Each server also has a process limit: 128 on Free, 256 on Starter, 512 on Pro, and 512 on Plus. Full details are on the pricing page.

One free server per person

Each account and each email address can have one free server. Claiming requires a verified email address and works with any sign-in method. Banned accounts can't claim.

Network

• Outbound mail ports 25, 465, and 587 are blocked. If your bot sends email, use your mail provider's HTTP API.
• Ports commonly used by mining pools are blocked.
• New outbound connections are rate-limited per server. Free allows 10 new connections a second, with bursts up to 40 and 50 open at once. Paid plans allow 30 a second, with bursts up to 100 and 200 open at once.
• Inbound traffic to the ports assigned to your server is allowed, so the bot can listen there, for example for webhooks. Ports per server: Free 1, Starter 1, Pro 1, Plus 2.
• Free servers share a free-tier address. Paid plans use a separate shared address with higher connection limits.

What gets a bot stopped

• A crash loop: 5 crashes within 10 minutes. The owner gets an email. Fix the error, then start it again.
• Sustained CPU: 90% or more of the plan's CPU limit for 30 minutes. The bot is stopped, not deleted.
• Going over memory: the process is killed. See troubleshooting.

What gets a server suspended

• Self-bot libraries, which automate a user account instead of a bot account.
• Crypto miners.
• Nukers, raid tools, and token grabbers.

Heavily obfuscated code can be flagged for review. The full rules are in the acceptable use policy.