Breaknorm
Sign inStart free

Product

SignalsPeopleCompaniesLocal businessesMCP and API

Plays

Post engagersTeam build-outChampion movedHiring surgeNewly fundedLookalikesAll plays

Data

Coverage by countryHiring dataJob changesEmail verificationCompanies by toolWho is hiringMarket mapsOutboundCompany profilesCompare
PricingDatasetsDocsSign in
Compare · backend frameworks

ASP.NET Web API VS Windows Communication Foundation

As of 30 October 2026, Windows Communication Foundation is named by 387 companies and ASP.NET Web API by 135; ASP.NET Web API skews to companies under 200 people (50% vs 51%), Windows Communication Foundation to companies over 1,000 (23% vs 28%).

As of 30 October 2026 · refreshed daily · counts move as websites, DNS and career sites are re-read.

The website-and-DNS footprint is not comparable between a marketing suite and a CRM: ASP.NET Web API's script and mail records show on hundreds of thousands of small sites, Windows Communication Foundation rarely leaves a trace outside its own apps. Compare on the job-posting numbers; use the footprint for reach.

ASP.NET Web API: 2–200 employees
50%
Windows Communication Foundation: 2–200 employees
51%
ASP.NET Web API: 1,000+ employees
28%
Windows Communication Foundation: 1,000+ employees
23%
Postings per company, 90 days
2.0 · 2.0
Website or DNS footprint
0 · 0
135companies name ASP.NET Web API
387companies name Windows Communication Foundation
65name both
266 · 771postings in 90 days, ASP.NET Web API · Windows Communication Foundation
02Side by side

Who chooses which

Share of each tool's companies in every segment. "Leans" marks a gap of more than two points.

By company size
SegmentASP.NET Web APIshareWindows Communication FoundationshareLeans
Self-employed11%31%even
2-10 employees75%277%even
11-50 employees2519%8722%Windows Communication Foundation
51-200 employees3627%8321%ASP.NET Web API
201-500 employees1713%5915%Windows Communication Foundation
501-1000 employees118%3910%even
1001-5000 employees1612%4512%even
5001-10000 employees54%123%even
10,001+ employees1713%328%ASP.NET Web API
By industry
SegmentASP.NET Web APIshareWindows Communication FoundationshareLeans
Technology & software8462%24864%even
Business & finance services2116%6617%even
Manufacturing & industry107%287%even
Consumer services & leisure64%72%ASP.NET Web API
Media & content32%62%even
Transport, logistics & rental32%92%even
Automotive21%21%even
Property & construction21%––outside top 12
Commerce & trade11%21%even
Public, community & associations11%31%even
Health care11%31%even
Utilities & infrastructure11%72%even
Hospitality & travel––31%outside top 12
By country
SegmentASP.NET Web APIshareWindows Communication FoundationshareLeans
United States7556%20553%ASP.NET Web API
India97%4211%Windows Communication Foundation
United Kingdom86%246%even
Australia64%82%ASP.NET Web API
Germany54%123%even
Canada43%82%even
France43%113%even
Poland32%72%even
Sweden32%––outside top 12
Brazil21%––outside top 12
Italy21%72%even
Belgium11%72%even
Spain––51%outside top 12
United Arab Emirates––31%outside top 12
Postings by team (share of each tool's postings)
SegmentASP.NET Web APIshareWindows Communication FoundationshareLeans
Software engineering49486%1,70783%ASP.NET Web API
IT operations & business systems183%924%even
Data & AI81%80%even
Engineering (non-software)31%90%even
Finance & accounting20%161%even
Marketing & communications10%60%even
Product, program & project management10%121%even
Customer service & success––40%outside top 12
Unclassified––40%outside top 12
Administration & office––10%outside top 12
Human resources––10%outside top 12
Logistics warehouse and transport––10%outside top 12
Cite this

Quote the sentence with the date and the link. The numbers change daily; the link always shows the current ones.

Windows Communication Foundation is named by 387 companies in job postings and ASP.NET Web API by 135; 65 name both. (Breaknorm, 30 October 2026, https://breaknorm.co/compare/asp-dot-net-web-api-vs-wcf)
How we know

Read from the source, not self-reported

Every number on this page can be traced to a page we crawled or a posting we read. Full methodology →

  • Job postingsRead hourly from career sites. A tool counts when the employer's own text names it as the team's system; both tools can count for one company.
  • Website and DNSScripts and embeds on the company's pages, plus SPF, DKIM, MX and CNAME records of its domain that point at the vendor.
  • SegmentsCountry, size and industry from the company profile built from its website.
  • Not a reviewNo ratings, prices or feature claims. For those, read the vendors.
FAQ

ASP.NET Web API vs Windows Communication Foundation: questions

Which is more used, ASP.NET Web API or Windows Communication Foundation?

By companies naming it in their own job postings, Windows Communication Foundation (387) over ASP.NET Web API (135). By website-and-DNS footprint, Windows Communication Foundation (0 vs 0), because its scripts and mail records sit on many small company sites.

Who chooses ASP.NET Web API?

50% of ASP.NET Web API companies have 2 to 200 employees, against 51% for Windows Communication Foundation. 28% of ASP.NET Web API companies have over 1,000 employees, against 23% for Windows Communication Foundation.

Do companies run both?

65 companies name both in their postings, usually ASP.NET Web API in marketing and Windows Communication Foundation in sales, or during a migration.

Where do these numbers come from?

From the employer's own text in job postings read hourly from career sites, and from scripts found on company websites in our crawl. No vendor data, no surveys.

Companies and people

Get either list your way

The same data as a search, over MCP and the API, as bulk files, or pushed to you as it changes.

Every company on either tool,
with the person who owns it

Filter on ASP.NET Web API or Windows Communication Foundation. Start free, no card.

  1. 01Sign up, no card
  2. 02Connect Claude, ChatGPT or an API key
  3. 03Ask for your market