One-Click Publishing

Click Publish in the toolbar to deploy your project live. Your site is available at yourname.xaeio.app with automatic HTTPS.

How Publishing Works

Website projects:

1. Dependencies are installed (npm install)

2. Production build is created (Vite)

3. Static files are uploaded to a global CDN

4. Site is live within seconds

Web App projects:

1. Frontend is built and deployed to CDN

2. Backend is packaged and deployed as a managed service

3. Database migrations run automatically (if PostgreSQL is enabled)

4. API is available at yourname.xaeio.app/api/

Choosing a Subdomain

On first publish, choose your subdomain. It stays the same for all future updates. Subdomains must be unique across all XAEIO users.

Updating Your Site

Click Publish again after making changes. Only changed files are updated — the process takes just a few seconds. The previous version is replaced immediately.

XAEIO Cloud vs XAEIO Private

XAEIO Cloud — Managed hosting on *.xaeio.app (default)
XAEIO Private — Self-hosted option for teams that need to run on their own infrastructure

SEO & Performance

The AI generates proper HTML structure for search engines:

Semantic HTML tags (header, main, footer, nav)
Meta tags and Open Graph tags
Responsive images with lazy loading
Fast loading with code splitting and CDN delivery

Build Errors

If the build fails during publish, XAEIO automatically attempts to fix the error using AI (up to 2 retries). If it still fails, you see the error message and can ask the AI to fix it in the chat.

Publish progress

A publish shows one progress bar from 0 to 100 %. Each step — endpoint check, code analysis, dependency scan, tests, build and deploy, upload, verification — owns a fixed band of the bar, and inside long steps the value keeps moving (scanner progress plus time-based interpolation). The bar never jumps backwards, not even when the analysis hands over to the deploy.

During the pre-publish code analysis the percentage rises live instead of sitting at "0 % analyzing code" until the scanners finish.

Taking a site offline

Unpublish removes the published site: its files are deleted from storage and the CDN cache is invalidated, so the subdomain stops serving.

The project itself is untouched — sources, database and history stay where they are, and you can publish again later.