Skip to content

You trust us with your servers. Here is how we handle that.

A control panel with access to your infrastructure owes you an explanation of how that access works. Briefly, and without marketing.

  • No root
  • Keys are encrypted
  • Every action in the log
  1. An encrypted keythe panel's database holds only ciphertext
  2. Own SSH port instead of 22password guessing gets banned by Fail2Ban
  3. The deploykin usernot root, and not by password
  4. A task in the logwho started it, what it did, how it ended
  5. Your server
  • Least privilege

    The panel gets exactly as much access as the operations you request require. No more.

  • Transparent actions

    Every operation is a task in the journal: you can see who started it, what it did and how it ended.

  • Your data stays yours

    Sites, databases and backups live on your servers and storage. Disconnect from the panel — everything keeps working.

Access

How we handle access.

Six rules the panel follows when working with your servers.

  1. Rule 1

    Keys under encryption

    SSH keys are stored only in encrypted form, and the decryption keys don't sit next to the data. A database leak alone doesn't grant access to your servers.

  2. Rule 2

    Automatic rotation

    The panel's management key is replaced regularly and automatically — without your involvement and without downtime.

  3. Rule 3

    A dedicated user, no root

    The panel works through its own system user. Root login and password login are disabled during initial server setup.

  4. Rule 4

    Own SSH port and key-only login

    During initial setup SSH moves from port 22 to its own port, login works by key only, and Fail2Ban is installed by default. The panel's addresses are added to the firewall rules and kept up to date automatically. The SSH port itself is open to any address, so you can reach the server with your key from anywhere.

  5. Rule 5

    Secrets are redacted

    Passwords and keys in .env files and configs are redacted when an AI tool reads them. SQL for the assistant runs under separate, restricted database users.

  6. Rule 6

    Backups stay with you

    Copies go to your own storage and can be encrypted before upload — you download the recovery key. We don't keep your backups on our side.

AI under control

The assistant can't do more than you allowed.

Scoped tokens, mandatory approvals for dangerous actions, a denylist of destructive commands and an audit of every call — allowed or denied.

MCP call logtoken: claude-code · operate level
tail_logallowed
deploy_websiteallowed
run_commanddenied: sudo level required
db_executedenied: no database access
Denied calls arrive as a notification
  • Every action in plain sight

    Every panel operation is a task in the shared journal: author, contents, status and output. AI and MCP actions are tagged separately and also written to the audit log, with notifications for denied calls.

    Operations center
  • Access revokes instantly

    Revoke an MCP token — access closes immediately. Disconnect a server from the panel — sites, databases and cron jobs keep running: Deploykin deletes nothing and leaves no locks behind.

Found a vulnerability?

Write to us directly — we'll respond fast, fix it and say thanks. We don't pursue good-faith security researchers. The machine-readable contact is in security.txt.

contact@deploykin.com

In the panel 203.0.113.21 Connect done in 4 min 52 s

Put us to the test.

7 days free. Connect a test server and look at the task journal with your own eyes.

  • 7 days free
  • No card required
  • Human support

We use cookies and the Yandex Metrica web-analytics service (including Session Replay) to improve the site. Details are in the privacy policy.