Skip to main content
Support channels vary by edition. Community edition users get support through GitHub Issues. SaaS edition users get email or dedicated support depending on their plan.

​
Community edition

The primary support channel for the Community edition is GitHub Issues.

​
Before opening an issue

1

Search existing issues

Search open issues and closed issues. Your issue may already have a resolution.
2

Check the troubleshooting guide

The Troubleshooting page covers the most common startup and runtime issues, including missing environment variables, auth errors, and scan failures.
3

Check the FAQ

The FAQ answers common questions about features, editions, and credential handling.

​
Filing a good bug report

A well-written issue gets resolved faster. Include:
  • Your InfraAudit version: docker compose exec api ./infraudit-api --version or infraudit version
  • Your operating system and deployment method (Docker Compose, Kubernetes, or binary)
  • Step-by-step instructions to reproduce the issue
  • What you expected to happen versus what actually happened
  • Relevant log output — redact all secrets and credentials before pasting
Open an issue →

​
SaaS editions

Email support with a 2 business day response time.Email: support@infraaudit.dev
Priority email support with a 1 business day response time.Email: support@infraaudit.dev — include “Professional” in the subject line to ensure priority routing.
Dedicated support with a 4-hour SLA for P1 issues. Includes:
  • A dedicated Slack channel with direct access to the engineering team
  • A named account engineer
  • Priority escalation path for critical issues
Contact your account manager to set up your dedicated support channel.

​
Documentation feedback

If something in the documentation is missing, unclear, or incorrect, the docs source is in pratik-mahalle/infraudit-docs on GitHub. Open a PR with your correction or an issue describing the problem.

​
Feature requests

Feature requests are tracked in GitHub Discussions. You can open a new request or upvote existing ones. Requests with strong community interest are prioritized in the roadmap. View or submit feature requests →

​
Security vulnerabilities

Do not report security vulnerabilities in public GitHub issues.
Email security@infraaudit.dev with:
  • A description of the vulnerability
  • Steps to reproduce
  • Your assessment of the severity
Security reports are acknowledged within 48 hours. For critical issues, a patch is typically released within 14 days.