This looks interesting, however:

* Please make the pricing public. I do not work for that big of a company, and hidden pricing usually means "very expensive", which means I probably I will not have budget for it

* Have you considered a "free-for-open-source" plan ?

* The public documentation is really too limited to get a good idea of what it does. There are plenty of tools in this area (which often disappoint), and most people will not take the time to setup their project just to get an idea of what it does. Is it a webapp ? Can I self host it ? What languages are supported ? Which tools does it compare to (more like Sonar? more like ELK ?) and why is it better ?

* When logging in using Github oauth, read+write permissions for all my public+private repos was asked.

* After logging in, the "Read the Docs" link gives an HTTP error 502.

* If I get it right, your tool will analyze all source code + runtime logs. I am pretty sure my company would not agree for closed-source software from a new, small company to get this level of access to our data, so you have to make to make very clear what data goes where...

Good luck!

Agreed on public pricing -- this looks like something that would be quite useful to my team, but I'm not even going to check it out unless I know the ballpark we are looking at.

The read/write access also is a red flag to me, unless there is really solid info on why write access is needed, and how everything is secured.

Hey Nicoulaj,

I'm planning to have this be free for open source. I may even open source it. The ballpark figure I want to target is $1k per month for medium size companies of 20-50 engineers/qa. But I'm still trying to get more data on that.

I'm offering a free trial until March right now. I do all of the integration for you. If you're interested in a demo, you can email me at yahn007 at gmail dot com.

Appreciate the feedback.

It sounds like it creates a mapping from lines to "bugginess." How much value do you think there would be in some sort of semantic analysis, e.g. "new function foo is suspect bc it calls bar, which has shown up in a lot of stack traces lately"?

> How much value do you think there would be in some sort of semantic analysis

Disclaimer: I'm the founder of GitSense (https://gitsense.com), which is also focused on predictive defect analysis, among other things.

Incorporating semantic analysis, by cross referencing semantic code changes with bug reports/static analysis report/stack trace reports/etc., will be absolutely critical for defect analysis and automatic code generation, in my opinion. It's also not trivial, both from a computation, storage and retrieval perspective. For example, running semantic diffs analysis on every revision (on any possible branch) and cross referencing the results with external data like bug reports, continous integration results, etc. is a very expensive/complex operation.

In order for ML to work, you need good datasets and in order to generate good datasets, you need lots of raw data (static analysis results, code change history, etc.) that can be data mined and cross-referenced, to produce meaningful data. Creating good datasets for ML, in a scalable manner, will require you to rethink how to extract, store and retrieve code related information.

With GitSense, it's designed to be installed on every developer desktop/workstation, which is how I solve the computation problem. Since every developer workstation is designed to be a continuous indexing machine, indexing can be distributed across dozens, if not hundreds or thousands of machines. Being able to index and cross reference as fast a possible, is absolutely critical, since the goal is to prevent developer mistakes from happening.

Generating semantic analysis is fairly straight forward. Incorporating it, is where the challenge lies.

Hey nickelbox,

This is among the several problems that I'm trying to solve. As a developer, when you're calling an existing function -- you don't really have any data at your disposal WRT the quality of that function. Likewise for modifying individual lines. To me, it seems obvious to want this information.

But I'm trying to test that hypothesis and see if other developers feel the same way.

Thanks,

Congrats on launching!

Why isn't the pricing non-public? Is it customized for each client / use-case? If yes, can you please brief what factors made it infeasible for making it non-public?

Hey dotmanish, in short, there's some research I want to do and people I want to consult before making that public. If you're interested, you can email at yahn007 at gmail dot com and we can chat.