Host a Blazor application on a Windows VPS in France
Blazor Server keeps one SignalR connection open per user: that render mode is what needs a machine of its own, not shared hosting.
Starting at €8/mo
Introduction
Two applications both called Blazor can need two very different kinds of hosting. Blazor Server runs your code on the server and keeps a SignalR connection open for every user: the machine holds the state of each session, and the smallest network drop shows up immediately on screen. That is the mode that justifies a server of your own. At By-Hoster the Windows VPS range starts at €8/month incl. VAT, delivered in 10 minutes with a dedicated IPv4 address and full administrator access.
Blazor WebAssembly tells the opposite story. Once published, the application is nothing more than a bundle of static files — HTML, JavaScript, .NET assemblies — downloaded by the browser, which then runs all the code on the client side. Such a bundle needs nothing beyond a server able to hand out files: our shared web hosting from €1/month does the job. Saying so costs us a sale; keeping quiet would cost you a server you do not need.
The VPS becomes the right tool again as soon as there is a Server mode, an API to host behind the WebAssembly bundle, or automatic interactive rendering mixing both. You then get a bare system: IIS, the ASP.NET Core runtime and its matching module install freely because you are administrator. Nothing else is preinstalled, the TLS certificate is set up through whichever mechanism you use, and the Microsoft licence stays your responsibility.
What the server brings to a Blazor application
One SignalR circuit per connected user
In Server mode every open tab creates a SignalR circuit that the server maintains and whose state it keeps in memory. Consumption therefore does not follow traffic but the number of concurrent sessions, and it grows with whatever your application stores per user. A dedicated VPS lets you measure that real consumption, then pick a configuration on evidence rather than blindly.
IIS and the runtime install, they are not shipped
The machine arrives with the operating system and nothing else. The Web Server role is added from Server Manager or in one line of PowerShell, then you install the ASP.NET Core runtime and the module that puts IIS in front of Kestrel, both downloaded from Microsoft. No panel forces a version, no prepared image decides for you, and the WebSocket protocol is enabled like any other Windows feature.
500 Mbps, dedicated IPv4 and Anti-DDoS
A Blazor Server application lives on its network link: the connection stays open for as long as the user is working. Every configuration includes a dedicated IPv4 address, Anti-DDoS protection and 500 Mbps — 1000 Mbps on Titan. Recovering a circuit after a micro-outage, however, is handled inside your application: that is code, not infrastructure, and we would rather not suggest otherwise.
NVMe, snapshots, VNC console, 24/7 support
NVMe storage, snapshots triggered from the client area before a runtime upgrade, self-service reinstallation, a fallback VNC console if a firewall rule locks you out of RDP, and human 24/7 support by ticket, Discord and phone. No commitment, 48-hour money-back guarantee, 10% off with annual billing. Only snapshots are included: there is no automatic off-site backup.
What actually gets deployed on these servers
A line-of-business Blazor Server app
An internal tool used by a known team, where Server mode simplifies everything: no API to write, the logic stays on the server and close to the database. This is the use case that genuinely calls for a dedicated machine and RAM.
Automatic interactive rendering
An application that starts in Server mode for the first paint, then switches to WebAssembly once the assemblies have downloaded. It needs both halves in one place: an ASP.NET Core server able to serve the static bundle and to hold the circuits.
The API behind a WebAssembly bundle
The static bundle can be served by shared hosting, but the ASP.NET Core API it calls needs a server. You host it here, with its database and background jobs, and you keep control over authentication and CORS.
A dependency that requires Windows
A .NET Framework library still used by the back office, a COM component, a driver or a business executable that only exists on Windows. That is where choosing Windows over Linux genuinely holds up, and not just out of habit.
Blazor and its SQL Server database
Application and database engine on the same machine: the connection string points at localhost and port 1433 has no reason to be exposed. SQL Server still needs its own licence, Express being free within its documented limits.
A staging environment at €8
A second Windows - Core VPS to test a runtime upgrade or an IIS configuration change before touching the server that does the work. Snapshot before the attempt, reinstall from the client area if the experiment goes wrong.
Frequently asked questions
The Windows VPS range starts at €8/month incl. VAT with Windows - Core (4 vCores, 8 GB of RAM, 50 GB SSD, 500 Mbps). Above it: Plus at €13 (8 vCores, 16 GB, 200 GB), the most popular configuration, Max at €26 (16 vCores, 32 GB, 500 GB) and Titan at €49.99 (24 vCores, 64 GB, 800 GB, 1000 Mbps). Annual billing takes 10% off. The price covers the machine, the network and the support; it includes no Microsoft licence.
This is the only question that matters before ordering. Blazor Server runs your code on the server and keeps one SignalR circuit open per user: memory is consumed per session, the app depends on a stable connection, and a machine of your own becomes necessary. Blazor WebAssembly, once published, is only a set of static files executed by the browser: it needs no server-side runtime at all. If you are in that second case and have no API, a Windows VPS is money spent for nothing.
Yes, and it is often the right call. After publishing, a WebAssembly application is a folder of files — index.html, JavaScript, .NET assemblies — that the browser downloads and runs itself. Our shared web hosting starts at €1/month and serves that perfectly well. The VPS only becomes useful again if you have an ASP.NET Core API behind it, a Server mode, or automatic interactive rendering combining both halves.
It depends on what your application keeps in memory per user: we publish no per-circuit figure, because nobody has measured it against your code. Our published sizing rule stays 4 GB for light use and 8 GB as soon as you add business software, SQL Server Express or several concurrent users. All our plans already start at 8 GB. With a database on the same machine and many sessions, Windows - Plus and its 16 GB at €13/month save you from counting memory.
No. By-Hoster delivers a bare system: Windows, full administrator access, and nothing else. The Web Server (IIS) role is added from Server Manager or in one line of PowerShell, with Install-WindowsFeature -Name Web-Server -IncludeManagementTools. You then install the ASP.NET Core runtime and the module that puts IIS in front of Kestrel, downloaded from Microsoft. It is a deliberate choice: no prepared image, no panel locking you to a runtime version.
Through whichever mechanism you already use: administrator access lets you install your usual tool, import an existing certificate into the Windows store and create the HTTPS binding in IIS. One point matters for Blazor Server: the circuit runs over WebSocket, so your TLS configuration must cover that connection like the rest of the site. By-Hoster supplies, renews and manages no certificate — we deliver the machine, you decide what runs on it.
Yes, and the Microsoft licence remains your responsibility: we install the system but neither supply nor resell a licence. Two points come up next. Windows Server allows 2 concurrent administrative RDP sessions; beyond that, application RDP access requires Microsoft RDS CALs — which concerns people opening a desktop on the machine, not your web visitors. And SQL Server needs its own licence: Express is free, Standard and Enterprise are paid.
Very often yes, and we would rather say so. ASP.NET Core is cross-platform: a Blazor Server app runs comfortably on Linux behind Nginx, and our Linux KVM VPS start at €4.99/month, with no Microsoft licence to buy. Windows keeps the advantage in three precise cases: a .NET Framework dependency, a COM component or an executable that only exists on Windows, or the need to open a graphical RDP session. Our Windows or Linux guide works through the trade-off.
In Blazor Server, the user loses their circuit and the interface freezes until it reconnects: that is the accepted trade-off of the model, and an unstable client-side network shows immediately. In WebAssembly, the application keeps running in the browser. On the server side, every configuration includes 500 Mbps, a dedicated IPv4 address and Anti-DDoS. Handling circuit recovery, though, belongs to your code: no infrastructure replaces it.
Three systems are offered at checkout, at no extra cost: Windows Server 2025 (mainstream support until 13 November 2029, security until 14 November 2034), Windows Server 2022 (mainstream until 13 October 2026, security until 14 October 2031) and Windows 11, a client system to keep for a workstation as it is not designed to host a multi-user service. The server runs in our single DC-FR_NA(01) datacenter in Nouvelle-Aquitaine, on KVM with Proxmox, under French jurisdiction and with no transfer outside the European Union.