Crash alerts, in Telegram
It restarts by itself and messages you in the chat you choose.
nodejshost alertssupport-desk-bot restarted after a crash, back online
TELEGRAM
No. 004821
ToEveryone who messages your bot
FromYour bot, on nodejshost
A telegram always arrives. Your Telegram bot should too: host your grammY or Telegraf bot here and it answers at 3am, with no webhook, no public URL and no server to keep awake.
Live chat, printed as it happens
/start
Hi Noa! What can I help you with?
Where is my order?
Order #4821 left our warehouse this morning. It reaches you tomorrow, 10:00 to 14:00.
Your bot keeps asking Telegram for new messages (long polling), which grammY and Telegraf do by default. Nothing has to reach in, so there is nothing to expose, certify or configure.
Form 1
@BotFather → /newbot 7012345678:AAH•••••
Message @BotFather, create the bot, copy its token.
DeliveredForm 2
BOT_TOKEN = •••••••• package.json
BOT_TOKEN goes in Environment, hidden. Upload your project or connect GitHub.
DeliveredForm 3
▶ npm start @SupportDeskBot is running
It installs, starts polling and answers. That's all of it.
DeliveredYour package.json already says how your bot runs, so there is nothing new to learn. We run npm ci (or npm install without a lockfile), then npm start, with your own hooks around them. Pick an example or edit it.
while installing
when starting
node bot.jsOn every pack, no add-ons.
It restarts by itself and messages you in the chat you choose.
nodejshost alertssupport-desk-bot restarted after a crash, back online
The process never sleeps, so reminders and daily digests fire on time.
cron("0 7 * * *") → 412 reminders
BOT_TOKEN is hidden in the dashboard and never in your files.
BOT_TOKENhidden
Every push is a version. One click takes you back.
v14 live · v13 restore
Hard CPU and memory limits. No other bot can see your token.
0.25 vCPU · 256 MB · non-root
Run tsx directly or build with tsc in prestart. Your call.
"start": "tsx src/bot.ts"
Subscribers, conversations, orders and reminders survive restarts. On a paid pack your bot gets its own PostgreSQL, with DATABASE_URL already set.
subscribers
PostgreSQL 17 · DATABASE_URL
| Chat | Name | Habit | Streak |
|---|---|---|---|
| 5821044193 | Noa | Read 20 pages | 41 |
| 9013377102 | Daniel | Walk 8k steps | 17 |
| 4487120036 | Maya | No sugar | 9 |
| 3065298847 | Yoni | Practice guitar | 64 |
Real screens of the dashboard you get.

Every bot you run at a glance: running or not, CPU and memory, start, stop and restart.
Each pack is a pool your bots and their databases share.
Tariff, per month
| Pack | Pool | Monthly | Plans |
|---|---|---|---|
| FreeTry one small bot, no card needed. | 1 · 256 MB · 0.25 vCPU · 1 GB | $0 | Start free |
| StarterOne bot that has to stay online, 24/7. | 1 · 1 GB · 1 vCPU · 5 GB | $5 | Choose Starter |
| ProFor developers running production bots.Most popular | 10 · 4 GB · 3 vCPU · 25 GB | $15 | Choose Pro |
| Custom packSize the pool yourself and pay only for what you set. | 1–50 bots · up to 32 GB | from$3.40 | Build your pack |
Prices in USD, billed monthly. Change or cancel your pack any time.
We don't take card payments on the site yet. For a paid pack, message us in the support chat and our team switches it on for you. Free you can start yourself.
No. Bots here use long polling: they ask Telegram for new messages, which grammY's bot.start() and Telegraf's bot.launch() do by default. Webhooks aren't supported, because bots have no public address.
A package.json with a start script, like "start": "node bot.js". We run npm ci (or npm install without a lockfile) and then npm start.
In the bot's Environment as BOT_TOKEN; your code reads process.env.BOT_TOKEN. It's hidden in the dashboard and never stored in your files.
Both work, in JavaScript or TypeScript. Run TypeScript with "start": "tsx src/bot.ts", or build it first with "prestart": "tsc".
In the bot's own PostgreSQL database, on a paid pack. It survives restarts and redeploys, and DATABASE_URL is already in the environment.
Yes. The process runs all the time, so timers and libraries like node-cron fire on schedule: reminders, digests and daily reports.
It restarts automatically, up to five times in a row, and we can message you on Telegram. The console keeps the error.
Node.js 22 and 24 (LTS) and 26 (Current). Switching applies the next time the bot starts.
No. nodejshost is an independent hosting service. We are not affiliated with, endorsed by or sponsored by Telegram. We host bots that people build for Telegram.