Skip to content

Deployments

Put an app, a server or a site live, then run it.

Open Deployments
Checked against the dashboard on November 20, 2026

Servers

A server is a machine, or a group of them, that is yours to run. A VPS, a Full Stack VPS and an External VPS each have their own create screen. A datacenter and a load balancer are set up in numbered steps, in a project's Deploy window like an app. You reach them two ways:

  • From a project's Deploy window: Datacenter and Load Balancer are cards in its Infrastructure group, and open their numbered steps inside the window. A VPS and a Full Stack VPS are not in the Deploy window.
  • From the + that adds anything: VPS, Full Stack VPS, External VPS and Load Balancer.

Once created, a server is a row in the Assets rail, and its page opens with the tabs listed under each kind below.

VPS

A server of your own, in the region you pick. It is one screen: the dotted world runs behind it, and the order is a bill on the right. It opens ready, with your nearest region, the smallest size, an operating system and a name chosen, so Deploy is one press away and every choice is a change to something already filled.

Pick a region

Five regions are drawn as continents: North America, Latin America, Europe, Asia-Pacific and Africa. Press a card or the map. A region with no Xuda datacenter yet is greyed and says Coming soon. Xuda picks the datacenter inside the region. See the region choice.

Pick a size

The server line shows a type, Shared, Optimized, Performance or Large (as many as the region offers), and under it the sizes of that type, each with its memory and monthly price.

Pick an operating system

The operating system line lists the images you can start from. The name starts from the one you pick, and follows it until you type your own.

Add what we recommend

Each option is a plus that joins the bill:

  • Auto Diagnose, a daily read only health check of the server. It opens a window for the checks it runs. It is only offered where the daily sweep runs.
  • Dedicated public IP, a real IPv4 address for the server. It is off, and says why, when none is free for the size or region. Without it the server still gets a free domain and an IPv6 address.
  • Auto backups, at a monthly price plus a price per gigabyte. If your plan does not include backups it opens the plans dialog.

Press Deploy

The total is the true monthly price. Deploy stays off while a region is being read and until the region, size, operating system and name are all set. After the press the same screen is the progress: the map flies to the datacenter, the choices fold into the bill, and the clock and the steps open above it. The steps are Provisioning server, Enabling backups (only if you ordered backups), Connecting, Installing resources and Activating.

If it fails, Back returns to the order with every answer kept, and Deploy again sends the same request once more. When it is live, Go to and the server's name opens its page.

Its tabs: Overview, Power, Resize, Domain, Files, Backups, Firewall, Logs, Team and Advanced.

Full Stack VPS

A server that comes with the Xuda tools an app needs: its own key, a project database, and a choice of which groups of Xuda tools that key may reach. Use it when you want to build on the box itself, or hand the whole box to an AI agent.

It is made in three steps, with a rail of steps on the start side and a footer with Previous, Next and the price.

Power

Where it runs and how strong it is: a region, then a server type and a size. There is no operating system to choose: the box's toolchain runs on the one the server sets.

Tools

Which groups of Xuda tools the box's one key can reach: Server files, Databases, Drive, Plugins, AI workspace, Build & releases, Logs, AI agents, Contacts, Email, Deploy & hosting, Platform info and MCP server. They are all on to start. Select all and Clear turn them all on or off. They are fixed when the box is created. At least one group besides MCP server must stay on, and the screen says Pick at least one group until one does.

Finalize Details

An option to enable automatic backups, and the box's name. Then Create Full Stack VPS.

After the press the progress is the deploy globe: a turning globe that drops onto the region the server lands in, and a summary card with its steps.

Its tabs: Overview, Data, Power, Resize, Domain, Files, Tools, Plugins, API keys, Backups, Firewall, Logs, Team and Advanced.

External VPS

A server you already own, on any provider, connected to Xuda over SSH. It costs nothing: the screen's price says Free. No password or private key is stored: you authorize Xuda with a one line command.

Enter the server's details

The host or IP, the SSH port (it starts on 22), the login user (it starts on root) and a name. The map finds the server as you type its address. Connect stays off until all of them are set.

