Build boundary
Static export only fits pages that do not depend on the Next.js server runtime. API routes, SSR, and dynamic server logic need normal deployment.
Next.js static
Publish a static exported Next.js site.
If your Next.js project can be statically exported, Appaloft can publish the `out` directory as a static site. Projects that need server components, API routes, or a long-running Node process should use the normal CLI/VPS deployment path.
Best for landing pages, docs, exportable apps, and frontend-only pages
Build output must include index.html and static assets
Next.js projects that need a server runtime should not be treated as static sites
Publish path
Small sites can use Cloud static upload; projects with an existing server can deploy the out directory with the CLI.
Verification checklist
Check the homepage, deep links, images, CSS/JS, base path, and 404 handling.
Deployment flow
1
Export static site
Run the project's Next.js build/export flow to produce the out directory.
2
Publish out
Choose the out folder in Appaloft, or deploy the same directory with the CLI.
3
Open URL
Verify routes, static assets, and error pages.
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.
Static site publishing
Connect build output, browser upload, CLI deploy, and one-click buttons for static site publishing.
Own server deployment
Tie the control plane, CLI, servers, rollback, and Cloud collaboration boundary into one self-hosting cluster.
AI deployment
Let the agent identify project shape first, then choose the skill, CLI, static publishing, or Cloud console path.
GitHub deployment
Use GitHub Actions to connect repository events to Appaloft deployment while keeping explicit workflows.