Can Vercel host ASP.NET Core?
Yes. Vercel’s ASP.NET Core deployment guide, published August 11, 2026, describes deploying a Docker container to Vercel Functions.
The documented workflow packages your ASP.NET Core app in a container, configures the service and port, then deploys it using Vercel’s tools. The function scales with traffic and can scale to zero. Follow Vercel’s current guide for the configuration and runtime limits.
What is Isoplane building?
Isoplane focuses on serverless hosting for async C# and .NET APIs: familiar .NET development, less infrastructure to manage and billing for active CPU time. Idle time between requests, I/O wait within a request and network egress are free.
We’re moving toward private preview and finalizing the SDK. We plan to support ASP.NET and Entity Framework at launch. Request early access and tell us what you’d like to build.
Compare the workflow you will actually use
“Vercel for .NET” can mean several things: a short initial setup, automatic deployments from Git, preview environments, or simply avoiding server maintenance. Think about which parts would make your day easier as you compare the options.
| Area | Vercel | Isoplane |
|---|---|---|
| Getting started | A public ASP.NET Core container deployment guide. | Request private preview access and discuss your app with us. |
| .NET application fit | Evaluate the container runtime and function limits for your app. | We’re starting with async APIs. Talk through your app’s requirements with us. |
| I/O wait | Active CPU billing pauses; provisioned memory remains billable during requests. | I/O wait is free. |
| Budgeting | Published pricing for CPU, memory and invocations. | We’ll release full pricing at public preview. Join the private preview conversation to discuss pricing today. |
Active CPU is only one part of Vercel’s bill
Vercel’s Fluid compute pricing separates active CPU, provisioned memory and invocations. During an I/O wait, CPU billing stops while memory billing continues until in-flight requests finish. Between requests, a paused instance incurs neither CPU nor memory charges.
For an API that spends much of its request duration waiting for a database, that distinction matters. Our CPU billing guide walks through the units to compare. If you’d like to compare costs for your own app today, request to join our private preview and we’d be happy to discuss pricing with you.
Which option should I explore?
If you need to deploy now and Vercel’s container route fits your app, its public guide is a concrete starting point. If you want to help shape a .NET-focused hosting experience with free I/O wait, we’d love you to request private preview access.
Tell us which deployment features are essential, along with your database, region and runtime requirements. These details help shape Isoplane’s deployment experience.