Run the command

Connect hands over one command, in a terminal frame, on the stage. Copy it and run it on your server. We check on our own once it has been copied, and Check now checks at once. The pane keeps the time and three steps: Server details, Run the command and Connected.

Connected

Once the server answers, we read its hostname, CPU, memory and disk and show them, and Go to the server's name opens its page. If a check does not get in, Check again tries once more. Nothing exists in Xuda until the server has answered, so Cancel simply goes back to the details as you typed them.

The pane also has a Logs manager switch, off by default, which is sent with the connect.

Its tabs: Overview, Logs, Files, Team and Advanced.

Datacenter

Where your deployments run and where their data lives. A datacenter is the storage backbone of a project: it hosts its data and syncs it across regions.

In the Deploy window, the Datacenter card opens three numbered steps in the same window. A step's number turns green once it is answered.

Where it runs

The region, as five cards with each continent's outline. One is picked for you from where you are, and on a wide window the map on the side follows it. A region with no Xuda datacenter yet is greyed and says Coming soon. Under the regions are the server type, as pills when there is more than one, and the sizes of that type, each with its memory and its monthly price. The smallest is picked for you.

How should this datacenter get its data?

How the datacenter gets its data, as three cards. Pick the mode; everything under it fine tunes it and never changes the pick. Start empty is picked for you.

  • Start empty: no data is copied. You populate it yourself.
  • One-time copy: copied across once, now. Later changes will not follow.
  • Live replica: kept in sync continuously, and survives a region going down. It needs an Enterprise plan.

For a copy or a live replica you then say where the data comes from, the main app or another of your datacenters, and which tables: all of them, only those marked as setup tables, or a list you pick. For a live link between two datacenters you choose one way or two way. An optional Sync Filter keeps only the documents that match a selector.

Name

The datacenter's name. It starts as Datacenter and the region, and follows the region until you type your own.

Deploy, at the foot, carries the whole month's price. With a step still open it creates nothing and scrolls to that step. Otherwise it creates the datacenter, and the same window shows the job's steps and a clock. The round arrow at the start of the header goes back to the cards.

A datacenter can also be made while you deploy an app: in the Deploy window, Where it runs has Somewhere new.

Its tabs: Overview, Usage, Analytics, Data, Drive, Backups, User Assist, Resize, Power, Replication, Notifications, Firewall, Logs and Advanced.

Load balancer

One address in front of several deployments of the same kind. It spreads traffic across them and supports failover. It runs on a Xuda farm server, so it reaches its backends over Xuda's private network.

In the Deploy window, the Load Balancer card opens three numbered steps in the same window. From the +, the same three steps open on a page of their own.

Select backends

Your deployments, read when the step opens and listed under their type's heading. Each is a card with its name, its region code and its address. Press a card to tick it, and again to untick it. Pick at least two, all of one type: ticking one of another type starts the pick again with that one. Web apps, installable apps, apps inside your site, members areas, preview links, APIs, VPS and Full Stack VPS are listed. Scheduled jobs and event triggers are not, since they have no address to balance. If there are none it says to deploy at least one first.

Where it runs

The region of the balancer's own server, as five cards, with the map on the side on a wide window. Then its server type and size. The smallest is picked for you.

Name

The balancer's name.

Deploy, at the foot, carries the whole month's price. With a step still open it creates nothing and scrolls to that step. Otherwise it creates the load balancer, and the same window shows the job's steps and a clock. The round arrow at the start of the header goes back to the cards.

Its tabs: Overview, Backends, Usage and Advanced.

The steps frame

A Full Stack VPS is made in the steps frame. On a wide screen a rail of numbered steps stands on the start side, the step's content is in the middle, and the footer has Previous, Next and, on the last step, the price and Create. Each step on the rail turns green with a tick once its answers are complete. On a phone the rail becomes a bar of numbered steps at the foot. If something is missing when you press Create, the screen says what in a band over the footer and takes you to the first step that is not complete. See the steps frame.

Where next

How is this guide?

Last updated on November 18, 2026