Install diversion with Homebrew Cask

Project links

• Homepage
• Package manager page

Commands and aliases

• dv
• darwin-arm64

Project history

Diversion was founded to build source control around the needs of creative teams working with code, artwork, audio, and other large assets. The company describes the resulting system as cloud-native version control with no server infrastructure required from users.

The product family expanded beyond its command-line and desktop clients to include Unreal Engine and Unity integrations, repository mirroring, CI/CD support, APIs, and workflows for AI-assisted development.

Adoption history

Diversion targets game development, virtual production, and other creative teams whose repositories combine source code with large binary assets. Official materials document integrations and workflows for Unreal Engine, Unity, CI/CD systems, and Git repository import.

Its positioning evolved from an alternative to Git and Perforce for game projects toward a collaboration platform for large repositories and parallel AI-agent workflows.

How it is used

Users authenticate with `dv login`, create or clone a repository, and use commands such as `dv status`, `dv branch`, `dv checkout`, `dv commit`, `dv diff`, `dv log`, and `dv merge`. A background agent synchronizes workspace content with the hosted repository.

For automation, official CI/CD guidance uses an API token with `dv authenticate`, starts the agent in the background, clones into a new or existing workspace, and waits for `dv status` to confirm synchronization. The documentation recommends storing tokens in the CI platform's secure secret facility rather than a plain environment variable.

Why package nerds care

Diversion is notable to package users as a proprietary, cloud-backed version-control system exposed through the `dv` CLI rather than a Git wrapper. It packages a centralized service, local agent, workspace synchronization, and familiar branch, commit, diff, merge, and log operations into a single client.

Its emphasis on large binary assets and automatically synchronized workspaces makes it relevant where Git LFS or self-hosted Perforce would otherwise add operational complexity.

Timeline

• 2023: Official blog material documents Diversion's focus on next-generation version control for game developers.
• 2025: Official product updates document expanding review, webhook, Unreal, and asset-management workflows.
• 2026: Diversion presents the platform as infrastructure for large repositories and parallel AI-agent development.

Related projects

• Git and GitHub repositories can be imported into Diversion, optionally with continuing synchronization.
• Perforce is a principal legacy alternative discussed in Diversion's official product material.
• Official integrations cover Unreal Engine and Unity.

Sources

• https://docs.diversion.dev/ci-cd
• https://docs.diversion.dev/cmd-ref/import
• https://www.diversion.dev/
• https://www.diversion.dev/about
• https://www.diversion.dev/blog