Why Blazor here
Blazor hosting that fits every render mode
Blazor lets you build interactive web UIs in C# instead of JavaScript — but different render
modes have very different hosting needs. Because we run on Windows Server and IIS with a real .NET
runtime, every flavour of Blazor feels at home here, from Interactive Server to WebAssembly to the
unified Blazor Web App model introduced in .NET 8.
Interactive Server and SignalR
Blazor Server (and interactive server render mode) keeps a live SignalR circuit
open between the browser and your app over WebSockets. Our platform keeps those
long-lived connections alive and gives each app its own dedicated RAM, so UI updates stay instant
even as your component tree grows.
WebAssembly and static assets
Blazor WebAssembly ships your app as static files that run in the browser. IIS serves them with
proper caching and compression, and because you get full control over the site root you can add
headers, fallback routing for deep links and your own web.config tweaks without
opening a support ticket.
Blazor Web App and streaming rendering
The unified Blazor Web App model in .NET 8, 9, 10 and 11 lets you mix static SSR,
streaming rendering and interactive islands in a single project. All of it runs unchanged on our
servers — deploy the whole app from Visual Studio and pick your render modes per component.
A real MSSQL backend
Most Blazor apps need data. Pair yours with a native SQL Server 2025 database and
connect Entity Framework Core directly, or manage it with SQL Server Management Studio. No external
database service to wire up — it is part of the same platform.
Start with the Blazor and SignalR Chat examples
When you create a website you can add a ready-made example in the last step of the wizard: a Blazor app with an interactive UI written in C#, or a SignalR Chat with real-time messaging over WebSockets. Neither needs a database, so you can see Blazor running on our hosting before you deploy your own code.
Hosting model and runtime settings
On the Scripting page you choose the ASP.NET Core hosting model: InProcess is recommended and OutOfProcess is supported with the DLL runtime. Environment variables are set per website in the Control Panel and applied on the next application start.
Blazor Server and WebAssembly hosting in one place
Whether you are building a dashboard with Blazor Server, a PWA with WebAssembly or a modern Blazor
Web App, our hosting has the persistent connections, dedicated resources and native SQL Server database support
Blazor relies on. Deploy from Visual Studio and go live in minutes.