If you want the Workers model—simple deployment, fast starts and CPU-based billing—for a C# API, there are several different paths to consider.
Can you run C# on Cloudflare Workers?
Cloudflare’s language documentation lists JavaScript, TypeScript, Python and Rust as first-class languages, with WebAssembly opening another route for compiled languages. C# projects can also target Workers through community tooling, such as this C# Workers project.
The practical question is whether your application and its dependencies fit that toolchain and runtime. Check support for your ASP.NET framework, database driver and any libraries that generate code at runtime.
Blazor hosting answers a different question
Cloudflare’s Blazor Pages guide hosts a Blazor WebAssembly frontend whose .NET code runs in the browser. Your server-side .NET API needs backend hosting of its own.
Where Isoplane fits
We’re building Isoplane for async .NET APIs, with a hosting model that charges for active CPU time and makes idle time, I/O wait and network egress free. Isoplane is an independent hosting platform for your .NET applications.
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.
| Your need | What to evaluate |
|---|---|
| C# code using Workers services | Community tooling, supported .NET APIs and access to the Workers bindings you need. |
| A Blazor WebAssembly frontend | Static frontend hosting, with a separate plan for the backend API. |
| An async .NET API with free I/O wait | Isoplane’s hosting model and launch compatibility, free to try in the beta. |
CPU billing needs a complete comparison
Workers already uses CPU billing. Its paid-plan pricing also includes a subscription and request charges. We’ll publish Isoplane’s full pricing when the beta opens, and running a project during the beta is free.
Start with the workload: CPU per request, I/O wait, request volume, database charges and network transfer. Our .NET CPU billing guide explains why a 200ms response can contain only 5ms of billable CPU.
What should I check before choosing?
- Can the runtime support your framework, packages and database access?
- Does it support the background work or state your app requires?
- Are the regions, limits and release workflow a fit for your users?
- Which resources does the provider charge for while your app waits for an external service?
If the Workers ecosystem is central to your app, evaluate its current C# tooling directly. If your priority is a home for async .NET APIs with free waiting time, sign up to be notified when the beta opens and try it with a real project.