How it works
Deploy from GitHub to your ASP.NET hosting
GitHub deploy connects a repository to your website. Enter the repository URL in the Control Panel, choose a branch and a deployment type, and publish with one click — the build runs on our server.
Four deployment types
Static copies the repository content to /wwwroot as it is, for plain HTML sites or output you build yourself. Build .NET app compiles .NET and ASP.NET Core projects with dotnet publish. Build Node.js SPA runs npm install and npm run build for React, Vue or Angular front ends. Node.js SSR app builds and runs server-rendered apps such as Next.js, Nuxt or Nest.js.
Build .NET apps without a pipeline
For .NET and ASP.NET Core applications we clone the repository, run dotnet publish in an isolated staging area and deploy only the compiled output. If the repository contains several projects, you choose which one to build. Recent builds and their logs are shown in the Control Panel.
Staging first, live when you say so
Enabling GitHub deploy does not touch your live site. Pull latest fetches the newest commit into a staging area, and the site changes only when you click Publish or Build & publish. Files that are not tracked by the repository, such as uploads or App_Data, are left untouched.
Automatic deploy on every push
On Premium plans you can switch on automatic deploy. Add the webhook URL and secret from the Control Panel to your repository on GitHub, and every push to the selected branch is pulled, built and published without a click. Deliveries are verified by their signature. Manual Pull and Publish work on the Free plan too.
Protected files
Production settings often differ from what is committed. List files or folders that should keep their live content — for example appsettings.Production.json, App_Data/ or uploads/ — and deploys will not overwrite them once they exist on the site.
Web Deploy and GitHub Actions
Prefer to publish from your own machine or pipeline? Download the publish profile from the Control Panel and publish from Visual Studio with Web Deploy, which uploads only changed files, or use the same Web Deploy login in a GitHub Actions workflow. FTP / SFTP remains available for file-level access.
Projects, output folders and start commands
If a repository contains several projects or front-end apps, you choose which one is built and deployed. For Node.js single-page apps you set the build output folder, and for server-rendered apps the start command is detected after the first build — both can be changed at any time in the Control Panel.
Try GitHub deploy for free
Start on the free ASP.NET hosting plan, then compare hosting plans and pricing when you want your own domain and automatic deploys.