Diversion

Overview

Diversion brings source code and large creative assets into a single distributed version-control workflow, with changes syncing to the cloud automatically. It is most compelling for game and other creative teams whose repositories strain tools built around code alone; the trade-off is that its collaboration features and higher-scale plans quickly become paid territory.

Its intended projects range from game assets and media to datasets. Diversion says repositories can reach tens of millions of files and hundreds of terabytes, with partial and shallow checkouts for working with a subset. Self-hosted deployment is also an option alongside cloud use. For a category-wide comparison, see Version Control Software.

Key features

Code alongside large assets

Diversion versions code with binary files such as textures, 3D models, audio, video, and datasets. Native large-file handling, sparse checkout, and file locking address practical problems in shared asset workflows: teams can keep those files with code, limit what they check out, and lock files when concurrent edits would be risky. The scale claims are ambitious, but the stated repository capacity and partial checkout options make the product particularly relevant to projects with very large working sets.

Game-engine workflows

An Unreal Engine integration supports UGS and Horde workflows. Diversion Connect puts sync status, commits, branches, and change history in the Unity Editor, reducing the need to leave the editor to check those version-control details. This focus is useful to game teams; teams outside those engines should weigh it alongside the broader file and collaboration capabilities.

Integrations and controls

Jenkins and TeamCity integrations cover named CI/CD workflows, and a RESTful Web API gives teams a route to custom integrations. Code and asset reviews, hard locks, and granular permissions are included from Studio upward, so teams needing formal review and access controls must budget for that tier rather than assume they come with Pro.

Security and deployment

Diversion says it completed a SOC 2 Type I audit and encrypts data in transit and at rest. Backups run hourly, daily, and monthly as well as point-in-time across multiple regions, with regular recovery testing. Enterprise options include on-premises and private-cloud deployment, while hybrid hosting is also supported. These choices suit organizations with hosting or operational requirements beyond a standard cloud setup, though the most extensive deployment options sit behind custom Enterprise pricing.

Pricing

The free plans make Diversion approachable for small or eligible groups, but their caps matter: storage and repository limits can make them short-lived options for asset-heavy projects. Paid plans add scale and team controls, with per-user costs that should be considered against the number of collaborators.

• Education: Free for up to 10 users, for eligible academic institutions. It is the clearest fit for qualifying educational teams that need no-cost access.
• Indie: Free for the first 5 users and eligible groups of up to 20 users; includes 100GB storage and up to 5 repositories. Each additional 100GB costs $10/m. This works for smaller eligible teams, but repository and storage limits constrain larger asset libraries.
• Pro - A: $25 a month per user, scaling to 50 seats. It includes 100GB storage, unlimited repositories, up to 3 webhooks, and $10/m for each additional 100GB. This is the practical starting point for teams that have outgrown the free caps but do not need Studio's review and permission controls.
• Studio - AA: $35 a month per user for up to 200 users. It includes everything in Pro plus code and asset reviews, unlimited webhooks, granular permissions, hard locks, and priority support with a dedicated Slack channel. The extra cost makes sense when structured reviews, tighter controls, or higher webhook needs are central to the workflow.
• Enterprise - AAA: Custom pricing by quote for unlimited users, on-premises or private-cloud deployment, multi-site deployment, SAML SSO, custom integrations, and 24/7 support SLA. It is aimed at organizations needing those deployment and support terms rather than just more seats.

A 21-day trial is available. The free plans are not interchangeable: Education requires academic eligibility, while Indie has user, storage, and repository ceilings.

Platforms

Diversion supports Windows, macOS, and Linux desktops, as well as web access and API use. Its platform options also include self-hosted deployment, giving teams a choice beyond a cloud-only setup.

Who it's for

Diversion is a strong fit for game developers and teams in virtual production, architectural visualization, AI/ML, and other creative work where large files sit beside code. Its engine integrations, asset locking, and high stated repository capacity align especially well with game production. A small code-only team that does not need large-file handling, specialist integrations, or collaboration controls may find its asset-oriented scope and paid tiers unnecessary.

Pros and cons

• Pro: Code and large binary assets share one version-control system, avoiding a separate workflow for common creative files.
• Pro: Partial and shallow checkouts address the practical burden of repositories that Diversion says can reach hundreds of terabytes.
• Pro: Unreal and Unity integrations, plus Jenkins, TeamCity, and a RESTful API, connect the product to named production and CI/CD workflows.
• Pro: Studio adds reviews, granular permissions, hard locks, and priority support for teams that need stronger collaboration controls.
• Con: Free plans impose eligibility, user, storage, or repository limits, which can be restrictive for large asset libraries.
• Con: Pro charges per user and starts with 100GB storage; additional storage is billed in 100GB increments, so growing teams must account for both seats and assets.
• Con: Reviews and key access controls begin at Studio, while advanced deployment, SSO, and 24/7 SLA support require Enterprise custom pricing.

Alternatives

Unity Version Control is worth considering for teams comparing another freemium option with unlimited cloud seats and 25 GB of included storage, though that smaller stated allowance is a different starting point for asset-heavy work.

Fossil may suit readers who prefer free, open-source software they can self-host. Apache Subversion is another free open-source version-control option. Mercurial is a free software alternative for readers considering another distributed version-control tool. GitButler offers a free, open-source standalone client for readers seeking a client rather than Diversion's cloud-native service.

Perforce P4 (Helix Core) is an alternative to compare for teams considering a service with a free tier capped at 5 users, 20 workspaces, and 3 Git repositories, or a Cloud plan priced at $39.00 per month. VisualSVN Server may suit Windows-focused teams looking for self-hosted software with a free Community plan for up to 15 users. Accessibility Test Framework for Android is another free alternative in the category.

Verdict

Choose Diversion if your team needs code and large creative assets managed together, especially in game or visual-production workflows where engine integrations, file locking, and selective checkouts matter. Its chief advantage is a single workflow designed for very large repositories; its chief drawback is that storage, seat, and collaboration needs can push teams from free access into paid tiers, with enterprise-grade deployment and support requiring a quote. For code-only projects without those demands, compare a simpler or free alternative first.