A production web process
Use a production start command, listen on 0.0.0.0 and read the assigned port from the environment. Express, Fastify, NestJS and other HTTP frameworks fit the same runtime contract.
Deploy and host a Node.js app with your coding agent
Put an existing Express, Fastify, NestJS or other Node.js HTTP app online from Claude Code, Cursor or Codex. Use GitHub or push directly to aidrop Git.
THE DEPLOYMENT CONTRACT
What the app needs in production
Your coding agent can inspect and change the repository. aidrop builds the committed revision and runs it when these requirements are explicit.
Durable data outside the container
Add managed PostgreSQL on Pro and above. Keep credentials in Project values and read them on the server; never ship private keys in browser code.
RUNTIME CHECKLIST
Make the build predictable
The exact framework matters less than a clear production contract. These are the details your agent should verify before the first build.
Installnpm ci (or the matching locked package-manager command)
Buildnpm run build, when the application has a compile step
Startnpm start or another non-development production command
NetworkListen on 0.0.0.0 and the PORT provided at runtime
HealthReturn a successful response from a lightweight HTTP route
import express from "express";
const app = express();
const port = Number(process.env.PORT || 3000);
app.get("/health", (_req, res) => res.json({ status: "ok" }));
app.listen(port, "0.0.0.0");FIRST-BUILD BLOCKERS
What usually needs fixing
Your agent can resolve these in the repository before it hands back a public address.
A development server starts
Replace vite dev, nodemon or a watch task with the production web process.
The app ignores PORT
Read the assigned PORT at runtime and bind the process to 0.0.0.0.
The lockfile and package manager disagree
Commit the correct lockfile and use its matching install command.
Files are treated as durable storage
Keep durable uploads and application data outside the disposable app container.
FROM GIT TO HTTPS
One deployment path your next session can repeat
Connect GitHub or use aidrop Git. Every build keeps the revision and log with the Project, while a successful deployment keeps the same public address for the next change.
Deployment checklist
- Pinned dependencies and production command
- Environment values kept outside Git
- Health endpoint answers on the assigned port
- Public HTTPS address after a successful build
ASK YOUR CODING AGENT
Start with a concrete deployment request
Deploy this Node.js app on aidrop. Check its production start command, listening host and PORT, environment values and health endpoint. Use its existing Dockerfile if it is production-ready; otherwise configure a source build. Resolve any build blocker before reporting the public address.
Connect Claude Code, Cursor or CodexWhich Node.js frameworks can I deploy on aidrop?
Any Node.js framework that can run as an HTTP process under the deployment contract can fit, including Express, Fastify and NestJS. The repository needs a reproducible install, an optional build step and a production start command.
Can aidrop deploy my existing Node.js Dockerfile?
Yes. Your coding agent can deploy an existing production-ready Dockerfile with an explicit build context. The container still needs to listen on 0.0.0.0 and the assigned port, and durable data must live outside the container.
How are Node.js environment variables handled?
Keep non-secret configuration and secret values in the aidrop Project instead of committing them to Git. Your app reads them from its runtime environment. The next agent session can see value names, not their secret contents.
Can the Node.js app use PostgreSQL?
Yes. Managed PostgreSQL is available on Pro and above. The database connection belongs to the Project, while credentials stay outside the repository.
Host your Node.js app
Start with a seven-day trial and deploy from the coding agent you already use.
7 days free · No credit card required