.NET Hosting With Git-Driven Deploys and Autoscaling
Push ASP.NET Core apps from your Git repo and let autoscaling handle traffic spikes within the limits you set. Add a load balancer and replicated nodes when you need high availability.
Connect GitHub, GitLab, or Bitbucket. Track releases and redeploy or roll back with repeatable settings.
Lock in a baseline resource level at a lower rate. Burst capacity bills only while active.
Switch .NET versions and set environment variables from the dashboard. The platform resolves entry points automatically.
Containers spread across separate physical hosts automatically. SSL certificates provision and renew without scripts or cron jobs.
Choose the .NET deployment model that fits your workload
Managed containers
Windows VMs
- Manual deploys via RDP and Server Manager
- Fixed vCPU + memory plans — no horizontal autoscaling, no IPv6
- Browser-based RDP or standard RDP client
- Install Windows Server roles (IIS, Active Directory) after provisioning
- Disk and network billed separately
Best fit when you need to manage Windows Server roles like IIS or Active Directory.
.NET version switching
Choose managed containers for most ASP.NET Core workloads. Choose Windows VMs when you need IIS, Active Directory, or other OS-level administration. The two models cannot be mixed in the same environment.
Each .NET container node runs one active application context. For microservice architectures, deploy each service as its own environment.
Set reserved cloudlets (128 MiB RAM + 400 MHz CPU each) and a scaling limit. See Autoscaling & cost controls.
Automate deploys, routing, and runtime ops
The platform handles domain routing, deployment automation, and runtime operations. Bring your own CI/CD pipeline or use the built-in deploy-on-push workflow.
Domain routing and cutover
Route traffic with CNAME records for a shared load balancer in dev or staging, or DNS A records for a dedicated public IP in production. Swap environments for near-zero-downtime releases.
Pre/post deploy hooks
Run scripts before or after each deploy, including database migrations, smoke tests, cache warming, or notification webhooks. Configure hooks in the dashboard and they run on every deployment.
Auto-deploy from Git
Enable webhook-driven auto-deploy so every push triggers a fresh build. Combine with hooks to run tests before the new version goes live.
.NET deploy variables
Set APP_NAME, ASPNETCORE_URLS, and RUN_OPTION to keep releases consistent across staging and production.
Environment cloning
Clone an environment to create an isolated copy for testing or migration. Clones preserve architecture and configuration.
Deploy your .NET app in minutes
Push from Git to deploy. Autoscaling, SSL, and daily backups are included on every plan.
Architect .NET for availability and scale
Web API (HA)
LB + .NET nodes + external DB/cache
Place ASP.NET API nodes behind a load balancer. Store sessions in Redis or a database so any node can serve any request. Add nodes during traffic spikes, and the load balancer distributes requests automatically.
Use case: SaaS API backends, headless CMS services.
Microservices
Service-per-environment .NET
Deploy each .NET service as its own environment. Services communicate over internal networking. Each environment scales independently, so a busy API gateway does not force your background workers to scale with it.
Use case: decomposed monoliths, event-driven architectures.
Web + DB cluster
.NET web tier + managed database
Pair an ASP.NET web app with a managed database cluster (MySQL, MariaDB, or PostgreSQL). The cluster handles replication and automatic failover. Add shared storage for file uploads when the app tier runs multiple nodes.
Use case: e-commerce platforms, agency client sites.
Terminate SSL once and protect every app node.
Diagram shows SSL ending at NGINX before traffic reaches .NET Core.
Common Questions
How does .NET deployment work on the platform?
Add your repository to Deployment Manager, select the branch and target environment, and deploy. The platform handles build and run automatically.
Is this Windows-based or container-based?
This is the managed container model: .NET runs in Linux containers with a platform-managed lifecycle. No Windows server administration is required.
What deployment variables can I configure?
APP_NAME (target folder or DLL entry point), ASPNETCORE_URLS (URL binding), and RUN_OPTION (additional dotnet run flags).
What is the single-context deployment model?
.NET runs one active application at a time per node -- not multiple apps sharing a single container. For microservices, deploy each service as its own environment with separate scaling controls and independent deployment cycles.
How does scaling work and how do I set baseline/max cost guardrails?
Configure a reserved baseline for standard load and a burst limit for peak traffic. .NET containers scale within that window. Autoscaling & cost controls has configuration details.
Can I deploy ASP.NET Core web apps?
ASP.NET Core web applications, APIs, and services are all supported. Configure ASPNETCORE_URLS for URL binding control.
How do load balancers work with .NET apps?
A load balancer distributes traffic across multiple .NET nodes. Keep your application stateless or use external session stores for reliable scaling.
Which databases can I connect to?
MySQL, MariaDB, and PostgreSQL are available as managed nodes. Entity Framework and Dapper work with the standard connection strings. Database Clusters covers replication and clustering.
When should I choose Kubernetes instead of .NET on App Hosting?
.NET apps that need container orchestration, custom pod scheduling, or multi-service architectures belong on Kubernetes. Kubernetes Hosting walks through the options.
Can you help migrate an existing .NET app?
Our team can help with .NET migrations: project structure, runtime targeting, and deployment configuration. Portability & Migration has the process.
Can I automate deployment checks for .NET releases?
Deployment Manager workflows pair with pre- and post-deploy checks to keep .NET releases repeatable and auditable.
No matching questions found.
Start your 14-day free trial
Deploy in minutes with managed autoscaling and clustering built in.
No credit card required.