Blazor Hosting: Complete Guide to Server, WASM & Auto

Blazor is the only mainstream web framework that lets you build full-stack interactive applications in C# and .NET. In .NET 10 LTS, Blazor supports four distinct render modes — Server, WebAssembly, Auto, and Static SSR — and the hosting platform you choose determines how well each of them actually performs in production.

This is a complete guide to Blazor hosting: what each render mode needs, what to look for in a host, and exactly what's included on every Adaptive Blazor hosting plan.

4 | Render Modes Supported

.NET 10 LTS | Latest Runtime


$9.49 | Plans From / mo


99.99% | Uptime SLA

!Blazor application interface

Why Blazor Deserves Specialized Hosting

Blazor isn't just "another web framework." It uses transport patterns that most hosting providers treat as edge cases:

  • Blazor Server runs on a persistent SignalR WebSocket connection — your host must handle long-lived connections, not just short HTTP transactions
  • Blazor WebAssembly ships the .NET runtime to the browser — your host has to deliver multi-megabyte payloads efficiently with Brotli compression and HTTP/2 or HTTP/3
  • Blazor Auto runs in both modes within the same session — your host has to do both well
  • Static SSR renders on the server but stays interactive — your host needs a real .NET process, not just a static-file server

Many "ASP.NET hosting" providers run Blazor as a sidecar on Linux containers. That works for trivial demos but creates real production friction with persistent SignalR connections, native IIS handlers, and the AOT-compiled binaries that Blazor WebAssembly needs.

Adaptive hosts Blazor on Windows Server 2022 with IIS 10 — the same configuration Microsoft optimizes for.

The Four Blazor Render Modes

Blazor Server

Your application runs on the server; the browser holds a thin JavaScript shim that communicates over SignalR. Every UI event (click, keystroke) is a network round-trip.

> ✅ Best for: internal LOB apps, dashboards inside a corporate network, apps with large server-side data that shouldn't ship to the browser, applications that already have a complex ASP.NET Core backend.

Blazor WebAssembly

Your application compiles to WebAssembly and runs entirely in the browser. The browser downloads the .NET runtime (1–3 MB) plus your app's DLLs (200 KB–2 MB) and runs them locally.

> ✅ Best for: public-facing SaaS, offline-capable apps, mobile PWAs, anything that needs to scale horizontally without per-user server load.

Blazor Auto (.NET 8+)

Starts in Server mode for fast first paint, then downloads WebAssembly in the background and switches modes for subsequent interactions. Best of both worlds when your application is structured for it.

> ✅ Best for: public SaaS where you want fast LCP and low-latency interactions both — increasingly the default for new public-facing Blazor apps.

Static SSR

Renders to plain HTML on the server, no interactivity unless you opt-in component-by-component with @rendermode InteractiveServer or @rendermode InteractiveWebAssembly.

> ✅ Best for: content-heavy sites, e-commerce product pages, documentation, anywhere SEO and LCP dominate.

For a deeper comparison with hosting trade-offs, see our Blazor Server vs WebAssembly guide.

What Blazor Hosting Actually Requires

| Requirement | Why It Matters | What to Look For |

|---|---|---|

| WebSocket / SignalR support | Blazor Server's transport | Native IIS WebSocket module enabled |

| Brotli compression | 15–25% smaller Blazor WASM payloads | Host serves .br files when browser supports it |

| HTTP/2 minimum, HTTP/3 ideal | Parallel asset download for WASM | TLS 1.2+, modern web server |

| Dedicated app pool | No cold starts when neighbors recycle | One IIS application pool per site |

| Long-cache headers on hashed assets | Returning users get instant load | Brotli + immutable cache |

