> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/ida-9.5/add-ons/teams/overview.md).

# 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`](/ida-9.5/add-ons/teams/how-tos/git-diff.md).

{% hint style="success" %}
Since IDA 9.4, Teams runs on **Git as the default backend.** Already on Vault? See the [Migration Guide from Vault to Git](/ida-9.5/add-ons/teams/how-tos/migrating-from-vault-to-git.md).
{% endhint %}

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)](/ida-9.5/add-ons/teams/concepts/git.md#large-file-storage-lfs).

### Vault repositories

The legacy Vault backend remains available for existing projects. You can switch it under **Options → General →** [**Teams**](/ida-9.5/ida-actions/options.md#teams-options).

## 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hex-rays.com/ida-9.5/add-ons/teams/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.