Why WJb

Why WJb

Background jobs and workflows should not depend on infrastructure.

Why WJb

WJb was designed to be lightweight, portable, and infrastructure-independent.

  • No external services.
  • No database requirements.
  • No message brokers.
  • No workflow designers.
  • No DSLs.

Runs Anywhere .NET 10 Supports

With zero required external dependencies, WJb works in ASP.NET Core, Worker Services, console apps, desktop apps, mobile apps, and Blazor WebAssembly.

  • ASP.NET Core
  • Worker Services
  • Console Applications
  • Desktop Applications
  • Mobile Applications
  • Blazor WebAssembly
  • Serverless Functions
Even entirely inside the browser with Blazor WebAssembly.

Built Around Code

Most workflow engines are built around infrastructure, configuration, and platform-specific tooling.

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. No magic. Just C#.

An unhandled error has occurred. Reload 🗙

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.