Updated September 2026 · Written and maintained by the Progression Agency strategy team
Modern .NET runs on Linux and Windows, in containers and on serverless platforms, which changed what ‘.NET hosting’ means. This guide covers the options for ASP.NET Core and Blazor applications (Azure App Service, Azure Container Apps, AWS and Google Cloud containers, Windows and Linux VPS, shared Windows hosting for legacy ASP.NET), .NET version support, performance, cost and how to choose, including what to do with a legacy ASP.NET Framework application.
On this page · 9 sections
The short answerHost ASP.NET Core and Blazor on Azure App Service if the organization is Microsoft-centric (identity, SQL, agreements), or in Linux containers on Azure Container Apps, AWS App Runner or Google Cloud Run otherwise; both are cheaper and simpler than Windows servers. Use a Windows VPS or Windows App Service only for legacy ASP.NET Framework (4.x) apps that need IIS and full-framework dependencies. Run a supported .NET version (an LTS release), keep the database on a managed service (Azure SQL, RDS, Cloud SQL) and put a CDN and WAF in front.
Comparisons are based on each project’s official documentation as linked in the text. Progression Agency builds with all of the technologies compared and has no affiliate relationship with any of them.
.NET hosting options
There are five realistic ways to host a .NET application in 2026: Azure App Service, a container platform such as Azure Container Apps or AWS App Runner, a Windows or Linux VPS, a Windows shared host for legacy apps, and Kubernetes for large estates. The table compares what each runs, who it suits and the effort it demands.
| Option | Runs | Best for | Effort | See |
|---|---|---|---|---|
| Azure App Service (Linux or Windows) | ASP.NET Core, Blazor Server, legacy ASP.NET (Windows) | Microsoft-centric organizations | Low | hosting on Azure |
| Azure Container Apps / AKS | ASP.NET Core in containers | Containerized apps, microservices | Low-medium / high | hosting on Azure |
| Azure Static Web Apps | Blazor WebAssembly, static front ends with API | Blazor WASM and SPAs | Low | hosting on Azure |
| AWS App Runner / ECS / Elastic Beanstalk | ASP.NET Core in Linux containers or on Windows EC2 | AWS-standardized organizations | Low-medium | hosting on AWS |
| Google Cloud Run | ASP.NET Core in Linux containers | Google Cloud teams | Low | hosting on Google Cloud |
| Linux VPS | ASP.NET Core behind Nginx or Caddy as a systemd service | Cost-driven teams with an operator | Medium | VPS hosting |
| Windows VPS or dedicated | IIS, legacy ASP.NET Framework, SQL Server | Legacy applications | High | dedicated server hosting |
| Shared Windows hosting (SmarterASP, HostForLIFE, InterServer, IONOS) | ASP.NET Core and Framework on shared IIS | Small legacy sites, low stakes | Low | shared hosting |
.NET versions and support
Microsoft ships a new .NET each November; even-numbered releases are Long-Term Support (three years) and odd-numbered releases Standard-Term Support (two years). Host on an LTS release (as of 2026, .NET 8 or .NET 10) and check the .NET support policy. ASP.NET Framework 4.8 remains supported as a Windows component but is legacy; new work belongs on ASP.NET Core.
Windows vs Linux for .NET
ASP.NET Core runs identically on Linux, and Linux hosting is cheaper (no Windows license), lighter and the default for containers. Windows is required only for ASP.NET Framework, IIS-specific modules, Windows authentication scenarios that cannot use Entra ID, or COM and full-framework dependencies. Microsoft’s hosting and deployment docs cover both.
Hosting Blazor applications
Blazor Server needs a persistent connection and runs on App Service, Container Apps or any ASP.NET Core host with WebSockets; Blazor WebAssembly is static files and belongs on Static Web Apps, Cloudflare Pages or any CDN with an API behind it; Blazor Web App (.NET 8+) mixes both and hosts like ASP.NET Core.
Databases and services
Use managed databases: Azure SQL or Azure Database for PostgreSQL, Amazon RDS (SQL Server or PostgreSQL), Cloud SQL. Keep secrets in Key Vault, Secrets Manager or the equivalent, and use Application Insights, CloudWatch or OpenTelemetry for observability. See backend hosting options.
What .NET hosting costs
Linux App Service or container hosting for a business app runs $50-$300 a month plus the database; Windows plans and SQL Server licensing add materially; a Linux VPS runs an ASP.NET Core app for $10-$60 plus an operator’s time; shared Windows hosting is a few dollars a month for small legacy sites. See website hosting cost and AWS vs Azure vs Google Cloud.
What to do with a legacy ASP.NET Framework application
A legacy ASP.NET Framework application still needs Windows and IIS, so the first job is to host it safely and the second is to plan the move to ASP.NET Core, which opens up Linux and containers. The sequence below is the one we follow.
- Stabilize: Windows App Service or a managed Windows VPS with patching, backups and monitoring.
- Assess: dependencies on full framework, IIS modules, COM, Windows auth.
- Migrate incrementally to ASP.NET Core using Microsoft’s upgrade tooling and a strangler pattern, moving routes as they are rewritten.
- Containerize the Core version and host on Linux; retire the Windows server last.
- See cloud migration services and .NET development services.
Choosing .NET hosting by situation
The right .NET host follows from three facts: which runtime the application targets, which cloud the organization already uses, and whether anyone will patch a server. The table maps the common situations to a recommendation.
| Situation | Recommendation |
|---|---|
| ASP.NET Core app, Microsoft-centric organization | Azure App Service (Linux) or Container Apps + Azure SQL |
| ASP.NET Core app, AWS organization | App Runner or ECS + RDS |
| ASP.NET Core app, Google Cloud organization | Cloud Run + Cloud SQL |
| Blazor WebAssembly front end | Static Web Apps or Cloudflare Pages + API |
| Legacy ASP.NET Framework | Windows App Service or managed Windows VPS, then migrate |
| Small internal .NET tool, low budget | Linux VPS behind Caddy |
| Regulated data | Azure or AWS with compliance controls; see SaaS hosting |
How Progression Agency hosts .NET
Linux containers on the client’s cloud (Container Apps, App Runner or Cloud Run) with a managed database, Entra ID or Cognito for identity, infrastructure as code and monitoring; Windows only for legacy applications during migration. See .NET development services and DevOps services.
Hosting or migrating a .NET application?
Tell us the framework version, dependencies and cloud; we will recommend the host, set it up and plan any migration.
Getting found in search
AI, AEO and what is changing
Paid media and lead generation
Websites and design
Choosing and working with an agency
Software and app development
Web development, platforms and hosting
- React vs Vue vs Angular
- Svelte vs React
- Astro vs Next.js
- Next.js vs React
- Web development frameworks
- What is a tech stack
- SSR vs CSR vs SSG
- React Native vs Flutter
- Vercel vs Netlify
- Cloudflare vs AWS
- AWS vs Azure vs Google Cloud
- Web hosting types compared
- Hosting for React and Next.js
- SaaS hosting
- WordPress hosting guide
- Backend hosting options
- Website hosting for small business
- Headless CMS vs traditional CMS
- WordPress alternatives
- Best CMS platforms
- Webflow vs WordPress
- Wix vs Webflow
- Framer vs Webflow
- Shopify vs WooCommerce
- Custom software vs off-the-shelf
- Website development cost
- Monolith vs microservices
- Custom website development services
- React development company
- Next.js development company
- WordPress development company
- Webflow development agency
- Front-end development company
- WordPress maintenance services
- Ecommerce website redesign services
- Website migration services
- DevOps services
- Cloud migration services
- Website speed optimization services
- Website security services
- VPS hosting explained
- Website hosting cost
- Cloud hosting explained
- Hosting a website on AWS
- Hosting a website on Google Cloud
- Hosting a website on Azure
- Dedicated server hosting
- Shared hosting explained
- WooCommerce hosting
- PHP hosting
- Best headless CMS platforms
- Headless WordPress
- Static site generators compared
- Small business website redesign services
- Angular development company
Social, content and brand
By industry and by situation
Frequently asked questions
What is the best hosting for .NET?
Can ASP.NET Core run on Linux hosting?
Do I need Windows hosting for .NET?
Which .NET version should I host?
Can I host .NET on AWS or Google Cloud?
How do I host a Blazor app?
How much does .NET hosting cost?
Is shared Windows hosting good for .NET?
Can I host .NET on a VPS?
What should I do with an old ASP.NET Framework app?
Which database should a .NET app use?
Does Progression Agency build and host .NET apps?
Is ASP NET hosting the same as ASP.NET Core hosting?
Where can I find hosting for ASP NET applications with SQL Server?
Is there any ASP NET hosting free tier worth using?
Do I need Windows VPS hosting for a .NET application?
Need help choosing or moving hosting?We recommend, set up, migrate and manage hosting for the sites and apps we build, and for sites built elsewhere.
Get a free marketing proposal
Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.
