Support for End-to-End HTTP/2 (gRPC) for Actor Container URLs
The Problem: I am building a high-performance Rust Actor using gRPC (Tonic) for internal data ingestion. The Load Balancer appears to downgrade the connection to HTTP/1.1 when communicating with the Actor container. This causes standard gRPC servers (like tonic in Rust or grpc-go) to crash immediately with Protocol Errors (HTTP 464) because they require an HTTP/2 transport layer.
The Request: Please add an option in the actor.json or Input configuration to enable End-to-End HTTP/2 (or gRPC mode) for the Container Web Server.
We can only share run info when the user has consented to us. This has been discussed elsewhere and you can review that discussion through Discord search.
My actor has received several negative reviews, and I believe the reviewers may be abusing the review system to damage its reputation. I reported this through your console interface, but even after a week, I still have not received any response.
I then contacted Ella on Discord for support, but I feel that her statements were inconsistent. You can check the screenshots below to see our conversation. Ella said that my actor had issues, but she could not tell me what those issues were, while my backend shows no errors at all.
Have the option to set the default RAM at which the actor runs in actor.json. We can alreade define maxMemoryMbytes and minMemoryMbytes. In my case I want to allow a high maxMemoryMbytes for 1% power users, for most users that's total overkill. So I would like to set the default at like 512. Currently it will always default to 4GB which is quite a lot if you're not doing browser automation.
It would be great if the "Actor Start" event could be displayed as a per-run-price on the pre-login agent page. $200/1000 looks a lot scarier then $0.20 per run. It already looks like this when you are in the post-login page
Feature request: It would be useful to have an option to hide or restrict Actor build logs, especially for published or shared Actors, since they may expose build configurations or sensitive data
Feature request: Request a more up-to-date version of https://apify.github.io/input-schema-editor-react for building INPUT_SCHEMA.json and ACTOR.json, and consider integrating it directly into console.apify.com
As a user, I’d like the ability to create private “issues.” I’ve had some trouble with my actor, and want to discuss with the developer, but I don’t want that discussion to be public. This seems like such an obvious feature that I assume the lack is intentional.
i would love to see a feature where we can make something like a "playlist" or a list of actors that we can share, maybe even like a workflow where anyone can build one and share a link, for example make a flow that uses an email extractor > email validator
Hey everyone! I'm running into an issue with the Apify Twitter Scraper and could use some help.
What I'm doing:
Trying to scrape X/Twitter data using Python.
Using our organization's paid API key for authentication.
The Problem: When I run the actor from my terminal, I get these "Free Plan" limit errors:
[Status message]: Users with the Free Plan can retrieve a maximum of 10 items... [Status message]: You cannot use the API with the Free Plan...
The Weird Part: Even though I'm using the org's paid key, the actor seems to be running under my personal Apify account (which is on the Free plan). When I check the Apify website, the run shows up in my account, not the organization's.
Has anyone else seen this? How do I force it to use the organization's context? Thanks!
The UX for PPE monetization could be improved. It is hard to see the default value for apify-actor-start. It will also be helpful if we can show here the $/1000
I’m not sure if my question fits this chat, but could someone explain why the arrangement of actors seems inconsistent, as shown in the attached image? Why is an actor with fewer users ranked above one with more users?
I’ve been thinking about how we, as Apify users, pay for actors and APIs, and I wanted to throw an idea out there. Right now, it feels like some projects fit best with subscription-style pricing (predictable monthly plans), while others really need pay-per-usage (since workloads can spike or stay small).
What if Apify offered a hybrid model?
A base monthly plan (so costs are predictable and budgets are easy). Extra usage-based charges when we go over the included quota.
This way: Casual users don’t get scared off by high upfront commitments. Power users still have room to scale. Apify also gets more stable recurring revenue instead of just spiky usage.
It feels like a win-win predictable for users, flexible for growth, and sustainable for Apify. Curious what others here think would you prefer a pure subscription, pay-as-you-go, or this hybrid approach?
I recently started publishing actors on Apify, and I believe my actors are very useful and relevant to many users. (Even though I only have a few users so far, the total profit after the first month has already exceeded $500.)
The issue is that my actors don’t rank very high since they were only just published. I think it would be great if there were a ranking section for “rising actors,” so that my actors — and others in a similar situation — could get more visibility.
With all due respect to industry standards but in pay per event model, we are charging per event. My event itself says that I will bill 2 USD per 1K records. While setting cost in Apify, I mentioned 2 USD only for thet event!
How come Apify displaying this as 2000 USD per 1K records!
This is freaking out customers! I have raised concern in Apify support since more than a week. I started saying to contact Apify support now to end customers as there is clearing nothing I can do about it as developer.
This pricing is wrongly displayed on public pages and inside Apify dashboard top bar
Scrape rightmove.co.uk to crawl millions of sale/rent real estate properties from United Kingdom. Our real estate scraper also lets you monitor specific...
Thinking about pricing, combining the (now legacy) rental model with PPR/PPE in the shape of a minimal monthly spend would be a key revenue unlock. I’d like to get the community’s thoughts on this.
This model works really well for me on Apify’s competitors, and I don’t think I’ll ever hit similar revenue numbers on Apify without a minimum spend per user.
Example from a competitor:
-Pricing starts at $10 for 1,000 events. After that, there are overages.
How this could look on Apify:
An actor can be set to PPE pricing, but he user always starts with $10/month, which includes 1,000 events. The $10 kicks in for the first paid request every month. “Overages” would follow the PPE pricing.
Fit with current plans:
Apify could keep the $39 / $199 / $999 pricing.
The free $5 plan stays without a minimum spend (basically a trial).
Example: on the $199 plan, the minimum spend could still be $10 but for 2,000 events (actor decides this).