Enterprise .NET Core 9 Hosting: Production Guide
When your .NET Core 9 application moves from a developer laptop to production, three things suddenly start to matter that didn't matter before: how your hosting provider isolates your app from neighbors, whether your database is a real SQL Server or a crippled "Express" edition, and how aggressively the platform recycles your app pool to make room for someone else's runaway process.
Most Windows hosting providers get all three wrong. We don't. Here's what production-grade .NET Core 9 hosting actually looks like — and how to evaluate whether your current provider is silently throttling your application.
99.99% | Uptime SLA
<50ms | Avg Response
$9.49 | Plans From / mo
30 day | Money-Back
Why .NET Core 9 Deserves Better Infrastructure
.NET 9 (released November 2024) shipped real improvements over .NET 8: faster JSON serialization, server GC optimizations that reduced Gen-2 pauses by up to 30%, improved JIT inlining, and HTTP/3 support out of the box. But those gains only show up in production if the hosting layer doesn't quietly take them back.
!Modern data center serving .NET Core applications
What Oversold Hosting Costs You
We've migrated dozens of teams off oversold ASP.NET hosts in the past year. The pattern is identical every time:
- Cold-start spikes every 20 minutes, when shared app pools recycle to free RAM for a noisy neighbor
- SQL Server timeouts during business hours, when a shared SQL instance hits 90% CPU
- Throttled outbound HTTP calls, because the shared NAT IP hit its rate limit on Stripe or SendGrid
- Inconsistent response times — median 80 ms, p95 1.2 s — on workloads that ought to be flat
> ⚠️ The hidden cost: These are not .NET problems. They are hosting problems your provider hopes you don't notice. Run an APM trace on your "slow page" and you'll usually find the .NET handler took 12 ms — the other 1.18 seconds was the hosting layer fighting itself.
The Four Things We Engineer Differently
Our entire ASP.NET hosting platform is built around four non-negotiables:
| Principle | What It Means | Why Most Hosts Don't Do It |
|---|---|---|
| Windows-first | IIS 10 on Windows Server 2022, not Mono or Linux containers running .NET as an afterthought | Linux is cheaper to operate at scale; we accept the cost difference |
| Dedicated IIS app pools | Every site runs in its own pool, with its own memory limit and CPU affinity, never sharing with other tenants | Limits how many tenants fit per server (we provision instead of oversell) |
| Real SQL Server 2022 | Full Standard or Enterprise SKUs, not Express; full Query Store, ledger tables, Always Encrypted | SQL Server Standard licensing is real money; most shared hosts ship Express to dodge it |
| No overselling | Every CPU vCore, RAM byte, and IOPS we sell is provisioned, not promised | Overselling is the entire business model of $2.99/mo hosting |
These aren't marketing claims. They're contractual, with a 99.99% uptime SLA, 💡 Why this breaks on shared hosting: On a host that recycles app pools every 20 minutes to reclaim memory, you never get the warm-up payoff. On Adaptive, app pools recycle on your schedule (or never, if you prefer). PGO gets to do its job.
Native AOT and Trimming
.NET 9 expanded Native AOT support to more ASP.NET Core scenarios. If you publish with true, you'll see smaller deployments, faster cold starts, and lower memory footprint — assuming your host can run AOT-compiled binaries on IIS. Our IIS 10 handlers support AOT natively; no manual configuration required.
HTTP/3 and QUIC
Windows Server 2022 includes the msquic.sys kernel driver, and .NET 9 lets you opt into HTTP/3 with two lines of code:
builder.WebHost.ConfigureKestrel(o =>
{
o.ListenAnyIP(443, listenOptions =>
listenOptions.Protocols = HttpProtocols.Http1AndHttp2AndHttp3);
});
Behind Cloudflare's HTTP/3-enabled edge, you get the full client-to-origin upgrade. Average tail latency improves 15–20% over HTTP/2 on lossy mobile networks.
![Cloud infrastructure topology
SQL Server 2022: The Other Half of Performance
Most ASP.NET Core applications are database-bound, not app-server-bound. If your hosting provider gives you "SQL Server" but it's actually Express, you've capped performance before you've written a single query.
| Feature | SQL Server Express (shared hosts) | SQL Server 2022 (Adaptive) |
|---|---|---|
| Max database size | 10 GB | Unlimited (within plan storage) |
| Max memory used | 1.4 GB | Multi-GB, scales with plan |
| CPU utilization | Single core | All cores, parallel query execution |
| Query Store | Not available | Enabled by default |
| Always Encrypted | Limited | Full support |
| Ledger tables | Not available | Full support |
| JSON document types | Not available | Native JSON support |
| SQL Agent | Not available | Yes |
| MariaDB option alongside | Not available | Included on every plan |
The difference matters for .NET 9 specifically because Entity Framework Core 9 emits queries that exploit modern SQL Server features: MERGE for bulk upserts, native JSON predicates, batched DELETE/UPDATE. On Express, those features either fail or fall back to chatty single-row patterns that destroy throughput.
> 🚀 Pro tip: If your provider's plan page says "MS SQL" without specifying the SKU, assume Express. Real SQL Server is a budget line item your hosting vendor will mention prominently if they include it.
Deploying to Adaptive: What You'll Need
When you set up a .NET Core 9 application on Adaptive, here's the typical workflow:
- Plan provisioning — Sign up; your IIS site, application pool, SQL Server 2022 / MariaDB databases, and Plesk Control Panel are ready immediately
- Code deployment — Publish via WebDeploy from Visual Studio, push via Plesk Git, or upload via FTP/SFTP
- Database restore — Restore your
BACPAC(SQL Server) ormysqldump(MariaDB) through Plesk's database tools - DNS — Point your domain at our nameservers (or update A/CNAME records) when you're ready to go live
- TLS — FREE SSL is provisioned automatically once DNS propagates
> ✅ Backed by our 30-Day Money-Back Guarantee: If our infrastructure isn't the right fit, you get your money back during the first 30 days — no questions asked.
Looking Ahead: .NET 10 LTS
.NET 10 LTS launched in November 2025 and is supported through November 2028. If you're starting a new project today, our .NET Core 10 LTS hosting is the better starting point. .NET 10 brings:
- The fastest .NET runtime ever — JIT inlining, AVX10.2 SIMD, improved Native AOT
- Built-in AI integration via
Microsoft.Extensions.AI - Post-quantum cryptography (ML-KEM key encapsulation, ML-DSA signatures)
- TLS 1.3 mandatory by default
- Three years of free security patches
Adaptive hosts .NET 9 and .NET 10 side-by-side on every plan. You can ship .NET 9 today and migrate to .NET 10 on your schedule — usually a single ` change.
What's Included on Every .NET Core 9 Plan
- Windows Server 2022 with IIS 10
- Dedicated IIS Application Pools — 1 GB RAM (Developer), 2 GB (Business), 4 GB (Professional)
- SQL Server 2022 databases (2 / 5 / 10 by plan) — not Express editions
- MariaDB databases (2 / 5 / 10 by plan) — included alongside SQL Server
- .NET runtimes: ASP.NET 2.0–4.8 Framework, plus .NET 7 / 8 / 9 / 10 LTS, plus Blazor
- FREE SSL on every site
- Automated backups
- AWS Virginia data center
- 24/7 expert support from .NET specialists
- 99.99% uptime SLA
- Plesk Control Panel for deployment and management
- DDoS protection and Web Application Firewall
- Higher Priority Resource Scheduling on Business and Professional
- Highest Priority Resource Scheduling + Higher Priority CPU Scheduling on Professional
- SmarterMail Pro available as a $1.99/mo add-on
- 30-Day Money-Back Guarantee
Frequently Asked Questions
Can I run .NET 9 and .NET Framework 4.8 on the same plan?
Yes. Every plan includes IIS handlers for every supported runtime. You can pin each application pool to a specific runtime — useful for hybrid environments running a modern .NET 9 API alongside a legacy WebForms app.
How do you handle .NET 9 cold starts?
Two ways. First, dedicated app pools mean we never recycle yours to free memory for someone else. Second, our IIS 10 configuration enables AOT handlers that skip the JIT on first request when your build supports it. Cold starts on a typical .NET 9 API ship at 80–150 ms.
What's the SQL Server connection limit?
We don't enforce arbitrary per-account connection caps. SQL Server 2022 default max is 32,767 — and we provision plans with enough RAM and CPU to support hundreds of concurrent connections without contention.
Will my .NET 9 app stay supported after Microsoft drops .NET 9?
Yes. Microsoft ended mainstream .NET 9 support in November 2025, but we continue running .NET 9 runtimes for existing customers indefinitely. When you're ready, our team will move you to .NET 10 LTS.
What about backup recovery?
We run automated backups on every plan. Restoration is initiated through our 24/7 support team — just open a ticket from your Plesk Control Panel.
title: Ready to Ship Your .NET 9 App on Hosting That Doesn't Throttle You?
description: Dedicated IIS app pools, real SQL Server 2022, AWS Virginia infrastructure, 99.99% uptime SLA. Plans from $9.49/mo.
cta-primary: View .NET Core 9 Plans | /asp-net-core-9-hosting-plans
cta-secondary: Talk to a .NET Specialist | /contact
Already running on a different host? Your .NET 9 application is portable — publish your build, restore your SQL Server BACPAC`, point DNS at our infrastructure. The 30-Day Money-Back Guarantee means you can validate the move risk-free. See real customer outcomes, or compare all ASP.NET hosting plans side by side.