Companies Using AWS Lambda

With over a decade of experience in web crawling and technographic analysis, I've been tracking serverless adoption since AWS Lambda's 2014 launch. This analysis draws on 70,209 enriched company profiles matched from 99,491 detected domains, a 70.57% match rate, as of our April 2026 crawl. The data below covers company size, age, industry concentration, geographic footprint, migration flows, tech stack overlap, and G2 review sentiment.

1. Growth trajectory

AWS Lambda's detection numbers tell two distinct stories. From 2015 through September 2024, domain counts hovered in the low thousands, growing from 33 total domains at launch to roughly 2,094 active by mid-2024. Then in October 2024, our improved detection signatures for server-side Lambda endpoints triggered a spike to 58,976 active domains in a single month. By April 2025, that number peaked at 93,152 before settling to 89,200 in July 2025.

The plateau since April 2025 isn't decline; it's stabilization after the detection methodology expansion. The underlying adoption trend has been steady since Lambda's general availability in 2015. Per AWS's 10th anniversary page (November 2024), over 1.5 million customers use Lambda each month and the service handles tens of trillions of requests monthly. Datadog's State of Serverless report independently confirms that 65% of AWS customers use Lambda, making it AWS's most popular serverless offering.

"The 45x jump in detected domains between September and November 2024 wasn't a sudden adoption wave. It was our crawlers finally catching Lambda endpoints that had been running for years. The real story is how many of these detections link back to companies founded after 2020." - Mehmet Suleyman, CEO at TechnologyChecker.io

Sales Signal: Lambda's addressable market is large and still expanding. The detection jump means sales teams now have visibility into tens of thousands of Lambda-using companies that weren't trackable before. Focus outreach on the 44% of Lambda customers founded in the 2020s, since younger companies are more open to adding complementary tools.

2. Customer profile

73.8% of Lambda customers have 10 or fewer employees. Combined with the 17.2% in the 11-50 range, over 91% of Lambda's user base operates with under 50 people. That's even more small-team-heavy than the serverless market average, and it reflects Lambda's pay-per-invocation model that eliminates infrastructure overhead for lean operations.

At the enterprise end, 219 companies with 10,001+ employees run Lambda. These include Adobe, Bloomberg, and ThyssenKrupp from our detection data, plus vendor-verified cases like Netflix (rule-based infrastructure), T-Mobile ("serverless first" company policy), and Capital One (container workloads). Most enterprise detections appear on subdomains, suggesting departmental or project-specific deployments rather than company-wide infrastructure. For example, Burger King's detection sits on franchising.bk.com, not the main consumer site.

The age distribution skews young: 44.12% of Lambda customers were founded in the 2020s, with another 37.59% from the 2010s. Over 81% are digital-native companies less than 15 years old. This tracks with serverless being a "born-in-the-cloud" architecture choice rather than something enterprises migrate to from existing infrastructure.

Sales Signal: Lambda's customer base splits into two distinct personas. The bulk (91%+ under 50 employees) are small teams that adopted serverless from day one and likely need monitoring, security, and cost optimization tools. The enterprise segment (219 companies with 10K+ employees) runs Lambda on isolated subdomains and may need governance, compliance, and multi-cloud management solutions.

3. Industry and geographic concentration

Software Development leads at 8.33%, but the industry distribution is remarkably flat. The top 10 industries collectively account for only 43% of Lambda's user base, and no single vertical exceeds 9%. Technology and IT verticals (Software Dev, Tech/Internet, IT Consulting) combine for 17.6%, but the remaining 82%+ spans everything from construction (2.76%) to healthcare (1.37%) to non-profits (1.45%).

Geographically, the United States accounts for 37% of Lambda customers (25,984 companies). The UK trails at 8.4% (5,891), followed by Germany (3,174), France (3,033), and Canada (3,032). English-speaking markets represent 54%+ of the total. Strong showings from Germany, France, the Netherlands, and Switzerland point to Lambda's traction in European enterprise, particularly in finance and industrial sectors. India (752 companies) is notably underrepresented given its tech workforce size, suggesting Lambda adoption there happens more through AWS enterprise accounts that don't show up on public-facing domains.

Sales Signal: Lambda's horizontal distribution means industry-specific targeting won't work well. Instead, target by company age (2020s founders), size (1-50 employees), and geography (US, UK, Germany). The European enterprise cluster (Germany, France, Netherlands, Switzerland combine for 13.6%) represents a distinct segment from the US startup majority.

4. Migration patterns

Lambda gains companies from every competing platform. The largest inflow: 2,161 companies moved from Vercel to Lambda (all-time), while only 696 went the other direction, a 3.1:1 gain ratio. Netlify shows an even more lopsided 6.3:1 ratio (1,567 gained, 248 lost). Google Cloud Functions runs 3.6:1 in Lambda's favor (921 gained, 257 lost).

