Managed SaaS
Managed SaaS
StackGen hosts and operates the platform in a StackGen cloud account. This model has the fewest infrastructure requirements for your team.
Architecture
StackGen runs the application in Kubernetes and manages its PostgreSQL databases, object storage, networking, security updates, backups, and platform upgrades.
Your infrastructure remains in your own cloud accounts. StackGen connects to those accounts only through the credentials and integrations that you configure for product workflows.
Responsibilities
StackGen:
- Provisions and operates the StackGen service.
- Maintains the application and supporting services.
- Applies platform upgrades and security patches.
- Monitors the service and handles platform recovery.
You:
- Configure your organization, projects, users, and access policies.
- Register an identity provider if you require enterprise SSO.
- Configure Git providers and cloud credentials used by your projects.
- Manage the permissions and rotation of credentials that you add to StackGen.
Customer requirements
Before onboarding, identify:
- Organization administrators and initial users.
- The identity provider and domains allowed to sign in.
- Git providers used for generated infrastructure code.
- Cloud accounts and the least-privilege roles StackGen workflows may use.
- Your data retention, compliance, and network access requirements.
For setup instructions, see StackGen settings, Microsoft Entra ID SSO, AWS IAM Identity Center SSO, and Git configurations.
When to use Managed SaaS
Use Managed SaaS when you do not require the StackGen application or its databases to run in your cloud account or data center. Choose Private SaaS if data residency requires a customer-owned cloud account. Choose on-prem / air-gapped if the platform cannot have external egress.