Deploy static exports
StaticX hosts the out folder created by a static Next.js export workflow.
Framework hosting
Deploy static Next.js exports generated with output export or another static export workflow.
StaticX hosts the out folder created by a static Next.js export workflow.
SSR, middleware, ISR, server actions, and API routes are not part of a plain static export.
Each exported build can become a StaticX release with domain, analytics, forms, and rollback context.
Configure Next.js for static output, build/export the out folder, and publish those files to StaticX.
Use a Next.js configuration that writes static pages and assets into out.
Remove or replace server-only features before uploading the export.
Publish the contents of out with index.html and route files visible at the expected paths.
Next.js can produce a static website, but not every Next.js feature survives static export. Pages that need runtime rendering must use a server-capable platform.
When the project can export cleanly, StaticX is a durable hosting layer for the generated files, with version analytics and rollback around each release.
Configure image handling so exported pages reference files that exist in the output folder.
Pre-render dynamic paths or avoid routes that require runtime generation.
Move API behavior to an external backend before deploying the static export.
Short, practical answers for using this page safely.
No. StaticX hosts static exports. SSR, middleware, ISR, and API routes require a runtime host.
Upload the contents of the out folder produced by static export.
Yes. Custom domains apply to the StaticX site after the static export is published.
Yes, if they build/export, verify out, deploy the output root, and return the live URL or exact error.