1-Click apps Deploy your code Pricing Guides Docs Support Log in Deploy an app

Deploy a Node.js App Without Docker in 2026

You don't need Docker, Kubernetes, or a Dockerfile to deploy a Node.js app. Push your code, get a live URL with SSL. Here's how to deploy Node.js without containers.

Apr 21, 2026 6 min readTutorial

On this page
  1. Why Developers Default to Docker (And Why They Shouldn’t Always)
  2. Method 1: Git Push Deploy (Zero Config)
  3. Method 2: Vercel / Netlify (Serverless)
  4. Method 3: Railway / Render (Managed PaaS)
  5. Method 4: Raw VPS with PM2 (Full Control, No Docker)
  6. Comparison Table
  7. When You Actually Need Docker
  8. Getting Started

Every Node.js deploy guide in 2026 starts the same way: write a Dockerfile, configure docker-compose, set up a multi-stage build, push to a registry, pull on the server, configure networking…

For a simple Express or Fastify app? That’s 30 minutes of infrastructure work for an app that took 5 minutes to build.

You don’t need Docker to deploy Node.js. Here are the alternatives - from zero-config to full control.

Why Developers Default to Docker (And Why They Shouldn’t Always)

Docker solves real problems: reproducible environments, dependency isolation, consistent deploys across machines. For production microservices at scale, Docker makes sense.

But most Node.js apps aren’t production microservices. They’re:

  • Side projects
  • MVPs and prototypes
  • Internal tools
  • API backends for a frontend
  • Bots and automation scripts

For these, Docker adds complexity without proportional benefit. You’re maintaining a Dockerfile, dealing with image sizes, debugging container networking, and managing a registry - all for an app that runs fine with node index.js.

Method 1: Git Push Deploy (Zero Config)

The simplest path. Push your code, get a live URL. Git push deploy means exactly that: the branch you push is the deploy trigger, and there is no pipeline to configure first.

# Install the CLI
curl -fsSL https://instapods.com/install.sh | sh

# Deploy from your project directory
instapods deploy my-app --preset nodejs

That’s it. No Dockerfile. No build configuration. The platform detects your package.json, installs dependencies, starts your app, and gives you a live URL with SSL.

What happens behind the scenes:

  1. Your code is uploaded to a real Linux server with Node.js 22 pre-installed
  2. npm install runs your dependencies
  3. Your app starts on the configured port (default: 3000)
  4. Nginx is configured as a reverse proxy with SSL
  5. A domain is assigned: my-app.fr-1.instapods.app

Subsequent deploys update the code and restart:

instapods deploy my-app

Cost: $3/mo (Launch plan) or $7/mo (Build plan for more resources) Setup time: Under 60 seconds You manage: Nothing SSH access: Yes - ssh instapod@my-app.fr-1.instapods.app

The SSH access is to a whole Linux server, which is the key difference from platforms like Vercel (no shell at all) or Railway (a shell inside one service). If something goes wrong, you can SSH in, check logs, inspect processes, install a package that stays installed, and debug in real time.

Method 2: Vercel / Netlify (Serverless)

For frontend-heavy Node.js apps (Next.js, Nuxt, SvelteKit), serverless platforms deploy without Docker:

# Vercel
npx vercel

# Netlify
npx netlify deploy --prod

Pricing is close to identical at the paid tier - see Vercel vs Netlify for where the $20/mo actually differs.

The catch: These platforms run your Node.js code as serverless functions, not as a persistent process. That means:

  • No WebSocket support (or limited)
  • No persistent filesystem (SQLite won’t work)
  • Cold starts on infrequent requests
  • No background jobs or cron
  • No SSH access
  • Usage-based billing that can spike

If your app is a Next.js frontend with API routes, Vercel works great. If your app is an Express API with SQLite, a WebSocket server, or long-running background processes, serverless won’t work.

Cost: Free tier available. Pro starts at $20/mo. Bandwidth overage charges possible. Setup time: 2-5 minutes You manage: Nothing SSH access: No

