Integrations

Your tools.
One engineering view.

Bring your repository evidence and work context together to understand delivery, investigate friction, and improve how your team builds with AI.

Start with GitHub in the hosted trial, or scope your toolchain for a self-hosted deployment.

Connect your existing environment

From modern Git to the systems you still rely on.

Connection methods and available evidence vary by provider. Choose the repositories and work you want to understand, then agree on access and setup.

Source control

Connect your repositories.

  • GitHub
  • GitLab
  • Bitbucket

Bring selected repositories into Binomial for engineering analysis. GitHub uses a native app connection; GitLab and Bitbucket use their supported credential-based setup.

The hosted trial starts with read-only GitHub access.

Self-hosted & on-premises

Work inside your environment.

  • Self-hosted Git
  • On-premises Git

Connect a Git repository using HTTPS credentials or an SSH key. Scope network reachability, authentication, repository access, and deployment requirements for your installation.

Private network connections require advanced setup.

Advanced setup · Legacy source control

Include the history that matters.

  • SVN / Subversion
  • CVS
  • Perforce
  • SCCS

Discuss the repositories you need to analyze and agree an import or connection approach for your environment. Direct repository upload and offline export are also available for scoped analysis.

Confirm compatibility and evidence coverage before purchase. An offline import can contain less workflow history than a live connection.

Advanced setup · Project management

Put code changes in work context.

  • Asana
  • Jira
  • Your project tools

Tell us where your team plans and tracks work. Scope how project and task context should accompany repository evidence, and agree the available connection or import path for your deployment.

Project-management connections are scoped with your team; they are not part of the self-service GitHub trial.

Run engineering with AI in mind

Turn connected evidence into a better next move.

Use Binomial to guide the questions your team asks, the experiments it runs, and the practices it improves.

  1. 01 / Understand

    See how the work moves.

    Review repository activity and delivery patterns with the source, scope, and collection state in view.

  2. 02 / Investigate

    Ask what is creating friction.

    Follow a finding into its evidence. Bring task complexity and team context into the discussion before drawing a conclusion.

  3. 03 / Improve

    Choose a focused experiment.

    Agree a change to AI-assisted development, review, or validation. Compare what follows with the baseline and discuss the result.

Repository activity alone does not establish AI usage or prove that AI caused an outcome. Direct AI-tool usage requires evidence from those tools.

Source code included

Deploy Binomial alongside your tools.

Buy the licensed source code and Dockerized distribution, run Binomial on your infrastructure, and configure the integrations agreed for your environment. Your team manages the installation and updates.

See the purchase and maintenance terms

Start with your environment.

Tell us your providers and versions, where they run, which repositories or projects you need, and any network or access constraints.

Discuss your setup