Page cover
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

What is Teams?

Teams is an IDA add-on that brings Git-based version control to IDA database files, letting multiple reverse engineers collaborate on the same IDB using standard Git workflows, with three-way merge and a readable, structural diff produced by IDA itself. The diff is plain text, so it works just as well in a terminal, a CI job, or an AI agent as it does in the IDA GUI. See Diffing IDA databases with git diff.

Teams is available as an add-on for supported IDA Pro plans.

Architecture

Git repositories (default)

The Git backend removes the need for a dedicated Teams server entirely. Any Git provider your team already uses, like GitHub, GitLab, Bitbucket, or a self-hosted instance, works out of the box. Git-based repositories are the recommended choice for all new Teams projects. Each team member works from a local clone of the repository using their own Git credentials. A small helper, git-ida, handles how IDA databases are stored and reconstructed in Git. It runs transparently in the background. With Git LFS enabled, even multi-gigabyte databases clone and check out in seconds instead of minutes, using a fraction of the disk and memory the older full/delta format needs. See Large File Storage (LFS).

Vault repositories

The legacy Vault backend remains available for existing projects. You can switch it under Options → General → Teams.

Online vs Offline Usage

Teams is designed to support flexible workflows. Users do not need to remain connected to the server at all times and can work offline as needed. A connection is only required when publishing changes so they become available to other team members.

Last updated

Was this helpful?