​

Quickstart

Cloudgeni is easiest to understand if you treat it as two connected systems:

• A Git-backed change path for branches, pull requests, and repository scans
• A cloud-backed context path for live resources, posture scans, and import workflows

Start with one Git provider and one cloud account or cluster.

​

1. Connect Git

Choose the workspace you want to configure, open Integrations, and select Git Providers. Supported Git providers:

• GitHub
• GitLab
• Azure DevOps

Bitbucket is visible in the UI as coming soon, but it is not available yet. Use Connect a Git provider if you want the provider-specific flow.

​

2. Connect A Cloud Or Cluster Provider

In the same workspace, open Integrations and select Cloud. Cloud connection methods:

• AWS: access key credentials
• Azure: Quick Connect or manual service principal
• GCP: keyless impersonation or service account key
• Kubernetes: read-only static-token or client-certificate kubeconfig
• OCI: API key credentials
• Exoscale: IAM API key and secret
• OpenShift: read-only static-token or client-certificate kubeconfig

Use Connect cloud accounts for the exact setup choices and least-privilege examples.

​

3. Pick One First Workflow

Once Git and cloud are connected, choose a workflow that matches what you want to do first.

​

4. Turn On Pull Request Reviews Per Repository

Connecting a Git provider is not enough by itself. Enable PR reviews for each repository from its settings under the Git integration. See Pull Request Reviews.

​

What This Covers

After these steps, you have the baseline required for most workflows:

• At least one active Git integration
• At least one active cloud integration
• A repository selected for code-side work
• A cloud account selected for live-state work

​

Next