Why WJb
Background jobs and workflows should run wherever .NET runs.
Why WJb
WJb was designed to be lightweight, portable, and infrastructure-independent.
- No external services.
- No databases required.
- No message brokers.
- No workflow designers.
- No DSLs.
Runs Anywhere
With zero required external dependencies, WJb can run anywhere .NET runs.
- ASP.NET Core
- Worker Services
- Console Applications
- Desktop Applications
- Mobile Applications
- Blazor WebAssembly
Including entirely inside the browser.
Built Around Code
Most workflow engines are built around infrastructure.
WJb is built around C#.
Actions, jobs, and workflows are regular C# code that can be debugged, tested, refactored, reviewed, and versioned using standard .NET tooling.
No infrastructure. No DSLs. Just C#.