Security
Your servers.Your rules.
HiPanel only sends commands to your servers when you ask and allow it. Your site data stays on your servers, secrets are encrypted, and you can leave at any time.
The only four ways a command reaches your server
Every change on a server starts from one of these four sources, and each one is a task with an initiator, a timestamp and a log.
You click an action
Create a site, issue SSL, reboot… every click becomes a logged task that runs exactly once.
You call the API with a token
Scripts and CI use a token you created, limited to the scopes you chose and never beyond your role.
You approve an AI suggestion
The AI assistant only reads until you approve. Changes show a confirmation card and run only when you approve them.
An automation you turned on
Deploy on push, backup schedules, post-deploy checks: they only run once you turn them on and stop as soon as you turn them off.
How HiPanel connects to your servers
Commands travel over SSH from HiPanel to the server, only when there is a task. The other direction only carries monitoring data.
A key per server
Each server gets its own ed25519 key pair generated by HiPanel. The private key is encrypted at rest and never shared between servers.
Pinned host keys
The server's host key is remembered after the first connection. If it changes unexpectedly, HiPanel refuses to connect instead of sending commands.
The agent only sends metrics
The agent on your server sends CPU, memory and disk metrics to HiPanel every 30 seconds with its own token. It never accepts remote commands.
How your data is protected
HiPanel only stores what it needs to manage your servers: configuration, encrypted access keys and task history. Site content never leaves your server through HiPanel.
Secrets are encrypted
SSH keys, root passwords, provider tokens, environment variables and backup repository passwords are encrypted at rest with AES-256-GCM. API tokens are only stored as hashes.
Your data stays on your servers
Site files and databases live on your VPS. Backups go straight to your S3 and are encrypted before they leave the machine; HiPanel keeps no copy.
No secrets in logs
Passwords, keys and tokens are never written to task logs or HiPanel's system logs.
Isolated per team
Every data query is scoped to a team. People outside your team can't see your servers, sites or tasks.
Every person, token and agent gets exactly the access it needs
Permissions are enforced by the API for every source: the web interface, scripts, CI or the AI assistant.
Role-based access
Owner, admin, developer, viewer. Every API route is checked in one place before it runs.
Tokens never exceed their creator
A token's effective permissions are its scopes intersected with its creator's current role, checked on every request.
AI with guardrails
The AI assistant uses your permissions, every change waits for your approval, and passwords never pass through the model.
Providers you authorize
You connect providers yourself with an API token or OAuth. HiPanel only uses the scopes you grant, and you can revoke them at any time.
A system user per site
Each site runs as its own Linux user, and per-site SFTP and SSH are only on when you need them.
API rate limits
Each token, user and IP address has a per-minute request limit to stop abuse.
You can always leave
Remove HiPanel's key from the server's authorized_keys file and uninstall the agent service, and HiPanel loses all access. Your sites, databases and configuration keep running because they are standard software on your machine.
Read more about how we handle personal data in our Privacy policy.
Ready to deploy your first site?
Create an account, connect a server and ship your site in minutes.