Self-Hosted Deployment on-premises
Deploy Unity Asset Manager in your own datacenter or colocation facility.
Read time 3 minutesLast updated a month ago
Deploy Unity Asset Manager in your own datacenter or colocation facility. Your IT organization or a solutions integrator implements and operates on-premises deployments. Unity doesn't provide a managed deployment service for on-premises environments. This model is best for organizations that operate internal infrastructure platforms, work with experienced IT delivery partners, and want greater control over hosting. Compared with cloud-hosted deployment, on-premises typically requires a higher upfront infrastructure investment and may offer lower recurring infrastructure costs over time, depending on your operating model and existing IT capabilities.
When on-premises is a good fit
On-premises deployment is best suited to your organization in these cases:
- You already operate internal infrastructure platforms
- You have data residency or hosting-control requirements
- You want greater control over the underlying environment
- You work with experienced IT delivery partners
- You expect relatively stable, predictable usage patterns over time
If you want lower operational overhead, faster scaling, and a more managed service model, choose cloud deployment instead.
Note
On-premises gives you control over hosting location and data residency, but it isn't a fully air-gapped environment. The platform gets software, container images, and releases from Unity's registry. The cluster either pulls them directly, or a connected host mirrors them into your own registry. Plan for a network path to Unity's registry.
Your responsibilities
On-premises, you, your IT organization or solutions integrator provides and operates the following core infrastructure services that keep the platform reliable in production:
- Compute capacity
- Kubernetes
- Storage systems
- Networking and firewalling
- Load balancing and ingress
- Database hosting
- Monitoring and logging
- Backup and disaster recovery
- Security and secrets management
In cloud-hosted deployments, many of these capabilities are delivered as managed services. On premises, you provide and operate them within your own infrastructure.
Benefits and considerations
Benefits
An on-premises deployment offers the following benefits:
- Greater control over infrastructure and hosting location
- Alignment with your internal IT, security, or compliance standards
- Potential long-term infrastructure savings for stable workloads
- Use of existing datacenter investments
Considerations
You need to consider the following operational and infrastructure requirements before you choose an on-premises deployment:
- You operate more infrastructure directly
- Scaling depends on hardware procurement and installation cycles
- You design and maintain high availability, backup, and disaster recovery in your environment
- You may need additional operational tooling for monitoring, storage, secrets management, and messaging
- Integrating your identity provider (IdP) or single sign-on (SSO) with the platform's bundled Keycloak
Delivery model
Your IT organization or solutions integrator implements and operates on-premises deployments. Unity provides the following:
- The Unity Asset Manager application and its container images
- The vpctl release CLI and versioned release and configuration packages
- Helm charts and deployment templates
- Supported architecture and deployment documentation
- Coordination support during planning and implementation phases
Your IT organization or solutions integrator owns the following activities:
- Hardware procurement and installation
- Datacenter setup
- Networking and firewall configuration
- Kubernetes platform deployment
- Storage and backup configuration
- Security hardening
- Patching and operational monitoring
Important
Unity doesn't provide a managed deployment service for on-premises environments. Your IT organization or solutions integrator must implement, operate, and maintain the deployment. Plan accordingly when you choose on-premises instead of cloud-hosted deployment.