Frontend
| Choice | Recommendation |
|---|---|
| Framework | React + TypeScript via Vite (default); Vue 3 if the team prefers; Svelte or Solid for the smallest bundles |
| SDK | @telegram-apps/sdk (+ sdk-react / sdk-vue) or the telegram-web-app.js script |
| UI | @telegram-apps/telegram-ui for native-looking components; Tailwind for layout |
| State | Zustand, Pinia or TanStack Query; keep it simple |
| Routing | Hash or memory router; respect Telegram’s Back Button |
| Build | Vite, code splitting, image compression, system fonts |
Performance rules: first render under one second on a mid-range Android device, bundle under 300 KB gzipped for the first screen, lazy-load everything else, use theme CSS variables for instant dark mode.
Backend
| Choice | Recommendation |
|---|---|
| Runtime | Node.js with NestJS or Fastify; Python with FastAPI; Go for high-throughput games |
| Auth | Verify initData HMAC on every request or exchange it once for a short-lived JWT |
| Database | PostgreSQL (managed), Redis for sessions, rate limits, leaderboards |
| Queues | BullMQ, Celery or cloud queues for broadcasts, payouts and webhooks |
| Payments | Bot API for Stars, Stripe/Adyen for cards, TON indexers for crypto |
| Bot | grammY (TypeScript) or aiogram (Python) with webhooks |
Games
Phaser 3 for most 2D games, PixiJS for custom rendering, Unity WebGL for 3D or existing Unity projects. Server-authoritative logic over WebSockets or batched HTTP; Redis sorted sets for leaderboards; anti-cheat on the server.
Blockchain
TON Connect (@tonconnect/ui-react), @ton/ton and @ton/core for transactions, Tact for new contracts, FunC for low-level work, indexers (TON API, TON Center) on the backend. See the TON Connect guide.
Infrastructure and tooling
- Hosting: static frontend on a CDN; backend on AWS, Google Cloud, Hetzner or Fly.io; Cloudflare in front for TLS, caching and bot protection.
- CI/CD: GitHub Actions with preview deployments per branch, each with its own test bot.
- Monitoring: Sentry for errors, uptime checks, dashboards for payment success and queue depth.
- Analytics: PostHog or Telemetree (built for Telegram), plus GA4 if marketing needs it.
- Local development: Cloudflare Tunnel or ngrok to expose HTTPS; Telegram’s test environment for payments.
Recommended stacks by project
| Project | Stack |
|---|---|
| MVP / utility | React + SDK + Telegram UI; NestJS; PostgreSQL; grammY |
| E-commerce | React + Tailwind; NestJS or FastAPI; PostgreSQL; Stripe + Stars; Shopify/WooCommerce sync |
| Community | React + Telegram UI; FastAPI; PostgreSQL; Stars subscriptions |
| Tap-to-earn | Lightweight TypeScript client; Node.js + Redis + PostgreSQL; queues; TON Connect |
| Casual game | Phaser 3; Node.js WebSockets; Redis; Stars + ads |
| Fintech | React; NestJS; PostgreSQL; TON Connect; Tact contracts; KYC provider |
Starter templates
Telegram’s telegram-apps GitHub organization maintains templates for React, Vue, Solid, Next.js and plain TypeScript with the SDK and UI kit configured. They are the right starting point for a prototype; production projects usually add their own backend scaffolding, auth and payments.
Prefer not to assemble it yourself? Full-cycle development or dedicated developers can take it from here.
* All prices and ranges on this page are indicative. The final cost is calculated for each project individually and depends on the complexity of the task, the number of developers and specialists required, and the delivery timeline you set. Use the ranges to understand the typical bracket, not as a fixed offer; the fixed price is confirmed in writing after scoping. Read our pricing terms.