Exactly, anything can be considered a service, and the one service
obviously not allowed it reselling. Reselling in my books equates to
not adding value on top of App Engine. It's really just rebranding.
Uploading someone else's static files onto App Engine (including
configuring app.yaml and so o
There is a gray area. Ikai talked about it, and I believe you fall right in
the middle of it. Anything can be considered a "service" by the
English definition, including, as you mentioned, simply uploading the files.
But I'm pretty sure you can't open up a website offering "upload services"
for $30
I don't see how your first example could be construed as reselling at
all. I do essentially exactly that for a couple of my own personal
websites. It's free and the pages load incredibly fast compared to
other hosting I've used. If a client is willing to pay me X$/month to
host their static files o
The gray area seems to depend, partly, on the complexity of the app. If, for
example, you build a 1 page static business-card website that you host on
GAE and charge $30/month for, that can be construed as selling hosting. On
the other hand, if your application is very large and complex and provide
That's allowed. We're more permissive than restrictive with the terms of
service. Unless you are reselling the baseline App Engine service, you
should not be in violation. You are in the clear if you provide App Engine
support, wrote an App Engine application, or sell access to some service
that ru
Yes and yes. This is the model employed by the Google Apps Marketplace.
- alkis
On Mon, May 17, 2010 at 11:43 PM, Baz wrote:
> To be painfully clear, if I develop a stand-alone app that a customer will
> pay me to deploy an instance of onto their own appengine account (with no
> talking betwee
To be painfully clear, if I develop a stand-alone app that a customer will
pay me to deploy an instance of onto their own appengine account (with no
talking between other instances of the app) - that is allowed, correct? And
on top of it, they can't pull the code since I did the entire deployment a
You're absolutely welcome to build a web service and sell access to the
service. In fact - we encourage it.
The terms prevent you from reselling *hosting* service for code - you cannot
sell the ability for users to write code and push it to App Engine servers,
then bill them for it. You are free t
I'm a bit unclear here as well. It's ok to build a web app, and
charge users to access it, right? e.g. $5 per user per month type
thing?
Taking this a little further, if you want to charge users based on
their resource usage (assuming you write code to keep track of that in
some way), is that ok?
It's not a violation for a developer to ask an organization to create an
account and charge for service to push versions to that application. In this
case it would be clear that the developer is charging for consulting time,
and the contract with the customer would state that the provided code will
Maybe I'm a bit confused by the original question, but I always viewed
the ability to hide source code as a major plus for using appengine.
For independent developers, who don't have access to IP lawyers, this
enables them to avoid the piracy problem entirely. I think the
scenario he mentioned, ex
Thanks a lot for the answer. I guess it makes sense to go the Private
server route then.
Cheers
Ankur
On May 12, 8:19 pm, "Ikai L (Google)" wrote:
> I'm going to preface this with a warning that I am not a lawyer, this is
> just my interpretation of the Terms of Service.
>
> It could be a possib
12 matches
Mail list logo
