> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gorules.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Project versions

> Understand the differences between v1 (Legacy) and v2 (Git-like) projects and how to migrate.

GoRules supports two project versions. **v2 (Git-like)** is the actively developed version with full version control, branching, and all new platform features. **v1 (Legacy)** uses simple document-based storage and is no longer receiving new features.

New projects default to v2. If you're still on v1, you'll see a banner in the BRMS:

<Note>
  You are using Project v1 (Legacy). Migrate to v2 (Git-like) for branches, webhooks, git sync and more.
</Note>

## Comparison

| Capability                           | v1 (Legacy) | v2 (Git-like) |
| ------------------------------------ | :---------: | :-----------: |
| Decision authoring                   |     Yes     |      Yes      |
| Simulator                            |     Yes     |      Yes      |
| Releases and environments            |     Yes     |      Yes      |
| Change requests (release deployment) |     Yes     |      Yes      |
| Change requests (model publish)      |     Yes     |       -       |
| Change requests (branch merge)       |      -      |      Yes      |
| Diff viewer (single model)           |   Limited   |      Yes      |
| Diff viewer (full branch)            |      -      |      Yes      |
| Conflict resolution                  |      -      |      Yes      |
| Repository with commit history       |      -      |      Yes      |
| Branches                             |      -      |      Yes      |
| [Git Sync](/brms/setup/git-sync)     |      -      |      Yes      |
| [Webhooks](/brms/setup/webhooks)     |      -      |      Yes      |
| [AI](/brms/ai/overview)              |    Basic    |      Yes      |
| [MCP](/brms/ai/mcp)                  |      -      |      Yes      |
| Semantic versioning for releases     |      -      |      Yes      |

All new features are developed exclusively for v2 projects.

## What v2 adds

### Repository and commits

v2 projects have a [repository](/brms/build/repository) that tracks every change with commits, authors, and timestamps - similar to Git. You can browse file history, view diffs, and understand exactly what changed and when.

### Branches, change requests, and conflict resolution

[Branches](/brms/build/branches) let team members work on rule changes in isolation. When changes are ready, they can be merged directly or go through a [change request](/brms/build/change-requests) workflow with configurable approval requirements. v2 also provides conflict resolution when merging branches with overlapping changes.

Both v1 and v2 support change requests for release deployment. In v1, change requests also apply when publishing a single model. In v2, change requests apply when merging a branch into main - covering all changed files in one review.

### Diff viewer

v1 includes a limited diff viewer for individual models. v2 extends this with a full branch-level diff viewer that shows all changes across every file in a branch, along with release comparison.

### Git Sync and webhooks

v2 projects can synchronize decisions to an external Git repository via [Git Sync](/brms/setup/git-sync) and notify external systems of events via [Webhooks](/brms/setup/webhooks).

## Migrating from v1 to v2

You can create a new v2 project from an existing v1 project using the **Duplicate project** option in **Organisation Settings → Projects**. This copies all your decision files into a new v2 project.

<Warning>
  v1 projects are not automatically upgraded. Your existing v1 projects continue to work, but they will not receive new features. Migrate to v2 to take advantage of branching, change requests, and all future platform improvements.
</Warning>

## Creating a v2 project

1. Go to **Organisation Settings → Projects**
2. Click **Create project**
3. Enter a name and project key
4. Select **Git-like** as the project version
5. Click **Create**

New projects default to Git-like (v2). See [Projects](/brms/setup/projects) for more details.