Static hosting lets you serve frontend assets (HTML, CSS, JavaScript, images) directly from Xano alongside your backend APIs. This is useful for single-page applications, marketing sites, documentation, or any static content that pairs with your Xano backend.
The CLI manages static hosting through a build-based workflow: you create a static host, then upload versioned builds as zip files.
Static host commands require a workspace ID, either from your profile or via the -w flag. Static hosts are referenced by name, and builds are referenced by ID.
List Static Hosts
Each static host shows its name, ID, and domain (if configured). Use -o json for the full JSON response.
| Flag | Description |
|---|
-w | Workspace ID |
-o | Output format: summary (default) or json |
--page | Page number for pagination (default: 1) |
--per_page | Results per page (default: 50) |
Builds
Builds are versioned snapshots of your static assets, uploaded as zip files. Each static host can have multiple builds, letting you track deployment history and manage versions.
List Builds
Each build shows its name, ID, and status. Use -o json for full details.
| Flag | Description |
|---|
-w | Workspace ID |
-o | Output format: summary (default) or json |
--page | Page number for pagination (default: 1) |
--per_page | Results per page (default: 50) |
Get Build Details
| Flag | Description |
|---|
-w | Workspace ID |
-o | Output format: summary (default) or json |
Create a Build
Upload a zip file containing your static assets as a new build:
Add a description to keep track of what changed:
| Flag | Description |
|---|
-f, --file | Path to zip file to upload (required) |
-n, --name | Build name (required) |
-d, --description | Build description |
-w | Workspace ID |
-o | Output format: summary (default) or json |
Typical Workflow
A common pattern for deploying a frontend alongside your Xano backend:
Name your builds with version numbers or timestamps so you can easily identify them later when listing builds.
Xano