Deploy .NET on Velixir
Push your ASP.NET Core source and Velixir builds it into a container image server-side, then runs it on managed Kubernetes with autoscaling and zero-downtime deploys. No Dockerfile, no local build, no publish profile to hand-tune.
Why deploy .NET on velixir
- Your target framework is read straight from your .csproj and Kestrel is detected automatically, so ASP.NET Core, Blazor, and Worker Service projects build and boot with zero config. No Dockerfile, no publish profile, no local dotnet publish.
- Managed Postgres pairs cleanly with Npgsql and EF Core: the connection string is injected as an environment variable, so your DbContext and dotnet ef database update migrations just work. Managed Valkey covers distributed IMemoryCache, output caching, and SignalR backplanes.
- Lift-and-shift legacy apps: because the framework comes from your csproj, an old .NET Core 3.1 or .NET 5 service deploys the same way a fresh .NET 10 minimal API does, with instant one-click rollback if a release misbehaves.
- EU data residency with regions in EU Central and NA East, unmetered bandwidth with no egress fees, plus optional high availability (a warm-standby replica) you can toggle on any plan for production ASP.NET workloads.
Works with your stack
Popular .NET frameworks and runtimes deploy as-is, no adapters.
Runtime versions
Pick your version and we pin the exact runtime for every build.
Legacy (past upstream end-of-life, still runnable for lift-and-shift):
From .NET source to production in three steps
Push your source
Git push, velixir deploy, a dashboard upload, or a connected GitHub repo. No Dockerfile.
We build it server-side
Velixir detects .NET, installs dependencies, and builds a container image on our infrastructure.
It goes live
Managed Kubernetes runs it with autoscaling, zero-downtime rolling deploys, and one-click rollback.
.NET hosting FAQ
Which .NET versions does Velixir support?
Everything from .NET Core 1.0 through .NET 10. The target framework is read directly from your .csproj, so you deploy whatever moniker (net8.0, net10.0, netcoreapp3.1, and so on) your project already targets. That makes lift-and-shift of older .NET Core services painless: no upgrade required to get onto the platform.
Do I need a Dockerfile or a publish profile?
No. Velixir detects the .csproj in your repo, restores, and builds your source into a container image server-side. There is no Dockerfile to write, no dotnet publish to run locally, and no .NET SDK needed on your machine or in CI to ship.
How do I connect to a database and run EF Core migrations?
Provision managed Postgres (billed hourly in EUR) and the connection string is injected as an environment variable your DbContext reads. Point Npgsql at it and run dotnet ef database update, or apply migrations on startup. Managed Valkey (Redis-compatible) is available the same way for caching and SignalR backplanes.
How do I deploy my .NET app?
Push source however you like: git push, the velixir deploy CLI command, a connected GitHub repo, or a dashboard upload. Velixir builds the image, pushes it to a private registry, and rolls it out with zero-downtime deploys. Autoscaling and one-click rollback are built in, and no credit card is required to sign up.
Deploy your .NET app in under two minutes
Push your code and Velixir builds, publishes, and deploys it to the region you pick, EU Central or NA East, with managed Postgres and Valkey a click away. No Docker, no YAML, and your first month's on us, up to €14.99.
No credit card to sign up. Add a payment method only when you're ready to deploy.