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.
We’re moving toward private preview and finalizing the SDK. We plan to support ASP.NET and Entity Framework at launch. Request early access to talk about your app with us.
| 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, private-preview fit and launch compatibility. |
CPU billing needs a complete comparison
Workers already uses CPU billing. Its paid-plan pricing also includes a subscription and request charges. We’ll release Isoplane’s full pricing when we enter public preview. If you’d like to compare costs today, request to join our private preview and we’d be happy to discuss pricing with you.
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, tell us about your app. We’ll use that conversation to assess private-preview fit.