Skip to content

Websites

Sites built with AI and hosted here.

Open Websites
Checked against the dashboard on November 19, 2026

Websites is where you make and run your websites. You can have as many as you like. Each one has its own address, its own versions, its own traffic and its own hosting plan, so a small landing page can stay on Free while a shop sits on a larger plan.

There are two ways to make a site, and both end in the same place:

  • Build with AI. You say what you do. The AI plans the pages, writes the words, picks the pictures and builds them.
  • Upload your files. You bring a folder or one HTML page, and it goes live on its own address.

Every site gets a free address ending in .xuda.app with a secure connection, on every plan. On a paid plan you can also connect a domain of your own.

A site is one of two kinds, shown as two big cards when you build. A Simple website (Serverless, Fast and free) is static pages served from our network: about 2 minutes to build, nothing to run, any earlier version and Undo, and the chat button with your assistant; its products and CMS content are written into the pages, so a product change shows only after a rebuild. A Full stack website (on your workspace server, Live and powerful) is built and run on your Workspace VPS: product changes reach the site within seconds, CMS content is read live, it can have server code and a database, and a store also gets a sitemap, product data and share previews; it costs the Workspace VPS a month, keeps its last 5 versions, and has no chat button yet.

Make your first website

Press New website

Press New website. With no website yet the page already offers Build with AI and Upload files in the middle of the page.

Describe it, or upload it

In the start box say what you are building, in your own words. Or open Upload files and pick a folder or one HTML page. You can also add pictures as references, use a Drive folder of pictures, or start from a profile or a store in your account. Or ask for it in any AI chat, on Home too: the chat brings your words, your pictures and what you dropped on its box (Commerce for your store) here, with Before we build open.

Drop what the site should use

Drag a module from the side rail, or one of its items, onto the start box, and each one does its own thing to the site. A phone line puts its number on the site as a tap to call link. A contact group becomes an Our team section with its people. A ticket form adds a Submit a ticket button. A Public Assistant becomes the site's chat button: she answers it herself, and the site's visitors talk to her without signing in (the AI Assistants module, dropped whole, adds a chat button too). Commerce makes it an online store that sells your products. A CMS table lists its records, a booking page adds a Book now button, a mailbox receives the contact form. A site from the wall under the box is used as a reference picture. Under the box, each item says in a few words what it will do. Drop a whole module (Phone, Contacts, Tickets and others) and, after you send, a card asks which of its items the site uses; a module with nothing to pick yet offers to open it so you can set it up. Branding brings your logo, colour and words about the business. Profiles, Meet, Portal and Domains ask which profile the site is about, which video room its Talk to us button opens, which customer portal its My account link goes to on every page, and which domain it goes live on. With no ticket form yet, the Tickets card can make one for you from your words or open the form builder, and the CMS card can make a new table. A Drive folder dropped on the box gives the site its pictures, and its card asks whether they go through the pages or into a gallery.

Choose how it is built

Pressing send opens Before we build over the whole page, as question cards, one at a time: first a card for each whole module you dropped, then a card for every item you dropped, whatever it is, that asks how the site uses it (where the phone number shows, photo cards or a list for the team, a contact as the contact person, in Our team or in About, a button or a page for tickets and bookings, a grid, a list or a page each for CMS records, a picture as the main picture, in a gallery or as a style reference, how much of a reference site to take, and for anything else a section of its own, a link or background only), then how it runs (Serverless, or on your workspace server), the pictures and the plan. The row at the top shows where you are and holds Previous and Next. Picking an answer moves to the next card; Previous on the first card closes them with your words still in the box. Choose how to build, which images to use and the plan it goes live on. The AI suggests some of it from your words. What the site includes (a contact form, a chat button, a cart, CMS content) is not asked: it comes from your words and what you dropped. A site made from your store starts on Full stack, where its product, collection, search and cart pages read the store live; you can still pick Simple. A Full stack card also says what database the site gets. Nothing is billed here. On the last card, press Build it. A knowledge base can also become the site's content or a blog, a booking page an upcoming events page, a mailbox a contact form or an address in the header or the footer, and a store can show its products as a read-only catalog with no cart, a list or a slider. A profile can also become a department page of its own. A single Meet room or profile can be dropped on its own too, and a room can also get a Meet us page with a Join button. A single customer portal can be dropped too: besides its My account link, it can get a Private area button in the header, or a page for visitors who are not signed in with a Sign in button. The domain the site goes live on can also be shown in the header, in the footer or in the site's words. Drop a finished Cast piece, or Cast itself and pick one, and its card asks whether it plays in the content, in a video gallery, on a testimonials page or on a product page. A testimonial voiced by a sample actor is never put on a site. A profile dropped also brings its chat button: a visitor signs in and is put through to the profile's owner or one of its people, who answer in their Chats. The box's + menu lists the same modules under Add a module, each with a line on what it does; picking one is the same as dropping it.

