Applies to: Node.js Hosting

Node.js Hosting Help

What is Node.js Hosting?

Find answers to common questions about how Node.js Hosting works, what it costs and what your app needs to deploy.

If you require:

Select a question to see its answer:

How does Node.js Hosting work?

With Node.js Hosting, you can connect to GitHub or upload a zip file. You don't need to set up Docker containers or install CLI tools. This can help if you built your app with an AI coding assistant and want a simple way to publish it.

Back to top

What type of apps can I host on Node.js Hosting?

Node.js Hosting supports most Node.js apps, static websites and single-page apps, including apps built with AI coding assistants. Frameworks that work with Node.js Hosting include React, Vue, Next.js, Remix, Express, Fastify and Nest.

Back to top

How is Node.js Hosting different from other hosting services?

Many hosting services require you to use CLI tools, set environment variables, work with containers and manage complex configuration. With Node.js Hosting, you can upload your app with drag and drop or deploy it from Git. You can also test it in a free preview before you pay.

Back to top

How much does Node.js Hosting cost?

You can create a limited number of preview apps for free. Preview apps are removed automatically after 30 days. To publish an app, upgrade to Pro.

Back to top

Is Node.js Hosting secure?

Yes. We automatically scan every deployment for malware and vulnerabilities, and check it against security best practices.

Back to top

Can I migrate my app from another hosting provider?

Yes. Export your app files from your current provider and upload them to Node.js Hosting. Test your app in the free preview first, then upgrade to Pro when you're ready to publish.

Back to top

Can I connect my existing domain to Node.js Hosting?

Yes. After you upload your app, you can change its domain in Settings.

Back to top

What are the requirements for my app?

Important requirements for your app to be deployable include:

  • Package.json file: Must exist at the top level of your project, with non-empty name, version and main.
  • Build script: Always defined. If nothing needs compiling, use "build": "echo build". Frameworks need a real build command.
  • Start script: Always defined. If it runs node, that file must exist.
  • Listen on the assigned port: Read the port from process.env.PORT (3000 is a common port to use).
  • Runtime packages in dependencies: Anything needed during build or start must be in dependencies, not devDependencies.
  • Do not upload node_modules: Exclude node_modules from your zip or Git repo.

If you've checked the requirements and are experiencing issues deploying, install the NODE_JS agent skill from GitHub for more assistance.

Back to top

More info