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

Creating one

Putting an app, an API or a job live is one window. Every type you can deploy, and what a project runs on, is a picture card in one list. You pick a card, and its setup opens in the same window as a few numbered steps, with most of the answers already filled in. Then you press Deploy.

This page follows that window from the top. For what each type asks of you, see Apps. For servers, see Servers.

Open it

On a project, press Deploy. The Deploy window rises over the project. Its title is Deploy, with your project's name and its latest build beside it, and its round close is at the end of the header. Escape closes it too. If an order is part way set up, closing asks first, because what you set is lost. A press on the backdrop never closes it.

Pick what you are deploying

The window opens on one list of picture cards. There are no tabs. Over the list is a row of pills, one per group, each with how many cards it holds. A pill scrolls the list to its group, and scrolling the list moves the pill. The window opens on On the web.

Each card is a picture of the thing it puts live, drawn in dots, with its name and one line under it. For a type the line is its technical name, for example SPA, one address under Web app. For the infrastructure it is a short description.

On a wide window, the side of the window shows the card in focus: the card under the pointer or the keyboard, drawn large in dots, with its name spelled on a line of lit dots (the LED) and its line under it. It shows Web app until you point at a card.

Cards that are not open yet

Some cards carry a badge and are drawn grey: Not open yet on Website with pages, the Node server, the MCP server and the iPhone, Mac, Windows and Linux apps, and Early access on the Android app. The side says the same beside the LED. Pressing one of these cards closes the window and opens a request to support for that type, so you are told when it opens.

Event triggers are open, but while they are in beta the server can refuse them when you press Deploy, and the window says so.

On the Infrastructure cards, a card with an Upgrade badge opens the plans dialog first, and one with an Early access badge closes the window and opens a request to support.

A VPS and a Full Stack VPS are not in this window: they start from Create. A mini app deploys from its own builder.

The steps

Press a type, for example Web app. Its setup opens in the same window as numbered steps. The header has a round arrow that goes back to all types and lets go of the pick, the type's name with its technical line, and a pill that says where the order is: Not live yet, Going live, Live or Deploy failed.

A step's number turns green once it is answered. The side keeps the picture of the chosen type, and the LED under it now says where the order stands. The caption under it says where it runs.

Which steps you see depends on the type. In order:

Where it runs

For every type that runs on a server, the first step is where it runs, and it is already answered. Each of your project's datacenters that is ready is a card with its name and its region, and the first one is picked, with a tick. Press another to pick it.

The last card is Somewhere new, a new datacenter made together with this deployment. It opens the New datacenter window over this one, with the same three numbered steps a datacenter's own setup has and the map beside them: where it runs (the region on the cards or the map, the server type and size), how its data gets there (Start empty, One-time copy or Live replica), and its name. Your datacenters drops the new one and goes back to your own, and Done puts the window away. When the project has no datacenter yet, Somewhere new is the one picked.

Under the cards is the Server the deployment runs on: one pill per size, each with its monthly price, and a line with the chosen size's CPUs, memory and disk. It starts on the cheapest.

For a web app, an embed, a preview, a members area or an installable app, How it loads comes next, under Runtime mode, as four picture cards: Loads in the browser, Loads in the browser, with a worker, Loads from the server, and Loads from the server, then lives in the browser, each with what it is good at. Each picture, in dots, lights the side that does the work, and the card you pick plays how the page travels from the server to the browser. It starts on Loads in the browser and is included in the price.

What opens first, or its list

The next step is the one thing only you can answer:

For a screen or a menu, the project's own screens and menus are small cards with their names, read from the chosen version. Press one to choose it. If the project has exactly one, it is chosen for you. While they are read the step says Reading your screens.

More settings, under the cards, opens the rest in place: for a members area or an installable app whether it opens on a screen or a menu of screens, the screen as a list you can search with its parameters (or the menu), and the project's global variables. Press it again to fold it away.

For an API, scheduled jobs and event triggers, the list is kept right in this step. A line over it says what it is for, in the warning ink until there is one:

  • Routes: each route is a row that opens in place for its path, name and program, with a cross to remove it. Add adds an empty route. The project's global variables are under the list.
  • Jobs: each job is a row with its name and its schedule in words, with Edit and a cross. Add opens a short form in place: the name, the cron expression, the batch program it runs and its parameters, with Cancel and Save.
  • Triggers: each trigger is a row with its name and the program it runs, with Edit and a cross. Add opens a short form in place: the name, the batch program, the table it watches, its parameters and Debounce (ms), with Cancel and Save.