Pick a look and build

The AI first shows its plan. Pick a look, say what to change, and press Build it. The pages are written one after another and appear in the preview as they are done, and a short list says where the build is. If you stop it, the pages it finished are kept and the box says which; Build it then reads Continue and builds only the pages still missing. A picture you attached as a reference is the look the AI follows: its layout, colours, type and spacing. For a Full stack site it goes on after the pages are written and tells you what the server is doing: installing and building, starting the site to check its pages, fixing what did not start. If the Workspace VPS was only just turned on, the build waits for it first. The draft is kept in Drafts, so you can leave and come back.

Change what you want

Say a change in the box, or point at a section of the preview and change only that part: rewrite it, give it a new picture, another layout, or take it out. Edit by hand is there too, and Undo puts back the last change.

Go live

Check the free address and the plan in the strip at the top, then press Go live. Until then only you can see the site. The plan is charged when the site goes live, and Free is never billed. A customer portal you picked in Before we build is linked at the same moment. If it could not be, the talk says so and where to link it.

Nothing is lost by leaving

A draft stays in Drafts with its talk. Leaving the builder before Go live asks first, and nothing is billed.

The jobs you will do most

Change a live website. Open the site and press Edit with AI. Say the change or point at a section. When you are happy, press Publish changes: the publish window says which version goes live and what it replaces. The version live now stays in History, so you can go back to it.

Put your own domain on it. Open the Addresses window. Connect one you already own, and the window shows the settings to add where it is managed and ticks each one when it is found. Or buy one on Xuda: it connects itself. Your own domain comes with every paid plan.

Go back to an earlier version. Open the History window and press Make live on the version you want. Visitors see it right away.

See who comes. The Traffic window shows how many requests the site had in the last 24 hours, 3 days or 7 days, where they came from and what is arriving now.

Share a website. Drag the site's card onto a person's face, in the top pane or wherever their face is shown. A menu asks how much they get: Read, Read and write, or Admin. The site is shared at the level you pick, and Undo in the message takes it back. Only your own sites drag, and a draft cannot be shared until it is a site.

Change the plan. Press the plan in the strip at the top of the site, or Change plan under the preview. The plan belongs to that one site.

What the Websites page tells you

The page shows every website of the workspace as a small browser window with the site itself in it. A live site has a padlock and a green Live chip. A site that is going live shows a loading line. A failed publish shows an error page with the first sentence of the cause, and a site never published shows a blank page with the date it was made. Drafts and sites being built stand in the same grid, with a Draft or Building chip.

A line at the top says how many websites you have, how many are live, and which one needs attention. Each card has one action that fits its state: Visit site for a live site, Edit with AI for one never published, Retry publish after a failure, or Change plan when the site is over its plan's storage.

From 13 websites the cards become a grid with search, filters by state and plan, and a bulk Move to another workspace.

What one website's page tells you

Press a card and you land on the site's Overview: three columns and the site itself under them.

  • Address says where visitors reach the site and how many addresses it has. It opens the Addresses window.
  • Version says which version is live and when it was published. It opens History.
  • Traffic says how many requests came in the last 24 hours, where most came from and the hours as a small chart. It opens Traffic.
  • Server appears for a Full stack website. It says whether the server runs and answers, and opens the Server window, where you can start, stop and restart it and read what it prints. For a website that sells from your store it also names the release of the store kit (@xuda/site) the site runs, which Xuda keeps current by itself, and Xuda opens the store's pages on the live site every half hour: a page that broke shows here as a red line naming it, before a buyer finds it.

A banner above the columns says when the last publish failed, when a version is waiting to be published, or that the site was never published.

The gear at the end of the row opens the site's settings: its name and free address, who can view it, and where it is filed, with moving, transferring and deleting. A chat button, a contact form or a customer portal is put on a site the way it was built: drag the Public Assistant, the mailbox or the portal onto an edit's box.

A site shared with you

When someone shares a website with you as an admin you can read its versions, addresses and traffic. Only its owner changes, publishes or deletes it, and a line at the top says so.

Where next

How is this guide?

Last updated on November 19, 2026