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

# Scale your infrastructure team. With agents. Safely.

> AI agents that understand your infrastructure context, write production-grade IaC, validate changes in sandboxes, and deliver pull requests.

Cloudgeni turns fragmented cloud operations into a Git-based workflow: connect cloud and Git,
aggregate findings, analyze IaC context, validate changes, and ship pull requests.

| 80%+                          | 10x                          | 24/7                         | PR-first                  |
| ----------------------------- | ---------------------------- | ---------------------------- | ------------------------- |
| Compliance workload reduction | Velocity and team enablement | Automated policy enforcement | Human-controlled delivery |

<Info>
  Your team stays in control. Agents never deploy directly; every infrastructure change is
  reviewable before it reaches your cloud.
</Info>

## Why Cloudgeni

Cloud infrastructure work is fragmented. Findings live in scanners, real state lives in cloud
accounts, intent lives in IaC repositories, and approvals live in pull requests.

Cloudgeni connects those surfaces so teams can:

* Reduce manual compliance and remediation work.
* Convert console-created resources into clean IaC.
* Detect drift between cloud state and code.
* Enforce security and policy standards before merge.
* Give developers self-service infrastructure without bypassing governance.
* Keep every change in Git with review, validation, and context.

## What You Can Do

<CardGroup cols={2}>
  <Card title="Remediate findings" icon="shield-halved" href="/features/cloud-compliance">
    Move from Prowler, Security Hub, Defender, Checkov, CIS, SOC 2, or ISO 27001 findings to
    reviewed IaC changes.
  </Card>

  <Card title="Detect configuration drift" icon="code-compare" href="/features/configuration-drift">
    Compare live cloud state with repository intent and turn drift into reviewable work.
  </Card>

  <Card title="Import ClickOps" icon="sitemap" href="/features/cloud-resource-import">
    Discover console-created resources and bring selected infrastructure under version control.
  </Card>

  <Card title="Review pull requests" icon="git-alt" href="/features/pull-request-reviews">
    Enforce correctness, security, and compliance standards before merge.
  </Card>

  <Card title="Run DevOps agents" icon="robot" href="/features/ai-devops">
    Ask agents to draft, explain, refactor, or validate infrastructure changes with repo and cloud
    context.
  </Card>

  <Card title="Schedule enforcement" icon="calendar-clock" href="/features/scheduled-runs">
    Run recurring checks and agent workflows so policy enforcement is continuous.
  </Card>
</CardGroup>

## How It Works

<Steps>
  <Step title="Connect">Link Git providers and cloud accounts through secure integrations.</Step>

  <Step title="Import">
    Aggregate findings, cloud resources, IaC structure, and repository context.
  </Step>

  <Step title="Analyze">
    Agents understand dependencies, policies, team conventions, and target infrastructure.
  </Step>

  <Step title="Validate">
    Proposed changes are tested with supported static, policy, and plan-style checks.
  </Step>

  <Step title="Ship">
    Cloudgeni opens production-ready pull requests with context and validation results.
  </Step>
</Steps>

## Agentic Cloud Ops

<CardGroup cols={3}>
  <Card title="Remediation Agent" icon="shield-check" href="/features/cloud-compliance">
    Fix compliance findings as real IaC, validate the change, and open clean PRs.
  </Card>

  <Card title="Drift Agent" icon="code-compare" href="/features/configuration-drift">
    Detect discrepancies between cloud state and IaC, then guide reconciliation.
  </Card>

  <Card title="Import Agent" icon="sitemap" href="/features/cloud-resource-import">
    Convert unmanaged cloud resources into idiomatic Terraform or Bicep.
  </Card>

  <Card title="DevOps Agent" icon="robot" href="/features/ai-devops">
    Turn natural language, templates, docs, and rules into validated IaC work.
  </Card>

  <Card title="PR Review Agent" icon="code-pull-request" href="/features/pull-request-reviews">
    Review every configured PR for infrastructure correctness, security, and policy issues.
  </Card>

  <Card title="Cost workflows" icon="chart-line" href="/features/cloud-monitors">
    Identify cloud signals that should become cleanup, rightsizing, or policy work.
  </Card>
</CardGroup>

## Trust Architecture

Cloudgeni is built for safe AI adoption in infrastructure:

* **Sandboxed execution:** agent work runs in isolated, ephemeral environments.
* **Credential isolation:** cloud access is read-first and deployment credentials stay in your
  controlled systems.
* **Pre-PR validation:** supported workflows validate changes before pull requests are created.
* **Multi-tenant RBAC:** environments, credentials, policies, and approvals are scoped.
* **Git-based audit trail:** every meaningful infrastructure change lands in reviewable Git history.

Read [Security Commitment](/trust/security-commitment) for the architecture and boundaries.

## Built For

| Team                   | Why it matters                                                                       |
| ---------------------- | ------------------------------------------------------------------------------------ |
| Platform Engineering   | Scale infrastructure delivery without scaling manual review and ticket handling.     |
| Security & Compliance  | Move from detection to fix while preserving policy gates and auditability.           |
| FinOps                 | Turn waste signals into cleanup, rightsizing, and policy work as code.               |
| Engineering Leadership | Adopt AI for infrastructure with pull-request control instead of unchecked autonomy. |

## Start Here

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Connect one Git provider, one cloud account, and run a first workflow.
  </Card>

  <Card title="Getting Started Overview" icon="book" href="/getting-started/overview">
    See how integrations, scans, findings, and agent sessions fit together.
  </Card>

  <Card title="Connect Git" icon="code-branch" href="/getting-started/connect-git-provider">
    Set up GitHub, GitLab, or Azure DevOps.
  </Card>

  <Card title="Connect Cloud" icon="cloud" href="/getting-started/connect-cloud-accounts">
    Choose the right access pattern for AWS, Azure, GCP, or OCI.
  </Card>
</CardGroup>