GoDaddy Launches Node.js Hosting, and Publishes the Rules Apps Must Follow

GoDaddy has added Node.js application hosting to its Web Hosting plans. The company dates general availability to August 12, 2026 and announced it eight days later. Apps run on Node.js 22 as a persistent process rather than a serverless function, on plans the company says carry a flat price, with no per-request or per-gigabyte charge.

The detail that decides whether an application fits sits in a second document. GoDaddy publishes a deploy contract on GitHub under an MIT license, with a validator and numbered error codes, setting out in testable form the rules an application is expected to follow.

Key facts

• What it is: Node.js app hosting included with GoDaddy Web Hosting plans, running Node.js 22 as a persistent process.
• Ways in: a zip upload of up to 100 MB, a connected GitHub repository, a command line tool, a REST API, or an agent skill.
• Published app allowances: one on Economy, ten on Deluxe, twenty-five on Ultimate, with two preview apps on each.
• Network limit: outbound traffic is restricted to HTTP on port 80, HTTPS on port 443, and GoDaddy’s managed MySQL.
• Mail: transactional email goes through a loopback gateway inside the container. Outbound SMTP is not routable, so external SMTP relays and Nodemailer do not work.
• Included by default: automatic HTTPS, a CDN that GoDaddy says is powered by Cloudflare, a web application firewall, and a managed MySQL database per published app.
• Regions: North America or Europe, chosen before the first deploy.

A Persistent Process, Not a Serverless Function

Rather than leaving process lifetime to the platform, an application runs as a continuous process, the way it behaves under npm start on a developer’s own machine. GoDaddy contrasts this with Netlify’s handling of Express apps through serverless functions.

The practical difference shows up in three places: values held in memory between requests, background jobs on a timer, and long-lived connections such as WebSockets. GoDaddy says each of those behaves as written in a continuous process, and often breaks or needs redesigning where code starts fresh on every request. For a small application with session state or a scheduled task, that removes a class of serverless-specific rewriting.

GoDaddy’s documentation instructs applications that need files to survive between deployments to write them to a /public/assets/ folder.

The Deploy Contract Is Public, and Written as Testable Rules

GoDaddy publishes the platform’s requirements as a versioned contract in an open repository, alongside a validator that checks a project against the rules it covers and returns numbered codes. The repository carries an MIT license, and the contract was last changed on August 4, eight days before the stated general availability date.

The requirements are concrete. A project needs a root package.json with a non-empty name, version and main, and the file named in main has to exist. Both a build and a start script must be defined, and build has to be present even when nothing compiles, where the contract accepts a placeholder such as echo build. Frameworks including Next.js, Nuxt, Remix, Nest and Vite need a real build command instead.

The application must listen on the port supplied in process.env.PORT rather than a hardcoded number, and bind to 0.0.0.0 where the framework requires a host. Packages needed at runtime have to sit in dependencies rather than devDependencies, because the platform runs a production install that omits the latter. Uploads should carry a lockfile and leave out node_modules.

Two further rules constrain how a project is packaged. The contract allows only one application per upload, so a monorepo has to be reduced to a single app folder with its own root package.json. And the project needs an .npmrc at its root pointing at the public npm registry, with the contract advising that a lockfile containing non-public registry URLs be removed and regenerated first.

Outbound Traffic Is Limited to Two Ports and One Database

The contract states that outbound connections are limited to HTTP on port 80, HTTPS on port 443, and GoDaddy’s managed MySQL. Anything else, it says, is unreachable from the container.

That decides the database question before it is asked. An application cannot open a connection to a database hosted elsewhere on a conventional port, and the contract states that external databases on other ports are not reachable, with the troubleshooting table naming remote port 3306 specifically. Applications that use a database are expected to use the managed MySQL instance that comes with each published app, reading its host, port, name, user and password from environment variables and using the mysql2 client.

Mail follows the same pattern. Every container runs an email gateway on loopback at port 2525, and applications are expected to post to it through a helper GoDaddy supplies rather than speaking SMTP. The documentation states that outbound SMTP is not routable from the container, which rules out Nodemailer, a self-hosted relay and third-party SMTP endpoints. The gateway applies GoDaddy’s sender-identity policy and forwards to the configured SMTP relay.

A controlled egress path is a familiar constraint on managed application platforms, and by our reading the choice here is a conventional one. It does mean the fit has to be checked before migration rather than after, because an application that depends on a direct connection to an external database on its native port, or on its own SMTP relay, needs changing before it can run here.

What Each Plan Includes

Node.js Hosting is included with a Web Hosting plan purchase rather than sold separately. The allowance that varies is the number of published applications: one on Economy, ten on Deluxe and twenty-five on Ultimate, with two preview apps available on each. GoDaddy says a free preview tier is available without a plan or a credit card, and that preview apps are private, requiring a login to view.

Every deploy is scanned for malware and vulnerabilities before it goes live. Published apps run behind automatic HTTPS, a content delivery network that GoDaddy says is powered by Cloudflare, and a web application firewall, all configured by default. Encrypted environment variables are provided, and the managed MySQL database includes a table browser and SQL editor. The region, North America or Europe, is chosen before the first deploy.

The terms on the way out are set out as well. If a Web Hosting plan is suspended, published apps stop serving but nothing is deleted, and reactivating restores them. If the plan is fully canceled, apps are frozen for 30 days, after which the apps, secrets, databases and storage are permanently deleted.

Where GoDaddy Points Larger Workloads

GoDaddy’s documentation recommends VPS Hosting for anyone needing root-level server control or serving millions of requests, and Managed Hosting for WordPress rather than Node.js Hosting for WordPress sites. The plan descriptions point the same way, naming a first client site on Economy, multiple apps on Deluxe, and a portfolio of client apps on Ultimate.

For hosting providers watching the category, the notable part is not the feature list. It is that a GoDaddy Web Hosting plan now carries an application runtime, at what GoDaddy describes as a flat price, with the platform’s constraints written down and much of the packaging checkable before uploading anything.

About the Data

The launch details come from GoDaddy’s announcement and the platform requirements from its published deploy contract, both read directly rather than from coverage of them. The contract was read at the revision it carried on August 21, and its revision date comes from the repository’s commit history. The plan allowances come from the table in the announcement itself. The GoDaddy pages used here returned errors to automated requests, so they were read in a browser on the same date. Plan pricing varies by market, term and promotion, and is not compared here. We did not put questions to GoDaddy for this article.