Perforce with Horizon
Horizon operates Perforce as a first‑class component of its governed development platform, combining studio DevOps expertise with Horizon TechOps to deliver secure, high‑performance asset pipelines.
Perforce as part of one governed operating model
Perforce plays a central role in many game development pipelines, particularly where large assets, unreleased content, and external collaboration are involved.
In Horizon, Perforce is not treated as a standalone service or a bolt‑on integration. It operates as part of the same governed platform that runs workspaces, CI/CD, automation, and environments.
Zero‑trust access around Perforce
Access to Perforce follows Horizon’s zero‑trust model using centralized identity, MFA, and role‑based access control.
Work is performed inside governed remote workspaces where possible, reducing local asset copies and minimizing IP exposure while preserving day‑to‑day workflows.
Co‑located by default for performance and simplicity
Horizon deploys Perforce together with developer and artist workspaces, CI/CD and automation, and high‑performance storage in the same environment and region by default.
This delivers low‑latency access, predictable performance, simplified networking, and easier automation across the pipeline.
Co‑development and external studios
External studios and partners access Perforce through the same governed operating model as internal teams.
Horizon avoids ad‑hoc VPNs and security exceptions, enabling clean onboarding and offboarding without disrupting the core pipeline.
Operational ownership as a joint effort
Studios using Perforce typically have deep expertise in how the tool is used day to day. Horizon TechOps does not replace this knowledge.
Instead, Horizon TechOps works alongside studio DevOps teams, taking responsibility for platform‑level concerns such as placement, security, scaling, backups, monitoring, and lifecycle management, while studios retain control over workflows, depot structure, and conventions.
When this model makes sense
This approach is particularly valuable for asset‑heavy AA and AAA studios, distributed teams, co‑development ecosystems, and publishers operating multiple pipelines.
Smaller teams with simple Git‑only workflows may not require this level of orchestration.
What Horizon does not change
Studios keep their Perforce licenses, depot structure, and workflows. Horizon governs the environment and operating model around Perforce rather than altering the tool itself.
©Game-Hosting GH AB. All rights reserved.