Telegram Mini App hosting: the web app, its API and the bot together
A Telegram Mini App is a web page Telegram opens from an HTTPS address, usually with an API behind it and a bot in front. On Livops one repository with all three starts in one click, the Mini App's /api reaches the backend on its own, the site is free and the bot is 19 credits a month. Here is how that compares with a VPS, Vercel, Railway and Render.
By Livops team, the people who build and run LivopsUpdated
A Telegram Mini App is rarely one thing. There is the web page Telegram opens, an API that page calls, and a bot that sends the button; often an admin panel and a database too. This page says what Telegram asks of each part, how the usual hosting choices split them up, what each costs from the providers’ own pages, and how the whole repository runs on Livops.
What does a Telegram Mini App need in production?
An HTTPS address for the web app
The Bot API describes a Mini App’s address as an HTTPS URL[1]. Plain HTTP without TLS is allowed only in Telegram’s separate test environment[2]. So the page needs a public address with a valid certificate before you can put it on a button.
A way to open it
Telegram supports seven ways of launching a Mini App, among them a keyboard button, an inline button, the menu button, the bot’s main Mini App and a direct link[2]. Only a Mini App opened from a keyboard button can send data back with sendData, up to 4096 bytes, in a service message to the bot[2]; anything richer goes through your own API.
An API that checks who is calling
The page gets initData from Telegram. Your server checks it: the secret key is the HMAC-SHA-256 of the bot token with the constant string WebAppData, and the hash of the sorted fields must match the hash that came with them; auth_date lets you refuse old data[2]. initDataUnsafe should not be trusted[2]. That check needs the bot token, so it belongs in a backend, not in the page.
A bot that keeps running
The bot sends the button and answers commands. It either polls Telegram in a loop or receives a webhook on port 443, 80, 88 or 8443[1]; either way something has to keep it up.
One address, or CORS
If the page and the API are on different addresses, every API call is cross-origin and the API must send CORS headers. If the page’s own /api reaches the API, the browser sees one origin and there is nothing to configure.
The options at a glance
| Option | What it is | Smallest paid always-on process | What you still maintain |
|---|---|---|---|
| Livops | A platform; site, API, bot and database in one project | Site free; bot 19 credits (19,000 so’m) a month | Your code |
| A VPS in Uzbekistan | A virtual machine with root | 82,000 so’m a month: 1 vCPU, 2 GB, 30 GB HDD (SmartCloud)[3] | The system, a web server, certificates, deploys, restarts |
| Vercel + a backend elsewhere | The Mini App on Vercel, the bot and API on another host | Vercel Pro is $20 a month per seat[9], plus the backend’s host | Two platforms and the link between them |
| Railway | A platform billed by usage | Hobby: $5 a month, including the same amount of usage[4] | Your code |
| Render | Static sites, web services and workers | Static sites free; a web service from $7 a month, 0.5 CPU and 512 MB[5] | Your code |
Other providers’ prices are from each provider’s own page, read on 20 November 2026; the dates are in Sources below. Livops prices are the ones the cabinet bills today.
Each option
Livops
The Mini App, the API and the bot are services of one project. Connect the repository, and if it holds all three they start in one click, the backend first and then the sites. Requests from the Mini App and an admin panel to /api reach the backend on their own. Servers are in Uzbekistan and payment is in so’m. You do not get root; for system software of your own, a VPS fits better.
A VPS
Everything on one machine, the cheapest 2 GB one at SmartCloud for 82,000 so’m a month[3]. You put a web server in front, get a certificate for the Mini App’s address, route /api to the backend yourself, and keep the bot running with a process manager. Full control, and every one of those pieces is yours to keep working.
Vercel with a backend elsewhere
Vercel serves the Mini App well, and a rewrite can forward /api/:path* to an external API without changing the address in the browser[7], so the page keeps one origin. The bot and a long-running API live on a second platform. The free Hobby plan is for personal or non-commercial use only[8]; a Mini App for a business is a Pro plan, $20 a month per seat[9].
Railway
Railway bills by usage. Hobby is $5 a month and includes that much usage[4], and it is paid by credit card[4].
Render
A static site for the Mini App is free to deploy[5], and a web service for the API starts at $7 a month[5]. A free web service spins down after 15 minutes without inbound traffic and takes about a minute to start again[6] — long enough for a Mini App’s first screen to hang.
One platform or two: what do you wire up?
Split across two platforms, you set the API’s address in the page’s build, handle CORS or a rewrite[7], keep two dashboards and two bills, and remember that a new API address means rebuilding the page. On one platform those links are inside one project: the page’s /api goes to the backend beside it, and a database’s address is written into the services that use it. Two platforms make sense when one of them is much better at one part; one platform makes sense when the parts change together, which for a Mini App they usually do.
Where can you run a Mini App for free?
- Livops: the Mini App, built as a static site, is free. The bot and a separate API need credits; on an account that has not paid yet, the first one runs for 15 minutes on a zero balance, once.
- Render: static sites are free[5]; a free web service sleeps after 15 minutes without traffic[6].
- Railway: the Free plan has $1 of usage a month, up to 1 vCPU and 0.5 GB per service, and services sleep after 5 to 10 minutes without outbound traffic[4].
- Vercel: Hobby is free[9], for personal or non-commercial use[8].
Telegram Mini App hosting on Livops
- In the cabinet, press New project and choose the Repository that holds the bot, the API and the Mini App.
- Livops reads the code and shows what it found: the site, the app, the bot. If the code needs a database, one is offered.
- Fill in the secrets before the first start — the bot token, and anything else the code reads. Mark a variable as secret and its value is never shown again.
- Start. The backend comes up first, then the Mini App and any admin panel.
- Open the Mini App’s address,
<name>.livops.app, with HTTPS already on, and give it to BotFather or to your bot’sweb_appbutton.
If the Mini App calls its API on its own address — fetch('/api/me'), or baseURL: '/api' — that path on the site is answered by the backend in the same project, so there is no CORS to set up and no API address to build in. A service’s address can also be read by another service through a reference in its variables.
- The bot polls by default. To use a webhook, switch Connection to Telegram in the bot’s settings and press Save and redeploy; the platform tells Telegram the address and the secret, and the bot’s own address, for a Mini App, stays direct. See webhook vs polling.
- To use your own domain, add it under the service’s Domains and create the DNS records shown; the certificate is issued once they are found.
- Every
git pushdeploys a new version, and if a build fails the previous version keeps running.
The Mini App as a static site is free. The bot is 19 credits a month (19,000 so’m), a separate API 39 credits (39,000 so’m), and one 500 MB database per team is free. One credit is 1,000 so’m, bought through Payme or Click. See Pricing.
Questions
Does a Telegram Mini App need HTTPS?
Yes. The Bot API describes a Mini App's address as an HTTPS URL. Only Telegram's separate test environment lets you open a Mini App over plain HTTP. On Livops every service gets an address with HTTPS from the start.
Can the bot, the API and the Mini App live in one repository?
Yes. Livops sees how many apps the repository holds and starts them all in one click: the backend first, then the sites. Requests from the Mini App to /api reach the backend on their own, and if the code needs a database, one is offered.
How do I know a request really comes from the Telegram user?
Check initData on your server. Telegram signs it with a key derived from your bot token, so the server recomputes the HMAC-SHA-256 and compares it with the hash field, and can also check auth_date. initDataUnsafe, read in the browser, should not be trusted.
Does the bot have to use a webhook for a Mini App?
No. The Mini App talks to your API over HTTPS; the bot can still get its own updates by polling, which is the default on Livops. Switch to webhook in the bot's settings if you prefer, and the platform sets it with Telegram for you.
What does a Mini App cost on Livops?
The Mini App itself, built as a static site, is free. The bot is 19 credits a month (19,000 so'm), a separate API is 39 credits (39,000 so'm), and one 500 MB database per team is free. Credits are bought in so'm through Payme or Click.
Can I use my own domain for the Mini App?
Yes. Add the domain to the service, create the DNS records the cabinet shows, and the certificate is issued on its own once the records are found. Give Telegram the new HTTPS address.
Who wrote this comparison?
The Livops team. Every price and limit of another provider on this page links to that provider's own page, with the day we read it.
Sources
- Telegram Bot API (core.telegram.org). Checked .
- Telegram — Telegram Mini Apps (core.telegram.org). Checked .
- SmartCloud — VDS plans (smartcloud.uz). Checked .
- Railway — Pricing (railway.com). Checked .
- Render — Pricing (render.com). Checked .
- Render — Deploy for free (render.com). Checked .
- Vercel — Rewrites (vercel.com). Checked .
- Vercel — Terms of Service (vercel.com). Checked .
- Vercel — Pricing (vercel.com). Checked .
Put your project online today
Connect GitHub or drop a folder. No card is asked for.
Deploy your Mini AppRelated
- Telegram bot hosting in 2026: the options comparedA Telegram bot needs a process that never stops, or a public HTTPS address for a webhook. On Livops it runs from a GitHub push for 19 credits a month (19,000 so'm). Here is how a VPS, Railway, Render, Fly.io and Vercel compare.
- Telegram bot webhook vs polling: which one to usePolling means your bot asks Telegram for updates in a loop; a webhook means Telegram POSTs each update to your HTTPS address. Polling is simpler and needs no address; a webhook needs HTTPS but no always-running loop. A bot uses one or the other, never both. On Livops both run for the same 19 credits a month.
- aiogram bot hosting: how to deploy an aiogram 3 botAn aiogram 3 bot needs one process that never stops, the token in an environment variable, state kept outside memory and a clean exit on SIGTERM. On Livops you push a repository with bot.py and requirements.txt, and it runs for 19 credits a month (19,000 so'm), polling or webhook.
- grammY bot deploy: polling, webhooks and hostingDeploy a grammY bot as one always-on Node.js process: bot.start() for polling, or webhookCallback() behind an HTTP server, with bot.stop() on SIGTERM. On Livops a repository with grammy in package.json runs as a bot from every push, for 19 credits a month (19,000 so'm).