Static sites
Sites that build to plain files skip containers entirely — built once, served from the edge.
When a build produces a static output directory (Astro without an SSR adapter, Vite, CRA, Gatsby, plain HTML), Buildfyio publishes the files to the edge file server instead of building a container. Deploys are atomic — the new release swaps in as a single symlink flip — and rollbacks are instant.
What you get
- No cold starts, no instance costs — static sites don't consume compute.
- Atomic releases and instant rollbacks.
- Web analytics injected into every published page automatically — see Analytics.
- Custom domains and TLS exactly like container apps.
Build settings
Detection fills the build command (astro build, vite build, …) and the output directory (dist, build). Dependencies — including devDependencies, where build tooling usually lives — are installed before the build runs; workspace members install from the repository root.
Static vs SSR — decided by the build
@astrojs/node) builds a server and runs as a container automatically; the same repo with output: 'static' publishes to the edge. Nothing to configure.SPA routing
Client-side routed apps (React Router, Vue Router) serve index.html for unknown paths, so deep links resolve. Framework-generated 404 pages are respected when present.