* 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
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