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

# FAQ

> Short answers to the product questions that come up most often when teams are getting Cloudgeni into a usable state.

# FAQ

## Does Cloudgeni write directly to my cloud account?

Not as the normal operating model.

Cloud integrations are there for read-side context, scanning, and inventory. The change path is
still repository-first: branch, pull request, and review.

## Do I need both Git and cloud on day one?

You need both for most cross-surface workflows, but not for everything.

* Static Analysis only needs Git
* Cloud Compliance and Cloud Monitors only need cloud
* AI DevOps, drift, and import flows usually become much better once both are available

## Are PR reviews enabled automatically?

No.

PR reviews are enabled per repository after the Git integration is connected.

## Which Git providers are available now?

GitHub, GitLab, and Azure DevOps.

Bitbucket is visible as coming soon, not as an available workflow.

## Which cloud providers are available now?

AWS, Azure, GCP, and OCI.

The setup path differs by provider, and those differences matter.

## What scan engines are actually exposed today?

* Repository static analysis: `checkov`
* Cloud compliance: `prowler-ocsf`
* Cloud monitors: `aws-security-hub` and `azure-defender`

## Can I call Cloudgeni from CI instead of using the UI?

Yes.

Use the [Scanning API](/api-reference/scanning-api) or the [CLI](/cli/overview).

## Does Cloudgeni certify compliance for me?

No.

It helps you organize findings by framework and prioritize remediation work. It does not replace a
full certification or audit process.