Teams is a collaboration add-on for IDA Pro recently revised to focus on two pillars: version control and team collaboration with features like Deep Links. It brings Git-based versioning and real-time sharing directly into IDA, so reverse engineering teams can work together on the same binaries without losing work, duplicating effort, or managing files manually.
With the most recent version of IDA, Teams has been fully integrated inside IDA with a significantly improved interface. With the upcoming IDA 9.4 release, we're bringing a new set of collaboration and version control features — including Git integration and Deep Links.
Teams is designed for teams, but the version control features are equally useful for individual analysts who want a reliable history of their work.
Teams add-on for IDA Pro will use Git as its version-control backbone. Teams works with any Git provider you already use — GitHub, GitLab, Bitbucket, or Gitea. No new server to deploy. No new credentials to issue.
Create or clone a repository. Repositories are designed to hold multiple IDA databases, so when you’re working across a family of related binaries it keeps everything in one place.
Start a new repository from your existing working directory, or clone a shared repository from a remote server. The git-ida compression filter is configured automatically, keeping repository size small by storing only the differences between database versions. Git LFS is also supported for teams working with large IDB files.
Commit. Commit regenerates the packed database and records your changes locally with a message you create. Optionally, you can Commit and Push at the same time.
Push and Pull. Push your commits to the remote when ready; pull to bring in your teammates' latest work. If a pull produces conflicts, IDA opens a three-way merge view so you can resolve them in context. (A fan favorite.)
Full revision history. History shows the complete Git log for the open database. Compare any two revisions, step through what changed commit by commit, or compare a past revision against your current working copy.
Local Changes. Before committing, Local Changes shows a semantic diff of everything you've changed since the last commit — renamed functions, updated types, new comments — so you know exactly what you're about to record. Made changes you want to discard? Revert rolls everything back to the last commit cleanly and immediately.
Semantic diffing. Differences between database versions are presented as meaningful analysis changes — not raw binary deltas. See what actually changed in the analysis, not just what bytes shifted.
Flexible infrastructure. Use your existing Git provider, or run Gitea in a single Docker container with as little as 1 GB of RAM for air-gapped or compliance-sensitive environments. The Teams documentation includes a ready-to-go docker-compose.yml.
Vault migration included. A command-line migration utility (team-migrate) moves existing Vault-based databases to Git. For setup and migration instructions, refer to the Teams Server Administration Guide.
Once your work is in version control, Teams will make sharing it with colleagues seamless. Multiple analysts can work on the same project simultaneously — each committing their own findings, pulling teammates' changes, and resolving conflicts through IDA's built-in merge tools.
Work together on the same binary - The binary one analyst opens is the same binary the whole team is improving. Changes sync through a shared Git repository, so there is no risk of conflicting versions going undetected.
Online or offline - Teams doesn't require a constant connection. Analyze on a airplane, in a SCIF, or off the grid. A connection is only needed when you publish.
Pull with smart auto-merge - Pull brings in teammates' latest commits. Non-conflicting changes — comments on different lines, renames at different addresses, non-overlapping type changes — are resolved automatically in the background. Real conflicts open IDA's interactive three-way merge view, side by side.
Manage multiple repositories - The Manage Repositories view lists every IDB repository on your machine. Pull and push across projects without needing to open a database first.
Deep Links, our latest update for 9.4, make it easy to point a teammate directly to something you've found — a function, an address, a string, a type — without any back-and-forth about where to look.
Share a location with a URL. Right-click any item in IDA and choose Copy Link. This generates an ida:// URL encoding the database, resource type, and exact location. Paste it into a chat, a ticket, a report, or an email.
Navigate to link. Navigation links take you directly to a specific location in IDA. A teammate can open the link in an existing IDA session, or use hcli, which will launch IDA if needed and automatically open the correct database and view.
Stable across reloads. Links are based on relative virtual addresses (RVAs) rather than absolute addresses. If a database is rebased, links still resolve correctly.
Nine resource types. Functions, addresses, strings, segments, names, imports, exports, types, and bookmarks can all be linked to directly.
Twelve view targets. Links can open in disassembly, graph, pseudocode, hex view, or any of the dedicated IDA windows — whichever makes most sense for what you're sharing.
Python API. Deep Links can also be opened programmatically via ida_kernwin.open_ida_link(), making them useful in scripts and automation workflows.
Whether you're a solo analyst who wants a reliable history of your work, or part of a team tackling a complex binary together, Teams is built for the way reverse engineers actually work.
Git integration and Deep Links are coming in IDA 9.4, expected mid-Summer 2026. If you'd like to be among the first to see a demo and try them, or if you have questions about adding Teams to your IDA Pro subscription, reach out to us at sales@hex-rays.com. We're happy to walk you through the features, discuss licensing, or set up a live demo.