The Apify web scraping, data extraction, and automation platform
Apify Web scraping and AI agent platformReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
453 reviews
from
External reviews are not included in the AWS star rating for the product.
Pre-Built Actors and a Clean API That Just Works
What do you like best about the product?
Pre-built actors. Clean API. Just works.
What do you dislike about the product?
No middle ground between cap & upgrade..
What problems is the product solving and how is that benefiting you?
Cuts time-to-proposal from hours to mins.
Great Scraping with Affordable Pricing but You Have to Do Some Trial and Error
What do you like best about the product?
The thing I like the most about Apify is that it's not just a tool, it's a proper community platform. Anyone can build their own actors and anyone can use them, which means theres almost always an actor available for whatever you want to scrape. The scrapers are really good and I've been able to get data that I genuinely didn't think was possible to pull without hiring a developer. The pricing is also not that bad compared to other tools in this space and on top of that they give you $5 free credits every month which is a nice bonus, it covers small tasks comfortably. For what it does, I really like it and find great value in Apify.
P.S. The UI is interesting, like it's easy and complex at the same time. It looks a bit complex but you can figure it all out in 5-10 mins.
P.S. The UI is interesting, like it's easy and complex at the same time. It looks a bit complex but you can figure it all out in 5-10 mins.
What do you dislike about the product?
There's just one thing I dislike about Apify which is that the quality of actors varies a lot depending on the developer who built them. So I always have to spend some time finding the right actor/scraper for what I want to do and then test one or two before I can actually start using one. Sometimes an actor looks great in documentation and then the results are off, or it breaks on certain websites. Also the pricing per actor can vary depending on who built it, so its not always predictable. You kind of have to do some test runs and keep a budget aside for that which is a bit annoying when your trying to move fast.
What problems is the product solving and how is that benefiting you?
I use it mainly for scraping data that I need for research and lead generation. Before Apify I either had to do things manually or use specific scrapers which only scraped some websites like one for google map, another for instagram or contact a developer to build something custom. It was very slow, painfully hard and expensive process. With Apify I can just find an actor, run it, and get the data I need within minutes most of the time. The $5 monthly free credit also means for lighter use cases I basically don't have to paying anything. It's saved me a lot of time and the community aspect means the platform keeps growing with more actors being added all the time. Not perfect, but for the price point its hard to complain too much.
Incredible, Affordable Structured Data Scraping with Easy Integrations
What do you like best about the product?
This is an incredible way to get various types of structured data. I use it to get information about leads, do social media research, general scraping, and a lot more. Cheap and super convenient.
It has a very simple and straightforward interface and I can easily integrate it with platforms like make.com or Claude Code.
It has a very simple and straightforward interface and I can easily integrate it with platforms like make.com or Claude Code.
What do you dislike about the product?
The actors in the store vary in quality. Some are better than others, and when it comes to general scraping, you need a bit of know-how to get the best results. It also takes some time to learn how to configure everything properly.
What problems is the product solving and how is that benefiting you?
I use it to scrape entire LinkedIn accounts, scrape websites into structured tables, and enrich leads—really, for any ad hoc task I have. It’s almost always the easiest and simplest way to get things done quickly.
Huge App Store of Scrapers Makes Data Extraction Fast and Affordable
What do you like best about the product?
The number of scrapers available in their app store is great, and it lets us avoid worrying about writing code so we can start extracting data right away.
With a small amount of money we can extract the data that costs us couple of thousands of dollar to extract.
With a small amount of money we can extract the data that costs us couple of thousands of dollar to extract.
What do you dislike about the product?
It lacks the scraper for outside of U.S websites.
What problems is the product solving and how is that benefiting you?
With the strength of the Apify Store and its community, we were able to get a great kickoff and avoid having to start everything from scratch.
Fast Scrapers with Powerful Built-In Infrastructure
What do you like best about the product?
What I like most is the speed to get a working scraper running. Prebuilt actors plus built-in infrastructure (proxies, scheduling, scaling) remove most of the setup work we used to handle manually.
What do you dislike about the product?
The main downsides are the learning curve for custom Actors and the cost becoming less predictable at scale (especially with heavy runs, proxies, and multiple workflows).
What problems is the product solving and how is that benefiting you?
Apify solves the problem of building and maintaining web scrapers in-house.
Instead of spending time writing and constantly fixing scraping infrastructure, we can rely on managed actors and built-in scaling. This reduces engineering effort, speeds up data collection, and makes scraping pipelines more stable.
Instead of spending time writing and constantly fixing scraping infrastructure, we can rely on managed actors and built-in scaling. This reduces engineering effort, speeds up data collection, and makes scraping pipelines more stable.
Robust Scrapers, Easy Integrations, and Consistently Strong Performance
What do you like best about the product?
Apify has an incredibly robust network of apps and scrapers to choose from. Its ease of use, affordability, and the simplicity of setting up integrations feel unparalleled, which helps drive successful deployments and consistently strong performance.
What do you dislike about the product?
The inconsistency of the pricing between the individual products. It feels quite arbitrary
What problems is the product solving and how is that benefiting you?
We use Apify constantly. The depth and breadth of the service offerings helps us create agents and bots with relative ease. The ability to test and iterate to ensure strong performance is a blessing and overall learning curve is quite slim.
The scraping infrastructure layer that small teams can't afford to build themselves
What do you like best about the product?
The actor marketplace is the standout feature — instead of building custom crawlers for every source type, there's almost always an actor that handles the platform-specific complexity already. Combined with the programmatic client API, it integrates cleanly into automated pipelines without manual intervention. The managed infrastructure handling rate limiting, retries, and JavaScript rendering means scraping becomes a reliable solved problem rather than an ongoing engineering burden for the team.
What do you dislike about the product?
Response structure consistency across actors is the biggest pain point — different actors can return data in unexpected shapes, including nested lists where flat results are expected, which requires defensive coding and can cause silent failures that are hard to diagnose. Documentation also drops off for edge cases, so unusual behavior often has to be discovered empirically. Better structured error reporting on failed runs would also save meaningful debugging time.
What problems is the product solving and how is that benefiting you?
Apify solves the content acquisition problem for our AI pipeline — reliably collecting web content across multiple source types without us owning crawler infrastructure. The direct benefit is that a small team can run a sophisticated, multi-source data collection operation that would otherwise require dedicated scraping engineering resources to build and maintain. That freed capacity goes toward the core product instead of infrastructure upkeep.
Great UX and Integrations, but Relevance and Customization Need Work
What do you like best about the product?
Good UX and diverse integrations pretty good price and performance
What do you dislike about the product?
sometimes the output is not super relevant and the actors are not super customizable
What problems is the product solving and how is that benefiting you?
scraping potential leads for my business
Essential tool for AI-powered automation pipelines
What do you like best about the product?
The Actor marketplace is incredibly valuable. I'm building an automated lead generation system using AI (Claude API for scoring, Playwright for automation) and Apify handles all the web scraping infrastructure. Pre-built Instagram Actors give me structured data that I pipe directly into my AI scoring pipeline. The REST API integration with my Node.js/Express backend was seamless — well-documented endpoints, predictable response formats, and solid error handling.
What do you dislike about the product?
The learning curve for building custom Actors is steeper than I expected. Also, some third-party Actors in the marketplace vary in quality — it would help to have more standardized output schemas across similar Actors.
What problems is the product solving and how is that benefiting you?
Before Apify, I was spending 60-70% of my development time on scraping infrastructure — proxy rotation, browser fingerprinting, anti-bot evasion, and data parsing. Now that's all handled by the platform, and I can focus on the AI and business logic of my application. It's reduced my time-to-market significantly and the per-usage pricing keeps costs predictable for a bootstrapped project.
From idea to 250,000+ rows in 6 weeks — without being a developer
What do you like best about the product?
The MCP gave me the ability to build and deploy 7 actors collecting 250,000+ rows of marketplace data in 6 weeks — by talking to Claude. The core primitives (call-actor, get-actor-run, get-actor-output) are the right shape for agentic workflows. search-actors and fetch-actor-details let me discover existing actors instead of reinventing the wheel. And search-apify-docs is underrated — having Claude pull up the right docs without context-switching to a browser is a small thing that compounds.
The bigger insight: Apify composes well with other MCPs. In my workflow it's Apify (collect) + Supabase (store) + Claude (orchestrate). Each does one thing; the conversation stitches them together. That multi-MCP pattern is where I think the real value is.
The bigger insight: Apify composes well with other MCPs. In my workflow it's Apify (collect) + Supabase (store) + Claude (orchestrate). Each does one thing; the conversation stitches them together. That multi-MCP pattern is where I think the real value is.
What do you dislike about the product?
The default Claude desktop / Cowork connector ships with a fairly limited tool set. The core operational tools (run history, abort, logs, schedule listing) do exist, but they’re tucked away in a separate MCP Configurator—and I didn’t even know the configurator existed until a PM personally walked me through it. Up to that point, I assumed those capabilities were missing entirely and ended up falling back to REST API workarounds.
This feels more like a discoverability problem than an actual product gap, but it still cost real time. Either ship the operations tools enabled by default, or make the configurator clearly visible during connector setup so it’s obvious where those features live.
This feels more like a discoverability problem than an actual product gap, but it still cost real time. Either ship the operations tools enabled by default, or make the configurator clearly visible during connector setup so it’s obvious where those features live.
What problems is the product solving and how is that benefiting you?
I’m building a market intelligence database for vintage synthesizers by pulling pricing history from eBay, Reverb, VEMIA, Yahoo Japan, and other marketplaces. It’s something I’ve wanted to do for years, but I couldn’t make it happen—the technical lift was simply too high for someone who hasn’t written production code in over a decade.
What changed for me is a new generation of enablers, and Apify is one of the main ones. The platform gave me both the runtime to deploy scrapers and the MCP to orchestrate them through natural language. As a result, what would have been a multi-month engineering project turned into a few weeks of conversation-driven setup: 7 deployed actors and 250,000+ entries collected in about 6 weeks.
Overall, the combination of Apify’s reach and the MCP’s accessibility has unlocked ambitions that used to feel locked behind “you need to be a developer.”
What changed for me is a new generation of enablers, and Apify is one of the main ones. The platform gave me both the runtime to deploy scrapers and the MCP to orchestrate them through natural language. As a result, what would have been a multi-month engineering project turned into a few weeks of conversation-driven setup: 7 deployed actors and 250,000+ entries collected in about 6 weeks.
Overall, the combination of Apify’s reach and the MCP’s accessibility has unlocked ambitions that used to feel locked behind “you need to be a developer.”
showing 1 - 10