The type's own settings

Three types have a step of their own, answered in place:

  • A members area has Access mode: pills for Invite only, Approval or Open, pills for the sign in methods (Password, Google, Email code, and at least one stays on), the people to invite, and a fold with how the interface behaves. It starts on Invite only with Password and Google.
  • An installable app has On the home screen: its short name, how it is displayed (Full Screen, Standalone, Minimal ui or Browser), a description, and its theme and background colours. It starts with the project's name, in full screen.
  • A preview link has In a phone frame: a row of device pills, and Light or Dark for the frame. It starts on an iPhone 12, dark.

Name

Name is what the deployment is called. It starts as the type's name and the screen it opens, and follows them until you type your own. Scheduled jobs start as Cron Job. Beside it, for a type that runs on a server, a line says the deployment has Its own xuda.app address, and under it that your own domain connects once it is live.

We recommend these options

The last step holds the extras. Each is a pill with a plus and its price, and it turns to a check and joins the total when you press it:

  • Automatic backups, for every type that runs on a server, at a monthly price plus a price per gigabyte. If your plan does not include backups, pressing it opens the plans dialog first.
  • See what your users see, for a web app, an embed, a preview and a members area: a live view of who is on it.
  • Works offline, for everything but an API, scheduled jobs and event triggers. A warning appears under the pills if the server or the datacenter has fewer than two CPUs, which is not recommended for it.

The foot

At the start of the foot is the version that goes live, as Version and its number. It starts on your latest build. Press it to open a short menu of the project's builds, newest first with their dates. The newest carries a Latest badge and the chosen one a check. Choosing another build reads the screens again from it. With no build it reads Version in the warning ink.

At the end of the foot is Deploy, with the whole month beside the word: the type's fee, the server, a new datacenter if you chose one, and each extra you added. It moves as you change them.

Under the steps, one line says what matters most right now:

A refusal from the server, if the last press was refused, shows in a red box under the line.

Press Deploy

Deploy (Build for an app built as a file) is never greyed out for something missing. If a step is still open, the list scrolls to it and its title shows in the warning ink, or it opens the version menu or the window that step needs. An empty name gets the cursor. If your plan is too low it opens the plans dialog. Otherwise it sends the order and charges for it.

The progress

After the press, the steps fold away and the order is locked. The same window shows the job:

  • The clock counts the job's true time: seconds first, then minutes and seconds. Under it the step counter says which step the job is on, for example Step 2 of 5.
  • The server's steps tick over a line: Provisioning server, Enabling backups (only if you added backups), Connecting, Installing resources and Activating.
  • The picture on the side fills from the foot as the job goes.
  • The foot says Deploying on its button, and the line says you can close the window: it carries on, and you are told when it is live.

When it is live

The pill turns to Live, the picture is full, and the line says how long it took. The address stands large under the steps, and pressing it opens it in a new tab:

  • Copy puts the address on the clipboard.
  • Connect your domain closes the window and opens the new deployment's Domain tab.
  • The foot button, Open it, opens the address in a new tab.

Scheduled jobs and event triggers have no address, so the foot offers Go to and the deployment's name instead, which opens its own page.

When it fails

The word Failed replaces the clock, and the reason shows under the step that failed, in the server's own words. Two buttons are in the foot:

  • Back returns to the steps with every answer kept, so you can fix what was wrong.
  • Deploy again sends the same request once more.

Infrastructure in the same window

The Instance, Datacenter and Load Balancer cards open their own numbered steps in this window:

  • An Instance: what it runs on, then its name. The instance gets its own copy of the project's data and latest build, and each datacenter and deployment of the project you keep picked is copied onto new servers of the same size, under the instance and billed to you every month (Deploy shows the total). It needs the Agency plan. The new instance opens like a project, with its own deployments.
  • A Datacenter: where it runs (a region as one of five cards, then a server type and a size), how it gets its data, and its name.
  • A Load Balancer: two or more of your deployments of one type to stand in front of, where its own server runs, and its name.

For a datacenter and a load balancer the side shows the region map instead of a picture, and it follows the region you pick. The round arrow at the start of the header goes back to the cards, as it does for every type. Deploy carries the monthly total, and with a step still open it scrolls to that step. After the press the same window shows the job's steps and the clock. Servers says what each step asks.

Where next

How is this guide?

Last updated on November 19, 2026