Your own VPS
Run a bot desktop on your own Linux server over SSH.
Requirements
Use an x86_64 Linux server with Docker, an SSH user allowed to run Docker without sudo, and the Docker client on the computer running GlinkBot. Docker access is root-equivalent: use a dedicated host and keep its firewall limited to the access you need.
This runs the bot's desktop on your VPS. The agent, conversations and provider credentials remain on the GlinkBot host. To move the whole application, see Server deployment.
Configure SSH
Add a named host to ~/.ssh/config on the GlinkBot computer:
Host my-vps
HostName your-server.example
User your-user
ControlMaster auto
ControlPersist 5m
ControlPath ~/.ssh/control-%C
ServerAliveInterval 30
ConnectTimeout 10
Use your own host and username. Connect manually to verify the host key, then check Docker:
ssh my-vps true
docker -H ssh://my-vps info
For Tailscale, use the server's Tailscale name as HostName. Tailscale does not close unrelated public ports automatically.
Connect in GlinkBot
- Open Settings → Desktops & browser.
- Choose Your own servers → Set up.
- Enter
my-vpsin Self-hosted VPS, then save. - Open your bot's computer settings, select the Self-hosted VPS backend and create or start its desktop.
Enter only the SSH alias. GlinkBot uses your SSH configuration and agent; do not paste private keys, passwords or shell commands into this field. No cloud-provider API key or GlinkBot sign-in is required.
Check the result
Confirm the selected bot computer is the VPS backend before sending work. If connection fails, repeat the SSH and Docker checks on the GlinkBot host. Verify permissions, reachability and host keys. Do not disable host-key verification to work around a failure.
GlinkBot documentation, reviewed for the 0.0.4 codebase. Public download availability can differ. Licenses and acknowledgments.