Perforce

Perforce, now sold as Perforce P4 and formerly known as Helix Core, is a centralized version control platform for code and large binary files, used by game, media and engineering teams.

Instead of spreading history across full local copies, P4 keeps files on a central server, called the depot, and each person works in a workspace. The vendor states that code and binaries live in the same repository, without depending on Git LFS, which Git needs for large files.

The branching model is called Streams. Sparse Streams create lightweight branches that only reference the files they need, instead of copying the whole branch. Permissions can be set per file.

P4 comes as a free plan, as a cloud service managed by Perforce (P4 Cloud) and as enterprise plans. The vendor also links the product to a Git connector for teams that use both systems.

All these points are descriptions from Perforce's own pages.

Perforce P4 has a free plan, a cloud plan at $39 per user per month and a Scale plan whose price the vendor does not publish.

• Free: $0, for up to 5 users and 20 workspaces, with 3 Git repositories and 3 lifetime support cases.
• Cloud: $39 per user per month, on a monthly commitment, hosted and managed by Perforce. The P4 Cloud page presents it for teams of up to 100 users, with 64 GiB of storage included, unlimited workspaces and unlimited support cases.
• Scale: adds unlimited workspaces, unlimited support cases and unlimited Git repositories to the Free plan. The price does not appear on the page; buying is by quote.

The buy page tells anyone needing other terms to request a quote from a Perforce representative. Educational institutions may qualify for a reduced or free license. Official training courses are sold separately from the license.

List prices published by the vendor, checked in October 2026. Through Nexforce Marketplace, Perforce can be purchased in Brazilian reais, with a Brazilian tax invoice (nota fiscal).

The main features of Perforce P4 are centralized version control, storage of large binary files alongside code, the Streams branching model and per-file permissions.

• Central depot and workspaces: history lives on the server and each person works in a workspace.
• Large binaries: according to the vendor, code and assets such as 3D models and textures sit in the same depot, without the Git LFS that Git needs for large files.
• Streams and Sparse Streams: structured branching, with lightweight branches that reference only the files they need.
• Granular permissions: the administrator sets who can read, edit or submit each file, a claim from Perforce itself.
• Monorepo: the vendor says P4 supports tens of thousands of users and unlimited files in a single repository. That is a marketing figure, to be tested on your own workload.
• Deployment: your own server or P4 Cloud, managed by Perforce.
• Version history to review changes and recover earlier states, as the Nexforce catalog describes.

Game development is the product's stated focus, and Perforce also publishes pages for media, entertainment and AI development.

Perforce P4 is worth it for teams that version large binary files alongside code, as in games and media, and less so for pure-code teams that already work well with Git.

Pros:

• It keeps binaries and code in the same depot, without Git LFS, according to the vendor.
• Per-file permissions, instead of only per repository or branch.
• Sparse Streams create lightweight branches that reference only the files they need.
• A free plan for up to 5 users, good for testing with a real project.

Cons:

• The Scale plan has no published price, so the budget depends on a quote.
• P4 Cloud, at $39 per user per month, is presented for teams of up to 100 users.
• The free plan caps at 5 users and 3 lifetime support cases.
• The model is centralized, with the server as the source of history, unlike distributed Git.
• Official training is sold separately.

The comparisons with Git come from Perforce itself and have no independent benchmark: test with your own repository before deciding.

The alternatives to Perforce are version control systems such as GitHub, Atlassian, Unity Version Control and Apache Subversion, and the choice depends on whether the team versions many binary files.

• GitHub: hosts Git repositories, the distributed model, and needs Git LFS for large files, as Perforce stresses in its comparisons. It is the common choice for source code.
• Atlassian: Bitbucket also hosts Git and integrates with Jira, which sits in the same ecosystem.
• Unity Version Control: a system aimed at game projects built in Unity, the current name of what used to be called Plastic SCM.
• Apache Subversion: centralized, open source version control, like Perforce, but without the commercial layers of managed cloud and support that P4 offers.

If the team is pure code and already uses pull requests, GitHub or Bitbucket tend to be enough. If there are large binaries and per-file access control, P4 is the candidate Perforce itself suggests comparing.