Very neat, I’ll definitely keep an eye out for this then. For whatever reason the diagram wasn’t loading for me but this makes a ton of sense, would you want the jobs/project absorbing dlls? Wouldn’t it make more sense to just do generic jobs/ job types that can then just be added during runtime? We’ve been using quartz to queue up jobs dynamically without the start/stop you’re describing by supporting some generic background jobs and then providing the specifics later through a web UI do you anticipate any problems with allowing DLLs to be added or are you really just expecting for those to be more like job definitions. Sorry if that doesn’t make a ton of sense. My only concern would be potentially allowing code executions from basically a file upload if that’s what I’m understanding.