Runtime and processes
Check .NET applications that need a supported runtime, Kestrel or service supervision, reverse proxying, environment configuration, logs, TLS, and deployment rollback.
Dotnet application hosting
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
Shared hosting for websites, email and PHP applications, with Virtualmin included.
See Web hosting →02Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
Check .NET applications that need a supported runtime, Kestrel or service supervision, reverse proxying, environment configuration, logs, TLS, and deployment rollback.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
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
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.
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.
Persist Data Protection keys to a folder that survives deploys. New keys on every restart invalidate cookies, tokens, and protected form values.
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
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour 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.