Stream
not sync
Mount a drive and open only the bytes you read, with no workspace to sync down to local disk before you can work.
Comparison
Swarmfile vs. Perforce
Perforce Helix Core is the incumbent for version-controlling huge binary assets, the backbone of AAA game and VFX pipelines for decades, and genuinely excellent at it. Swarmfile is a different shape: version control you mount instead of check out, on a managed cloud, not a self-hosted server your team runs and syncs workspaces to. Here's the honest side-by-side, both ways. Last reviewed September 2026.
The frame that matters
SaaS
not a server
Cloud tier, identity, storage durability, and alarms are managed. Perforce Helix Core is a server you run.
LAN
P2P mesh
Every workstation seeds its neighbors. One cloud fetch per office, with no proxy or edge server to deploy per site.
Where Perforce is stronger today: it's proven at extreme scale over decades, ships native Unreal and Unity integration, and a generation of artists work its checkout flow by muscle memory. We don’t hide it. See the full side-by-side below.
IncludedPartial or with conditionsNot offeredA highlighted row marks where one side clearly leads.
Product shape
Capability
Swarmfile
Perforce
How users access files day-to-day
Mount a drive on every workstation. Resolve, Premiere, Revit, Unreal open files at native paths and stream only the bytes actually read, with no workspace to sync, no checkout step to browse.
Create a workspace and
p4 sync files down to local disk before you can open them; check out (p4 edit) to change. The proven VCS shape for huge binaries.Local disk footprint
✓A few MB of metadata until a file is read; byte-range streaming with an LRU block cache. A 5 TB project isn't 5 TB on your disk.
◐What you work on is synced to a local workspace. Narrow/sparse workspace views help, but the files you touch live on disk.
Who it's built for
Editors, artists, BIM coordinators, surveyors who just want files to appear. Version control is there in the web UI if they want it, not a daily ritual.
Studios and pipelines that already live in changelists and workspaces, usually with a Perforce admin keeping the server healthy.
Perforce is a version control server you sync workspaces from. Swarmfile is a drive you mount and stream from. Different muscle memory: pick the one that matches how your team already opens files.
Deployment & operations
Capability
Swarmfile
Perforce
Runs as
✓Managed SaaS: identity, billing, storage, GC, alarms all run for you. On Enterprise, a self-hosted control plane (the same code, not a fork) runs on a third-party, Workers-compatible runtime you host. A fully air-gapped deployment is on the roadmap.
◐Self-host the Helix Core server (yours to run, patch, back up) or use their managed Cloud tier. On-prem control is the default and a genuine strength for some buyers.
Remote offices / distributed teams
✓LAN-first P2P mesh + cloud fallback on every plan. The first person at a site warms it, everyone after is on the LAN. No per-site appliance.
◐Add Helix Proxy / Edge / Broker per site and configure replication to make remote work fast. Powerful, but it's infrastructure to stand up.
Who administers it
No Perforce-admin role; the platform is operated for you.
Typically a dedicated Perforce/DevOps admin, especially as depots and user counts grow.
Swarmfile is operated for you. Perforce Helix Core is a server you run (or their newer Cloud tier), plus per-site infrastructure for remote teams.
Locking, presence & worksharing
Capability
Swarmfile
Perforce
Exclusive locking for un-mergeable binaries
✓Exclusive entry locks with heartbeat and long-lived offline checkout locks (Pack & Go), hub-enforced across machines on macOS, Windows and Linux. On Windows the mount also enforces the native lock Revit and SolidWorks take on open, no plugin. A hub-enforced byte-range lock API is there to build finer-grained integrations against; no app uses it out of the box today.
✓Exclusive checkout (
+l) and atomic changelists, refined over decades, the workflow the binary-asset world standardized on. Whole-file granularity.See who has a file open, live
✓Real-time presence roster driven by the lock lifecycle, in the web dashboard and the Desktop App.
◐
p4 opened and have-lists show it on demand; less of a live, at-a-glance presence surface than a dedicated UI.This is Perforce's home turf and it earns the credit. Swarmfile brings exclusive locks plus a live presence surface, minus the server.
Branching, merge & review
Capability
Swarmfile
Perforce
Branch a variant
Per-mount branches over shared content-addressed blocks: branching a 4 TB project is instant and near-free on disk.
Streams (Perforce's branching model) plus classic branches: mature and powerful, workspace-based.
Review before a change lands
✓Built-in merge requests with required-approval counts + branch protection, plus per-file comments and @mentions in the web dashboard. No extra product to deploy.
◐Helix Swarm (a separate product) adds review. Capable, but another thing to stand up and run.
Multiple pending changelists at once
✓Open several changelists on one mount and switch which one's current, so an unrelated quick fix doesn't force you to submit a large in-progress batch first. Move a staged file (or all of them) to a different open changelist without unstaging and restaging.
✓The model this is built on:
p4 has natively supported many pending changelists per workspace for decades, with p4 reopen -c to move files between them.Collaboration & non-technical users
Capability
Swarmfile
Perforce
Web collaboration surface
✓Comments, @mentions, an activity feed, RFIs/submittals, share links, and presence, built in, aimed at people who don't live in a terminal.
◐P4V plus add-on products (Swarm, Helix DAM). Powerful, but assembled from parts and aimed at technical users.
External / client review, no paid seat
✓A named guest gets a kernel-level read-only mount of one folder, plus password-gated share links with expiry and access caps. The weekly client-review motion for M&E and AEC.
-No native no-seat guest-review motion; external reviewers mean licensing or exporting files out.
Security & compliance (managed)
Capability
Swarmfile
Perforce
Encryption, residency & data protection
✓AES-256 at rest on every paid plan, opt-in end-to-end, EU/US data residency at no extra cost from Starter up, Reed-Solomon erasure coding, and inline ransomware quarantine, all operated for you.
◐Strong enterprise security, but on-prem it's yours to configure, harden, and operate; the Cloud tier is managed.
Identity & access
✓OIDC SSO, SCIM, LDAP sync, folder ACLs and Windows DACL projection on Pro, no admin required. SAML SSO via an adapter, on Enterprise.
✓Mature LDAP/SSO/permissions, configured and run by your Perforce admin.
Ecosystem, scale & integrations
Capability
Swarmfile
Perforce
Battle-tested at extreme scale
◐In production today: real, but new and independent, not a decades-old incumbent.
✓Decades in AAA games and VFX at thousands of users and petabyte depots. The proven incumbent when scale is the whole question.
Game-engine integration
◐Works with any app through the mounted drive; no first-party Unreal/Unity source-control plugin today.
✓Native Unreal and Unity source-control integration, the default the games industry is already built around.
Where Perforce's decades show. We're honest about it: at extreme scale and inside game-engine pipelines, Perforce is the proven default.
Pricing
Capability
Swarmfile
Perforce
List price
Starter $5/seat and Pro $25/seat: transparent, per seat, self-serve, with a 7-day trial. Card on file, nothing charged until day 7. A trial covers up to 2 seats; add more once it converts.
Free up to 5 users / 20 workspaces. Cloud tier $39/user/mo (up to 100 users); Scale and Platform tiers are custom-quoted, and self-hosted licensing is sales-led.
Machine access (render/build nodes)
✓Headless machines use an API-key allowance, not seats: 2/seat included on Starter (min 5) and 5/seat on Pro (min 10), then $2/key/mo. A 100-node farm doesn't buy 100 seats.
Licensed per user; build and automation servers typically run under a named user account, so machines consume licenses like people do.
Total cost of ownership
✓The seat price covers the managed service; no server or proxies to run. Keep an independent backup for critical data.
◐Add server infrastructure, per-site proxies/edge, backups, and admin time to the license, especially self-hosted.
Where Swarmfile is stronger today
- No server to run. There's no Helix Core server or Proxy/Edge/Broker per office, and no Perforce-admin headcount. The platform is operated for you; critical data should still have an independent backup.
- No workspace to sync. You mount a drive and stream only the bytes you open. A 5 TB depot doesn't become a 5 TB local workspace; browsing a million files touches no disk.
- Remote-first, no per-site appliance. LAN-first P2P mesh plus cloud fallback on every plan. One cloud fetch warms an office; everyone after is on the LAN. No edge servers to configure per location.
- Locking that hands off live. Exclusive entry locks with heartbeat and long-lived offline checkout locks (Pack & Go) for reserving a file while you work offline, on macOS, Windows and Linux. Plus a live presence roster and one-click request-to-unlock, so a held file hands over without a Slack message. For integrators, a hub-enforced byte-range lock API is there to build finer-than-whole-file locking against.
- Non-technical users never learn a VCS. Editors, colorists, BIM coordinators, and surveyors just open files. The commit/branch/merge surface is in the web dashboard for those who want it, invisible to those who don't.
- Modern collaboration is built in. Comments and @mentions, an activity feed, RFIs/submittals, share links, presence, and guest reviewers: one product, not P4V plus Swarm plus Helix DAM assembled together.
- Managed security and compliance. AES-256 at rest on every paid plan, opt-in E2E, EU/US residency at no extra cost from Starter up, erasure coding, ransomware quarantine, OIDC SSO/SCIM/LDAP and ACLs on Pro, configured and operated for you, not by your admin.
- Transparent, self-serve pricing. $5/seat and $25/seat, published on the pricing page, start today. No sales call to learn the price of the base product.
- Multi-vertical from day one. Software, games, media, geospatial and AEC, not only game and film pipelines.
Where Perforce is stronger today
- Proven at extreme scale. The single biggest thing Perforce has. Decades in AAA games and VFX at thousands of users and petabyte depots. If scale and a track record are the whole question, Perforce is the safe answer and we won't pretend otherwise.
- Native game-engine integration. Unreal and Unity ship with first-party Perforce source-control support; the games industry's pipelines are built around it. We work with any app via the mounted drive, but we don't ship an engine plugin today.
- The checkout workflow is muscle memory. A generation of technical artists reflexively 'check out' in P4V or straight from the Unreal editor, and the whole games pipeline is wired to that habit. We enforce exclusive locks too, but we don't have decades of that workflow standardized around us, or a checkout button inside the engine editor.
- On-prem control by default. Self-hosted, air-gap-capable, entirely under your control, without needing a separate Enterprise tier. Our self-hosted control plane is Enterprise-only, and a fully air-gapped deployment is still on our roadmap. If 'it must run on our own iron, offline' is a hard requirement, Perforce meets it out of the box.
- A deep, mature tooling ecosystem. P4V, P4VS, Swarm, Helix DAM, and integrations across build systems and DCC tools: decades of surrounding software. We're younger and our ecosystem is smaller.
- Free for up to 5 users. For a small indie team with the ops capacity to run the server, Perforce is free at the low end. Our Starter is a paid per-seat plan.
Moving from Perforce
The honest version: there’s no p4 history importer today. You bring the head revision across, history in Swarmfile starts from there, and Perforce stays around read-only for everything older.
- Bring the head revision. Point swarmfile-migrate at a synced workspace or a NAS copy of the depot's latest state. Run it with --dry-run first to check your --exclude patterns; the real run verifies every file against the source by default and keeps a local state database, so re-running the same command resumes instead of starting over.
- History starts in Swarmfile from there. The import lands as the project's starting point. Every save after it is versioned, branchable and reviewable in Swarmfile; changelists from before the move don't come across.
- Keep Perforce read-only for the past. Leave the old depot up (or archived) as the read-only record for older revisions, blame and audits, and stop submitting to it once the team is working on the mount.
Pick the shape that matches your pipeline.
If your team lives in game-engine pipelines, needs proven petabyte-scale, and has the ops capacity to run a server, Perforce is a great answer. If you'd rather mount a drive, stream only what you open, and skip the server, the workspace sync, and the per-site proxies, start a trial.