Node.js hosting
on Shipped.
Take your JavaScript or TypeScript server online. Shipped runs the service and connects the resources around it, so you can keep building the product.
Keep your application entry point
Deploy a Node.js web service with the production start command your project uses. That can be an API framework, a full-stack application, or a custom HTTP server. Shipped starts the service and provides its public URL, while your application remains responsible for its routes and responses.
Separate requests from longer work
A request handler should not have to wait for a large import or a batch of email to finish. Run a separate Node.js worker for queued work and use scheduled jobs for recurring tasks. Both can connect to the same app services without sharing the web process lifecycle.
Keep runtime configuration out of source
Supply database connections and integration credentials as secrets. Use different values in staging and production, and inspect build and service logs when something goes wrong. Your agent can deploy local source through MCP, or GitHub can remain the starting point for your release workflow.
A little more detail
Questions about Node.js?
Can Shipped run a TypeScript Node.js project?
Yes. Keep the TypeScript build or execution setup your project requires in its deployment configuration. The production command should start the application using the runtime and output you have tested.
Should my Node.js worker run inside the web service?
A separate worker is useful when jobs need their own capacity or must continue independently of incoming requests. Keep job state in a durable queue or database rather than only in the web process memory.
From your workspace to the web