NODE.JS HOSTING

If your app needs a continuously running server process (Express API, WebSocket connections, background jobs), you need a platform that runs Node.js: Render, Railway, Fly.io, or a VPS like DigitalOcean. If your Node.js project is a frontend that compiles to static files (React, Vue, Astro), you don't need a server at all. Build locally, upload the output to Static.app, and the CDN serves your files globally without any server management.

Any framework whose build step produces static HTML, CSS, and JavaScript files. This includes frontend frameworks built with Node.js tools: React (Vite or CRA), Vue, Angular, Svelte, Next.js (static export mode), Nuxt (generate mode), Astro, Gatsby, Eleventy, Hugo with Node.js tooling, Hexo, and Docusaurus. If running npm run build creates an output folder with an index.html file, the result works on Static.app.

Any tool that outputs static files: Vite, webpack, Parcel, esbuild, Rollup, Turbopack. If it creates an output folder with HTML, CSS, and JS, it works on Static.app.

Static.app hosts the compiled output of Node.js projects (HTML, CSS, JS files). If your app needs a continuously running server process (WebSockets, database connections), you'll need that server hosted separately.

No, and you should never include node_modules in your upload. This folder contains your project's development dependencies and can be hundreds of megabytes. Upload only the build output folder (dist/, build/, or out/) which contains the compiled, minified files that browsers actually need. A typical build output is 2-10MB compared to node_modules which can be 500MB+.

Set them locally before running the build command. Build tools bake them into the output. There's no server-side runtime on Static.app, so env vars must be compile-time.

SSR needs a running Node.js process to render HTML on each request. Static.app serves pre-built files without a server runtime, so traditional SSR doesn't work here. The alternative is Static Website Generation (SSG), where HTML is rendered once at build time and the output is static files. Next.js (output: 'export'), Nuxt (nuxt generate), and Astro all support SSG. The result is the same fast HTML, just pre-built instead of rendered per request.

Host the frontend on Static.app and the backend API on a separate service (Render, Railway, Fly.io). This separation is actually a best practice for performance and reliability.

Yes, and this is actually one of the best use cases. Tools like TypeDoc, JSDoc, Swagger UI, Redoc, and Docusaurus generate complete HTML documentation sites from your code or API specs. Run the generation command, ZIP the output, and upload. The documentation loads fast from the CDN, and you can password-protect it for internal team access or publish it publicly for your API consumers.

Some shared hosting providers support Node.js through cPanel, but the setup involves SSH access, configuring the Node.js application manager, setting up a reverse proxy, and managing process restarts. It's complex and often unreliable on shared hosting. If your Node.js project produces static output, Static.app replaces all of that: ZIP your build folder, upload, and the website is live in seconds. No terminal access, no cPanel, no configuration files.

Static.app offers a free trial so you can test the full workflow before committing. Paid plans start at $5/monthnth with 500MB storage and unlimited traffic. For context, alternatives like Heroku start at $7/month for always-on dynos, Render charges $7/month per service, and Railway uses usage-based billing that can vary. If your Node.js project compiles to static files, Static.app is typically the cheapest always-on option.

Heroku runs your Node.js server process. Static.app serves your build output as static files. Heroku is for server-side apps. Static.app is for frontend output. Static.app is simpler and cheaper for static content.