DocsBest practices

Choosing the right plan

How to size RAM and CPU without overpaying.

Best practices 5 min read

Most projects need far less than people expect. The right approach is to start small, measure for a few days, then adjust. Changing plan takes seconds and never requires a redeploy.

Typical needs

ProjectUsual memorySuggested start
Small Discord bot (1–50 servers)80–200 MBFree or Starter
Discord bot with music / Lavalink400 MB – 1 GBPro
Small REST API100–300 MBHobby or Launch
API with heavy traffic500 MB – 2 GBGrowth, with 2 instances
Queue worker / cron jobs100–400 MBFree or Worker

Signs you should upgrade

  • Memory stays above 80% of your limit for long periods.
  • Your service is restarted with an Out of memory message in the logs.
  • CPU is pinned at 100% and response times climb.
  • You need a feature only available on higher plans, such as custom domains or multiple instances.

Signs you can downgrade

If memory stays under 40% and CPU under 20% for a week, you are very likely on a plan that is too large. Drop one level and keep an eye on the Metrics tab.

Check the Metrics tab over a full week before deciding. Weekend and evening traffic often looks very different from a Tuesday morning.
Was this article helpful?