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

Development Platform

The Development Platform is the visual application builder and the machinery behind it. You author an application as visual programs, a checker validates them, a build freezes them into a numbered release, and a deployment runs that release. Everything happens inside a project, a real, isolated database of its own, not a row in a shared table.

From an empty account to a running app

Create a project

Open Create > Project, leave "Choose a boilerplate" empty to start blank or pick one to clone it, name the project and press Create. Xuda provisions a dedicated database, pins it to a region, installs the default plugins and creates the project's Drive folders.

Author it in Studio

Press Studio in the project header. The tree switches between five roots: Programs, Tables, Globals, Routes and AI Agents. Every save is immediate and synced live, there is no separate "save the app" step.

Check and build

From the Create-a-build dialog, press Check Programs to walk the project for errors and warnings, then Create build: pick major, minor or patch and press Build. A build is an immutable, numbered snapshot; nothing in Studio afterward changes a build that already exists.

Deploy it

Press Deploy in the project header and pick a target. A deployment tracks a build, not your live Studio tree, so you can keep working in Studio all day without touching what is published.

Building and deploying are separate acts

Build as often as you like without publishing anything. Nothing your users see changes until a deployment is created or updated to a new build.

Open the project to your own code

A developer API key

On the project's API tab, create a key with Full access, every method your account can call, or Custom access, an explicit allowlist. Scope it to one project there, or to the whole account from /dashboard/developers.

The same key over MCP

An MCP session built from an API key registers every method that key can call as a tool, with the tool's input schema derived straight from the method's own declared fields.

The Studio authoring API

Methods to list, fetch, create, save, delete and validate a project's Studio documents directly, the same node factory Studio itself uses, so a node created this way is identical to one made by hand. Validate a candidate document before you save it; saves carry the revision you fetched and are rejected as a conflict rather than silently merged.

Plans

Authoring, checking and building are on every plan, Free included, and neither the checker nor a build spends AI credits. Publishing needs Pro: a single-page app, a multi-page app, an embed, a PWA, an API, a cron job or a user group. An instance or a marketplace listing needs Agency. A mini app deploy is available on Free.

Over the API

How is this guide?

Last updated on November 15, 2026