AWS Fargate VS Azure Functions_
As of 4 November 2026, Azure Functions is named by 1,300 companies and AWS Fargate by 626; AWS Fargate skews to companies under 200 people (48% vs 34%), Azure Functions to companies over 1,000 (39% vs 28%).
As of 4 November 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: AWS Fargate's script and mail records show on hundreds of thousands of small sites, Azure Functions rarely leaves a trace outside its own apps. Compare on the job-posting numbers; use the footprint for reach.
- AWS Fargate: 2–200 employees
- 48%
- Azure Functions: 2–200 employees
- 34%
- AWS Fargate: 1,000+ employees
- 28%
- Azure Functions: 1,000+ employees
- 39%
- Postings per company, 90 days
- 2.1 · 2.8
- Website or DNS footprint
- 0 · 0
Who chooses which
Share of each tool's companies in every segment. "Leans" marks a gap of more than two points.
| Segment | AWS Fargate | share | Azure Functions | share | Leans |
|---|---|---|---|---|---|
| Self-employed | 22 | 4% | 24 | 2% | even |
| 2-10 employees | 52 | 8% | 70 | 5% | AWS Fargate |
| 11-50 employees | 106 | 17% | 150 | 12% | AWS Fargate |
| 51-200 employees | 144 | 23% | 228 | 18% | AWS Fargate |
| 201-500 employees | 74 | 12% | 183 | 14% | Azure Functions |
| 501-1000 employees | 53 | 8% | 133 | 10% | even |
| 1001-5000 employees | 85 | 14% | 220 | 17% | Azure Functions |
| 5001-10000 employees | 26 | 4% | 75 | 6% | even |
| 10,001+ employees | 64 | 10% | 217 | 17% | Azure Functions |
| Segment | AWS Fargate | share | Azure Functions | share | Leans |
|---|---|---|---|---|---|
| Technology & software | 351 | 56% | 569 | 44% | AWS Fargate |
| Business & finance services | 133 | 21% | 296 | 23% | even |
| Manufacturing & industry | 33 | 5% | 119 | 9% | Azure Functions |
| Media & content | 24 | 4% | 30 | 2% | even |
| Consumer services & leisure | 23 | 4% | 37 | 3% | even |
| Commerce & trade | 13 | 2% | 47 | 4% | even |
| Public, community & associations | 10 | 2% | 33 | 3% | even |
| Health care | 9 | 1% | 29 | 2% | even |
| Automotive | 8 | 1% | 14 | 1% | even |
| Utilities & infrastructure | 8 | 1% | 49 | 4% | Azure Functions |
| Property & construction | 5 | 1% | 34 | 3% | even |
| Transport, logistics & rental | 5 | 1% | 28 | 2% | even |
| Segment | AWS Fargate | share | Azure Functions | share | Leans |
|---|---|---|---|---|---|
| United States | 391 | 62% | 699 | 54% | AWS Fargate |
| United Kingdom | 44 | 7% | 110 | 8% | even |
| Germany | 28 | 4% | 60 | 5% | even |
| Japan | 16 | 3% | – | – | outside top 12 |
| Canada | 15 | 2% | 49 | 4% | even |
| India | 13 | 2% | 40 | 3% | even |
| Spain | 12 | 2% | 14 | 1% | even |
| Australia | 8 | 1% | 34 | 3% | even |
| France | 8 | 1% | 28 | 2% | even |
| Sweden | 7 | 1% | 25 | 2% | even |
| Brazil | 6 | 1% | – | – | outside top 12 |
| Poland | 6 | 1% | – | – | outside top 12 |
| Netherlands | – | – | 31 | 2% | outside top 12 |
| Belgium | – | – | 22 | 2% | outside top 12 |
| Portugal | – | – | 11 | 1% | outside top 12 |
| Segment | AWS Fargate | share | Azure Functions | share | Leans |
|---|---|---|---|---|---|
| Software engineering | 1,148 | 66% | 2,375 | 52% | AWS Fargate |
| Data & AI | 202 | 12% | 786 | 17% | Azure Functions |
| IT operations & business systems | 176 | 10% | 705 | 16% | Azure Functions |
| Product, program & project management | 29 | 2% | 18 | 0% | even |
| Engineering (non-software) | 19 | 1% | 84 | 2% | even |
| Sales | 9 | 1% | 12 | 0% | even |
| Customer service & success | 8 | 0% | 5 | 0% | even |
| Unclassified | 4 | 0% | 3 | 0% | even |
| Design & UX | 2 | 0% | – | – | outside top 12 |
| Business development & strategy | 1 | 0% | 4 | 0% | even |
| Marketing & communications | 1 | 0% | 3 | 0% | even |
| Quality, safety & environment | 1 | 0% | 5 | 0% | even |
| General management & consulting | – | – | 16 | 0% | outside top 12 |
| Finance & accounting | – | – | 6 | 0% | outside top 12 |
| hospitality and food service | – | – | 3 | 0% | outside top 12 |
| skilled trades and field service | – | – | 3 | 0% | outside top 12 |
| construction and civil | – | – | 2 | 0% | outside top 12 |
| Legal, compliance & risk | – | – | 2 | 0% | outside top 12 |
| Administration & office | – | – | 1 | 0% | outside top 12 |
| manufacturing and production | – | – | 1 | 0% | outside top 12 |
The companies behind each column
Companies using AWS Fargate →
Companies using Azure Functions →
paas serverless ranked →
Quote the sentence with the date and the link. The numbers change daily; the link always shows the current ones.
Azure Functions is named by 1,300 companies in job postings and AWS Fargate by 626; 0 name both. (Breaknorm, 4 November 2026, https://breaknorm.co/compare/aws-fargate-vs-azure-functions)
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.
AWS Fargate vs Azure Functions: questions
Which is more used, AWS Fargate or Azure Functions?
By companies naming it in their own job postings, Azure Functions (1,300) over AWS Fargate (626). By website-and-DNS footprint, Azure Functions (0 vs 0), because its scripts and mail records sit on many small company sites.
Who chooses AWS Fargate?
48% of AWS Fargate companies have 2 to 200 employees, against 34% for Azure Functions. 28% of AWS Fargate companies have over 1,000 employees, against 39% for Azure Functions.
Do companies run both?
0 companies name both in their postings, usually AWS Fargate in marketing and Azure Functions 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.
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 AWS Fargate or Azure Functions, and get 1,000 records free.