Getting Started with Helio Audit

Adopt Helio Audit by deploying the platform, connecting your Git provider, selecting Repositories, and enabling AI Reviews on Pull Requests. Findings appear as Issues and Suggestions where developers already work.

Adoption path

1. Choose how Helio Audit will run in your environment
2. Connect at least one Git provider (GitHub, GitLab, or Bitbucket)
3. Select Repositories to analyze
4. Enable AI Reviews on Pull Requests
5. Act on Issues and Suggestions, and apply Policies as needed

1. Choose a deployment approach

Helio Audit is designed for self-hosted and enterprise environments so source code stays under your control. Supported deployment targets include Docker, Docker Compose, Kubernetes, Linux hosts, and major cloud providers.

• Installation — choose an install path
• Self-hosting overview — deployment options and privacy goals
• Self-hosting architecture — how Helio Audit fits your environment

Use the deployment configuration provided with your Helio Audit installation for environment-specific setup.

2. Connect a source control provider

Helio Audit connects and synchronizes Repositories from:

• GitHub
• GitLab
• Bitbucket

Authentication, permissions, and webhook setup follow the integration configuration shipped with your Helio Audit release.

3. Select Repositories

After a provider is connected, choose which Repositories Helio Audit should manage and analyze. Helio Audit can:

• Synchronize Repositories from the connected provider
• Detect languages, frameworks, and project structure
• Analyze beyond individual Pull Requests with broader Repository scans

4. Enable AI Reviews

With Repositories connected, Helio Audit enhances Pull Request Reviews with automated analysis:

• AI Change Review — summaries and repository-aware change understanding
• AI Pull Request Review — bugs, security concerns, and maintainability Issues before merge
• Security Pull Request Review — secrets, vulnerable dependencies, and IaC misconfigurations
• Comment resolution assistance — guidance to close review threads

See AI Reviews and How AI Reviews work.

5. Use findings in your workflow

Findings include AI explanations and remediation guidance. Teams typically consume results:

• On the Pull Request in the Git provider
• In IDE extensions
• Through CLI tools for local or staged changes

For security-focused findings, see Security and Secrets detection.

6. Align Reviews with Policies

Use Policies and Organization standards so Reviews apply consistent expectations across projects.

Quick links