Hacker News Reader

Thanks for sharing your concerns, and I understand where you're coming from. I encourage you to check out the TOS's for Google App Engine and Heroku and other cloud-hosting services, which have similar wording, as I understand it. If you have suggestions on better wording that meets the needs of what we need to be able to do to provide the service etc., we welcome suggestions on that. Thanks.

View on HN

I understand what you mean, most legalese can seem quite imposing out of context. The nut of the problem for me is that it's obvious you're intending a profit making venture (tos, etc.) but you aren't telegraphing where the money comes from. With heroku, etc. it's clear what their intent would be (paid hosting) even when embryonic or unstated. As many IDE's are free without service terms if your intent is to sell SaaS, perhaps a "beta testers get free (blip) when we launch" - or whatever. That at least would keep me from worrying on the monster behind the curtain.

thanks, we put a bit on that here:

https://coderbuddy1.appspot.com/help

If CoderBuddy is free, how will you make money to pay the bills?

Our goal is to keep providing our current services for free, and expand those free services. We expect to earn revenues from advertising and from helping software developers earn money for their work. We may also charge fees to a tiny percentage of heavy users of disk/bandwidth/cpu to cover costs, but those should only apply after usage of a generous free quota.

Reply on news.ycombinator.com