Kite only works in the directories for which you have enabled it.
In order to show you information about the libraries and APIs you are interacting with, Kite sends some information about the code you are writing to our backend. This includes:
As you would expect, all traffic goes over https.
Once again, this information is only collected for directories for which you explicitly enable Kite.
Our backend contains an index of tens of thousands of python libraries, including documentation, examples, and models of how public-domain code uses these libraries. This index is simply too large to ship to each client.
One of Kite’s goals is to bring all the programming information available on the internet to your development workflow. It turns out that the internet contains a lot of information about programming, so Kite is architected as a cloud service. The up side is: the internet contains a lot of information about programming, so Kite can give you some incredibly helpful information.
Many developers have already chosen to trust their code to services such as Github and Bitbucket. Furthermore, many of us already implicitly trust some of our deepest secrets to chat apps such as Slack. If you use any of these services or any like them, it is probably because they have earned your trust over time through transparency, product quality, and well-considered privacy policies. At Kite we understand that trust is built over years but can be destroyed in a moment. We plan to earn your trust the hard way, starting with writing this page.
Kite does not have an on-premise offering at the moment. If you are interested in an on-premise or AWS co-managed installation of Kite servers, please email firstname.lastname@example.org.