> ## Documentation Index
> Fetch the complete documentation index at: https://docs.infraudit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Get Help and Support for InfraAudit: All Plans

> How to get help with InfraAudit: GitHub Issues for the Community edition, email support for SaaS plans, and dedicated support for Enterprise.

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](https://github.com/pratik-mahalle/infraudit-go/issues).

### Before opening an issue

<Steps>
  <Step title="Search existing issues">
    Search [open issues](https://github.com/pratik-mahalle/infraudit-go/issues) and [closed issues](https://github.com/pratik-mahalle/infraudit-go/issues?q=is%3Aissue+is%3Aclosed). Your issue may already have a resolution.
  </Step>

  <Step title="Check the troubleshooting guide">
    The [Troubleshooting](/self-hosting/troubleshooting) page covers the most common startup and runtime issues, including missing environment variables, auth errors, and scan failures.
  </Step>

  <Step title="Check the FAQ">
    The [FAQ](/resources/faq) answers common questions about features, editions, and credential handling.
  </Step>
</Steps>

### 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 →](https://github.com/pratik-mahalle/infraudit-go/issues/new)**

## SaaS editions

<AccordionGroup>
  <Accordion title="Starter plan">
    Email support with a **2 business day** response time.

    Email: [support@infraaudit.dev](mailto:support@infraaudit.dev)
  </Accordion>

  <Accordion title="Professional plan">
    Priority email support with a **1 business day** response time.

    Email: [support@infraaudit.dev](mailto:support@infraaudit.dev) — include "Professional" in the subject line to ensure priority routing.
  </Accordion>

  <Accordion title="Enterprise plan">
    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.
  </Accordion>
</AccordionGroup>

## Documentation feedback

If something in the documentation is missing, unclear, or incorrect, the docs source is in [pratik-mahalle/infraudit-docs](https://github.com/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](https://github.com/pratik-mahalle/infraudit-go/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 →](https://github.com/pratik-mahalle/infraudit-go/discussions)**

## Security vulnerabilities

<Warning>
  Do not report security vulnerabilities in public GitHub issues.
</Warning>

Email [security@infraaudit.dev](mailto: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.