External VPS · bring your own server

Already have a server?
Hand it to your AI.

Keep the VPS you already run, on any provider, and put Xuda's control plane on top of it. Authorize with one command (no passwords or keys ever stored), and manage it from the dashboard: files, logs, domains, firewall, a public web URL, and AI agents that operate the whole box over MCP.

Any provider
No passwords or keys stored
Free to connect
Revoke any time
Connect a serverStep 2 of 3
Host / IP203.0.113.10
SSH port22
Login userroot
Authorize with one line
$curl -fsSL xuda.io/connect/ab12 | sh
SSH verified · specs read AI-operable
Works with any provider:HetznerAWS EC2OVHLinodeOracle Clouda home lab
Any

Provider: Hetzner, AWS, OVH, your lab

1

Command to authorize · ~60s to connect

0

Passwords or private keys stored

Free

To connect: it's your server

Don't migrate. Adopt.

You already pay for the server. Now actually run it.

Most servers are managed from a terminal, one SSH session at a time, no dashboard, no monitoring, no easy way to point an AI at them. External VPS leaves your box exactly where it is, on the provider you already use, and gives it the Xuda control plane: one place to see it, manage it, and let AI agents operate it.

How connecting works

Three steps. About a minute. Zero secrets stored.

You stay in control of access the whole way. Xuda is added as an authorized key you can revoke any time, and we never see a password or a private key.

  1. 01

    Point Xuda at your server

    Give the host or IP, the SSH port, and the login user. That's all we need to find it, nothing sensitive.

  2. 02

    Authorize with one command

    Xuda hands you a single line that adds its public key to your authorized_keys. You run it; we never log in with a password or hold a private key.

  3. 03

    We verify and connect

    A quick SSH check confirms access, reads the server's specs, and your VPS appears in the dashboard, ready to manage and hand to AI.

What you get once it's connected

Your server, with a brain and a dashboard.

Everything you'd normally cobble together with scripts, cron jobs and a monitoring add-on: in one place, and operable by AI.

AI control over MCP

Point AI agents, codex or Claude Code at the box and have them operate it in plain language, the same agentic control as a Xuda-provisioned server.

Files & services

Browse, edit, search and tail files, watch disk usage, and start, stop and restart system services, from the dashboard or via AI.

Logs & monitoring

Stream application, request and security logs, and see live CPU, memory and disk usage on at-a-glance cards. Observability without an agent to install.

Domains, firewall & web URL

Open and close firewall ports, connect a custom domain with automatic DNS + SSL, and expose a public web URL at your-name.xuda.app.

Live server status

A real-time read of the machine, specs, health and resource usage, pulled over SSH and shown the moment it connects.

Team access

Invite teammates to the connected server with the same roles and sharing you use across the rest of your Xuda projects.

AI control, on your hardware

Point an agent at it. Talk to your server.

Once connected, your server's capabilities are exposed over Xuda's MCP layer. Your AI agents, or your own codex / Claude Code, can read and edit files, tail logs, manage services, open firewall ports and connect domains, in plain language. The same agentic control as a Xuda-provisioned box, on infrastructure you already own.

  • Files, logs, services, domains and firewall, all over MCP.
  • You choose what's exposed, least privilege by toggle.
  • Key-based access you can revoke from the dashboard in one click.
agent → my-hetzner-box (MCP)
agent> why is the app pod restarting?
→ vps_fs_tail /var/log/app.log … OOM at 02:14
agent> restart nginx and open port 443
→ vps_fs_service_action restart … ok
→ agent_firewall_open 443 … ok
agent> put it live on shop.mysite.com
→ agent_domain_connect … DNS + SSL ✓
agent>
Connected on your terms

A connection you can trust, and take back.

Adopting a server shouldn't mean handing over the keys. The whole flow is built so you never give up control of access.

No secrets stored

Key-based, scoped access

Revoke any time

External VPS vs the alternatives

Keep your server. Lose the busywork.

External VPS isn't a new box. It's a control plane for the one you have. Here's how connecting an existing server compares to running it by hand, or to spinning up a fresh Xuda Full Stack VPS.

External VPS You
Manage it by hand
Full Stack VPS
Use a server you already own
Works on any provider
Cost to connectFreeFreeFrom VPS pricing
One-command, key-based connect~
No passwords or keys stored~
One dashboard + live monitoring
AI control over an MCP server
Files, logs, domains, firewall, web URLmanual
Ships pre-loaded with the platform stack
Best forServers you already runTotal DIY controlA fresh, loaded box
Common questions

Answers before you have to ask.

Bring your own server. Keep your provider. Gain an AI.

Connect the VPS you already run in about a minute, no migration, no secrets stored, and manage it from one dashboard with AI agents that can operate the whole box. Revoke access any time.

It's your hardware. This just makes it smart.