Aissue with current pricing model and storage
I’m building an actor that scrapes media (images, audio, and short videos) and stores them in key–value storage.
According to the monetization guide, storage costs are deducted from my revenue. This makes it hard to set a price, because storage usage is very dynamic: files can be very small or very large, and storage is billed by the hour while users might keep their files forever and never delete them.
I feel like I’m missing something here. Does anyone have an idea how to handle this?
According to the monetization guide, storage costs are deducted from my revenue. This makes it hard to set a price, because storage usage is very dynamic: files can be very small or very large, and storage is billed by the hour while users might keep their files forever and never delete them.
I feel like I’m missing something here. Does anyone have an idea how to handle this?
Solution
I believe that the only storage costs that affecting the developer are the costs related to the data stored in
the developer storagethe developer storage, and the costs related to the data an actor stores in the users storage only during the actor run for PPR and PPEthe data an actor stores in the users storage only during the actor run for PPR and PPE. For PPR and PPE the users pay for keeping the data in the storage after the run is finished, the price is not too much though.
