The docs have been restructured for better navigation. Found a broken link or have feedback to share? Let us know
here.
Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Git

Since IDA 9.4, Teams includes Git integration, bringing familiar version control workflows to collaborative reverse engineering. Git-based repositories are recommended for new Teams projects.

Using Vault already? See the Vault to Git Migration tutorial to get started.

The Git backend removes the need for a dedicated Teams server (previously known as the Hex-Rays Vault server). If your team already has a Git provider account, such as GitHub, GitLab, or any self-hosted instance, that's all you need: no dedicated Teams server installation, no admin provisioning, and no additional credential management. Every user authenticates with their own Git account, points IDA at a repository, and starts collaborating immediately.

Teams menu with Git backend

Prerequisites

  • IDA Pro 9.4 installed and an active IDA license with Teams add-on

Setup

Before using the Git backend commands under the Teams menu, complete the following steps:

  1. Install Git. IDA ships with git-ida, a small helper for storing and reconstructing IDA databases in Git. It is picked up automatically from tools/teams. You only need a system-wide Git installation. If Git is missing, IDA will tell you when you trigger a Git action.

  2. Set up a repository for the IDB you want to work with:

    • Teams → Create Repository — turns the directory containing the current IDB into a new Git repository. Optionally, link it to an empty remote URL at this step.

    • Teams → Clone Repository — downloads an existing shared repository to a folder of your choice.

  3. Set your Git identity (user name + email). On your first commit, IDA opens the Repository Settings dialog so you can set them. If you already have a global user.name / user.email configured, IDA picks them up automatically.

For HTTPS remotes, IDA will prompt you for credentials the first time they are needed and store them securely in the OS keychain.

What's Next?

You're ready to collaborate on your IDB. See Working with Git for day-to-day operations: committing, pushing, pulling, viewing history, and resolving conflicts.

Last updated

Was this helpful?