Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

Dotnet application hosting

.NET application hosting in Canada

Plan a Linux-compatible .NET deployment with the runtime, database and background services your application needs. Check platform dependencies before choosing a VPS.

Hosting options

Compare the services for your project.

Your requirements

What does your project need?

01

Runtime and processes

Check .NET applications that need a supported runtime, Kestrel or service supervision, reverse proxying, environment configuration, logs, TLS, and deployment rollback.

02

Data to protect

Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.

03

Network access

List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.

04

Deployment and maintenance

Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.

Field guide

Kestrel behind a proxy, deployed with rollback

ASP.NET Core apps usually serve through Kestrel with a reverse proxy such as Nginx or Apache handling public TLS and forwarding requests. Run the app as a supervised service so it restarts after crashes and reboots, and forward the original scheme and host headers, or generated links and redirect targets will point at the internal address.

Memory sizing for .NET follows the working set of the running app plus the garbage collector's headroom, and container or VM limits should be visible to the runtime. The frequent deployment failure is a locked or half copied output directory, so publish to a fresh folder per release and switch the service to it, keeping the previous folder for rollback.

01

Forwarded headers setup

Configure the forwarded headers middleware and tell it which proxies to trust. Without this, HTTPS redirects loop and the app logs every client as the proxy address.

02

Data Protection keys

Persist Data Protection keys to a folder that survives deploys. New keys on every restart invalidate cookies, tokens, and protected form values.

03

Environment per deployment

Set the environment name through the service definition, not a file copied with the build. A staging build running as Production can send real email and write real data.

Planning

Access, backups and handover

Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.

Free guide

.NET application hosting in Canada: planning checklist

Use the detailed checklist to plan setup, access, migration and recovery with your team.

Download PDF →
Help choosing

Tell us about your project.

Send us the software you use, your storage needs and your launch or moving date.

Ask about hosting

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move