Contact

Reach the project through the right channel.

Use GitHub for reproducible bugs, the security policy for sensitive reports, and the documentation for setup guidance before opening an issue.

Start with the right channel.

AidiPanel is a developer-focused project, so the best contact path depends on what you need: product questions, bugs, security reports, sponsorship, or documentation feedback.

Bug reports

Open a GitHub issue with your OS version, install command, error message, and relevant log excerpt.

Open issue

Security reports

Please do not publish sensitive vulnerabilities in a public issue. Use the repository security policy when reporting security problems.

Security policy

Documentation feedback

If a guide is confusing, outdated, or missing an edge case, open an issue and mention the page or command you followed.

Read docs

Sponsor or support

If AidiPanel helps your workflow, sponsorship helps fund VPS testing, documentation, and continued development.

Sponsor

What to include when asking for help.

  • A clear description of what you expected and what happened instead.
  • OS version, architecture, provider, and whether the VPS was fresh.
  • The AidiPanel version and install or CLI command you ran.
  • Relevant log lines with passwords, tokens, private keys, and real customer data removed.

Security-sensitive messages.

For possible vulnerabilities, avoid posting exploit details, credentials, private IPs, backup URLs, or server secrets in public. Give enough context to reproduce the issue safely, then wait for a private follow-up channel if needed.

Never share secrets publicly.

Remove access tokens, root passwords, database credentials, SSH keys, cookie values, and customer data before posting logs.

Response expectations.

AidiPanel is maintained independently. Support is best-effort unless a separate support arrangement exists. Clear reports with reproducible steps are easier to investigate and usually receive better answers.