I&#x27;m using Linux but I won&#x27;t consider installing a native application even if it were available, or if I had a Mac or Windows. Web apps proved to be good enough for issue tracking (maybe I&#x27;m telling this to the wrong people given your choice, which I respect), my browser is open all the time and it has offline capabilities. Furthermore, it can be updated more conveniently.<p>Another point is that issues are useful if shared. I shared links to issues to customers and coworkers countless times and included them in reports. A web client solves at least one problem, maybe two. First, they might not want to install (or pay for) another tool. Second, Ship references issues with the ship:&#x2F;&#x2F; url, which won&#x27;t work unless you have Ship installed. A <a href="https:&#x2F;&#x2F;" rel="nofollow">https:&#x2F;&#x2F;</a> url would work for everybody but then you need to share two different URLs which would be cumbersome. I&#x27;m sure you already found a solution to that.<p>Your site doesn&#x27;t address explicitly one fundamental aspect: the data are hosted on your server, like issues stored in GitHub, Jira, etc and you&#x27;re selling the service, or will be. Is this correct? What&#x27;s the pricing? Thanks.