BuiltWith alternatives, sorted by why you are leaving
BuiltWith sells one domain at a time by the credit and the lists by the month. Most teams looking for BuiltWith alternatives want the list, cheaper. 3 replacements below, each one matched to a specific reason.
If what you want is companies that run a technology and are spending now, TheirStack is the closest of these BuiltWith alternatives: it filters companies by technology through the API at 3 credits a company, with no $295 plan in front of the list. If you already pay for Apollo seats, its organization enrichment returns a technology stack for 1 credit. If you want technographics as one paid add-on on a broader company record, Crustdata charges 2 extra credits for it. This page carries three picks because the directory carries no other vendor that scans websites for technology the way BuiltWith does.
Prices and limits for every option below are read off the vendor's own page. These are the BuiltWith competitors that each answer a named problem.
The 3 reasons people actually leave
If none of these is your situation, the honest answer is that you should probably stay. The 21 providers in the Signal APIs listing are where these replacements come from.
1 · The list is a plan, not a lookup
A domain lookup through the BuiltWith API is 1 credit, $0.0495 at the entry rate with a 2,000 credit minimum. The Lists API, which returns every site using a technology and is what most sales teams buy BuiltWith for, requires a subscription: Basic at $295 a month for 2 technology reports, Pro at $495 and Team at $995.
2 · A stack is not a buying signal on its own
BuiltWith tracks 127,928 technologies across 491.9 million domains, with trends going back more than 18 years. It tells you what a site runs. It does not tell you whether the company is hiring for it, migrating off it or budgeting around it, which is the question a sequence is usually built on.
3 · Throughput and the one-read rule
The API allows 8 concurrent requests and 10 a second. Bulk jobs take up to 5,000 domains, and BuiltWith deletes the results after the first successful read, so a pipeline that fails between fetching and storing has paid for data it no longer has.
3 BuiltWith alternatives, and what each one fixes
Ordered by how closely each one answers the reasons above, not by price.
| Provider | Entry price | Unit cost | Free tier | Best for |
|---|---|---|---|---|
| BuiltWith | $99 for 2,000 lookups | $0.0495 per lookup | Free individual lookups on builtwith.com, and a Free API with summary counts at 0 credits | Baseline |
| TheirStack | $49/mo | $0.0327 per API credit, entry plan | A free trial with company and API credits, no card required | Best for hiring and technology signal with filter depth |
| Apollo API | $49/seat/mo | $0.0196 per credit | Free plan with API access, 900 credits per seat per year granted monthly, so 75 a month | Best all-in-one GTM API |
| Crustdata | Quote only | Sold in credits; no public dollar price for a credit | $20 in free credits on every new account, on the self-serve In-DB endpoints | Search wide for pennies of a credit, then pay only for the fields you keep |
Read from each vendor's own pricing page on 24 October 2026.
The case for each one
Each one below is matched to a reason rather than scored, and each one names what you give up by taking it. A replacement with no downside is a replacement nobody has actually run.
TheirStack
Companies filtered by the technology they use, through the API, at 3 API credits a company from a $49 monthly plan.
Of the BuiltWith competitors in this directory, TheirStack is the closest for the job most people bring to BuiltWith: a list of companies that use a given technology. Its company search filters by technology and returns companies at 3 API credits each, and a dedicated endpoint returns every technology a company is known to use at the same 3 credits.
The price falls with volume. API credits start at $49 a month for 1,500, which is about $0.098 a company, and fall to $1.50 per 1,000 credits at the million-credit tier, about $0.0045 a company. Unused paid credits roll over for 12 months, so a quiet month is not lost.
The data comes from job postings as well as the stack, which is the difference that matters for outbound. A company posting for a Salesforce administrator is telling you about budget, not just about a script tag, and TheirStack can push new matching companies to a webhook as they appear.
What you give up
Breadth of detection from the website itself. BuiltWith reads 491.9 million domains for 127,928 technologies, with spend history and a confidence score on each detection; TheirStack is strongest where companies publish job postings.
When it is the wrong answer
Front-end and ecommerce technology on small sites that rarely hire. A shop running a theme and a payment plugin may never post a job that names either, and BuiltWith will still see both on the page.
Apollo API
If you already pay for Apollo seats, organization enrichment returns the technology stack for a domain at 1 credit.
Apollo's organization enrichment returns firmographics, technology stack and headcount for a domain at 1 credit, which at $0.0196 a credit is under half BuiltWith's $0.0495 entry rate per lookup. For a team already enriching people there, the stack is one more field on a call it may already make.
The catch is the seat. Basic is $49 a seat a month billed annually with 30,000 credits a seat a year, so the cheap credit is only cheap if you were buying the seat anyway. Enrichment runs at 1,000 requests a minute with no hourly or daily cap, well above BuiltWith's 10 a second.
Apollo also publishes an MCP server at mcp.apollo.io/mcp, so an agent that researches an account can ask for the stack alongside the contacts without a second vendor or a second key.
What you give up
Depth on the technology itself. BuiltWith returns detection dates, spend history, confidence scores and relationships between sites; Apollo returns the stack as one field on a company record.
When it is the wrong answer
Building a list of every site running a technology. That is BuiltWith's Lists API or TheirStack's company search, not an enrichment call one domain at a time.
Crustdata
Technographics as a paid add-on to a full company record: 2 credits a company, 4 with technographics.
Crustdata's company enrichment is 2 credits a record, and requesting technographics adds 2 more for each company that returns them. The rest of the record comes with it: headcount, funding, hiring and the other company groups Crustdata prices as add-ons.
Technographics also work as a search filter. Crustdata's docs say search never returns technographics, only filters on them, and a company search filtered that way bills 1 extra credit a result on top of the 0.03 base. Size the result set before you run it at scale.
What Crustdata does not publish is the dollar price of a credit. New accounts get $20 in free credits, self-serve packs are priced in the dashboard, and the rate limits are per endpoint, 15 a minute on company enrichment.
What you give up
A published price. BuiltWith states $0.0495 a lookup and $295 to $995 for the list plans; Crustdata's dollar rate is only visible inside its dashboard.
When it is the wrong answer
A fast backfill through the real-time endpoint. Company enrichment allows 15 requests a minute, so 100,000 domains take about four and a half days that way; the batch endpoint is the route for volume, capped at 5 jobs in flight by default.
What you would actually pay, on each one
Every provider on this page publishes a rate card, so the real numbers can sit next to each other rather than behind a summary. The plan you want is the one whose included volume covers a normal month for you, not the cheapest one on the page.
BuiltWith
BuiltWith publishes 4 tiers, none of them free, and the paid ladder runs from $295 to $995.
API credits
- 1 credit a domain lookup, $0.0495 each at the entry rate
- BuiltWith quotes $99 for a 2,000 lookup batch
- 2,000 credits is the minimum purchase for an account
Basic
- 2 technology, 2 keyword and 2 retail reports
- 1 system login
- CRM integration
Pro
- Unlimited technology and keyword reports
- Unlimited retail reports, 1 login
- CRM integration
Team
- Everything in Pro
- Unlimited Pro logins
TheirStack
TheirStack publishes 11 tiers, none of them free, and the paid ladder runs from $49 to $5,500.
1,500 API credits
- 1,500 jobs, or 500 companies, or any mix
- $32.67 per 1,000 credits
- Unused paid credits roll over for 12 months
5,000
- $20.00 per 1,000 credits
10,000
- $16.90 per 1,000 credits
20,000
- $12.00 per 1,000 credits
50,000
- $8.00 per 1,000 credits
5,000,000
- $1.10 per 1,000 credits, the floor of the ladder
5 steps between the fifth and the last are not drawn here. The cost model below reads all 11.
Apollo API
Apollo publishes 4 tiers, one of them free, and the paid ladder runs from $49 to $119.
Free
- Full API access, not a trial of it
- Granted monthly, so 75 credits a month in practice
- 2 sequences and basic filters
Basic
- $588 a seat a year, credits granted upfront and pooled across the team
- 2,500 credits a month, at $0.0196 each
- Annual billing saves 24% against paying monthly
Professional
- 4,000 credits a month, at $0.0198 each
- AI lead scoring and multi-touch outreach
Organization
- 72,000 credits a seat a year, so 6,000 a month
- $0.0198 a credit, so the rate is flat across every paid tier
- The three-seat minimum makes $357 a month the real floor
Crustdata
Crustdata publishes 3 tiers, one of them free.
Free
- Every new account
- The self-serve In-DB endpoints
- Enough to test your own use case
Self-serve
- Search, enrich, jobs and web endpoints
- Packs valid 12 months, or auto top-up
- Dollar rate not printed on the public pages
Enterprise
- Live people and company endpoints
- Contact enrich and recurring credit grants
- A lower rate per credit as volume grows
Read the included volume before the headline price. A plan that costs twice as much and carries five times the credits is the cheaper plan, and on this page that is the usual case rather than the exception.
What each one costs at your volume
BuiltWith first, then every replacement. The model picks the cheapest published plan that covers your volume on each one, which is the comparison a row of entry prices cannot make.
BuiltWith
Priced on the volume you use, so the plan that covers a normal month is the one that decides the bill.
TheirStack
Priced on the volume you use, so the plan that covers a normal month is the one that decides the bill.
Apollo API
Priced on the volume you use, so the plan that covers a normal month is the one that decides the bill.
Crustdata
Publishes no price, so there is nothing here to model and the lines below say what to ask for.
Plans are read from each vendor's own pricing page and the model picks the cheapest one that covers you, so these are list prices on the billing term each vendor publishes, annual where that is how it prices, before any discount you negotiate. Crustdata publishes no price, so nothing is modeled there and the panel says what to ask for instead.
What a year costs at three volumes
The same plan-fit arithmetic as the model above, run out to a year, because an annual number is what a budget actually asks for.
The priced columns move with volume, through a bigger plan or more seats.
| A year at | BuiltWith | TheirStack | Apollo API | Crustdata |
|---|---|---|---|---|
| 1,000 a month | $1,188 API credits | $1,200 5,000 | $588 Basic | Quoted |
| 10,000 a month | $5,940 API credits | $4,800 50,000 | $2,352 Basic | Quoted |
| 50,000 a month | $29,700 API credits | $10,800 200,000 | $11,760 Basic | Quoted |
Crustdata does not publish enough to price a year, so that column is marked rather than filled. These are list prices on the published plan that covers each volume, on the billing term each vendor publishes, so they are the number before you negotiate.
Where the data comes from, and what you may do with it
The question that arrives late and expensively is who is allowed to hold the data. A migration is the moment to check it, because you are signing a new contract anyway.
| Provider | Fields returned | Coverage | Compliance | Redistribution |
|---|---|---|---|---|
| BuiltWith | Technographics, Firmographics | Global | None published | Not stated |
| TheirStack | Job postings, Technographics, Firmographics, Intent and news | Global | GDPR DPA | Not stated |
| Apollo API | Work email, Mobile phone, Firmographics, Technographics, Job postings, Intent and news, LinkedIn profile, CRM records | Global | GDPR DPA SOC 2 Type II CCPA | Not stated |
| Crustdata | Work email, Personal email, Mobile phone, Firmographics, Technographics, Job postings, Job changes, Intent and news, LinkedIn profile | Global | None published | Not stated |
None of these states a redistribution position on its pricing or docs pages. Internally that never matters. Put the rows in something your customers can see and it becomes the question your legal team asks first.
Two practical notes that apply to every provider on this page. A compliance badge describes the vendor rather than your use of it, so a GDPR DPA does not give you a lawful basis for the outreach you send. And every one of these vendors runs its own opt-out, which means a person who asks you to delete their record has to be removed from your copy as well as from theirs.
Moving off BuiltWith
Written against TheirStack, the first pick above, because the steps are the same whichever one you take and the specifics are what make them useful. Swap the name and the order still holds.
Measure the thing you are about to lose
Replay 100 of the queries, URLs or lookups you really send through BuiltWith and record the usable results, the failures and what each one cost. Without that baseline every provider looks cheaper per call than the one you are paying for today.
Check which fields change
TheirStack returns every field BuiltWith does, so nothing downstream has to change shape. Confirm the values rather than the keys: the same field can be named, typed or formatted differently on the other side.
Rewrite the auth and the limits, in that order
BuiltWith authenticates with an API key in an Authorization: API header, or the KEY query parameter for compatibility; Bearer on the MCP server. TheirStack uses a bearer token.
The limits are the part that bites later. BuiltWith's limits: 8 concurrent requests and 10 requests a second, then a 429.
TheirStack's limits: 4 requests a second once you have paid; free accounts also capped at 10 a minute and 400 a day. A loop tuned to the first will either crawl or get throttled on the second.
Run both for one billing cycle
Keep the old key live and route a slice of real traffic to the new one. A month is the shortest honest test, because credit expiry, rollover and the overage rate only show up at renewal and those are where the surprises live.
Cancel on the renewal date
Credits on most of these plans do not survive a downgrade. Check what happens to the balance you have already paid for, and time the switch so you are not buying the same records twice.
The step people skip is the first one, and it is the only one that cannot be done after the fact. Once the old key is off you have nothing to compare the new one against, so a provider that is quietly worse on your workload looks like a provider that is fine.
What practitioners say about TheirStack
Transcribed as written and linked to the thread. A Reddit claim is a signal rather than a fact, so nothing here is the only source for any figure on this page.
There is no official job-postings API, which is why this category exists
Job sites don't provide public APIs, they want that ad revenue. There use to be scripts to scrape their HTML but most no longer work. You can search github to find some now mostly abandon projects.
r/cscareerquestions · May 2023 · 12 points
This is the structural reason a provider can charge for job postings at all. The boards publish no publicly usable API because the listings are their advertising inventory, so the data reaches you either through a scraper you maintain yourself or through somebody who maintains one for you. TheirStack is the second option with a rate card attached, and the rate card is what you are really comparing against your own engineering time.
It is a 2023 comment and the abandoned-project problem has not improved since, which is the part to weigh. The question for your own build is not whether you can scrape a board this week but whether you want to own that maintenance the next time the markup changes.
14 threads read on 13 October 2026, searched by vendor name. Scores and dates are the comment's own. Nothing here is the only source for a price or a limit on this site: every figure in the tables above comes from a vendor's own page.
What practitioners say about Apollo
The one part of this page that is not a vendor claim. The comment below makes its point in crude words, so we summarize it in our own words and link the thread. A Reddit claim is a signal rather than a fact, so nothing here is the only source for a figure on this page.
The rate limit, not the credit price, is what people actually hit
In our words: A practitioner building on the API says the rate limits are what their team hit, that they got past them by routing requests across three Apollo accounts, and that Apollo charges per request even when a lookup returns nothing.
r/gtmengineering · May 2026 · summarized rather than quoted
Two halves worth separating. The limit is real and it is on this page: 200 requests a minute, 400 an hour and 2,000 a day on Basic, with enrichment on a separate 1,000 a minute and no hourly or daily cap. That split is why a bulk job and a per-row loop feel like different products.
The charge-on-no-output half needs care, because Apollo publishes 0 credits when nothing is found and that matches what we read. What a miss does spend is a request against the rate limit, and when the limit is the binding constraint that is the cost you feel. Pooling accounts to get round a published limit is a terms question before it is an engineering one.
11 threads read on 13 October 2026, searched by vendor name. Scores and dates are the comment's own. Nothing here is the only source for a price or a limit on this site: every figure in the tables above comes from a vendor's own page.
Should you actually switch?
The short answer is at the top of this page. Before you act on it, run the test below, because it is the cheapest way to find out whether that answer holds for you.
Take a hundred accounts whose stack you already know, look them up through a free tier or trial on each, and count which tools each one reports correctly and which it misses. What you are buying is detection depth: how many of the tools each one gets right.
Head to head, and in a stack
Before you switch, try the waterfall in Clay.
Clay runs a waterfall across 150+ data providers from one table, without a separate contract with each. A lookup that finds nothing costs no data credit, and the free plan includes 500 actions a month.
Frontal is a Clay Elite Studio Partner.
Switching from BuiltWith, answered
What is the best BuiltWith alternative?
It depends on why you are leaving, which is how this page is organized rather than ranked. The first pick here is TheirStack, which this directory lists as the best for hiring and technology signal with filter depth, at $49/mo. The case for it, and what you give up, is in the section above.
Is there a free alternative to BuiltWith?
Yes, 2 of the replacements here do. Apollo: Free plan with API access, 900 credits per seat per year granted monthly, so 75 a month. Crustdata: $20 in free credits on every new account, on the self-serve In-DB endpoints.
How were these alternatives chosen?
By the reason teams leave, not by a score. The page opens with the reasons teams leave and matches a replacement to each one.