Where a Telegram bot actually lives
A Telegram bot does not run inside Telegram. The messenger simply passes messages to your code, and that code has to execute somewhere. Yandex Cloud offers that somewhere: virtual machines, serverless functions and managed databases.
For an owner, the issue is consequences, not technology. Who is responsible when the bot is down at night? Where are customer requests stored? What does it cost to keep everything running after launch? A Tashkent shop taking orders through a bot loses money every minute it is offline.
Three ways to run the bot
The right choice depends on load and how complex the scenarios are. For a typical bot with a catalog, a cart and payment through Click or Payme, a serverless setup is often enough. A virtual machine makes sense when the logic is heavy.
- Cloud Functions: code runs on demand and you pay for actual execution. Good for lead forms, FAQs and notifications, though execution time is limited.
- Serverless Containers: the same serverless behavior, but the bot is packaged as a container. Handy when it has many dependencies.
- Compute Cloud: a regular virtual machine with full control. Suits queues, background jobs and complex CRM integrations, but updates and security become your job or your contractor’s.
Webhook or long polling
A bot can ask Telegram for updates itself (long polling) or receive them at your address (webhook). Serverless functions pair with webhooks: Telegram sends a request to an HTTPS endpoint, the function replies and goes idle. Long polling needs a process that never stops, which means a machine or container.
Plan for repeated deliveries too. If the bot replies slowly or with an error, Telegram sends the same update again. Without protection against duplicates, a customer gets two order confirmations and your records show two identical requests.
Where data and leads go
A bot without a database is just an auto-responder. Requests, order history, marketing consents and conversation state all need storage. A managed cloud database spares you backups and upgrades, but ties the project to the platform.
Decide up front where leads end up: a CRM, a spreadsheet, a private managers’ chat, or all three. Pass the lead source along, such as the ad campaign or Instagram post. Otherwise end-to-end analytics cannot show which advertising actually brings people into the bot.
What to check for Uzbekistan
Uzbek personal data legislation includes requirements for storing citizens’ data on servers inside the country. A bot that collects names and phone numbers falls under that logic. Before choosing a platform, talk to a lawyer about where the data will physically sit and whether a foreign cloud is acceptable for it.
Also confirm how you will pay for cloud services from Uzbekistan. And build the bot so it can move to another host, including a local one, without a rewrite.
What the ongoing cost includes
Cloud resources are only one part of the budget. Ask your contractor to itemize costs and settle whose account the cloud sits under. It should be yours. Otherwise, if you change contractors, you risk losing access to the bot and your customer base.
- Development: scenarios, admin panel, broadcasts.
- Cloud: compute, database, traffic, file storage.
- Integrations: Click, Payme, CRM, SMS providers.
- Support: monitoring, library updates, fixes after Telegram API changes.
Where to start
Before picking a platform, answer four questions: what the bot must do, how many requests per day you expect, what data it collects and who will maintain it. The answers show whether you need a serverless setup, a virtual machine or something simpler.
At markdev we build Telegram bots for businesses in Uzbekistan and choose the hosting to fit the task, not the team’s habits. If you want to discuss your bot, leave a request and we will review the scenario and suggest a launch setup.
FAQ
Can I run a Telegram bot on Yandex Cloud without my own server?
Yes. With Cloud Functions or Serverless Containers the bot works through a webhook without an always-on machine. Complex bots with background jobs are better on a virtual machine.
Does a simple bot need a database?
Not if it only answers standard questions. Once it handles requests, orders or broadcasts, you need to store data.
Which cloud account should I use when ordering a bot?
Your own. The contractor gets access to work in it, but you remain the owner of the resources and the data.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.