Resources & billing
Choose vCPU, memory and storage for your app
Pick vCPU, memory and storage for your live environment, see the monthly price before you commit, and change resources later with a quick restart.
Updated 3 min read
You choose how much computing power your live environment gets: vCPU, memory and storage. You see the monthly price before creating the app, and you can change resources at any time. Staging is free and has a fixed size, so these choices only affect live.
Available sizes
- vCPU: 0.25, 0.5, 1, 2, 4 or 8.
- Memory: 256 MB, 512 MB, 1 GB, 2 GB, 4 GB, 8 GB or 16 GB.
- Storage: any whole number from 1 to 500 GB.
New apps start at 0.5 vCPU, 512 MB memory and 5 GB storage, which costs ₹255 per month plus GST.
What the price looks like
Live is priced at ₹300 per vCPU, ₹150 per GB of memory and ₹6 per GB of storage per month, billed by the hour. Some common sizes, before 18% GST:
- 0.25 vCPU, 256 MB, 1 GB: ₹75 + ₹37.50 + ₹6 = ₹118.50 per month.
- 0.5 vCPU, 512 MB, 5 GB: ₹150 + ₹75 + ₹30 = ₹255 per month.
- 1 vCPU, 1 GB, 10 GB: ₹300 + ₹150 + ₹60 = ₹510 per month.
- 2 vCPU, 2 GB, 20 GB: ₹600 + ₹300 + ₹120 = ₹1,020 per month.
- 4 vCPU, 8 GB, 50 GB: ₹1,200 + ₹1,200 + ₹300 = ₹2,700 per month.
See How billing works for hourly billing and GST, or the pricing page.
How to choose
- Memory is a hard limit. If your app uses more than you chose, the process is killed with an out-of-memory error (exit code 137). Check the Metrics tab and leave headroom. See App crashed: out of memory.
- vCPU is a limit too. If CPU sits near 100% in the Metrics tab and responses are slow, add vCPU.
- Storage is your persistent disk mounted at
/data. Size it for uploads, SQLite files and anything else you keep. See Persistent storage. - Small Node.js or Python APIs and static sites usually run well on 0.25 to 0.5 vCPU with 256 to 512 MB. Next.js and Django apps often want 1 GB of memory.
Change resources later
- 1
Open Settings, then Resources
Open the app and go to Settings, then Resources.
- 2
Pick new sizes
The new monthly price is shown as you change values.
- 3
Save
The change is applied to live with a quick restart of the current version. There is no rebuild.
If we are briefly short of capacity for a larger size, you see a friendly message asking you to try again shortly. If you have set a monthly spend limit, a change that would exceed it is held back, see Spend limits and invoices.
Frequently asked questions
Does changing resources rebuild my app?
No. Live restarts quickly with the current version and the new limits.
Can I change staging resources?
No. Staging is free with a fixed size of 0.25 vCPU, 256 MB and 1 GB.
What happens if my app uses more memory than I chose?
The process is stopped with an out-of-memory error (exit code 137). Increase memory in Settings, then Resources.
Related articles
- How billing works: hourly pricing with GST examplesDployHub bills live apps by the hour from simple monthly rates, adds 18% GST, and sends one invoice a month. Worked examples show exactly what you pay.
- Persistent storage: keep files safe under /dataEach live app gets persistent storage mounted at /data. Learn what survives deploys, how to store uploads and SQLite files, and how to add more space.
- App crashed out of memory (exit code 137)Exit code 137 means your app ran out of memory. Learn how to confirm it in metrics, add more RAM, and tune Node.js heap size or gunicorn workers to fit.
- Spend limits, invoices and paying with UPI or cardSet a monthly spend limit, add your GSTIN for a GST invoice, and pay monthly DployHub invoices online with cards, UPI or netbanking through Razorpay.