Static site

Publish static websites without standing up a whole server first.

Appaloft can publish build output from Vite, Astro, Next export, documentation sites, or plain HTML as a reachable URL. Start with Cloud browser upload, or use the CLI and self-hosted control plane when the site belongs on your own server.

Entrypoint

Browser upload / CLI

Best for

Static sites and frontend build output

Required file

index.html

Checks

routes, assets, secrets

Outcome

Reachable URL

Static artifact example

npm run build
# Output is usually dist/, out/, or build/
# Cloud: choose static files in Appaloft and publish
# CLI: appaloft deploy ./dist --config appaloft.yml

Open console View CLI path

Aligned with

Cloud static artifact upload strategy, website quick upload copy, and public Appaloft static resource deployment path.

Works for dist, out, build, public, and similar static output folders

Cloud upload checks files, publishes a URL, and leaves a replacement path

Self-hosted deployment still runs on infrastructure you control

Confirm index.html, routes, and assets before publishing

Best fit

Landing pages, docs sites, frontend SPAs, exported Next/Astro/Vite projects, and static asset bundles that do not need a long-running backend process.

Cloud quick upload

Choose static files from the website or console. Appaloft reads the files, creates a static resource, uploads the artifact, and publishes a URL after validation.

CLI and self-hosting

If you already have your own server, the CLI can read the static output folder and use the regular Appaloft resource deployment path. Cloud does not replace the public Appaloft deployment model.

Pre-publish checks

Run the build first, confirm the entry file exists, check asset paths, and keep .env files, private keys, tokens, database dumps, and local caches out of the static folder.

Deployment flow

Build

Run the project's build or export command to produce dist, out, or an equivalent static directory.

Choose path

Small sites can start with Cloud upload; projects with an existing server can use the CLI or self-hosted control plane.

Verify URL

Open the published URL and check the homepage, deep links, images, CSS/JS, and error page.

Keep following the same deploy path.

Appaloft SEO pages are organized around real deployment tasks. Each page should lead to the next useful step, not stand alone.

Static site publishing

Connect build output, browser upload, CLI deploy, and one-click buttons for static site publishing.

Blueprint marketplace

Official Blueprints help users choose app templates, then hand deployment back to Cloud and related entrypoints.

AI deployment

Let the agent identify project shape first, then choose the skill, CLI, static publishing, or Cloud console path.

Own server deployment

Tie the control plane, CLI, servers, rollback, and Cloud collaboration boundary into one self-hosting cluster.