Method 3: Railway / Render (Managed PaaS)

Railway and Render detect your Node.js app from package.json and deploy without a Dockerfile:

# Railway
railway up

# Render
# Connect your GitHub repo in the dashboard

Both platforms use buildpacks (similar to Heroku) to detect your runtime and build your app. No Dockerfile required.

The catch: Both use container-like isolation under the hood (even if you don’t write a Dockerfile). This means:

  • Persistent filesystem is limited or ephemeral
  • Railway: usage-based pricing, so the bill moves with load
  • Render: free tier has cold starts (30-second spin-up), databases cost extra ($7/mo+)
  • Both have SSH now (railway ssh; Render on paid instances, not Free), but it is a shell inside one service, not a server you administer. A package you install by hand does not survive the next deploy

Cost: Railway ~$5-15/mo (usage-based). Render $7/mo (Starter) + database extra. Setup time: 5-10 minutes You manage: Nothing SSH access: A shell inside the service (Render: paid instances only)

Method 4: Raw VPS with PM2 (Full Control, No Docker)

For developers who want full control without Docker, a VPS with PM2 is the traditional approach:

# On your VPS
ssh root@your-server

# Install Node.js
curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
sudo apt-get install -y nodejs

# Clone your app
git clone https://github.com/you/your-app.git /var/www/app
cd /var/www/app
npm install --production

# Start with PM2
npm install -g pm2
pm2 start index.js --name my-app
pm2 save
pm2 startup

Then you still need:

  1. Nginx as a reverse proxy (15-20 lines of config)
  2. Certbot for SSL (Let’s Encrypt)
  3. UFW for firewall rules
  4. Git hooks or CI for deploy automation

Total setup: 1-3 hours for someone who’s done it before.

Cost: $4-6/mo (Hetzner, DigitalOcean) Setup time: 1-3 hours You manage: Everything - OS updates, Node updates, nginx, SSL renewal, PM2, firewall, backups SSH access: Yes (it’s your server)

Comparison Table

MethodDocker RequiredCost/moSSHPersistent FSSetup Time
Git push deploy (InstaPods)No$3-7YesYes60 sec
Vercel/NetlifyNo$0-20+NoNo2-5 min
Railway/RenderNo$5-15+Service shellLimited5-10 min
VPS + PM2No$4-6YesYes1-3 hours
Docker on VPSYes$4-6YesYes30-60 min

The Docker option is included for comparison. Notice it’s the most expensive in time for the same cost as the VPS + PM2 approach. Docker adds build complexity without adding functionality for a single Node.js app.

When You Actually Need Docker

Docker earns its complexity in specific scenarios:

  • Multiple services with different runtimes (Node + Python + Redis) on one server
  • Team standardization where 10+ developers need identical environments
  • CI/CD pipelines that build and push images to a registry
  • Kubernetes deployments where container images are the unit of deployment
  • Reproducibility requirements where “works on my machine” isn’t acceptable

For a single Node.js app? instapods deploy or pm2 start gets you to production faster with less overhead.

Getting Started

If your Node.js app has a package.json with a start script, you’re ready to deploy without Docker:

{
  "scripts": {
    "start": "node index.js"
  }
}

The fastest path to a live URL:

instapods deploy my-app --preset nodejs

Your app is live with SSL, custom domain support, and SSH access. No Dockerfile. No container registry. No orchestration.

Deploy your Node.js app - $3/mo

Keep reading

  1. How to Migrate From Railway: App, Postgres and Env VarsMoving off Railway? Step by step: export your variables, dump Postgres, redeploy from GitHub, move your domain, and rotate every secret on the way out.9 min
  2. How to Back Up n8n Workflows and Credentials (2026 Guide)Back up self-hosted n8n properly: export workflows and credentials, save the encryption key, and know which of the three methods actually restores.9 min
  3. The n8n Encryption Key: Where It Is and What BreaksWhere n8n stores its encryption key, how to read or set N8N_ENCRYPTION_KEY, and exactly what happens to your credentials if you lose or change it.9 min