Publish Express public assets
StaticX can host the public folder or generated frontend files from an Express project.
Framework hosting
Serve static assets generated by an Express project. StaticX is not a runtime for Express servers.
StaticX can host the public folder or generated frontend files from an Express project.
Express route handlers, sessions, middleware, and database logic need a runtime host outside StaticX.
When the public assets change, publish them as a StaticX version while backend services remain separately deployed.
Separate the browser-facing assets from the Express runtime and deploy only the static folder.
Use the Express static folder or generated frontend build that contains files safe for visitors.
Do not upload routes, middleware, private config, database code, or .env files.
Publish the public folder to StaticX and keep API URLs pointed at the real backend.
If you mean “run my Express server,” StaticX is not the right runtime. If you mean “host the public assets from my Express project,” StaticX is a clean fit.
This split is useful when a marketing site or documentation frontend is static but still talks to an API hosted elsewhere.
Upload files from express.static or a frontend build, not application internals.
Configure frontend API calls to reach the deployed Express backend.
Session handling, auth callbacks, and database writes remain server responsibilities.
Short, practical answers for using this page safely.
No. Express middleware needs a Node runtime. StaticX hosts static public files only.
Yes. Upload the browser-facing public folder if it contains the static site files visitors need.
Keep them on a backend host and have the static frontend call those URLs.
Yes for the static frontend hosted on StaticX. Backend API domains are managed separately.