A server for a Telegram Mini App
A Mini App is a web app that opens inside Telegram: a shop, a booking form, a game or a customer account. From the outside it is a bot with a button; inside it is an ordinary website with an API and a database. Here is which parts need a server and which VPS to take.
The short answer. A Mini App runs fine on a KVM VPS with 1–2 vCPU and 2 GB of memory in Europe, with its own IPv4 and a domain with HTTPS. One server holds the frontend, the API, the bot webhook and PostgreSQL; you need more memory when the database grows or the app processes files.
What a Mini App consists of
The app has three parts. The frontend is HTML, CSS and JavaScript that Telegram opens by a link; the URL must be HTTPS only — in production, plain HTTP and bare IP addresses are not accepted. The backend is the API the frontend calls: orders, profile, payments. The bot takes commands and payments through a webhook. The frontend can be served from the same server or through a CDN (see CDN: when a website needs one); the backend and the bot usually live together. A Let's Encrypt certificate is free; how to issue and renew it is in SSL certificates.
Checking the user on the server
On launch, Telegram passes the app initData: who opened it, the launch time (auth_date) and a signature, hash. The frontend must not trust this data — the backend checks it. According to the Telegram documentation, the server computes HMAC-SHA-256 over the sorted fields with a key derived from the bot token and the string WebAppData, compares it with hash and rejects stale data by auth_date. That is why the bot token lives only on the server, never in the frontend code.
The bot webhook and the network
The bot receives updates through a webhook, and Telegram has strict requirements for it: IPv4 only (IPv6 is not supported for webhooks), ports 443, 80, 88 or 8443, TLS 1.2 or newer. The webhook URL is not a secret only Telegram knows, so set a secret_token when registering it: Telegram sends it in the X-Telegram-Bot-Api-Secret-Token header of every request, and the server rejects requests without it. A server without its own IPv4 will not do — see IPv6-only VPS. The server goes in Europe, as for an ordinary bot: it talks to api.telegram.org all the time, and latency to it matters more than latency to users. While the webhook is down, Telegram keeps updates for no longer than 24 hours, so downtime should be noticed at once — see Server monitoring. More on bot load in VPS for a Telegram bot.
Database, payments and background jobs
Keep users, orders and balances in PostgreSQL rather than in files — see A database on a VPS. Digital goods inside a Mini App are sold for Telegram Stars: before the payment the bot receives a pre_checkout_query and must answer within 10 seconds, or the payment is cancelled. So the webhook must not wait for slow work: mailings, reports and file processing go to a queue (see Scheduled jobs: cron and queues). Mini App load is uneven: after a post in a channel hundreds of people open the app within minutes, so spare memory matters more than the number of cores.
What the server costs
In the accsly.io catalog on 18 November 2026, Europe with its own IPv4 has 680 plans with 1 vCPU and 2 GB at 425 hosts; the monthly median with monthly billing and no prepayment is €9.49 for plans priced in euros, $12 in dollars and 770 ₽ in roubles. With 2 vCPU and 2 GB there are 576 plans, median €13.90, $20 and 885 ₽. Selections: VPS for a Telegram bot, VPS for Node.js and VPS in the Netherlands.