--- title: "BuiltWith alternatives: free and paid, compared (2026) - JobsPipe" description: "Free BuiltWith alternative for one-off lookups, paid tools compared for lead lists and an API, and the signal none of them read: job postings." canonical: https://jobspipe.dev/builtwith-alternatives --- > **Facts:** Free: 1,000 free credits, one time. Paid: from $49/month for 25,000 jobs. 12 months of history on every plan. Jobs from 30+ sources. Try it without a key: `curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search` # BuiltWith alternatives: scan any tech stack free. Paste a domain below for a free instant tech-stack lookup - a real BuiltWith alternative you can run right now, no signup. Then read my honest test of the main alternatives, sorted by what you were actually buying from BuiltWith, with a side-by-side table, the one signal none of the scanners read, and an FAQ. By Dvir Atias, Founder, JobsPipe · Updated 2026-09-24 · 11 min read Bottom line The best free BuiltWith alternative is a live tech-stack scan: paste a domain into the tool at the top of this page and get the technologies on its public site in seconds, no signup. For frontend-only checks the Wappalyzer extension and crft.studio are also free; for backend tools read from infrastructure, Bloomberry is the pick; for what a company is hiring to build, job postings are the only public source. Free tech-stack lookup ## Free BuiltWith alternative: scan a domain now Detects 7,000+ technologies from a live scan of the public site - frontend, analytics, CDN, payment, and SaaS tools. No account, no card. No signup required. 10 free scans per hour. [Browse more scans](https://jobspipe.dev/stack). ## Which BuiltWith alternative fits what you were buying BuiltWith has crawled the web for the better part of two decades, says it tracks more than 127,000 technologies across hundreds of millions of domains, and its lead-list business - “give me every site running Shopify Plus in Germany” - is the reference product for technology-based prospecting. Its pricing reflects that: Basic is $295 a month and covers only two technologies, Pro is $495 and Team is $995, billed for the whole machine whether you need it or not. That is why people search for alternatives, and the searches split into four different buyers. | You were buying BuiltWith for | Closer-fit alternative | | --- | --- | | Lead lists by technology | HG Insights, SimilarTech, ZoomInfo (Datanyze) | | Per-domain lookup API | JobsPipe Stack Scan, Wappalyzer API | | Free one-off checks | This page's scan, WhatRuns, Netcraft site report, browser extensions | | Self-hosted detection | Open-source Wappalyzer forks | | What a company is adopting, not just serving | Job-posting technographics (JobsPipe jobs API) | **HG Insights, SimilarTech and Datanyze (ZoomInfo)** are the lead-list competitors: if your product is a prospect list filtered by installed technology, these are the direct substitutes, priced for sales teams and sold as platforms. **WhatRuns and Netcraft** cover the free end: a lightweight extension with a good hit rate on modern frameworks, and the veteran site report for hosting, certificates and infrastructure detail. Neither is in the tested table below because neither offers an API to build on. Disclosure up front: JobsPipe sells a tech-detection API and a jobs API, so we compete in the lookup and adoption categories only. For lead lists at BuiltWith scale we will point you elsewhere. See also the [Wappalyzer alternatives](https://jobspipe.dev/wappalyzer-alternatives) comparison, the [technographic data providers](https://jobspipe.dev/technographic-data-providers) round-up, and the [technographics](https://jobspipe.dev/technographics) pillar for the category background. ## Comparison table | Tool | Free option | API | Detection | Reads internal stack from job postings | Best for | | --- | --- | --- | --- | --- | --- | | JobsPipe(us) | Yes - instant domain scan, no signup | Yes - REST API on the free tier | 7,000+ technologies from a live scan | Yes | Free scan + API + the internal stack from job postings | | BuiltWith | Single-site lookup only; no bulk free tier | Paid plans only | Large frontend technology index | No | Historical trend data and brand recognition | | Wappalyzer | Free extension; 50 lookups/month registered | Yes - credit-based, paid | Frontend technology fingerprints | No | The default browser-extension tech check | | Bloomberry | Free API key with 1,000 test credits | Yes - REST, self-serve from $199/mo | Infrastructure signals: DNS, subdomains, cert logs | No | Adoption and churn events on 1,700+ B2B tools | | crft.studio | Yes - free single-site lookup tool | No public API | Frontend detection on one site | No | A quick free one-off check, no account | | RB2B | Free tier for person-level reveal | Integrations, no general tech API | Visitor de-anonymization, not tech scan | No | Identifying who visits your own site | Pricing and limits change often - verify current plans on each vendor’s site before you buy. ## The reviews ![JobsPipe](https://jobspipe.dev/brand/glyph/mark.svg) ### JobsPipe(our tool) [jobspipe.dev](https://jobspipe.dev) Best for: Developers and data buyers who want a free instant scan, a real API, and the internal stack read from job postings. Full disclosure - this is our tool, so I am putting the honest caveats up front. The scan above is half the pitch: paste a domain, get back the technologies running on its public site in a couple of seconds, free, no account. It detects 7,000+ technologies from a live scan rather than a pre-crawled index, so it reflects what the site serves right now. The other half is the jobs API: every posting JobsPipe collects carries the technologies it names, so the same key answers 'which companies are hiring for Snowflake' or 'what does this company's engineering team actually run', which no homepage scan can. It is not a historical-trends archive like BuiltWith, and a single live scan is not a 500-million-site database - if you need decade-long adoption curves, BuiltWith still owns that. Pros - Free instant domain scan with no signup, embedded right at the top of this page. - Detects 7,000+ technologies from a live scan, so results reflect the current site. - REST API available on the free tier, not gated behind an enterprise quote. - Reads the internal stack from job postings, which frontend-only scrapers cannot do. Cons - No multi-year historical trend archive the way BuiltWith has. - Live scan reads the public site; the posting signal only covers companies that are hiring. - Younger product with a smaller integration ecosystem than BuiltWith. ![BuiltWith](https://jobspipe.dev/favicons/builtwith.png) ### BuiltWith [builtwith.com](https://builtwith.com) Best for: Teams that specifically need BuiltWith's historical trend data or its brand recognition on stakeholder reports. BuiltWith is the incumbent and the free single-site lookup is genuinely useful for a one-off check. Where it frustrated me is the gap between the free page and the paid product: the $295-a-month Basic plan caps you to two technologies, and any real bulk or API workflow lands you on the $495 Pro plan fast. The historical trend data is the real moat - if you need to see how Shopify adoption moved over a decade, nothing else here matches it. For just 'what does this site run today', it is the most expensive way to find out. Pros - Longest-running historical dataset on web-technology adoption. - Free single-site lookup is fine for ad-hoc curiosity. - Brand recognition means reports get accepted without explanation. Cons - Basic plan ($295/month) caps you at two technologies; unlimited starts at $495/month. - No free bulk lookups or free API access. - Frontend-only, so backend and internal tooling are invisible. [Scan BuiltWith's own tech stack →](https://jobspipe.dev/stack/builtwith.com) ![Wappalyzer](https://jobspipe.dev/favicons/wappalyzer.png) ### Wappalyzer [wappalyzer.com](https://wappalyzer.com) Best for: Anyone who wants the de-facto browser extension for quick checks, plus a clean credit-based API when they scale up. Wappalyzer is what most people actually reach for. The free browser extension is fast and accurate for single sites, and the API is the cleanest in this group if you want to wire detection into an enrichment pipeline. The catch is the free tier - 50 lookups a month with no API access, paid plans start at $250 a month, and plan credits expire after 60 days, so it is not a free bulk solution. The project also went closed-source, which is why it has its own alternatives page. For frontend detection at a lower price than BuiltWith, it is the safe default. Pros - Free, accurate browser extension that is the category standard. - Clean credit-based API built for engineers. - Bulk lookups scale to large lists on paid plans. Cons - Free tier is 50 lookups/month with no API; plan credits expire after 60 days. - Frontend-only detection, same blind spots as BuiltWith. - Lead-list filtering is thinner than sales-led platforms. [Scan Wappalyzer's own tech stack →](https://jobspipe.dev/stack/wappalyzer.com) ![Bloomberry](https://jobspipe.dev/favicons/bloomberry.svg) ### Bloomberry [bloomberry.com](https://bloomberry.com) Best for: Sales teams who want to know the week a company starts or stops paying for a specific B2B tool, including software that never touches the website. Bloomberry takes a different route: instead of scraping the live site or mining job postings, it reads infrastructure signals - new subdomains, DNS records, certificate transparency logs and product-specific deployment footprints - and keeps re-checking them, so it can call churn as well as adoption. That is the one approach here that surfaces CRMs, AI assistants and other backend tooling BuiltWith fundamentally cannot detect, and it is timely: adoption typically shows within 3-7 days, churn within 1-2 weeks. The tradeoff is scope - it tracks a curated 1,700+ B2B products rather than every frontend fingerprint, and it is priced as a sales-signal product, so it pairs with a free live scan rather than replacing one. Pros - Detects backend and off-website tools invisible to frontend scrapers. - Tracks churn as well as adoption, with events surfacing in days. - Self-serve REST API with a free 1,000-credit test key. Cons - Covers 1,700+ B2B products, not the full frontend fingerprint catalog. - No free lookup tool; self-serve plans start at $199/month. - Not a substitute for live frontend detection. [Scan Bloomberry's own tech stack →](https://jobspipe.dev/stack/bloomberry.com) ![crft.studio](https://jobspipe.dev/favicons/crft.png) ### crft.studio [crft.studio](https://crft.studio) Best for: A free, no-account single-site lookup when you just need to check one domain and move on. crft.studio is a free tool page, and that is exactly why it ranks for this term: zero friction, paste a domain, see the stack. It is great for a one-off and proves the point that the winning format for 'BuiltWith alternative' is a free instant tool, not a paywall. There is no public API and no bulk workflow, so it stays a single-site utility rather than something you build on. Pros - Genuinely free single-site lookup with no account. - Fast and frictionless for a one-off check. - Clean result page, easy to read. Cons - No public API to automate against. - No bulk lookup or list enrichment. - Frontend detection only. [Scan crft.studio's own tech stack →](https://jobspipe.dev/stack/crft.studio) ![RB2B](https://jobspipe.dev/favicons/rb2b.png) ### RB2B [rb2b.com](https://rb2b.com) Best for: Teams that want to de-anonymize visitors on their own site rather than scan a third party's stack. RB2B shows up in this conversation but it is a different job. It identifies the people and companies visiting your own website, not the technology stack running on someone else's. If your real question is 'who is on my site right now', RB2B answers it. If your question is 'what does this domain run', it is the wrong tool - a live tech scan or a job-posting detector fits better. Pros - Person-level visitor identification with a free tier. - Useful for warming up inbound on your own site. - Integrates with common sales and marketing stacks. Cons - Not a tech-stack scanner for third-party domains. - Coverage is US-weighted for person-level reveal. - Different category from BuiltWith entirely. [Scan RB2B's own tech stack →](https://jobspipe.dev/stack/rb2b.com) ## The blind spot every homepage scanner shares Detection - BuiltWith’s, Wappalyzer’s, ours - sees what a company serves on its public website. It cannot see the data warehouse, the CRM, the cloud account or the platform migration that started last quarter. The public signal for those is hiring: job postings name the technologies a company is actually investing in, often before anything ships. The chart is the share of active postings on the ten boards JobsPipe collects that name each tracked technology. Most of the list never appears on a homepage. - Python4.7% - AWS3.1% - SAP2.9% - Microsoft Azure2.8% - Salesforce1.9% - Power BI1.8% - Java1.7% - Google Cloud1.7% - Kubernetes1.5% - React1.3% Share of active postings naming each technology, top 10 of the tracked list. A posting can name several technologies, so shares do not sum to 100%. Pairing a homepage scan with a company’s postings answers the question sales teams are really asking: not “what is on their site” but “what are they betting on next”. Every posting in the JobsPipe API carries `technology_slugs`, so `skills_or` returns every company hiring for a technology and `company_name_or` returns one company’s internal stack. The per-technology lists live at [companies using each technology](https://jobspipe.dev/companies-using), and the named companies behind each one are in the [technologies directory](https://jobspipe.dev/technologies). [Which companies use Python?](https://jobspipe.dev/technologies/python) · [Which companies use Amazon Web Services?](https://jobspipe.dev/technologies/aws) · [Which companies use SAP?](https://jobspipe.dev/technologies/sap) · [Which companies use Microsoft Azure?](https://jobspipe.dev/technologies/azure) · [Which companies use Salesforce?](https://jobspipe.dev/technologies/salesforce) · [Which companies use Microsoft Power BI?](https://jobspipe.dev/technologies/power-bi) How this was measured Measured from active postings on the ten collected boards whose text names the technology (deduplicated by posting id). Generated 2026-09-09. Shares only: JobsPipe publishes percentages, not counts. Technology mentions are extracted from each posting’s title and description against a curated lexicon. Shares are published only above a minimum posting count. ``` curl -X POST https://api.jobspipe.dev/v1/jobs/search \ -H "Authorization: Bearer $JOBSPIPE_API_KEY" \ -H "Content-Type: application/json" \ -d '{"skills_or":["kubernetes"],"status":"active","limit":24}' ``` ## BuiltWith alternatives FAQ What is the best alternative to BuiltWith?+ It depends on which part of BuiltWith you were using. For technology-filtered lead lists, HG Insights, SimilarTech and Datanyze (inside ZoomInfo) are the direct competitors. For a per-domain lookup API, JobsPipe Stack Scan and the Wappalyzer API are the developer-shaped options. For free one-off checks, the scan on this page, WhatRuns and Netcraft's site report cover most needs. For what a company is adopting rather than serving, job-posting technographics are the only public source. Is there a free BuiltWith alternative?+ Yes. The fastest free BuiltWith alternative is a live tech-stack scan: paste a domain into the tool at the top of this page and you get the technologies on its public site in a couple of seconds, no signup. crft.studio, the WhatRuns extension and Netcraft's site report are also free for single-site checks, and open-source Wappalyzer forks can be self-hosted without licence fees. What no one offers free is unlimited bulk lookups with lead-list export - that workflow is paid everywhere. BuiltWith vs Wappalyzer - which is better?+ For most teams Wappalyzer is the better value. Detection coverage for frontend technologies is comparable, the API is cleaner, and paid plans run lower than BuiltWith at equivalent volume. Stay on BuiltWith only if you specifically need its multi-year historical trend data, or if non-technical stakeholders trust the BuiltWith brand on reports. For one-off checks, both have a free path - Wappalyzer's extension and BuiltWith's free single-site lookup. What can a technology-detection tool not see?+ Anything not served on the public website: the cloud platform, databases, data warehouse, CRM, ERP, internal languages, observability stack and any migration in progress. The public signal for those is hiring: job postings name the technologies a company is investing in, often before anything ships. Pairing a homepage scan with a company's job postings covers both what is live today and what is being built next. How accurate are BuiltWith alternatives?+ Accuracy depends on method. Live frontend scanners (JobsPipe, Wappalyzer, crft.studio) are highly accurate for technologies that leave a fingerprint in the page and reflect the current site. They cannot see backend or internal tools. Infrastructure-signal detectors like Bloomberry catch some of those by reading DNS, subdomains and certificate logs, across a curated catalog of B2B products. Job-posting technographics see the internal stack directly but only for companies that are hiring, and they record hiring intent rather than a purchase. Combining a live scan with the posting signal gives the most complete picture. Which BuiltWith alternatives have an API?+ JobsPipe offers a REST API on its free tier for both the stack scan and the jobs search. Wappalyzer and Bloomberry offer APIs on paid plans, Bloomberry with a free 1,000-credit test key, and BuiltWith's API is paid only. crft.studio has no public API. If API access without an enterprise quote is the priority, start with the free JobsPipe scan above and the API behind it. How does JobsPipe Stack Scan compare to BuiltWith?+ Stack Scan is a per-domain enrichment API: one POST returns the detected technologies as JSON with categories and confidence scores, from a live scan that is cached, on a self-serve key with a free tier. BuiltWith's strength is breadth and history - long-term tracking and lead lists across the whole web - at prices built for sales teams. For enriching domains inside your own product, the API shape wins; for buying prospect lists, BuiltWith's category wins. Can I join tech-stack data with hiring data?+ That is the JobsPipe differentiator. Frontend scrapers tell you what a company runs today; job postings tell you what it is hiring to build next. Every posting in the JobsPipe API carries technology\_slugs, so a skills\_or filter returns every company hiring for a technology, and company\_name\_or returns one company's internal stack. Bloomberry adds a third angle - adoption and churn read from infrastructure signals - but it does not run a live frontend scan or read job postings. ## Further reading [ Comparison Wappalyzer alternatives Free options first, FOSS forks, and paid replacements. ](https://jobspipe.dev/wappalyzer-alternatives)[ Pillar Technographics, explained What technographic data is and what job postings add. ](https://jobspipe.dev/technographics)[ Data Companies using each technology Who is hiring for Salesforce, AWS, Snowflake and more. ](https://jobspipe.dev/companies-using)[ Free tool Tech-stack lookup Scan any domain and browse recent and featured scans. ](https://jobspipe.dev/stack) Free instant scans, a real API, and the internal stack from job postings. Key in 30 seconds. ## Further reading - [How Does BuiltWith Work?](https://jobspipe.dev/blog/how-does-builtwith-work) --- Try it with no key: `curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search`. AI agents: the full machine-readable index of this site is https://jobspipe.dev/llms.txt?src=md-twin - API quickstart, MCP server, pricing. Free key (1,000 jobs to start): https://jobspipe.dev/signup