Deploy and Host Discord.js Bot on Railway

A JavaScript Discord gateway worker with discord.js 14.27.0, /ping and /help, locked dependencies, and separate readiness/liveness endpoints. This is not a website: no public domain, database, or volume is required.

About Hosting Discord.js Bot

The service uses Node 24 LTS and a digest-pinned Alpine image, runs as the non-root node user, and installs production dependencies from package-lock.json. Keep one replica and sleeping disabled for its persistent gateway connection.

Required Discord setup

Create an application in the Discord Developer Portal.
Set the required Railway DISCORD_TOKEN to that application's Bot token. A generated secret, application ID, client secret, or dummy token is not a substitute.
Invite the application to your guild with OAuth2 scopes bot and applications.commands, granting permission to send command replies.
Deploy and wait for command registration and gateway connection.
In Discord, invoke /ping and /help. Global command propagation can take time and is controlled by Discord.

A real bot token is mandatory. Missing/rejected credentials or failed command registration prevent readiness. Real provider login, command propagation, permissions, and chat replies require validation with your own token; no live Discord E2E verification is claimed.

Variables and readiness

DISCORD_TOKEN: required, user supplied, with no default. Keep it out of source control and logs.
PORT: internal health listener, default 3000. HOST defaults to 0.0.0.0 inside the container. No public HTTP interactions endpoint is implemented.
/health, /healthz, /ready, and / report readiness only when both command registration and the gateway are ready; otherwise they return 503.
/live is process liveness, not bot readiness. Railway uses /health with a 60-second startup allowance and an on-failure restart policy.
Gateway disconnect/reconnect events affect readiness. A deployment healthcheck is not continuous provider-outage monitoring. Missing credentials, startup failures, and timeouts exit rather than leaving a healthy HTTP-only worker.

Commands and maintenance

/ping reports gateway latency; /help lists loaded commands. Add modules under src/commands/ exporting a SlashCommandBuilder as data and an asynchronous execute(interaction) function. Registration replaces the application's global command list with these definitions: use a dedicated application and review removals before redeploying. Only the Guilds intent is enabled; these slash commands do not require privileged intents.

The worker has no persistent application storage. Add a database deliberately if your custom commands need durable state. Local provider-mock tests do not establish real Discord delivery or a built container's behavior.

Common Use Cases

A JavaScript slash-command starter for a Discord community.
Extending /ping and /help with your own commands.
A single gateway worker without a public web service.

Dependencies for Discord.js Bot Hosting

A Railway worker, a real Discord Bot token, and a correctly scoped guild invitation.

Deployment Dependencies

Template source.
discord.js.
Node 24 and the committed npm lockfile.

Why Deploy Discord.js Bot on Railway?

Railway runs the gateway worker and provides environment variables, logs, deployment healthchecks, and restart policy. You supply the Discord identity and verify command delivery in your own guild.