Self-Hosting Helio Audit
Helio Audit is built for enterprise environments that need AI-powered code review and security analysis while keeping source code under Organizational control. Self-hosting runs the platform in infrastructure you operate.
Why self-host
- Source code privacy — Repositories and analysis stay inside your network boundary
- Enterprise operations — align with existing platform, identity, and compliance practices
- Deployment flexibility — run on containers, Kubernetes, Linux hosts, or cloud providers you already use
What you self-host
You host the Helio Audit platform that:
- Connects to Git providers (GitHub, GitLab, Bitbucket, and related tools in your stack)
- Runs AI Reviews on Pull Requests and related change analysis
- Performs security and quality analysis, including secrets, dependencies, and infrastructure signals
- Surfaces findings to developers in Pull Requests, IDEs, and CLI workflows
- Provides reporting for engineering and security stakeholders
Your Git providers and CI systems remain separate. Helio Audit integrates with them rather than replacing them.
Supported deployment options
| Option | Role |
|---|---|
| Docker | Containerized deployment |
| Docker Compose | Multi-container deployments |
| Kubernetes | Cluster-based production deployments |
| Linux hosts | Non-orchestrated or traditional server installs |
| AWS, Azure, GCP, Hetzner | Cloud or dedicated infrastructure |
See Installation to choose a path. Follow the release artifacts and configuration shipped with Helio Audit for procedure-level steps.
How self-hosting fits the product
Helio Audit plugs into Git, IDEs, CI, cloud, and chat tools your team already uses, instead of forcing a separate disconnected workflow.
Security considerations
Self-hosting is a primary control for data residency and access. Product security capabilities—application security analysis, secrets detection, dependency and infrastructure checks—are described in Security.
Operational hardening (network policy, identity provider integration, backup) should follow your Organization’s standards and the configuration shipped with your Helio Audit release.
When self-hosting is the right model
- Source code cannot leave your environment
- Platform teams must operate the review and security stack
- You need to align Helio Audit with internal SSO, audit, or compliance processes