> 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/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. All with native diff and three-way merge built directly into IDA.

{% 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](/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.

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


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.