Companies Using Angular

Angular is the framework that most rewards being measured rather than discussed. The discussion has been settled for years: React won the mindshare argument, Angular is the enterprise option, and AngularJS is dead. Our crawl agrees with exactly one of those three statements.

Start with the footprint. TechnologyChecker.io detects Angular on 129,917 domains, ranking it 11th in JavaScript Frameworks with 1.89% of the category. Directly above it, at rank 10, sits AngularJS with 139,752 domains. The framework Google retired at the end of 2021 still has the larger live footprint than its own replacement, more than four years after the last release.

That claim deserves a hostile reading, because AngularJS is partly detected by a broad pattern that matches script filenames containing the word angular, and a loose pattern is exactly how a technology gets over-counted. So we graded it. Angular and AngularJS both expose their version number, which only the precise detection clauses can read, and a detection carrying a version cannot have come from the loose filename pattern alone. 93.35% of AngularJS detections carry a version string. Strip out every unversioned detection, the most punitive correction available, and AngularJS still finishes ahead of Angular. The result holds.

Angular has spent nine years replacing AngularJS and has not yet passed it. The migration that the industry treats as ancient history is, on the evidence of live domains, still unfinished.

The second finding is about Angular's relationship with its own release train. Angular ships a major version roughly every six months, and because it writes the version onto the page, we can read what each site is actually running rather than inferring it. Twenty distinct major versions are live right now. The most popular single release, Angular 21, holds 14.50%. Angular 22, the current release, holds 10.14%. Below them the distribution simply refuses to concentrate: Angular 20 at 9.27%, 17 at 8.68%, 19 at 8.61%, 18 at 7.57%, and a long descending tail that runs all the way back to Angular 2. Version 3 is absent, which is correct, because Angular skipped it.

Grouped into bands, 33.92% of version-graded Angular sites run version 20 or newer, 24.86% run 17 to 19, and 41.22% run version 16 or older. The largest single group is the one furthest behind. For a framework whose entire value proposition to large organisations is a predictable upgrade cadence, that is an awkward measurement, and it is the clearest quantitative expression of a complaint Angular teams have voiced for years: the cadence is predictable, but keeping up with it is expensive.

The third finding explains the second. Angular's customer base is old and large in a way its category neighbours are not. 13.97% of Angular companies employ more than 200 people, against 5.15% for React Router measured in the same crawl. 8.72% were founded before 1960, against 1.88%. Financial Services and Banking together account for 6.99% of matched companies. Organisations like these upgrade frameworks on procurement and audit cycles, not on release schedules, and a base weighted toward them will always trail the current version.

The detections themselves show the same thing. Angular does not usually appear on the marketing homepage. It appears on identity.att.com, signin.adp.com, software.cisco.com, services.boeing.com, account.kp.org and a Bayer shareholder portal. These are identity systems, partner consoles and support tools: long-lived internal applications where a rewrite is a budget line rather than a weekend. Deloitte, AT&T, Boeing, Cisco, AXA, Kaiser Permanente, TD Bank, Itau Unibanco and Axis Bank all serve Angular from production subdomains.

Geographically, Angular is the least American framework in its category. The United States accounts for only 20.32% of matched Angular companies. Germany takes 10.50%, more than two and a half times its 3.98% share of React Router's base in the same crawl, and India (6.99%) and Brazil (6.70%) both finish ahead of the United Kingdom (4.92%). If you sell developer tooling and your pipeline is US-weighted, Angular is where the non-US demand is.

Angular's install base is not a market to be won or lost this quarter. It is a maintenance estate: older companies, larger teams, internal applications, and 41.22% of it sitting on a release from 2023 or earlier.

One number cuts against the decline narrative. Angular's domains leave at a lower rate than anything comparable. Since we began tracking it in March 2026, 9,630 domains have dropped Angular, a 6.52% loss rate against its live base. Over the same window React lost 30.65% of its observed domains, Vue.js 10.90% and React Router 10.57%. Some of React's figure is a detection artifact rather than real churn, which we discuss on the React Router page, but Angular's low rate is not an artifact in the other direction: its signal is a version attribute the framework writes itself and read successfully on 99.43% of detections. Angular sites stay Angular sites.

We also tested the co-occurrence data for the story everyone expects, which is teams leaving Angular for React, and it does not survive testing. Angular domains that lose a React signal outnumber the reverse by more than ten to one, which looks decisive until you check React's behaviour everywhere else: React lost 1.31 million domains across the whole corpus in the same period. Set against that base rate, the flow into Angular is roughly one and a half times what you would expect from React's signal decay alone, nowhere near enough to call a migration. We publish no switching figures for Angular for that reason. A corridor has to beat the base rate before it means anything, and this one does not.

What to do with this. If you sell to Angular teams, the version spread is your segmentation. The 41.22% on version 16 or older are carrying real upgrade debt and are the audience for migration tooling, audits and long-term support. The 33.92% on version 20 or newer have working upgrade pipelines and buy different things. If you sell into the modern JavaScript ecosystem generally, note that Angular's base barely overlaps it: jQuery still appears on 44.46% of Angular domains and Bootstrap on 32.44%, against Tailwind CSS at 21.58%. And if your product depends on Angular's default change detection, the 8.84% of Angular domains running without Zone.js are the leading edge of a shift that will eventually reach the rest.