Deployment models
StackGen deployment models
StackGen offers three deployment models. The StackGen product remains the same. The location, operating responsibility, release process, and network requirements change.
| Managed SaaS | Private SaaS | On-prem / air-gapped | |
|---|---|---|---|
| Runs in | StackGen cloud account | Your AWS, Azure, or Google Cloud account | Your data center |
| Infrastructure owner | StackGen | You | You |
| Platform operator | StackGen | StackGen | Your team |
| Upgrades | StackGen applies releases | StackGen applies releases through GitOps | Your team installs packaged releases |
| Data location | StackGen-managed data services | Databases and object storage in your account | Databases and object storage in your environment |
| Network access | Internet service | Outbound access to the deployment repository, image registry, and identity provider | No external egress required |
| Support access | StackGen-managed | Only the access you grant | Logs and diagnostic bundles that you export |
Choose a deployment model
Choose Managed SaaS when you want StackGen to host and operate the entire platform.
Choose Private SaaS when StackGen and its data must run in your cloud account, but you want StackGen to manage application releases and upgrades.
Choose on-prem / air-gapped when the platform must run without external network access and your operations team can own installation, upgrades, rollback, and first-line diagnosis.
Private SaaS and on-prem both keep application data in your environment. On-prem also moves release delivery, image management, upgrades, and operational access to your team.
Prepare for deployment
Your StackGen representative confirms supported versions, capacity, and the final architecture before deployment.