Proper Plan Storage Scaling

Background:
Currently, each plans only have 100 GB storage (soft) limit, whether it’s a:
- 4 GB RAM plan that wouldn’t expect to use that much storage, or
- 32 GB RAM plan that expect having multiple huge worlds and/or data to take up more than 100 GB of the disk.

Problem:
Sure, they can request more storage limit by opening a ticket, but that’s a lot of extra steps just to get your basic storage needs. Reduce friction for users.

Some people also expect to see proper storage limit on the plans before buying it, if they don’t see the limit, they can get suspicious and turns away from buying. Transparency builds trust.

Solution:
We should implement proper scaling so it’s FAIR for each plan as they require different storage needs.

Example:
- 4 GB RAM plan get 60 GB storage
- 32 GB RAM plan get 480 GB storage

Pros:
- Fair resource allocation across plans

- Better user experience (no support tickets)

- Higher trust and transparency

- Improved sales and conversion

- Lower support workload
- Easier backend planning

Note:
- Make sure legacy plans are handled gracefully. Either grandfather them in or provide easy migration paths for users.
- You might also want to do the same with the CPU count. Be transparent about it so users can trust you more.