It doesn't actually run the job but could be used to trigger them.
I think the idea could work if you could write the tasks as snippets of JS, think IFTT/Zapier but with a code editor.
It would definitely need to include:
* Web code editor for jobs (JS, Python, Ruby, Perl, Go, etc., etc.)
* Results served over an authenticated API (e.g., servicename.com/api/<username>/<jobname>/files/result.csv would get you the latest result.csv file generated by your script, .../<jobname>/20140419/files/result.csv would get you yesterday's, etc.)
* Jobs could probably be both scheduled (i.e., cron-like) or triggered via a webhook
I actually wrote a Node.js PaaS that I never open sourced & periodic short lived jobs was one of my use-cases.
Let's continue via email.
hello at duncanmsmith.com
Ideally, it would have the following features:
* Pay once, run forever (pay for the job up front and never again -- no recurring billing to worry about)
* Configure once, run forever (use Docker/LXC in the background to allow custom environments and absolve the user of the dependency headaches that can arise when running multiple jobs on a single machine)
* Easy to use
I've been casually working on this as it's a pain point I've experienced numerous times (e.g., running a daily job that should cost ~50 cents per month, which is substantially below any available VM price).
Would anybody use this? Other thoughts?