Deploying a Node.js bot (grammY, discord.js, Bolt) to production

Checklist

A start script in package.json and a committed lockfile.
Config from process.env; locally use node --env-file=.env.
Handle SIGTERM so deploys stop the bot cleanly.
Listen on process.env.PORT for webhook mode.

FROM node:20-slim
WORKDIR /app
COPY package*.json ./
RUN npm ci --omit=dev
COPY . .
USER node
CMD ["npm", "start"]

Deploy

Railway: Tutorial: deploy a bot on Railway · Vultr: Tutorial: bot on a Vultr VPS with systemd

Templates: grammY · discord.js · Slack Bolt · WhatsApp

Options we use and recommendAffiliate links: if you sign up, BotNetwork may earn a commission at no extra cost to you. See all recommendations

VPS / cloud

Vultr

A cloud provider with small VPS plans in many regions. You get full root access and predictable monthly pricing; updates, firewall and backups are your responsibility.

Best for: always-on bots where you want full control.

OfferNew users can get up to $300 in trial credit, per Vultr's promo terms.

Try Vultr

Affiliate link

Platform as a service

Railway

A deployment platform: connect a GitHub repository or Dockerfile and Railway builds and runs it, with logs, environment variables and managed databases. Usage-based pricing, so check how always-on services add up.

Best for: gateway bots and workers without managing a server.

OfferNew users get $20 in credits.

Try Railway

Affiliate link

Frequently asked questions

Which Node.js version?

Our templates target Node.js 20 or newer; use an active LTS line.

npm ci or npm install?

npm ci in production: it installs exactly the lockfile.

Why does my bot reply twice after a deploy?

The old and new copies overlapped; handle SIGTERM and avoid running two replicas of a polling or gateway bot.