TeleBotHost

Spend the night on the bot, not the box.

TBH in one breath.

TeleBotHost (TBH if you are in a hurry) is where Telegram bots live without a VPS. You paste a BotFather token, write what the bot should do in TBL, hit Launch, and message it. We run each update in the cloud and stop when it finishes.

That is the whole pitch. No SSH. No webhook maze. No Node process you keep alive with hope and PM2.

Start free Contact us

In short

People kept renting servers just to answer chat messages. The bot was twenty lines. The infra was a second project. We built TBH so that second project goes away.

You still write real logic. TBL is Tele Bot Language: regular JavaScript with helpers made for Telegram. You are not stuck in a toy builder forever. You also do not assemble a framework before /start works.

When someone messages your bot, Telegram talks to us. We match the update to a command, run it in a sandbox, and let it reply, call an API, or touch db. Then we tear the run down. Clean exit. Next message gets a fresh start.

If that sounds like what you wanted from a VPS, minus the rent and the 3am alarms, you are in the right place.

The names, plainly

Acronyms only help if they mean something when you say them out loud.

TBH
TeleBotHost. The platform. Console, hosting, sandbox, delivery. The place your bots live.
TBL
Tele Bot Language. The JavaScript you write in the console. Helpers like Bot, Api, HTTP, and db are already loaded. One command handles one update, then it is done.
Serverless here
You do not manage a machine. Capacity flexes with traffic. You still choose a plan when you need more headroom. You just do not pay for a lonely VPS sitting idle between messages.

Who this is for

Not a persona deck. Just the people we keep in mind when we ship.

  1. 01

    You want a bot live tonight

    You have an idea and a BotFather token. You do not want to rent a VPS first. Paste the token, write a command, hit Launch, then message the bot on Telegram.

  2. 02

    You already know JavaScript

    You can write the logic. You just do not want PM2, nginx, SSL renewals, and a process that dies when the host reboots. That is a fair ask.

  3. 03

    You run more than one bot

    Side projects pile up. Free includes unlimited bots, so you do not open a new server for every experiment. Keep the quiet ones. Grow the busy ones when they earn it.

What you actually get

The useful parts, without the brochure tone.

  • A console that does the job

    Add a bot, write commands, check logs, launch. You should not need a deploy pipeline for a chat bot.

  • TBL: JavaScript with the bot bits ready

    Bot, Api, HTTP, and db are there without imports. require() pulls other TBL commands you wrote, not a random npm tree.

  • Runs that start and stop

    An update comes in. Your command runs in a sandbox. Then it exits. Nothing stays humming in the background waiting to break.

  • Storage next to the reply

    Built-in db covers user, bot, and global scopes. Keep scores and settings without standing up Redis “just for now.”

  • Webhooks handled for you

    Telegram delivery is our problem. You do not point domains, renew certificates, or debug nginx at midnight.

  • Room to grow when you need it

    Free is real. Paid plans buy longer runs, more storage, ads off, higher Webhook/WebApp limits, and better support. Month to month. Cancel anytime.

What we keep coming back to

These shape the plans, the runtime, and the docs.

  1. 01

    Ops should not be the hobby

    Building the bot is the fun part. Keeping a box online is not. If the platform cannot carry the boring work, we are not done.

  2. 02

    Short code beats clever infra

    Five honest lines that answer a message beat fifty lines of bootstrap. We care about that feeling more than looking like a full Node monorepo.

  3. 03

    Free has to be useful

    Unlimited bots. No card to start. Ads on Free help keep the lights on. When a bot goes live for real users, Freemium is a dollar to turn ads off. You upgrade when the numbers say so, not because we locked the front door.

  4. 04

    Clear limits beat surprise bills

    Timeouts, storage, parallel runs, and Webhook/WebApp caps are written down. Telegram updates themselves are not capped. We would rather you know the ceiling than find it in an invoice.

What we are not

Saying this out loud saves everyone a week of wrong expectations.

  • A general Node host

    You cannot upload any Express app. TBL is sandboxed on purpose. That is how we keep bots isolated and the platform stable.

  • A replacement for every database

    Built-in db is for bot state: progress, settings, simple records. If you need a warehouse, keep the warehouse. Call it from TBL when you need to.

  • A promise that nothing ever breaks

    Telegram can reject calls. Networks hiccup. We watch the platform, harden what we can, and answer when you write. We do not pretend the internet is perfect.

If that clicks, try this next

Open the console and try a Free bot. Check pricing when you care about ads, timeouts, or Webhook headroom. Ping us on Telegram or email if something feels stuck. We would rather answer a short question than watch you wrestle alone.

Start free See pricing Read the docs @update_chat Contact

Ready when you are

Token in. Command written. Launch. Free to start. No card required to try it.

Start free View Docs