Perforce P4 Licensing Explained: Editions, Seats and Pricing

This page answers the licensing questions buyers actually ask about Perforce version control — what the plans include, whether build agents consume seats, which servers in a distributed topology need a licence, and what is genuinely free. Figures are Perforce list prices in USD.

Helix Core or P4? The naming changed

Perforce rebranded its version control platform in March 2025. If you are reading older documentation or an old quote, this mapping is the translation table:

The prefix is a useful signal. Products that took the P4 prefix are part of the core version control platform. Products that took the Perforce prefix are separate products with their own licensing and, in some cases, a completely different licensing model. P4V, the visual client, kept its name.

What are the P4 plans?

What is actually free?

More than most people expect, and the free tier has a structure worth understanding because it is an either/or, not a single cap.

An unlicensed P4 server gives you either:

• Unlimited files for 5 users and 20 client workspaces, or
• Unlimited users and workspaces for up to 1,000 files

That second option is genuinely useful and widely overlooked — a large team can evaluate P4 properly as long as the depot stays under a thousand files.

Also free:

• P4 Code Review (formerly Swarm). Perforce’s documentation is unambiguous: it is free to use with any P4 Server and requires no separate licence. If you have been quoted for it as a line item on a self-hosted deployment, question that.
• P4V and the command-line clients. The server licence is what you pay for.
• P4 One, the newer version control client aimed at artists and designers. It works standalone without a P4 Server licence and can connect to studio infrastructure later.

Do build agents and automation consume licences?

If your last P4 renewal predates February 2026, your CI/CD and build accounts are probably still sitting on full-price named seats. This is the single most actionable cost lever in current P4 licensing and it is worth raising explicitly at renewal, because Perforce does not publish Bot User pricing — it is negotiated.

A third class, Git Only licences, exists for users who only need restricted depot access.

Which account types are free?

Separately from the licence classes above, P4 has server-side user types that consume nothing:

• standard — consumes one licence each
• operator — admin and monitoring accounts. No licence required.
• service — accounts used for replication between servers. No licence required.

Auditing your user list for accounts that should be operator or service rather than standard is a legitimate, documented optimisation that costs nothing to implement.

Which servers in a distributed topology need a licence?

Perforce’s rules here are clear and more generous than most people assume:

The dividing line is failover capability, not geography. An edge server in another studio costs you nothing in licensing; a standby that could be promoted does. This applies to P4D version 2013.2 and later.

Named or concurrent licences?

This catches out teams who have used Perforce ALM, which is a different product with a fundamentally different model — ALM offers both named and floating licences through a License Server, where up to five concurrent users can share one floating licence with a 30-minute reservation window after logout. That model does not carry over to P4. If someone on your team is sizing P4 on the assumption that shift workers can share seats, correct it early.

Where P4 contracts catch buyers out

The 45-day auto-renewal window

Perforce order forms automatically renew for successive terms of equal length unless one party gives written notice of non-renewal at least 45 days before expiry. Miss that window and you are committed to another full term. Put the date in a calendar the day you sign.

Perpetual licensing is gated at 50+ users

Perpetual licences still exist but Perforce positions them for teams of 50 or more, as a one-time purchase plus annual maintenance. Below that, you are buying 12-month subscriptions. Perforce’s current master terms are written subscription-first.

What happens to your data if you do not renew

Perforce’s master terms require you to immediately cease using the offering, with a three-month export window for cloud content, after which Perforce has no obligation to retain it. For self-hosted deployments the practical position is that your depot files remain on your own disk but you lose the right to run the software. The exact terms vary by agreement, and it is a bad thing to discover at expiry — contact us and we will get you the terms that apply to yours in writing.

Audit rights

Verification is limited to no more than once in any twelve-month period and is scope-limited. Reasonable, but worth knowing it exists.

Support tiers are narrower than you might assume

Standard support is included with a subscription or maintenance and covers Monday to Friday business hours. Twenty-four-hour emergency coverage is a paid add-on called Critical Care, and weekend upgrade support is separately arranged. There is also a paid managed service, P4 Remote Administration. If you run a global studio with weekend releases, price the add-ons in from the start rather than discovering them during an incident.

Frequently asked questions

Licensing terms and published pricing verified 18 September 2026 against Perforce’s product pages, master terms, supplemental terms and administrator documentation. Self-managed pricing is quote-only and not published by Perforce. ReleaseTEAM is a Perforce partner and runs Perforce deployments, health checks and migrations — including migrations off Perforce to Git and GitLab where that is the right call.