Companies Using Blazor

I analysed Blazor against our September 2026 crawl. We detect it on 13,563 domains, and 6,029 of them match a company record. The question people bring to this page is usually some version of "does anyone actually run Blazor in production?", so I've tried to answer it with sites you can open yourself. Our write-up on technology detection methods explains how a script on a page becomes a detection.

What we count, and the platforms inside the count

The detection is narrow and hard to trip by accident: the Blazor object the framework puts on the page, or one of its startup scripts, such as blazor.server.js or blazor.webassembly.js. Apps built on the .NET 8 template load blazor.web.js instead, which isn't on that script list, but they set the same object, so they're caught. In a random sample of 24 live domains, 17 of the 20 pages that loaded were first-party Blazor apps, and one embedded somebody else's Blazor widget.

The correction that matters is hosted platforms. Grouping every live domain by server address turned up five platforms serving Blazor to their customers: 1,134 used-car dealer sites on CarsForSale, 169 amateur sports-league sites on one platform hosted in Canada, 115 parked four-letter domains on a single lander, 95 domains belonging to OrganVue, a medical-imaging viewer, and 78 Italian hotel sites. Two third-party widgets add 70 more. That's 1,661 domains, 12.1% of the live base. The detections are correct, but the unit is wrong: each dealer bought a CarsForSale website, and CarsForSale chose Blazor. I've left the fleets out of the named list and the stack figures.

"The forum threads asking who runs Blazor in production are mostly answered by pages you'd never reach from a homepage: a grocer's account site, a university registrar, a football club's hospitality booking. Blazor went where .NET teams build tools behind a login." - David Thomson, CTO at TechnologyChecker.io

Sales signal: treat each hosted platform as one account. CarsForSale is a single buyer for anything that touches its 1,134 dealer sites, and the dealers themselves aren't Blazor prospects.

Portals, not homepages

Of the 50 organisations in our named list, 46 run Blazor on a subdomain: account.sprouts.com, registrar.wsu.edu, careers.pike.com, supplierportal.unioncoop.ae, whistleblower.gac.com. Pertamina is the rare exception, with blazor.web.js on www.pertamina.com. The same split explains an odd co-occurrence: WordPress shows on 11.24% of non-fleet Blazor domains, most likely because the marketing site and the Blazor app are separate builds under one domain.

I also read the startup script on the 114 verified sites where it was visible on 26 September 2026. 59 load blazor.web.js, the Blazor Web App model introduced with .NET 8, which can render on the server, in WebAssembly or both. 35 load blazor.server.js and 20 blazor.webassembly.js. Among organisations big enough to make our list, half already run the current model, and server-side rendering still outnumbers pure WebAssembly.

Denmark shows the platform route working in Blazor's favour. GoPublic, a Copenhagen CMS for municipalities and state agencies, loads Blazor on its sites, and 93 of the 258 live .dk Blazor domains run on it, among them Holbæk Kommune, Finanstilsynet, Datatilsynet and the Folketingets Ombudsmand. Unlike the dealers, each of those is a separate public body that bought a CMS, so I've kept them in.

Sales signal: sell to the team behind the subdomain, not the brand on the homepage. The buyer for account.sprouts.com is an application team, and it may never have met the marketing team that owns sprouts.com.

Who the non-fleet users are

With the fleets removed, 5,394 matched companies remain. 52.68% have 1 to 10 employees and 23.83% have 11 to 50, but 205 have more than 1,000, and every one of those survives the fleet cut. Software Development leads the industries at 11.46%, then IT Services and IT Consulting (7.95%) and Financial Services (4.08%). Retail falls from 5.26% on the full base to 2.82%, and Motor Vehicle Manufacturing leaves the top ten: that's the dealer fleet disappearing.

Geography moves the same way. The United States drops from 1,692 matched companies to 1,215 without the fleets, while the United Kingdom (479), Germany (302) and the Netherlands (266) barely change. Add Denmark (166) and Sweden (162), and those five European countries hold 1,375, more than the US.

Sales signal: a Blazor list is a .NET list with a European tilt. The nine European countries in the non-fleet top 15 hold 1,829 matched companies against 1,215 in the US, so plan for GDPR-compliant outreach and local-language copy.

The usage line and the churn figure

The chart runs from 5,080 domains in June to 13,563 in September 2026, and almost all of the rise is on our side. The July step came as our detection widened: 4,876 of today's live domains were first seen that month, with ordinary .NET stacks and no new platform behind them. A quarter of the live base (3,544 domains) was first seen in August or September, and the domains we crawl turn over every month. Nothing here supports a growth rate.

675 domains have dropped Blazor since we began tracking it in March 2026, and none of the destinations we checked qualifies as a switching corridor. The largest outflow to another framework, 72 domains that dropped Blazor and now run Vue, fails on overlap: 72.6% of the sites that ever ran both still do. React is more interesting in the other direction. 271 live Blazor domains no longer run React, but that's only 1.39 times what chance would produce, below the 2x we require.

"Everyone asks whether teams are leaving React for Blazor. In our data a few hundred sites have dropped React while running Blazor, which is barely above chance. The two mostly serve different teams." - David Thomson, CTO at TechnologyChecker.io

Sales signal: Microsoft ends support for .NET 8 and .NET 9 on 10 November 2026, according to its .NET support policy, and .NET 10 is the long-term release. Every Blazor app still on 8 or 9 has an upgrade due this autumn, which is a better outreach trigger than any switching story.

The stack around Blazor

Outside the fleets, IIS answers on 45.39% of Blazor domains and Kestrel, .NET's built-in web server, on 17.56%. Microsoft Azure hosts 31.05% and Microsoft 365 runs email on 30.12%. Across all live Blazor domains, 43.88% also carry an ASP.NET signal. This is a Microsoft estate from web server to inbox.

The UI layer is less settled. Bootstrap, which Microsoft's project templates ship with, sits on 47.57%, Tailwind CSS on 21.22% and MudBlazor on 17.79%. MudBlazor is a component library that lives almost entirely inside Blazor: 2,169 of its 2,195 domains also run Blazor. Commercial suites show up too, with Syncfusion's component CDN loading on 56 Blazor domains and Telerik's on 51.

Sales signal: component vendors compete for the same slot. A site on MudBlazor or plain Bootstrap is a prospect for a commercial grid or chart library; one already loading Syncfusion or Telerik is spoken for, so winning it means a displacement.

Key takeaways

1. 13,563 domains, and 17 of 20 random pages that loaded were first-party Blazor apps.

2. 12.1% of live domains are hosted platforms, led by 1,134 CarsForSale dealer sites; the named list and the stack figures exclude them.

3. 46 of 50 named organisations run Blazor on a subdomain portal, not a homepage.

4. Of 114 large sites, 59 use the .NET 8 blazor.web.js model, 35 Blazor Server and 20 WebAssembly.

5. No switching corridor to or from React, Vue or Next.js clears our bar.

How to use this list

Exclude the five hosted platforms first, then segment by what the subdomain does: account portals, careers sites and supplier portals have different owners inside the same company. Pair the list with IIS or Azure if you sell Microsoft-side services, and with MudBlazor, Syncfusion or Telerik if you sell components. The full list of 13,563 Blazor domains, with firmographics for 6,029 matched companies, is at TechnologyChecker.io.