Just to answer here as well (I'll be in touch), the easiest pitch is to content creators who want to remove the "deploy stuff to some server in order to show pr

Just to answer here as well (I'll be in touch), the easiest pitch is to content creators who want to remove the "deploy stuff to some server in order to show progress to clients and coworkers" step from their work flow. Obviously, this is most applicable to people working on web designs or web app development. Another way to think of it, is that anyone who uses dynamic DNS today might find PageKite is a better fit for certain tasks. Dynamic DNS only works when a device is immobile and you have a visible, unfiltered IP. PageKite doesn't have those limitations, and is way easier to set up. There are many reasons to want to be able to run a simple server on a personal computing device, we've just been beaten out of the habit of even considering it by firewalls and NAT. So you are absolutely right that the value is often unclear to people at first - we have a definite up-hill struggle ahead in marketing this. I am optimistic though, because so far most techies who have given it a try found it so convenient all their objections melted away.