> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudgeni.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Set up Cloudgeni with one Git provider and one cloud account, then run a workflow that matches the product as it exists today.

# 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 of each.

## 1. Connect Git

Go to `Settings` -> `Integrations` -> `Git`.

Supported providers in the current app:

* GitHub
* GitLab
* Azure DevOps

Bitbucket is visible in the UI as coming soon, but it is not available yet.

Use [Connect a Git provider](/getting-started/connect-git-provider) if you want the provider-specific flow.

## 2. Connect Cloud

Go to `Settings` -> `Integrations` -> `Cloud`.

Current cloud setup paths:

* AWS: manual credential flow in the UI
* Azure: Quick Connect is the supported path
* GCP: keyless impersonation or service account key
* OCI: manual credential flow

Use [Connect cloud accounts](/getting-started/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.

<CardGroup cols={2}>
  <Card title="Static Analysis" icon="magnifying-glass" href="/features/static-analysis">
    Scan an IaC repository with Checkov and work from file-level findings.
  </Card>

  <Card title="Cloud Compliance" icon="clipboard-check" href="/features/cloud-compliance">
    Run framework-based cloud scans against a connected account.
  </Card>

  <Card title="Cloud Resource Import" icon="diagram-project" href="/features/cloud-resource-import">
    Select discovered resources and hand them off to an agent-backed import flow.
  </Card>

  <Card title="AI DevOps" icon="robot" href="/features/ai-devops">
    Start an agent session with repository, cloud, and documentation context.
  </Card>
</CardGroup>

## 4. Turn On Pull Request Reviews Per Repository

Connecting a Git provider is not enough by itself.

PR reviews are enabled at the repository level from the repository settings screen under the Git
integration. That matches the code path used by the web app and PR review service today.

See [Pull Request Reviews](/features/pull-request-reviews).

## What This Covers

If you only do the steps above, you will have the same baseline the app expects 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

<CardGroup cols={2}>
  <Card title="Overview" icon="book" href="/getting-started/overview">
    See how the product surfaces fit together.
  </Card>

  <Card title="Scanning API" icon="code" href="/api-reference/scanning-api">
    Trigger the same scan flows from scripts and pipelines.
  </Card>
</CardGroup>