Security at AIO Panel
A control panel has root on your server. Here is what we do to deserve that, and how to reach us if you find a problem.
Updates with rollback
The panel updates itself from aiopanel.net. Every release is checked after installation and rolled back automatically if it fails. Operating-system security updates can be applied unattended.
Signed, verified builds
Official builds are published with their hashes. The license server verifies the build hash on every check-in, so a modified panel cannot use a paid license.
Passkeys and 2FA
Passkeys, TOTP two-factor authentication with recovery codes, login lockouts, API tokens with scopes and IP allowlists, and a full audit log of every action.
Hardened defaults
UFW firewall presets, Fail2ban jails, ModSecurity with the OWASP core rules, ClamAV scans, TLS everywhere, and a security advisor with one-click fixes.
Reporting a vulnerability
Send details to the address below, with steps to reproduce. Please give us time to fix the issue before publishing.
- security@aiopanel.net ·
/.well-known/security.txt - We acknowledge reports within two working days and publish fixes in the changelog.
- A public bug-bounty program accompanies the 1.0 release; see the roadmap.
What the license check sends
Licensed panels refresh their token about once a day. The request contains exactly these fields and nothing about your customers or websites:
keyserverIdhostnamepanelUrlversionaccountsbuild.hashbuild.keysThe free plan never contacts the license server.
Your data
aiopanel.net stores your account, invoices and license activations. Privacy questions: support@aiopanel.net.