Deployment Process
Process for deploying Governance Studio on your infrastructure.
Prerequisites
Section titled “Prerequisites”Governance Studio can be deployed on any public cloud or self-managed infrastructure provided that its prerequisite dependencies are provisioned. These include:
- Domain name with DNS access (required for platform access and authentication redirect URIs)
- Kubernetes 1.21+
- Helm 3.8+ (installation guide)
- Persistent volume provisioner support in the underlying infrastructure
- Ingress controller - NGINX Ingress Controller recommended (installation guide)
- TLS certificate management - cert-manager for automated certificate provisioning (installation guide)
- Certificate Issuer - A cert-manager Issuer or ClusterIssuer configured (e.g. Let’s Encrypt) (configuration guide)
Deployment Process
Section titled “Deployment Process”Follow these steps in order to deploy the Governance Platform:
Step 1: Prepare Configuration Files
Section titled “Step 1: Prepare Configuration Files”Start by creating values.yaml and secrets.yaml files using the Chart Values guide. These files will hold the platform configuration.
Step 2: Provision External Resources
Section titled “Step 2: Provision External Resources”Governance Studio requires three types of cloud resources. Work through each guide below and fill in the configuration files as you go:
Object Storage (Required) - Choose one provider for storing governance documents and artifacts:
- AWS S3 Bucket - Amazon’s object storage service
- Azure Blob Storage - Microsoft Azure’s blob storage
- Google Cloud Storage (GCS) - Google Cloud Platform’s object storage
Key Management (Required) - Choose one provider for managing cryptographic signing keys:
- Azure Key Vault - Microsoft Azure’s key management service
- AWS KMS - Amazon’s Key Management Service
Authentication (Required) - Choose one identity provider for user authentication:
- Auth0 - Managed identity platform with OIDC support
- Microsoft Entra ID - Microsoft’s enterprise identity platform
All guides provide CLI-first setup instructions with web console alternatives. Mix and match providers based on your cloud infrastructure and organizational requirements.
Step 3: Deploy to Kubernetes
Section titled “Step 3: Deploy to Kubernetes”Once external resources are provisioned and configuration files are complete, follow the Helm Deployment guide to deploy the platform to the cluster.
Platform Architecture
Section titled “Platform Architecture”The Governance Platform uses the Governance Platform Helm Chart to orchestrate services on Kubernetes. The platform uses a microservices architecture:
- Governance Studio - User interface for managing governance processes
- Governance Service - API endpoints that drive governance processes
- Integrity Service - API endpoints for data integrity and auditability
- Auth Service - Authentication and authorization service
- PostgreSQL - Shared database across all services
The Helm chart has an enabled flag for each component if you wish to deploy only part of the platform.
Customization
Section titled “Customization”The platform can be customized for your deployment, including company name, logo, feature flags, and infrastructure scaling. Refer to the Chart Values documentation and individual chart repositories for all available options.