Standard SaaS
Vendor-operated platform with standard isolation and regional configuration.
Enterprise & Private Deployment
Deploy the platform in the model your enterprise requires.
The standard SaaS deployment suits many organizations. Others have requirements around residency, network boundaries, customer-controlled cloud, private connectivity, or operational ownership.
Overview
When the standard environment does not meet the constraints.
Enterprise & Private Deployment defines and implements an approved deployment model aligned with the customer's security, residency, operational, and integration requirements.
Objective
Provide an Applied SAFe® Platform deployment architecture aligned with enterprise security, residency, operational, and integration requirements.
Deployment patterns
Five patterns, where technically supported and agreed.
Enterprise SaaS configuration
Additional enterprise controls or region-specific setup around the standard service.
Hybrid deployment
Selected customer data or components remain in the customer environment while approved platform services operate elsewhere.
Customer-controlled cloud
Selected deployment components operate within a customer-controlled cloud environment.
Private / on-premises
A dedicated deployment model for environments requiring stronger infrastructure control, subject to product capability and commercial scope.
How the service works
Five steps from requirements to established operations.
Define requirements
Capture security requirements, data classification, residency, identity, network constraints, operational responsibilities, integrations, availability, and support expectations.
Select the deployment pattern
Identify the supported model that best fits the requirements.
Design the architecture
Define environment boundaries, connectivity, identity, data flows, secrets, operations, monitoring, and responsibilities.
Implement and validate
Deploy the agreed environment and test representative platform and integration workflows.
Establish operations
Define responsibilities for upgrades, support, monitoring, incident handling, backup, and lifecycle management.
Operations are defined explicitly
- Upgrades
- Support
- Monitoring
- Incident handling
- Backup
- Lifecycle management
Deliverables
- Deployment requirements
- Target architecture
- Responsibility model
- Deployed environment where included
- Security and integration configuration
- Validation results
- Operational documentation
Related
Identity & Enterprise Integration
Identity and deployment constraints are usually decided together.
Integration Architecture
Deployment boundaries follow from the integration design, not the other way round.