We’re starting with async .NET APIs, with a free public beta on the way. Here’s what we’re building for launch and how to tell whether your app fits.
Start with your API
Isoplane is focused on C# and .NET APIs that use ordinary async and await. Application state can stay in an external database. The hosting model makes idle time and I/O wait free, with active CPU billed by the millisecond.
ASP.NET and Entity Framework at launch
We plan to support ASP.NET and Entity Framework at launch to make porting your existing applications easier. This includes dynamic LINQ queries, reflection and runtime code generation.
Isoplane’s runtime doesn’t require AOT compilation, so most existing async .NET apps run with minimal modification. Native dependencies, background processing and platform-specific requirements are the areas to check first.
Interpreted execution
Isoplane runs your app’s compiled IL on a .NET runtime inside the sandbox. You build with dotnet build and deploy the result, with no AOT step and no runtime to compile or ship. We’re still finalizing the SDK.
State and durable instances
The initial focus is APIs with application state in external databases. We’re working on durable instances that retain state between requests.
What the beta means
When the beta opens you’ll be able to create an account, deploy a real project and run it at no cost. Leave your email and we’ll let you know when it’s live. We’ll share code samples, deployment guides and a detailed benchmark blog post as that work matures.
We’ll publish full pricing when the beta opens. You can explore the billing model in our .NET CPU billing guide.
What to check before you deploy
- Your .NET version, framework and key dependencies.
- Your database and any external services the API calls.
- Required regions, background work and stateful behavior.