Arun A.
AA
Founder
Small-Business (50 or fewer emp.)
"Powers how our product searches the web, finds sources and extracts clean content"
4.5/5
What do you like best about Firecrawl?

What I like best is that Firecrawl handles the whole web layer for us in one API. We use it to search the internet, suggest relevant sources to our users, and extract clean content from those pages. Before, that would have meant stitching together several tools.

The most helpful part is how reliable it is. Over the last 30 days we ran more than 5,400 successful jobs with a success rate of about 98.8%, so we rarely have to deal with failed requests or edge cases. The content comes back clean and structured, so it's ready for our AI pipeline without much post-processing.

Other upsides: it's quick to set up, the docs are clear, and the usage dashboard makes it easy to track credits and usage by endpoint. As a small team, we get to spend our time building our product instead of maintaining extraction infrastructure. Review collected by and hosted on G2.com.

What do you dislike about Firecrawl?

The main downside for us is credit planning. We're on the Hobby plan, and with our product running search and content extraction every day, we went past the monthly allowance quickly. Right now we're near the bottom of our balance with over two weeks to go before it resets. It isn't always obvious upfront how many credits a request will use, which makes it harder to forecast costs as our usage grows.

The concurrency limit on the lower tiers can also be a bottleneck when many users ask for sources at the same time. A small share of jobs still fail on certain sites, so we've had to build retry handling on our side.

None of these are dealbreakers. More flexible mid-tier pricing or pay-as-you-go top-ups would make it much easier for growing teams like ours. Review collected by and hosted on G2.com.

See what 696 reviewers think of Firecrawl

4.6 out of 5 · Verified reviews from real users

Read all reviews