Cloudgeni Docs
These docs are written around the product that exists in the codebase today:- Git integrations for repositories, pull requests, and code-side workflows
- Cloud integrations for live inventory, posture scans, and import workflows
- Agent sessions for guided infrastructure changes that still end in branches and pull requests
Start Here
Quickstart
Connect one Git provider, one cloud account, and run a first workflow.
Overview
See how integrations, scans, findings, and agent sessions fit together.
Connect Git
Set up GitHub, GitLab, or Azure DevOps.
Connect Cloud
Choose the right access pattern for AWS, Azure, GCP, or OCI.
Core Workflows
AI DevOps
Start and manage agent sessions with repository and cloud context.
Static Analysis
Run Checkov-backed repository scans and triage code findings.
Cloud Compliance
Run framework-based cloud scans against connected accounts.
Cloud Monitors
Review native findings from AWS Security Hub and Azure Defender.
Cloud Resource Import
Turn discovered cloud resources into an agent-guided import workflow.
PR Reviews
Enable repository-level automated reviews for incoming pull requests.
For Automation
Scanning API
Trigger repository and cloud scans from scripts or CI.
CLI
Use the Bun-based CLI for auth, integrations, scans, and drift operations.
Notes On Scope
These docs intentionally stay close to the current implementation:- They avoid older remediation narratives that no longer match the product structure
- They describe CI/CD integration as API and CLI patterns, not as a managed plugin surface
- They call out provider differences where the app really behaves differently