I strongly urge Apify to reconsider the forced migration and instead allow developers to choose the pricing model that fits their specific use-case. Forcing a PPE model on a stable, 4-year-old business is counterproductive for several reasons: Reliability Over Volume: My Trustpilot scraper has a 99.2% success rate because I deliberately throttle requests and use residential proxies to bypass anti-bot detection. PPE punishes this stability. If I have to absorb compute and proxy costs, maintaining this level of quality becomes a massive financial risk. Broken Migration Tools: The PPE calculator is incorrectly reporting my data, claiming a 50% customer loss. In reality, my Actor is seeing consistent MoM growth with well over 100+ active paying customers. This high volume already generates significant monthly platform revenue for Apify (excluding rental fees), yet your tools fail to reflect this reality. Financial Impact: Moving to PPE introduces a 20% commission on my total revenue and forces me to manage complex resource costs. This is a huge burden for a developer, especially when I’ve just adjusted my rental pricing on April 10th to reflect the high maintenance required for this specific target. My/our shared customers prioritize predictability and stability. While PPE might work for new, low-maintenance projects, the rental model is what has made this Actor successful over the last 4 years and most of my customers happily pay as long as it is stable. I will have to make cost cutting and introduce potential less stability to absorb compute and proxy costs with a PPE model. Actor: https://apify.com/casper11515/trustpilot-reviews-scraper