In the last year alone, Lambda gained 1,530 companies from Vercel and 644 from Google Cloud Functions. The 1-year Vercel-to-Lambda flow (1,530) accounts for 71% of all-time switches from Vercel (2,161), suggesting this migration corridor has accelerated recently.

"The 6.3:1 gain ratio against Netlify surprised me. Netlify built its brand on simplicity, and Lambda is traditionally seen as more complex. The data suggests companies outgrow simpler platforms and migrate to Lambda when they need finer control over execution, not the other way around." - Mehmet Suleyman, CEO at TechnologyChecker.io

Sales Signal: Companies migrating from Vercel and Netlify to Lambda represent a high-intent buyer segment. They've chosen to trade simplicity for control, which means they likely need developer tooling, observability, and CI/CD solutions built for Lambda. The 1,530 recent Vercel-to-Lambda switches are warm leads for any tool in the serverless operations space.

5. Technology ecosystem

The typical Lambda customer's tech stack is heavy on analytics and modern JavaScript. Google Tag Manager (70.58%) and Google Analytics 4 (57.91%) dominate the analytics layer, both well above market averages for any single technology. Cloudflare at 63.13% is the clear CDN winner.

On the development side, React (21.12%) and Next.js (9.21%) are the top framework choices. The React-to-Next.js ratio (2.3:1) suggests many Lambda users build React apps that don't use Next.js's built-in serverless functions, choosing Lambda directly instead. Amazon S3 (9.85%) and CloudFront (8.15%) co-adoption is lower than expected for an AWS service, indicating that many Lambda customers use non-AWS CDNs and storage providers.

Sales Signal: The low Amazon CloudFront co-adoption (8.15%) signals that Lambda customers aren't locked into the full AWS ecosystem. Tools that integrate with both AWS and non-AWS infrastructure have a stronger value proposition than AWS-only solutions. The 21% React adoption is also a targeting filter: Lambda users building React frontends need deployment, testing, and monitoring tools optimized for that stack.

6. G2 review signals

Across 992 G2 reviews, ease of use tops the positive sentiment with 47 mentions, followed by scalability (35) and cost-effectiveness (27). The negative side is dominated by resource limitations (36 mentions), which is actually the highest single-sentiment count across both pros and cons. Cold start performance drew 23 combined mentions across "slow performance" (13) and "lagging performance" (10) categories.

Cross-referencing with our migration data: the resource limitations complaint (36 mentions) doesn't seem to drive churn. Lambda's net migration is positive against all competitors, and the 14,020 previously-used-count (out of 113,511 total-ever) translates to only a 12.3% all-time abandonment rate. Users complain about limits but stick with the platform anyway, which aligns with AWS's history of gradually raising those limits (Lambda went from 5-minute to 15-minute max execution time in 2018, for example).

Sales Signal: The gap between resource limitations complaints (36 mentions) and actual churn (12.3%) creates an opportunity. Companies that hit Lambda's limits need solutions that work around them: orchestration tools (Step Functions), compute offloading (ECS/Fargate), or optimization platforms. They're frustrated but not leaving, so they're buying complementary tools instead.

7. Key takeaways

1. Market position: #3 in serverless with 99,491 detected domains, but ranking is partly a detection artifact since Lambda runs server-side.

2. Core customer: Digital-native micro-business, founded post-2010, under 50 employees, based in the US or Europe.

3. Growth phase: Mature service (launched 2014) with expanding detection visibility. Adoption is stable; our data coverage is what's growing.

4. Competitive moat: Net positive migration from every competitor. The 6.3:1 ratio against Netlify and 3.1:1 against Vercel show companies graduating to Lambda, not away from it.

5. Key vulnerability: Resource limitations are the #1 complaint on G2. AWS has been slow to raise cold start performance and memory limits relative to competitors like Cloudflare Workers.

6. Enterprise angle: 219 companies with 10K+ employees use Lambda, mostly on subdomains. Enterprise adoption is project-level, not platform-level.

8. Sales applications

Outreach template (for serverless tooling vendors): "Hi [Name], I noticed [Company] runs AWS Lambda on [detection_url]. We work with [similar company] to [solve specific Lambda pain point, e.g., reduce cold starts by 40%]. Based on TechnologyChecker.io data, companies your size in [industry] typically pair Lambda with [tech from stack data]. Would a 15-minute call make sense?"

Targeting strategy on TechnologyChecker.io: Filter for AWS Lambda customers + founded 2020-2025 + 1-50 employees + United States. This yields the highest-intent segment: young, small companies that chose Lambda deliberately and are actively building their tool stack. Layer on React or Next.js detection for developer tooling pitches.

Competitive angle: Target the 1,530 companies that switched from Vercel to Lambda in the past year. These companies just made a platform decision and are actively rebuilding their deployment pipeline, making them ideal buyers for CI/CD, monitoring, and serverless-specific DevOps tools.

For the full dataset of 70,209 enriched companies using AWS Lambda, including industry, size, location, and tech stack filters, visit TechnologyChecker.io.