You want to write your API, deploy it and get back to building. Compare the current Vercel route for ASP.NET Core with what Isoplane is building for async .NET apps.
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.
A free public beta is coming, and we plan to support ASP.NET and Entity Framework at launch. Leave your email and we’ll let you know when it opens.
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. | Sign up for the beta and deploy with isoplane deploy. |
| .NET application fit | Evaluate the container runtime and function limits for your app. | We’re starting with async APIs, with ASP.NET Core and Entity Framework planned for launch. |
| 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. | Full pricing is published when the beta opens; running a project during the beta is free. |
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, and full pricing follows when the beta opens.
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 a .NET-focused hosting experience with free I/O wait, sign up to be notified and try Isoplane with a real project when the beta opens.