Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: make pay-per-result pricing explicit #1117

Merged
merged 3 commits into from
Jul 31, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,41 @@ At the end of each month, we will then add up all rental fees collected in that

## Pay-per-result pricing model {#pay-per-result-pricing-model}

If you make your Actor pay-per-result instead, you will set the price per 1,000 results, and users will be charged for your Actor solely based on the number of results your Actor produces. That's your _revenue_. The underlying [platform usage](https://docs.apify.com/platform/actors/running/usage-and-resources) the Actor generates, using the free plan unit pricing, is your _cost_. Your profit which is then paid to you is computed as 80% of the revenue minus the costs, i.e. `(0.8 * revenue) - costs = profit`. This profit is also paid out monthly.
If you make your Actor pay-per-result instead, you will set the price per 1,000 results, and users will be charged for your Actor solely based on the number of results your Actor produces. That's your _revenue_. The underlying [platform usage](https://docs.apify.com/platform/actors/running/usage-and-resources) the Actor generates, using the pay-per-result unit pricing defined below, is your _cost_. Your profit which is then paid to you is computed as 80% of the revenue minus the costs, i.e. `(0.8 * revenue) - costs = profit`. This profit is also paid out monthly.

### Pay-per-result unit pricing for cost computation

| Service | Unit price |
|---------------------------------|----------------------------|
| 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 |

:::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.

Suppose you host 50GB of data for 30 days. To calculate this in GB-hours:

- 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.

:::

Note that only revenue and cost for Apify customers on [paid plans](https://apify.com/pricing) 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.

Expand Down