How to choose the right pod size for your app
Choose Base, M, L or XL by what your app needs, then check its RAM and CPU use with real tasks.
App Cities · 1 min · Updated
Pod sizes describe capacity. They do not change your app's features. A bigger pod gives its services more room to work. It does not fix broken code. Start by listing what runs together, then test with the tasks your users will do.
The steps
- Count all services, not just the frontend. Your backend, database and background jobs share the pod's RAM and CPU.
- Use the project check as a starting point. A suggested size is not a promise that every workload will fit.
- Test a full task, such as saving a file or running a report. Watch memory use and response time while it runs.
- If you need more room, review the size change and its price. Approve it yourself before your AI applies it.
A common question
Should I buy XL right away?
Not by default. Test a smaller size that fits your services, then increase it when the measurements show a need.
Ready to try your project?
Prepare your project, check the prices and choose how you want to deploy.