Feature Request: Official .NET / C# SDK support

[gimmickj]

Summary

Is there a roadmap for an official .NET/C# SDK for DBOS? Currently DBOS supports Python, TypeScript, Java, and Go, but there's no .NET support yet.

Context / Use case

I work in the .NET ecosystem (C#, ASP.NET Core, PostgreSQL) and have been evaluating durable execution / saga orchestration options after several messaging libraries in the .NET space (MassTransit, MediatR) moved to commercial licensing. DBOS's Postgres-native, library-embedded approach (no separate orchestration server) fits very well with a PostgreSQL-centric .NET stack, and is a much lighter alternative compared to running a full Temporal cluster.

I believe there's real demand for this in the .NET community — many teams are already invested in PostgreSQL and are looking for lightweight durable execution options that don't require standing up additional infrastructure.

Questions

1. Is a .NET/C# SDK on the roadmap? If so, roughly what priority/timeline relative to the existing language SDKs?
2. Is the core protocol (system database schema, workflow/step checkpoint semantics, recovery logic) documented well enough that the community could contribute a third-party .NET SDK, if official support isn't planned soon?
3. Would the DBOS team be open to reviewing/supporting a community-maintained .NET port if someone in the community built one?

Happy to help test or provide feedback on a .NET SDK if this moves forward. Thanks for building DBOS — the architecture is a great fit for teams that don't want to run separate workflow orchestration infrastructure.

[kraftp]

Thanks for filing this! We are currently evaluating the possibility of adding SDK's in both C# and Rust, the two most requested unsupported languages. We don't yet have a definite timeline.

With regards to a community-maintained SDK--I'm frankly not convinced that's feasible. The DBOS SDKs are a ton of work to build and maintain with many subtleties and edge cases. Reviewing and supporting a (presumably AI-generated) C# or Rust SDK would not be easier than building it ourselves.

[gimmickj]

Thanks for filing this! We are currently evaluating the possibility of adding SDK's in both C# and Rust, the two most requested unsupported languages. We don't yet have a definite timeline.

With regards to a community-maintained SDK--I'm frankly not convinced that's feasible. The DBOS SDKs are a ton of work to build and maintain with many subtleties and edge cases. Reviewing and supporting a (presumably AI-generated) C# or Rust SDK would not be easier than building it ourselves.

Thanks for the update!

Just in case it's useful, there is already an early community effort to bring DBOS to C#:

https://github.com/phaser/dbos-transact-csharp

It's still experimental, but the maintainer has already done quite a bit of work exploring how DBOS could fit into the .NET ecosystem.

If the DBOS team decides to build an official C# SDK in the future, it might be worthwhile reaching out to the maintainer early. Even if the official implementation ends up being completely different, coordinating on package names, APIs, or migration paths could make adoption much smoother for the .NET community.

Really excited to see C# being considered alongside Rust. I'd be happy to help test an official SDK when the time comes.

[kraftp]

Thanks for filing this! We are currently evaluating the possibility of adding SDK's in both C# and Rust, the two most requested unsupported languages. We don't yet have a definite timeline.
With regards to a community-maintained SDK--I'm frankly not convinced that's feasible. The DBOS SDKs are a ton of work to build and maintain with many subtleties and edge cases. Reviewing and supporting a (presumably AI-generated) C# or Rust SDK would not be easier than building it ourselves.

Thanks for the update!

Just in case it's useful, there is already an early community effort to bring DBOS to C#:

https://github.com/phaser/dbos-transact-csharp

It's still experimental, but the maintainer has already done quite a bit of work exploring how DBOS could fit into the .NET ecosystem.

If the DBOS team decides to build an official C# SDK in the future, it might be worthwhile reaching out to the maintainer early. Even if the official implementation ends up being completely different, coordinating on package names, APIs, or migration paths could make adoption much smoother for the .NET community.

Really excited to see C# being considered alongside Rust. I'd be happy to help test an official SDK when the time comes.

Got it, thanks for letting us know about that effort, we'll reach out to the maintainer!