docs: merge monetization content in platform docs #1476
Conversation
merge of monetization content from Academy to Platform docs move images adjustments to formatting
TC-MO
added
documentation
| 1. **Free**: Users can run the Actor without any additional charges beyond the platform usage costs generated by the Actor. | ||
| 2. **Rental**: Users pay for the platform usage costs. However, after a trial period, they need to pay a flat monthly fee to the developer to continue using the Actor. | ||
| 3. **Pay per result**: Users don't pay for the platform usage costs. Instead, they pay the developer based on the number of results produced by the Actor. | ||
| 4. **Pay per event**: Users don't pay for the platform usage cost the Actor generates. Instead, they pay based on specific events defined by the developer, such as generating a single result or starting the Actor. |
There was a problem hiding this comment.
Suggestion: Please, add that the events are triggered programatically from the Actor source code.
| | Request queue - reads | **$0.004** / 1,000 reads | | ||
| | Request queue - writes | **$0.02** / 1,000 writes | | ||
|
|
||
| Only revenue and cost for Apify customers on paid plans are taken into consideration when computing your profit. Users on free plans are not reflected there, although you can see statistics about the potential revenue of users that are currently on free plans in Actor Insights in the Apify Console. |
There was a problem hiding this comment.
although you can see statistics about the potential revenue of users that are currently on free plans in Actor Insights in the Apify Console This is no longer true, let's remove this part please.
| | Compute unit | **$0.4** / CU | | ||
| | Residential proxies | **$13** / GB | | ||
| | SERPs proxy | **$3** / 1,000 SERPs | | ||
| | Data transfer - external | **$0.20** / GB | | ||
| | Data transfer - internal | **$0.05** / GB | | ||
| | Dataset - timed storage | **$1.00** / 1,000 GB-hours | | ||
| | Dataset - reads | **$0.0004** / 1,000 reads | | ||
| | Dataset - writes | **$0.005** / 1,000 writes | | ||
| | Key-value store - timed storage | **$1.00** / 1,000 GB-hours | | ||
| | Key-value store - reads | **$0.005** / 1,000 reads | | ||
| | Key-value store - writes | **$0.05** / 1,000 writes | | ||
| | Key-value store - lists | **$0.05** / 1,000 lists | | ||
| | Request queue - timed storage | **$4.00** / 1,000 GB-hours | | ||
| | Request queue - reads | **$0.004** / 1,000 reads | | ||
| | Request queue - writes | **$0.02** / 1,000 writes | |
There was a problem hiding this comment.
Please, let's remove the whole time storage part, it's not relevant here.
| :::note What are Gigabyte-hours? | ||
|
|
||
| Gigabyte-hours (GB-hours) are a unit of measurement used to quantify data storage and processing capacity over time. To calculate GB-hours, multiply the amount of data in gigabytes by the number of hours it's stored or processed. | ||
|
|
||
| For example, if you host 50GB of data for 30 days: | ||
|
|
||
| - Convert days to hours: _30 * 24 = 720_ | ||
| - Multiply data size by hours: _50 * 720 = 36,000_ | ||
|
|
||
| This means that storing 50 GB of data for 30 days results in 36,000 GB-hours. | ||
| ::: |
There was a problem hiding this comment.
This is not relevant and can be removed.
There was a problem hiding this comment.
This is an old screenshot. Let's wait until PPE is release (probably tmrw) and put it new screenshot.
There was a problem hiding this comment.
I think we can release this is as is, and PPE and screenshot will be updated & added in a separate PR
| - Actor Analytics for usage statistics | ||
|
|
||
|  | ||
|
|
||
| - Individual Actor Insights for detailed performance metrics | ||
|
|
||
|  |
There was a problem hiding this comment.
There is only single Actor analytics section now, uner Actors > Developement > Analytics. You can select any subset of Actors you want to see analytics for there.
There was a problem hiding this comment.
I've added new screenshot & updated where the information can be found, but there are two issues
- I don't have any paid actors or used by others so it looks super bare even with blurring the data
- Screenshot is pretty long to try and capture the whole analytics page, maybe we can skip it here and just let people know where they can find it?
There was a problem hiding this comment.
Yep, we can just redirect to the correct page. In the future, the analytics functionalities would benefit from it's own dedicated page in docs.
There was a problem hiding this comment.
I'll remove the screenshot for now then
merge of monetization content from Academy to Platform docs
move images
adjustments to formatting
fix typos