4 ms·

Is this "free right now" or "free forever"? Are you running this as a public utility or have an aim to turn it into a business?

inconshreveable 13y ago
The intention is that the current feature set is free forever. It's possible that in the future there might be additional new features worth charging for. If necessary, a small cost may be added for very-high bandwidth usage of the service, but as long as I'm under my network usage quota, that shouldn't be necessary.
- pixelmonkey 13y ago
  Very interesting. I'm going to give it a whirl. I like how simple your API is. The HTTP auth feature is also a great idea. I run a distributed engineering team for a startup and this could actually be useful for when people share stuff with each other. Currently, we tend to just deploy to a "hack server", but there's often some local data & setup that is annoying to reproduce on a server, especially for an experiment. This could let people share their stuff more easily with each other. I also like the idea of using this to share a locally-running IPython Notebook instance to share code with someone else.
  - inconshreveable 13y ago
    Awesome! I really like the ipython notebook idea. I've kicked around the idea of having the server component keep track of which tunnels are currently open by all of the developers on an "account" and then exposing them in the web interface so you would have an easy index to your coworkers' dev work. That might be one of those extra features I try charging for since it's more business-targeted. Feel free to get in touch if you have any ideas of features you'd like to see built on top. contact (at) ngrok dot com
    - tmzt 13y ago
      Would it be possible to support XMPP Streams like those used in the OLPC project? You could then share a service with other users over jabber, or browse the services exposed by a jid.

4 ms·

Is this "free right now" or "free forever"? Are you running this as a public utility or have an aim to turn it into a business?

by pixelmonkey 13y ago

inconshreveable 13y ago
The intention is that the current feature set is free forever. It's possible that in the future there might be additional new features worth charging for. If necessary, a small cost may be added for very-high bandwidth usage of the service, but as long as I'm under my network usage quota, that shouldn't be necessary.
- pixelmonkey 13y ago
  Very interesting. I'm going to give it a whirl. I like how simple your API is. The HTTP auth feature is also a great idea. I run a distributed engineering team for a startup and this could actually be useful for when people share stuff with each other. Currently, we tend to just deploy to a "hack server", but there's often some local data & setup that is annoying to reproduce on a server, especially for an experiment. This could let people share their stuff more easily with each other. I also like the idea of using this to share a locally-running IPython Notebook instance to share code with someone else.
  - inconshreveable 13y ago
    Awesome! I really like the ipython notebook idea. I've kicked around the idea of having the server component keep track of which tunnels are currently open by all of the developers on an "account" and then exposing them in the web interface so you would have an easy index to your coworkers' dev work. That might be one of those extra features I try charging for since it's more business-targeted. Feel free to get in touch if you have any ideas of features you'd like to see built on top. contact (at) ngrok dot com
    - tmzt 13y ago
      Would it be possible to support XMPP Streams like those used in the OLPC project? You could then share a service with other users over jabber, or browse the services exposed by a jid.