How it works
One governed operating model across development and production.
Horizon works by orchestrating the systems involved in development and production through one governed control plane. It standardizes how teams work, how software moves through environments, and how policy, access, and visibility stay consistent across the lifecycle.
Horizon is designed to replace fragmented operating models with one governed platform. Instead of asking studios to manage separate tools, policies, and environments in parallel, Horizon governs how those systems connect and behave together. The goal is not simply integration. The goal is lifecycle continuity across development and production.
It starts with the control plane
At the center of Horizon is a governed orchestration layer. That layer sits above individual tools and services and helps studios retain flexibility in how their pipeline is assembled while gaining consistency, policy alignment, and clearer operational ownership. The exact stack is configurable, but the operating model remains governed.
This is what makes Horizon different from a loosely stitched set of tools. It is not just a collection of components. It is the platform layer that governs how the broader development and production pipeline works over time.
What spans both sides
What makes Horizon powerful is what stays consistent across both development and production. Identity and access, policy and governance, secrets and configuration, observability, and operational ownership are applied across the full lifecycle rather than being handled separately in each stage. The same rules, controls, and visibility follow the software end to end.
That creates a more coherent operating model with fewer hidden handoffs and less drift between environments.
Development and production under the same model
Horizon is built around a simple idea: development and production are different domains, but they should operate under the same governed model. On the development side, Horizon standardizes how teams work through secure remote workspaces, workflow orchestration, build, test, and delivery automation. On the production side, it governs how software moves into and runs across test, staging, and live environments.
That reduces the fragmentation that often builds up between the way software is created and the way it is ultimately run.
Typical capabilities Horizon can orchestrate
Horizon can govern a configurable platform across the broader lifecycle, including:
- IDP and workflow orchestration
- remote workspace lifecycle management
- GitHub, GitLab, or Perforce for source and asset workflows
- Jenkins and Argo CD for build and delivery automation
- Vault for secrets and credentials
- Kubernetes environments across development, testing, staging, and production
- central observability and logging for operational and executive visibility
The point is not that every studio uses the same stack. The point is that Horizon is designed to govern the pipeline as one coherent model.
Security and governance built in
Horizon includes centralized identity, policy, and access controls as part of the operating model. This includes centralized identity, MFA, RBAC, segmented access patterns, time-boxed contractor access, centralized logging, and audit-ready visibility.
That means governance is not bolted on after the platform is built. It is embedded in how the platform works.
Why this model matters
When workspaces, build pipelines, environments, access, secrets, and observability are governed together, teams spend less time dealing with fragmented setups and inconsistent workflows. Horizon is designed to reduce non-productive time, improve onboarding, strengthen governance, and create more consistency across environments.
That is why this page is not just about listing components. It is about showing how those components become a governed system instead of a pile of disconnected tools.
Managed rather than self-assembled
Horizon is delivered as a managed service. Studios do not need to design, integrate, and operate the platform themselves in order to get the benefits of a governed model. That reduces the burden of internal platform engineering while still allowing the operating model to adapt to the studio’s workflows, compliance needs, and infrastructure choices.
This is an important part of how Horizon works in practice: managed outcomes instead of asking clients to assemble and govern a complex stack alone.
©Game-Hosting GH AB. All rights reserved.