P4, formerly Helix Core, is centralised version control built for repositories measured in terabytes, where most content is binary art assets that cannot be merged. Exclusive file locking stops two artists editing the same model, and clients only pull the files they need. Perforce says 19 of the top 20 AAA game studios use it. It is a different tool for a different problem, not primarily a Git host.
At a glance
- Hosting
- Self-hosted or Perforce-managed cloud
- Licence
- Proprietary
- Free tier
- Free for up to 5 users, 20 workspaces and 3 Git repositories, self-hosted
- Paid plans
- P4 Cloud $39/user/month billed monthly, for teams up to 100. Scale and Platform plans on quote
- CI/CD
- Integrations
- Issue tracker
- Separate product
- Reads Actions YAML
- No
- Imports from GitHub
- Code only
- SAML / SSO
- Yes
- Used by
- Standard across AAA game studios; Unreal Engine tooling assumes it.
Strengths
- Handles multi-terabyte repositories of binary assets
- Server-enforced exclusive checkout on binary files
- Unreal Engine and Unity integrate with it directly
Trade-offs
- Centralised, not distributed; Git hosting is limited, with 3 repositories on the free plan
- Expensive beyond the free five-user tier
- Needs dedicated administration
Moving from GitHub
A full change of version control model, from distributed to centralised. Git history can be converted, but branching, locking and workflow all differ. Plan this as a project, not a migration.
git clone --mirror https://github.com/user/repo.gitcd repo.gitgit remote set-url --push origin <new Perforce P4 (Helix Core) remote>git push --mirror
Comparison pages
- Perforce vs Git
A distributed open-source tool and a centralised commercial server, compared on the problems that make teams choose between them.
- Hosting for Subversion, Perforce and large binary files
Every platform in the directory that hosts Subversion, runs Perforce, or handles large binary files with exclusive locking.
Other enterprise and large-binary version control
| Platform | Hosting | Free tier | Paid plans |
|---|---|---|---|
| Unity Version Control | Cloud or on-premises | Free for up to 3 seats with 5 GB of storage | Per-seat pricing through Unity, with storage charged separately |
| Perforce TeamHub | Cloud or on-premises | None. The free tier was discontinued on 28 July 2025. | Standard (cloud, 1 GB per seat), Premium (cloud, 5 GB per seat) and Enterprise (on-premises), all billed annually on quote |
Frequently asked questions
Is Perforce P4 (Helix Core) free?
Free tier: Free for up to 5 users, 20 workspaces and 3 Git repositories, self-hosted. Paid plans: P4 Cloud $39/user/month billed monthly, for teams up to 100. Scale and Platform plans on quote.
What licence is Perforce P4 (Helix Core) under?
Proprietary.
Can Perforce P4 (Helix Core) be self-hosted?
Hosting: Self-hosted or Perforce-managed cloud.
Does Perforce P4 (Helix Core) have CI and read GitHub Actions workflows?
CI/CD: Integrations. Reads GitHub Actions YAML: No. Imports from GitHub: Code only.
How do I move from GitHub to Perforce P4 (Helix Core)?
A full change of version control model, from distributed to centralised. Git history can be converted, but branching, locking and workflow all differ. Plan this as a project, not a migration.
Source
Read on 15 November 2026 from www.perforce.com. Prices and limits change without notice; confirm with the vendor before you decide.