Skip to content
Decision guide

Static site or VPS: start with whether the project needs runtime.

Static site deployment fits already-built HTML/CSS/JS output. VPS/CLI deployment fits projects that need persistent processes, APIs, workers, cron, database connections, or service-level recovery paths.

Static site deploymentVPS deploymentDeployment checklist

Checklist

Output folder

Is there a clear `dist/`, `out/`, or build output directory?

Server runtime

Does it depend on API routes, SSR, workers, cron, or a long-running process?

Secrets

Does it need database URLs, tokens, SSH keys, or provider credentials?

Health

Does it need health endpoints, process status, and logs?

Rollback

Does rollback need service state, not only replacing static files?

Static site boundary

Astro, Next.js static export, docs, landing pages, and content sites often fit static deployment. The key is that the output folder opens correctly, including deep links and asset paths.

VPS boundary

When a project needs a background process, port, Docker/Compose, database connection, or queue worker, do not pretend it is static. CLI/VPS paths preserve logs and recovery.

Hybrid projects

Many projects split cleanly: static frontend through static publishing, API/worker through VPS or self-hosted control plane. Internal links should send users to the matching deploy entrypoint.

Rollout steps

1

Check build output

If the output can be served directly by a static server, try the static site path first.

2

Check runtime

If server runtime is needed, use CLI/VPS or self-hosted deployment paths.

3

Check verification

Static checks cover deep links/assets; service checks cover health/logs/status/rollback.

FAQ

Which path for Next.js?

Static export can use static site deployment. Server runtime, API routes, or SSR should use service deployment.

Which path for Astro?

Default static output fits static sites. SSR adapters or server logic should use service deployment.

Is VPS deployment always more complex?

It is fuller, but it gives logs, health, process status, and rollback paths for projects that truly need runtime.

Related topics

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.