Interesting, thanks for that. Our model for the compute-time-plus-markup was the plethora of companies that make money doing a similar model with storage -- Dr

Interesting, thanks for that. Our model for the compute-time-plus-markup was the plethora of companies that make money doing a similar model with storage -- Dropbox being the shining example. But you raise a good point that those are inherently more predictable for the users. You know that you need N Gb of storage because that's what's on your hard drive, whereas knowing how many seconds a calculation will take is much less knowable. Of course, if we were to take the more-technical route suggested by others on this page (ie. moved from being a "super-powerful programmable spreadsheet" to being "easy cloud supercomputing [with a shiny spreadsheetlike interface]") then perhaps our current pricing model would make sense. On the other hand, if we stick to the spreadsheet model, you could well be right. Hmm. Food for thought. Thanks for the pointer, anyway, and in particular for the reference to Heroku's dynos -- always good to know how people have successfully solved similar problems! Oh, and thanks for the heads-up re: the sheet that needed a sign-in, I've fixed that, and 1025 as well (it seemed to have the same problem).