I've run Quartz.NET jobs for years, and for most of that time I waited for someone to ship a proper dashboard. Eventually I stopped waiting and built the one I wanted. By the time I got serious, the official dashboard had already shipped - but it's Blazor, and Blazor and I never got along. So I kept going, and it became Cronlight: a plain web UI served as static files, with no Blazor or per-user server connection.

Full disclosure: a lot of this was built with AI tools. I drove the design, reviewed the code, argued with the model plenty, and it has unit and end-to-end tests running in CI. I'm not going to pretend I typed it all myself.

It drops into the ASP.NET Core app that already runs your scheduler - your scheduler, no connection string or schema of its own, never a second scheduler behind your back.

What it does:

Browse, create, and edit jobs (cron, one-time, interval) with the schedule in plain words and next fire times as you type, in any time zone.…