Log in via Github, Gitlab, Bitbucket, or Azure Devops. We'll guide you through the process of selecting which repos you want GitClear to process on your behalf. During the subscription trial, up to three repos can be selected.
Paying subscribers have no limit on the number of repos analyzed.
We'll email you once we've processed about 6-12 months of your repo history. The time required depends entirely on the size of the repo being imported, but we almost always have some results available for viewing within 24 hours.
We process commits from the most recent commits backwards, so the initial data you can view will be your team's most recent work.
GitClear does use various forms of caching to keep long-range charts at sub-1s load times, so in the early stages of your data importing, there are likely to be some irregularities between charts as the various caching systems are populated. This process should work itself out within 2-5 days. Please do email us firstname.lastname@example.org if you see any data anomalies more than 5 days after you initiated your import.
Any stakeholder who wants to get a visual, short-term or long-term summary of their team's development work.
For Developers, Lead Developers, and Managers who want to keep abreast of day-to-day developer activity, the Commit Activity Browser is a great starting point.
For Developers, Lead Developers, CTOs, and VP of Engineering who want to more deeply understand how development evolving within particular systems, the Directory Browser is built to help answer these questions. Here you can navigate through your repos to see which directories have had most work change happening within them lately. You can also see which directories have the most tech debt, and which developers have been principally involved in the changes for each directory (useful when Engineering Management needs to identify an expert on the "X system").
For CTOs, VP of Engineering, and CEOs, the Historical Activity stats help you get the highest-level, data-backed summary of how rapidly the team is evolving their various projects. To glean a high-level understanding for how the velocity of the team is changing over months or years, the Historical Activity pages
The security of your code is GitClear's top priority. Our preferred strategy to ensure security borrows from the world of open source: be as transparent as possible. To that end, we've created a Comprehensive Security Overview page to describe the numerous interleaving mechanisms that keep your sensitive code from prying eyes.
In short, you control whether GitClear retains any the code content that is processed to generate our graphs. If you choose to have GitClear retain code contents (useful when using GitClear as a code review solution), that code is encrypted at rest, with each line using a unique initialization vector that must be combined with a decryption key.
We also offer an On Premises Enterprise version, where all of your data can be processed and stored on your own servers, with no code ever transmitted to our servers.
We write about this at length here, in a post that we update every few months as new competitors debut, and old competitors add new features.
tl; dr GitClear is the only product that digs underneath the trivially gameable metrics to produce durable, accurate engineering insights.
GitClear is the flagship product of Alloy.dev, a productivity-centric company based in Seattle, Washington. We started working on GitClear in 2016 and utilized it as an internal tool to help us manage a large team of developers building Bonanza.com. The product was dogfooded for about three years before finally being good enough to release a beta version to the public in 2019.
The parent company Alloy.dev is a bootstrapped company with no obligation to investors or outside parties. Our only incentive is to deliver a tool that is accurate and powerful enough to earn customer trust. Our team of developers uses GitClear every day, and the site is deployed with fresh updates every day or two. Here's the Line Impact that has been invested into GitClear as of early 2021:
This graph was captured in Q1 of 2021. We intend to continue to evolve GitClear at brisk pace for years to come.
Pretty much all of them. If there's a language you want analyzed that isn't on our list, email email@example.com and we can get it added within a couple days.