We are delighted to finally announce the release of GitClear Enterprise, a version built to install on-premises behind your firewall. This has been a project that we've been working on for the better part of a year, and has been far-and-away our most-requested feature.
Here are some details about what Enterprise is and how it works.
A version of GitClear that can work on site, within any company's infrastructure.
Everything that our current site does, including Commit Browser, Directory Browser, and the rest of our tools built to improve code clarity and developer throughput. We also process all pull request stats and comments to help drive clear collaboration across your team.
Given that you'll fully control the scaling and deployment of your Enterprise instance, we also enable some features not present in GitClear.com: The ability to process data further back than our cloud offerings can presently go, for example, and the ability to connect to on-prem git provider instances.
All of the platforms that our current site does, including GitHub, GitLab, Azure Devops, and Bitbucket Server -- either their hosted enterprise version, or their standard version.
Request a demo or drop us a line at support@gitclear.com.
Our Enterprise offering is ideal for medium- or large-scale companies. These companies often require intense scrutiny for any software that will be used within their firewall, particularly software that is analyzing the code -- one of the company's most precious assets.
GitClear's Enterprise version offers the opportunity to own and host all of your processed code data. Many companies find this preferable to integrating with a cloud-based service such as we have previously offered.
It's a self-contained docker image that includes a guided install via a single command instruction. The total download size is about 3 GB compressed.
The application requires periodic license validation, which is generally consummated within a few megabytes of communication per month. Aside from that, the Enterprise install needs to be able to connect to the provider of your source code.
Highly dependent on how many active developers you'll be processing. For best performance, we recommend at least 64gb of available RAM and 8 cores per 500 active developers OR roughly 200 commits per day (whichever is higher) being processed. You can probably get by with less, but performance may suffer in some areas.
The bare minimum recommended settings observed to run the app is 16gb and 4 CPU cores.
Currently, the rack rate for GitClear Enterprise is $35 / developer / month for an annual subscription, with additional costs if you sign up for Data Insights. We offer free (self-serve) trials of Enterprise at no cost, with additional costs for in-depth technical support (depending on your specific environment's needs). For more information, you can reach out to our sales and onboarding team at hello@gitclear.com.
If you have an existing GItClear container running:
Then to retrieve the image URL and load it into Docker:
The first time you start the container, run the setup wizard from inside it:
It walks you through your license key and verification code, whether GitClear should send email (and your SMTP settings if so), whether to enable diagnostics/log uploading, and a handful of other one-time choices. It asks each question fresh every time it runs, rather than defaulting to whatever you answered before -- so it's meant for first-time setup, not for tweaking a single setting afterward (see "Tweaking config variables after install" below for that). Once it finishes, your answers are written to /data/enterprise.env on the gitclear-data volume -- so they survive container restarts and upgrades -- and copied into the running container as .env.
When GitClear sends you a new image, load it and swap the container the same way you did for the initial install: stop and remove the old container, docker load the new archive, then start the new container (or docker-compose down/up if that's how you're running it). None of this touches the gitclear-data volume, so your database and repos carry over untouched.
Once the new container is up, apply its migrations from inside it:
This runs any pending database migrations, re-verifies your license against GitClear's servers, and restarts the app's internal services (nginx, Redis, Resque workers, cron) so the new code takes effect. It's the same command shown under "First-time setup" above -- just run against a freshly-loaded image instead of a brand-new install.
There are two layers of settings, depending on what you're changing.
Day-to-day settings -- the admin contact email, whether errors get reported back to GitClear, SSL verification, SAML login, signup lockout, chart glimpse host overrides, the data retention window, auto-refresh behavior, contributor-merge behavior, and the number of background workers -- live in the app itself. Visit /enterprise_configs as an enterprise admin to change them. Everything there takes effect immediately except the worker count, which needs a restart afterward:
Setup-time settings -- SMTP credentials, the license key, database/Redis overrides, and anything else the wizard originally asked you -- live in /data/enterprise.env on the gitclear-data volume, copied into the container as .env. To change one of these, either re-run the wizard (config/enterprise_setup, above) or edit .env inside the container directly, then restart services for the change to take effect:
Container-level output -- what's printed to stdout, useful when the app is failing to start at all:
Application logs live inside the container, under the standard Rails log/ directory at /home/deployuser/gitclear/current/log/. Web request logs go to enterprise.log; each background job type (commit processing, PR processing, issue tracker syncing, etc.) gets its own file. Get to them with:
These files live in the container's own filesystem, not on the persisted gitclear-data volume -- they survive a container restart, but not a docker rm/recreate.
Rather than digging through them yourself, the "Upload logs" option on the Data tab of /enterprise_configs (/enterprise_configs?tab=data) is usually the fastest path when troubleshooting with us: pick which log categories and how many days back, and it bundles and ships them straight to GitClear's support team.