Companies Using Express

I've tracked Express's adoption across our dataset of 169,570+ websites, and the patterns are worth examining closely.

Growth Trajectory

Express grew from 4 domains in September 2012 to a peak of 140,706 active domains in March 2025, then declined to 79,494 by July 2025. The 2014-2024 decade saw explosive growth, coinciding with Node.js's enterprise adoption. The sharp 2024-2025 peak reflects detection methodology changes and domain churn, not actual market contraction. Express's 7.15% market share ranks it 4th in web frameworks, behind ASP.NET variants but ahead of Laravel. This isn't a framework in decline. It's a mature platform with 341,424 domains that previously used Express, showing high churn typical of JavaScript frameworks where teams migrate to newer tools like Next.js or Fastify.

Sales Signal: Express's installed base is massive but aging. Companies using Express for 5+ years may be evaluating Next.js or NestJS. Target newer Express adopters (post-2020) who are building greenfield APIs. They're less likely to churn and more open to complementary tooling like monitoring, API gateways, or testing platforms.

Customer Profile

Express users are 74.68% founded after 2010, with the 2010s (40.69%) and 2020s (33.99%) dominating. Pre-1990 companies account for just 6.42%, showing Express is a digital-native technology. The enriched company list includes global enterprises like Accenture, IBM, Deloitte, Siemens, DHL, Oracle, HSBC, FedEx, Disney, and Saudi Aramco. All using Express for internal APIs, microservices, or subdomain applications rather than public-facing sites. This pattern is critical: Express powers backend infrastructure, not marketing sites.

Sales Signal: Express customers value flexibility and control over convention. They've chosen an unopinionated framework because they need to integrate with diverse systems (legacy databases, third-party APIs, polyglot microservices). Pitch tools that enhance rather than replace their stack. API observability, schema validation, rate limiting, or security layers that wrap Express without forcing a framework change.

Migration Patterns

Express gained 12,730 companies from ASP.NET (2.75:1 ratio), 9,122 from Ruby on Rails Token (1.73:1), and 7,647 from Ruby on Rails (2.64:1). These migrations reflect teams moving from monolithic server-rendered frameworks to API-first architectures. Express lost 5,265 to Ruby on Rails Token and 4,625 to ASP.NET, but net migration is positive across all top competitors. The 1-year data shows slowing churn, only 2,037 ASP.NET migrations in the last year versus 5,336 in the last 5 years, suggesting the ASP.NET-to-Node migration wave has peaked.

Sales Signal: Two-sided opportunity: (1) Companies migrating to Express need developer tooling (TypeScript support, testing frameworks, deployment automation). (2) Companies migrating from Express to Next.js or NestJS need migration services, gradual rollout strategies, or hybrid framework support. The churn rate (341K previous users vs. 170K active) suggests ~67% attrition over the framework's lifetime, target the 33% who stick around as loyal users.

technology stack

Express users pair the framework with React (47.81%), making MERN stack (MongoDB, Express, React, Node.js) the dominant architecture. Nginx (44.84%) reverse proxy is common for production deployments. Cloudflare (50.14%) and Amazon (45.49%) show strong cloud and CDN adoption. Next.js (18.38%) co-occurrence is rising, reflecting teams using Express for APIs while Next.js handles frontend. Google Analytics (63.12%) and Google Tag Manager (64.45%) are prevalent, showing Express backends power analytics-heavy applications.

Sales Signal: Express teams are JavaScript-first but infrastructure-aware. They use modern cloud tooling (Cloudflare, AWS, Google Cloud) and analytics stacks. Underrepresented categories include APM (application performance monitoring), error tracking, and API documentation tools, gaps in their stack that represent upsell opportunities. Tools that integrate smoothly with Express middleware (e.g., Sentry for errors, DataDog for metrics) will resonate.

What G2 Reviewers Say

The key signal from G2 reviews: convenient middleware setup leads with 1 mention as the top-cited strength. On the flip side, complex customization appears in 1 mention as the primary concern. This tells us that users who have adopted the platform value its core functionality, and vendors addressing the complex customization gap have a clear prospecting angle.

Key Takeaways

Express isn't dying, but it's no longer the default choice. The framework sits at a crossroads: entrenched in enterprise infrastructure yet losing mindshare to Next.js and Fastify in greenfield projects. The customer base is digital-native, JavaScript-first, and infrastructure-aware, with strong enterprise representation (Fortune 500 companies across consulting, manufacturing, logistics, finance, and energy). Migration data shows Express capturing ASP.NET and Rails refugees while slowly bleeding to Next.js. The 74.68% post-2010 cohort reflects a framework chosen by companies built for the cloud, not retrofitted into it.

Sales Applications

For sales teams targeting Express users on TechnologyChecker.io, here are practical prospecting strategies:

Outreach template: "We noticed [Company] uses Express for your API infrastructure, our data shows Express teams commonly pair it with React and Nginx, which aligns with your stack. We help Express users [solve specific problem: monitor API performance / secure endpoints / automate deployments] without ripping out the framework. [Example: Company X reduced API latency by 40% while keeping their Express setup.] Would you be open to a 15-minute demo?"

Targeting strategy: Filter TechnologyChecker.io for companies using Express + React + Cloudflare + founded 2015-2020. This cohort is mature enough to have scaling problems but young enough to invest in tooling. Exclude companies also using Next.js (they may be mid-migration). Prioritize industries with high regulatory or performance needs (finance, healthcare, logistics).

Competitive angle: Companies migrating from ASP.NET or Rails to Express (check the 1Y migration data) are in infrastructure transition, they need developer training, CI/CD pipelines, and cloud migration support. Companies migrating from Express to Next.js need gradual rollout tooling, API versioning strategies, or hybrid framework support.

Explore our full dataset of 74,315 enriched companies using Express at TechnologyChecker.io, filter by industry, employee size, founding year, and co-occurring technologies to build your ideal customer list.