TLDR:
All actors are split into two categories: Apify-managed and Community-managed.
Apify-managed actors are best for mainstream use cases (e.g., scraping Google). Community-managed have a wider range of available use cases (e.g., scraping local e-shops).
Apify takes full responsibility for the Apify-managed actors. Apify only hosts Community-managed actors.
Apify support is not responsible for addressing issues with Community actors or pushing new features. For this, use the Issues tab.
Apify Store has more than 1,000 ready-to-use actors. The first actors in Store (Google Maps Scraper, Web Scraper, Content Checker…) were created by the first Apifiers. As time went on and our platform evolved, we opened Apify Store to actors made by non-Apify developers, so their solutions can find their users more easily.
As you know, most scrapers need regular check-ups and maintenance in order to function and stay in good condition. So how do we maintain 1K+ of them? Well, first of all, we split them into two categories: those managed by Apify (about 1/10) and those managed by our talented Community Developers (about 9/10). Let’s look at the differences and expectations for each category:
| Apify-managed | Community-managed |
👀 Examples | Scrapers for well-known websites, e.g. Twitter Scraper | Scrapers for specific websites, e.g. Hepsiburada Product Scraper |
🧑💻 Ownership | Created and maintained by Apifiers. | Created and maintained by independent developers. |
🛠 Maintenance | All maintenance, updates, and bug fixes are done by Apifiers. | All maintenance, updates, and bug fixes are done by the developers that created and published these actors. Apify does not access their code, only hosts it. |
✨ Features and functionality | We are selective about which use cases have the best potential to become actors and serve the most users. Our best work is on mainstream actors. | Community-managed has a wider range of interests. This category is best for specific features and actors. You can suggest your actor ideas here. |
👷♀️ Reliability and testing | Subject to meticulous reliability testing to meet Apify's quality and performance standards. | Tests are strongly recommended to the developers but not enforced. |
☝️ Support and issues | Comprehensive support and responsibility for addressing posted issues. Direct communication with our users. | Issues and questions to be raised in the scraper's Issues tab. Apify cannot help with issues with Community actors. Store terms and conditions |
✍️ Documentation | Extensive documentation resources available. | Documentation resources available. |