What a brilliant, yet simple, yet brilliant idea!<p>Observation: Online cron jobs are not unlike online containerized web services (both involve running code) -- the difference is in the invocation event -- online web services are typically invoked in response to an HTTP (or other protocol) request, online cron jobs are invoked in response to a timer event, that is, in response to a specific, pre-scheduled, time.<p>So we have both request-based and pre-scheduled time-slot based -- invocation methods...<p>In theory there could be online code invocation -- <i>based on a series of user-defined events and/or conditions...</i> sort of like "if the time is X" and "the temperature in Siam is 52 degrees" and "Our shipping partner in the far east has just shipped 50,000 widgets" -- then send them an email... or invoke some code which does something like that...<p>Or perhaps, a connected web search just returned a new web page containing specific search terms -- now run some code to process that page in some way, and return the results formatted to some format...<p>The possibilities are endless...<p>Observation: There's not just code that lives online -- but <i>there are all sorts of conditions, other than http requests and pre-scheduled time slots</i> -- that could cause code to be invoked, for one reason or another...<p>Perhaps there's a future business for creating a <i>control panel for users to invoke their online code</i> -- in response to different types of events/sets of conditions -- occuring in the real and/or digital world...<p>Anyway, once again, great idea for online cron jobs -- and I wish you all of the success in the world with your business!