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

Apps

Every app, API and job is a deployment of a project. You choose the kind in the Deploy window; this page says what each kind is and what it needs. Each kind has a plain name on its card and, under it, a line with its technical name.

A card marked Not open yet or Early access is drawn grey and does not open a setup. Pressing it closes the window and opens a request to support for that feature.

Every kind that runs on a server has the same steps: where it runs (your datacenter and the server size), the name and the options we recommend, with the version as a small menu at the foot. What differs is the step after where it runs, the one thing only you can answer, and for some kinds a step of their own settings. That is what each section below is about.

On the web

Web app

One address that loads the project: a single page app. You can use the address as a link on your site or in a frame.

It needs: what opens first, one of the project's screens. It also asks: how it loads, under the server sizes in Where it runs, which defaults to loading in the browser.

Installable app

The project as a progressive web app: a web deployment that a browser can offer to install on a phone or a computer, like an app.

It needs: what opens first, a screen or a menu of screens. Its settings are in its own step, On the home screen: the short name shown on the home screen (it starts as the project's name), a description, how it is displayed (Full Screen, Standalone, Minimal ui or Browser) and a theme and background colour.

Inside your site

A code you paste into another page or site so the project shows inside it, instead of at an address of its own.

It needs: what opens first, the screen that should appear inside the embedded area.

Members area

An address with sign in: an app meant for a client, a team or a private rollout rather than the public.

It needs: what opens first, a screen or a menu. Its settings are in its own step, Access mode:

  • Access mode: Invite only (signups are off; only someone already invited can join), Approval (anyone can sign up, then waits for an admin to approve them in the Team tab) or Open (anyone who signs up joins at once). It starts on Invite only.
  • Sign-in methods: Password, Google and Email code (a six digit code sent to the address, valid for ten minutes), as pills. Password and Google start on, and at least one stays on. Once it is deployed, Send myself a test code on its Setup tab sends a real code to your own address so you can check the mail path.
  • Users: people to seed onto the deployment when it is created. Once it exists, manage members on its Team tab.
  • Interface behaviour, folded under the people: hide the Create button for members, make this deployment their dashboard, and how the sidebar starts for them.

A members area adds a Team tab to its page, besides Setup.

The project in a phone frame, as a link you can share, so a reviewer can try it before it goes live.

It needs: what opens first, one of the project's screens. Its settings are in its own step, In a phone frame: a row of device pills, and Light or Dark for the frame. It starts on an iPhone 12, dark.

Website with pages

A multi page app on its own address, opening on a menu of screens. It is drawn on the screen but not open yet.

On a phone and on a computer

An iPhone, Android, Mac, Windows or Linux app is a file built from the project's live web deployment: a Web app, an Installable app, a Website with pages or an Inside your site deployment that already exists. These kinds do not run on a server of yours, so they have no Where it runs step, no server and no datacenter, and the total is the kind's own fee alone.

None of them opens a setup yet: the iPhone, Mac, Windows and Linux apps are not open yet and the Android app is in early access. Pressing one of their cards closes the window and opens a request to support for that app. Make the web deployment first.

On a server

API

Addresses that other systems, websites or tools call, each running one of the project's API programs.

It needs: its routes, kept as a list in its second step, with the project's global variables under them. Add adds a route, and pressing its row opens its path, its name and the API program it runs, in place. A cross at the end of the row removes it. A colon in a path marks a parameter, so /users/:username matches /users/john. The build is the version menu at the foot.

Scheduled jobs

Programs that run on a timetable on the project's own server side.

It needs: its jobs, kept as a list in its second step. Each job is a row with its name and its schedule in words, with Edit and a cross to remove it. Add opens a short form in place: a name, a cron expression (for example 0 9 * * *, read back in words once it is typed), the batch program it runs, and that program's parameters. Add as many as you need; each runs on its own schedule. The job's Save stays off until the name, the expression and the program are set. The programs come from the version chosen at the foot.

Event triggers

Server logic that runs when your data changes: each trigger runs a batch program when a table changes.

It needs: its triggers, kept as a list in its second step. Each trigger is a row with its name and the program it runs, with Edit and a cross to remove it. Add opens a short form in place: a name, a batch program, and the program's parameters. The program must watch a fixed table on the Xuda database: the form names the table under the program, and when the program has no fixed table it warns instead and the trigger cannot be saved. Debounce (ms) folds rapid changes into one run.

Node server and MCP server

A Node server is your own server code, one of the project's JavaScript programs running on a server. An MCP server is the project's API as tools an AI client can call. Both are drawn on the screen but not open yet.

What each kind gets when it is live

The page of a deployment has tabs, and they depend on the kind.

  • Web app, Installable app, Inside your site, Preview link and API have the full set: Overview, Setup, Launch, Analytics, Usage, Resize, Domain, Backups, User Assist, Firewall, Power, Logs, Notifications and Advanced. A Web app has no Setup 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.
  • The phone and computer apps add Publish.

Where next

How is this guide?

Last updated on November 17, 2026