Deployments
Put an app, a server or a site live, then run it.
A deployment is something of yours that is live: an app people open, an API other software calls, a job that runs on a schedule, a server. Xuda has no separate "Deployments" list. Each thing you put live becomes a row in the Assets rail, and opening that row opens its own page, with a tab for everything you can do to it.
So this area has two halves: getting something live, and the tabs you then run it from.
What you can put live
In the Deploy window a project becomes one of these. Each is a deployment of the same project, so one project can be live in several ways at once. The window draws every kind as a card with a picture of the thing it puts live, in groups you reach with a row of pills.
Some kinds are drawn but not open yet: Website with pages (MPA), the iPhone, Mac, Windows and Linux apps, the Node server and the MCP server, and the Android app is in early access. Their cards are drawn grey with a badge. Pressing one closes the window and opens a request to support for it. Apps says what each kind needs.
A machine, or a group of them, that is yours to run. Each has its own create screen.
Datacenter and Load balancer (and Instance) are also cards in the Infrastructure group of the Deploy window, and are set up in numbered steps inside it. A VPS and a Full Stack VPS start from Create. Servers says what each one needs.
Websites, Domains and Mini Apps are modules of their own: see Modules. XU Code is a kind of project you create, and has its own pages under Developers.
Getting an app or an API live
Everything starts from the project. The order is one window: every kind as a picture card, and the kind you pick opens its setup as a few numbered steps in the same window, most of them already answered.
Open the Deploy window
On a project, press Deploy. A window opens over the project, on one list of picture cards. A row of pills over it, On the web, On a server, Infrastructure, On a phone and On a computer, scrolls the list to each group.
Pick what you are deploying
Press a card, for example Web app. On a wide window, the side draws the card you point at in dots, with its name on a line of lit dots. A press opens the kind's steps, with your datacenter, the smallest server, your latest build and a name already filled in.
Check where it runs
The first step is where it runs: your datacenter, picked for you, or Somewhere new, a new datacenter made with this deployment. Under it are the server sizes and, for a web kind, how it loads.
Answer what only you can
Then comes what opens first, one of the project's screens as cards, or the routes, jobs or triggers of the kind you picked, kept as a list in the step. If the project has exactly one screen it is picked for you. A members area, an installable app and a preview link add a step of their own settings, then every kind has its name and the options we recommend, each a pill that adds to the total.
Press Deploy
The version is a small menu at the foot, and Deploy carries the true monthly price. One line under the steps says what would stop you: what is still left to answer, that your plan is too low, or which card will be charged. Deploy is never greyed out for something missing: pressing it takes you to the step that still needs an answer.
Watch it go live
The same window now shows the server's steps and the clock, and the picture on the side fills as the job goes. When it is live the address stands under the steps, with Copy and Connect your domain, and Open it in the foot. Scheduled jobs and event triggers have no address, so the foot has a button to the new deployment's own page instead.
If the deployment fails, the reason shows under the step that failed. Back returns to the steps with every answer kept, and Deploy again sends the same request once more. Creating one walks the whole window.
Where it then lives
Open its row in the Assets rail. The page has tabs, and they depend on the kind. These are the ones an app deployment can have, in order:
Not every kind has every tab. Scheduled jobs and event triggers have no Launch, Domain, Firewall, Analytics or User Assist tab, since nothing visits them. A members area adds Team. An installable build adds Publish.
A server has its own set. A VPS has Overview, Power, Resize, Domain, Files, Backups, Firewall, Logs, Team and Advanced. A Full Stack VPS adds Data, Tools, Plugins and API keys. A datacenter adds Replication. A load balancer has Overview, Backends, Usage and Advanced. An External VPS has Overview, Logs, Files, Team and Advanced.