How ServerDog reaches your servers.
ServerDog has no cloud. The Mac app connects to each server over your own SSH connection and talks to a small open-source agent through a Unix socket that only root can open. Your SSH keys, provider tokens and database passwords stay in the macOS Keychain, and no third party holds access to your servers.
By ServerDog. Updated .
Key facts
- ServerDog connects from your Mac to your servers over SSH with your own key. No vendor’s server sits in between.
- The agent on each server is open source (Go, Apache 2.0). It listens only on a Unix socket that only root can open, has no TCP port and never updates itself.
- SSH keys, cloud provider tokens and database passwords are kept in the macOS Keychain. A token is sent only to the provider it belongs to.
- Removing a server from ServerDog does not touch the server. It keeps running with everything installed.
With a hosted panel, the vendor’s cloud sits between your Mac and your servers and keeps your SSH key, your cloud token and your Git token. Your servers let the vendor’s key log in as root and keep SSH open to it, so a breach at the vendor could reach every server it manages. With ServerDog there is nothing in between: the three secrets stay in your Mac’s Keychain, only your key can log in as root, and the agent listens on a root-only Unix socket with no port.
The connection: your own SSH
ServerDog uses the SSH client that ships with macOS and the key you already use: one from your SSH agent or 1Password, a key file, or a new key the app generates for you. It opens one SSH connection per server and reaches the agent by forwarding its Unix socket through that connection.
Host keys are checked strictly. ServerDog keeps its own list of known hosts, and if a server’s fingerprint changes it stops and asks you whether to trust the new one before it connects again. For a server on a private network, it can log in to a jump host with the same key and connect onward.
The agent: small, open source, and silent on the network
Each server runs one ServerDog process, an agent written in Go and published under the Apache 2.0 licence. It does the work the Mac app asks for: creating sites, running deploys, reading metrics and logs.
- It listens only on
/run/serverdog/agent.sock, a Unix socket owned by root with mode 0600. - It has no TCP listener, so it opens no port and needs no firewall rule.
- It never updates itself. The Mac app replaces it when you choose to, and restores the previous version if the new one doesn’t start.
- It has no web interface and no login page.
Secrets: in your Keychain
SSH keys the app generates, cloud provider tokens, Git tokens and database passwords are stored in the macOS Keychain on your Mac. A token goes only to the service it belongs to: a Hetzner token to Hetzner, a GitHub token to GitHub.
Each site gets its own read-only deploy key, created on the server. The private half never leaves the server, and the public half is added to one repository, not to your whole Git account.
Your Keychain, not their database
SSH keys and tokens stay in the macOS Keychain. A token is sent only to the service it belongs to, and each site gets its own read-only deploy key whose private half never leaves the server.
An agent you can read
The agent is open source under Apache 2.0. It listens on a Unix socket only root can open, has no TCP listener and never updates itself. You reach it through your own SSH connection.
Nothing to leave behind
Your servers stay in your own cloud account. Removing one from ServerDog never touches the VPS, and your sites keep running on a standard Ubuntu stack.
The firewall: closed unless listed
ServerDog sets up ufw on every server it provisions. On a server that hosts sites, SSH, HTTP and HTTPS are open; every other port is closed until you add a rule. When you turn on the private network, the database, Redis and Memcached listen there too, and only the servers you add to the network get through.
How is this different from a hosted panel?
A hosted panel has to reach your servers from its own cloud, so it keeps an SSH key that can log in as root on each one, along with your cloud provider token and access to your Git account. With ServerDog there is no such party. See the comparisons with Laravel Forge, Ploi and RunCloud, or all comparisons.
What happens when you stop using ServerDog?
Your servers live in your own cloud account and run a standard stack: Nginx, PHP-FPM, your database and systemd services. Removing a server from ServerDog never touches it. The server keeps running with everything installed, and you can add it again whenever you like.
Questions
Can the makers of ServerDog access my servers?
No. ServerDog has no cloud service and no account that holds your keys. The app runs on your Mac and connects to your servers with your own SSH key, so its makers cannot reach them.
Does the ServerDog agent open a port on my server?
No. The agent listens only on a Unix socket at /run/serverdog/agent.sock, owned by root with mode 0600. It has no TCP listener, so there is nothing to scan and nothing to add to your firewall.
Is the ServerDog agent open source?
Yes. The agent is written in Go and published under the Apache 2.0 licence, so you can read exactly what runs as root on your server. The Mac app is closed source.
Where does ServerDog store my SSH keys and API tokens?
In the macOS Keychain on your Mac. A cloud provider token is sent only to that provider, and a Git token only to its Git host. Database passwords are generated on your Mac and kept in your Keychain.
Does ServerDog need root access?
Yes. Setting up a server means installing packages and configuring services, so ServerDog needs root access over SSH. The difference from a hosted panel is who holds that access: you, from your Mac, with your key.
What happens to a server when I remove it from ServerDog?
Nothing. The server keeps running with everything installed, including the agent, and you can add it again at any time. ServerDog only deletes the server at your cloud provider if you tick that option yourself.
Does the agent update itself?
No. The agent never updates itself. When a new version is available the Mac app offers to replace it, and restores the previous one if the new version doesn’t start.
Last updated by ServerDog.