Staticx
Sign in Create account

Build output guide

Deploy static framework builds with the right output folder

Framework-specific notes for build commands, output directories, routing fallbacks, environment values, forms, and rollback-ready deployments.

Deploy compiled browser files

StaticX hosts the output that browsers can load, not long-running application servers or private backend code.

Framework routing matters

SPAs, static exports, and generated content each need different fallback and asset-path checks before publishing.

Versions make framework changes reversible

Each build can become a deployment version, so UI changes, asset changes, and content updates stay measurable and rollback-ready.

Framework hosting pages

Choose the page that matches the exact workflow, file type, builder, or framework you are trying to ship.

Framework hosting React Hosting Deploy React apps after building them into static assets with Vite, Create React App, or another static build pipeline. Framework hosting Node.js Hosting Host static assets produced by Node.js tooling. StaticX does not run long-lived Node servers. Framework hosting Next.js Hosting Deploy static Next.js exports generated with output export or another static export workflow. Framework hosting Angular Hosting Publish Angular static builds with immutable deployments and custom domains. Framework hosting Vue Hosting Host Vue static builds from Vite or Vue CLI with version history and rollback. Framework hosting Express Hosting Serve static assets generated by an Express project. StaticX is not a runtime for Express servers. Framework hosting Astro Hosting Deploy Astro static output with forms, analytics, custom domains, and rollback. Framework hosting Bootstrap Hosting Publish Bootstrap HTML/CSS/JS sites directly from a folder or ZIP archive. Framework hosting Designmodo Hosting Upload static Designmodo exports and manage releases, domains, forms, and analytics in StaticX.

Questions about Framework hosting

Practical answers for choosing the right StaticX workflow.

Does StaticX run framework servers?

No. StaticX hosts static build outputs. Server-side rendering, API routes, and long-running runtimes need a separate backend host.

Which folder should I deploy?

Deploy the framework output root, usually dist, build, out, public, or another generated folder that contains index.html and assets.

Can framework forms use StaticX?

Yes when the rendered HTML form follows StaticX form rules or submits to a compatible endpoint.