| SPA fallback routing | Deep links to client-side routes | /* → index.html for WASM |

| Real .NET runtime, not Mono | Auto, Server, and SSR all need it | Windows Server + IIS 10 |

Every Adaptive Blazor plan ships all of the above by default — no manual configuration required.

!Modern .NET application stack

What's Included on Every Adaptive Blazor Plan

We don't sell a separate "Blazor plan" — every ASP.NET hosting plan supports Blazor fully. Here's exactly what each tier ships:

ASP.NET Developer — $9.49/mo

  • 2 Websites — perfect for a Blazor app + a separate staging site
  • 30 GB High-Performance SSD
  • 50 GB Guaranteed Bandwidth
  • Dedicated IIS Application Pool (1 GB RAM) — sized for small/mid Blazor Server apps (~50 concurrent users) or any size Blazor WASM
  • 2× SQL Server 2022 databases + 2× MariaDB databases
  • FREE SSL on every site
  • Plesk Control Panel
  • 5 subdomains, 5 FTP accounts, 5 domain aliases

ASP.NET Business — $17.49/mo (Most Popular)

  • 5 Websites
  • 50 GB High-Performance SSD
  • 100 GB Guaranteed Bandwidth
  • Dedicated IIS Application Pool (2 GB RAM) — sized for production Blazor Server apps (~150 concurrent users)
  • 5× SQL Server 2022 databases + 5× MariaDB databases
  • Higher Priority Resource Scheduling — smoother performance under load
  • 10 subdomains, 10 FTP accounts, 10 domain aliases

ASP.NET Professional — $27.49/mo

  • 10 Websites
  • 200 GB High-Performance SSD
  • 250 GB Guaranteed Bandwidth
  • Dedicated IIS Application Pool (4 GB RAM) — sized for high-traffic Blazor Server (~400 concurrent users) or complex Auto-mode apps
  • 10× SQL Server 2022 databases + 10× MariaDB databases
  • Highest Priority Resource Scheduling + Higher Priority CPU Scheduling
  • 25 subdomains, 15 FTP accounts, 15 domain aliases

> 💡 Blazor Server capacity rule of thumb: Each connected user holds 5–20 MB of server state. The Developer plan's 1 GB pool comfortably runs ~50 concurrent users; Business at 2 GB handles ~150; Professional at 4 GB handles ~400. Past that, scale vertically or partition users across multiple sites.

All Plans Include

  • .NET 10 LTS plus side-by-side .NET 7, 8, 9, and ASP.NET 2.0–4.8 Framework
  • Blazor Server, WebAssembly, Auto, and Static SSR — all four render modes
  • Windows Server 2022 with IIS 10
  • FREE SSL on every site
  • Automated backups
  • DDoS protection and Web Application Firewall
  • AWS Virginia data center
  • 99.99% uptime SLA
  • 24/7 expert support from .NET specialists
  • GitHub Actions / Azure DevOps / WebDeploy publishing
  • SmarterMail Pro add-on at $1.99/mo
  • 30-Day Money-Back Guarantee

Blazor Server Specifics

Blazor Server's persistent SignalR connection is the most often-misconfigured part of any Blazor deployment. Three things to know:

WebSocket Support is Required

The default fallback (long-polling) ships, but every interaction takes 2–3× longer than WebSocket. IIS 10 on Windows Server 2022 supports WebSockets natively and we enable the module by default — verify by checking Sec-WebSocket-Accept in your response headers.

Connection State Lives in RAM

Each connected Blazor Server user holds component state, dependency-injection scope, and authentication context on the server. Plan capacity accordingly:

// Trim allocations per-circuit

builder.Services.AddServerSideBlazor()


.AddCircuitOptions(o =>


{


o.DisconnectedCircuitMaxRetained = 100;


o.DisconnectedCircuitRetentionPeriod = TimeSpan.FromMinutes(3);


o.MaxBufferedUnacknowledgedRenderBatches = 5;


});

Idle Timeout Behavior

By default, disconnected circuits live for 3 minutes — long enough that a user's tab refresh doesn't lose state. Tune this based on your traffic pattern.

Blazor WebAssembly Specifics

Three pieces of WASM-specific configuration that make a measurable difference:

Enable AOT for CPU-Heavy Apps

<PropertyGroup>

<RunAOTCompilation>true</RunAOTCompilation>


<WasmStripILAfterAOT>true</WasmStripILAfterAOT>


<BlazorWebAssemblyEnableLinkerOptimization>true</BlazorWebAssemblyEnableLinkerOptimization>


</PropertyGroup>

AOT adds 30–50% to bundle size but improves CPU-bound code 2–10×. Use it for data grids, charting, image processing; skip it for thin UI shells.

Lazy-Load Heavy Routes

<ItemGroup>

<BlazorWebAssemblyLazyLoad Include="Admin.dll" />


<BlazorWebAssemblyLazyLoad Include="Reports.dll" />


</ItemGroup>

The single highest-leverage Blazor WASM optimization. See our Blazor WebAssembly performance guide for the full optimization checklist.

Brotli Compression

Adaptive's IIS 10 configuration serves .br files when the browser sends Accept-Encoding: br, falling back to .gz, then identity. Make sure your dotnet publish includes the compressed variants (it does by default in Release mode).

Blazor Auto Specifics

Blazor Auto requires your components to be render-mode aware — anything that uses server-only services (raw IConfiguration, server-only DBContext) won't survive the switch to WebAssembly. The pattern is:

@page "/dashboard"

@rendermode InteractiveAuto


<h1>Dashboard</h1>


@if (OperatingSystem.IsBrowser())


{


<p>Now running in WebAssembly</p>


}


else


{


<p>Running on server (still downloading WASM)</p>


}

For new public-facing Blazor apps in 2026, Auto is increasingly the right default — you get fast first paint (Server) and low-latency interactions (WASM) without committing to either mode's trade-offs in isolation.

Static SSR for Marketing and Docs

If you have a marketing site, blog, or documentation as part of your Blazor app, use Static SSR for those routes. The HTML is fully rendered server-side, ships to the browser in one round-trip, and ranks beautifully in search.

@page "/docs/{Slug}"

<!-- No @rendermode = static SSR -->


<h1>@Doc.Title</h1>


<article>@((MarkupString)Doc.Html)</article>

You can mix Static SSR (for content) with Interactive components (for the app) in the same project.

Frequently Asked Questions

Which plan should I pick for Blazor Server?

For Blazor Server, RAM is the primary constraint. Estimate 10 MB per concurrent user (conservative).

  • Developer (1 GB): up to ~50 concurrent users — internal tools, small SaaS
  • Business (2 GB): up to ~150 concurrent users — production SaaS
  • Professional (4 GB): up to ~400 concurrent users — heavy production traffic

Past that, partition users across multiple sites (you have 5–10 websites depending on plan).

Which plan should I pick for Blazor WebAssembly?

For pure WebAssembly, the constraint is static file delivery and API throughput, not server RAM. Any plan works — the Developer plan ($9.49/mo) handles most public Blazor WASM apps comfortably. Upgrade to Business or Professional when your backend API workload grows.

Does Adaptive support Blazor Hybrid (MAUI Blazor)?

Yes — the server-side API and database layer that backs a MAUI Blazor Hybrid app runs identically to any ASP.NET Core 10 backend. The mobile/desktop app itself ships through app stores or installers.

What about SignalR scale-out?

For most Blazor Server apps, vertical scale is sufficient. If you need to scale across multiple servers, SignalR supports a backplane (Redis, SQL Server, Azure SignalR). Talk to our team about specific configurations.

Can I run Blazor Server and Blazor WASM on the same plan?

Yes. Every plan supports multiple websites (2/5/10 by plan tier), and each website can be a different Blazor application. Run a Blazor Server admin tool alongside a Blazor WebAssembly customer-facing app — the dedicated app pool keeps them isolated.

Is Blazor Auto worth using over plain Server or WASM?

For new public-facing Blazor apps in 2026, yes. Blazor Auto gives you the LCP of Server-mode plus the post-load interaction latency of WASM. The cost is more complex testing (your components run in two modes) and slightly larger total payload (WASM downloads alongside the initial Server render).

Does Adaptive support .NET 10 LTS for Blazor today?

Yes. All plans include the .NET 10 LTS runtime, .NET 9, .NET 8 LTS, .NET 7, and ASP.NET 2.0 through 4.8. You can run any combination side-by-side.

title: Deploy Blazor on Infrastructure Built for It

description: All four render modes. Real Windows Server 2022 + IIS 10. SQL Server 2022 + MariaDB databases. Dedicated app pools, 99.99% uptime SLA, AWS Virginia. Plans from $9.49/mo.


cta-primary: Compare Blazor Plans | /blazor-hosting-plans


cta-secondary: Blazor Hosting Overview | /blazor-hosting

For deeper dives, read our Blazor Server vs WebAssembly hosting guide for the trade-offs, Blazor WebAssembly performance guide for optimization techniques, or .NET Core 10 hosting comprehensive guide for the runtime that powers it all.

Back to Blog