External VPS
Connect a Linux server you already own to the Xuda dashboard over SSH, free, with nothing but a public key ever stored.
External VPS connects a third-party Linux server, on any provider, to your Xuda account over SSH
and gives it the same kind of project screens a Xuda-hosted server has. It is not hosting: Xuda
never provisions, bills, resizes, reboots or destroys the machine. The only credential that
changes hands is Xuda's own public key, which you append to your own
~/.ssh/authorized_keys with one command; remove that line and Xuda is locked out.
Every server-touching feature is opt-in per feature. An un-granted feature does not silently work, it shows a grant panel first.
A connected server has five tabs: Overview, Logs, Files, Team, Advanced. There is deliberately no Power, Resize, Backups, Domain or Firewall tab, those all belong to servers Xuda runs; your machine's power, size, backups, DNS and firewall stay with your provider and with you.
Before you start
- A Linux server you control, on any provider. There is no provider API involved, so any Linux box works the same way.
- A way to log into it yourself, to run one command during the connect flow.
- The server reachable from the internet on its SSH port.
Verification accepts any login user and port. The Files tab, the developer SSH tunnel and Auto
Diagnose currently connect as root on port 22 regardless of what you entered, so a server
connected as another user or on another port verifies fine and then those three features fail.
Connect a server
Open the connect wizard
From Create, pick External VPS, "Connect a server you already own, over SSH."
Enter the server's details
Host/IP (required), SSH port (defaults to 22), login user (defaults to root).
Name it and generate the authorize command
Enter a name, then press Generate authorize command. This is the moment the server is
created in Xuda, in a pending state, so you can close the wizard and come back later. The command
is one line: it creates ~/.ssh if needed, appends Xuda's public key to
authorized_keys, and fixes permissions. It appends rather than overwrites, so existing keys are
untouched, and it sends nothing of yours anywhere.
Run it on your server, then verify
SSH into your server as the login user you entered, paste the line, press Enter. Back in the wizard, press Verify connection. Xuda connects out non-interactively, in batch mode (so a password prompt is a failure, not a wait), with a 10 second timeout. On success it reads the kernel and hostname, the login user, vCPU/memory/disk, and the SSH host key fingerprint, and stores them on the server record.
Finish
The server appears in the sidebar under the servers group with an External badge.
If verification fails, the server stays pending with the real reason shown, usually "unreachable or key not authorized yet." Fix the cause and verify again as many times as needed, or press Regenerate for a fresh command.
Decide what Xuda may touch
Because the machine is yours, every feature that reaches into it is off until you switch it on. Open Advanced > Access:
You do not have to grant these up front. Each feature offers its own grant panel in place: open the Files tab, read what it wants, press Grant. Every grant and revoke is recorded with who and when, and revoking takes effect immediately.
Browse and edit files
Open Files and press Grant the first time. The tree loads from /root. From there:
click through or search by name or content, open a file in the editor (5 MB limit, above that is
download-only), create/rename/delete/upload, tail a .log file live, and open the disk usage
breakdown.
After editing a config, use the service actions row instead of a terminal: nginx test/reload,
Apache test/reload, Caddy reload, systemctl daemon-reload, or a named unit's
status/reload/restart/start/stop. This is an allowlist, not a command runner.
Watch the server's health
Open Overview and grant Overview metrics. Each load opens one SSH session, takes two CPU and network readings a second apart plus a memory and disk reading, and turns that into a sample. Nothing is installed on your server. History improves with how often you look: up to the most recent 2000 samples are kept per server, and the Live toggle re-polls every two minutes.
Publish a public HTTPS address
On Overview, in Server Info, find the Web URL row and press Enable. Xuda
allocates https://<app_id>.xuda.app/ and proxies it to your server's port 80. Open the gear to
change the upstream port. Turn off web URL stops serving it immediately; the subdomain stays
reserved for re-enabling later.
Give a developer SSH or SFTP access
Find the SSH securely row on Overview and press Connect. Create a named access (for
example maria-laptop), optionally with an expiry; the connection token is shown once and only
its hash is stored. The modal gives per-OS websocat install lines and ready-made ssh/sftp
commands against 127.0.0.1:2222; the tunnel terminates at
wss://<subdomain>.xuda.app/__xuda_ssh.
Suspend, edit, regenerate or delete an access from the same modal; suspension and deletion take effect at the tunnel itself, immediately. Session history records the envelope (who, from where, when, how much data), never the contents, the tunnel is end to end encrypted. A separate switch turns on in-server command history if you want interactive shell commands recorded too.
Turn on the daily health check
A paid add-on at $5/mo, gated on the Auto Diagnose consent. Once a day Xuda connects read-only, runs a fixed bundle of checks (load average, memory, root disk, failed systemd units, top processes), and grades each ok, warn or error. AI log analysis draws on your account's AI credits on top of the add-on price; a run with no credit left skips the AI part rather than failing.
Share with a teammate
External VPS uses a single role: Admin, with full access to all five tabs. There is no read-only role. For someone who should work on the box without running your Xuda account for it, give them a named developer SSH access instead of a team seat.
Disconnect
Two separate halves:
- Remove from Xuda. Advanced > Danger Zone > delete. Xuda deletes its own record only; the machine is never powered off, wiped, resized or modified.
- Cut Xuda's access on the server. Delete Xuda's key line from
~/.ssh/authorized_keysyourself.
To pause rather than disconnect, switch the access opt-ins off instead; that is reversible in one click.
What does not work here today
- Firewall control. No Firewall tab, and the agent firewall tools need a Xuda-provisioned server behind them.
- A Domain tab and automatic DNS to the server's IP. Point a domain at the server yourself,
or use the free
xuda.appweb URL. - Backups. The consent scope exists, but there is no Backups tab to run one from. Use your provider's snapshots.
- A custom login user or SSH port on the Files tab, the developer tunnel and Auto Diagnose.
Those three connect as
rooton port 22 regardless of what the wizard was given.
Cost
Connecting and running an External VPS is free: no hosting charge, no plan gate, no cap on how many you connect. The only paid piece is Auto Diagnose at $5/mo per server, plus AI credits for its log analysis.
Next
For a server Xuda builds and bills instead, see Create and run a VPS. To put a domain in front of this server's web URL, see Domains.