If the data is not confidential, but you’re worried about someone messing with your computations, it still might be worthwhile to use defensive strategy and jus

If the data is not confidential, but you’re worried about someone messing with your computations, it still might be worthwhile to use defensive strategy and just run the same task multiple times on separate instances and compare results before accepting output. Since the task can be scheduled in parallel, there’s no significant overhead and it’s still way cheaper than Amazon/Google. It’s not exactly replacement for EC2, but there’s a lot of applications that would fit Gridspot just fine. But I guess one has to be much more aware of all the security issues when writing for a platform like this. The Gridspot folks should perhaps consider creating solid list of best-practice guidelines. Now can someone also create Gridspot for storage? :)