LIVE500,000+ active users · every system below is in production right now

Infrastructurethat stays up.

Telegram bots, APIs and real-time voice infrastructure — designed, deployed and operated by one developer who wrote all of it. When something breaks at 3am, the person who fixes it already knows why.

Bot API + MTProto
WebRTC voice, no wrappers
Go · Python · TypeScript
A watchdog on every service
kustbots · consolemoderation
In production

Not a portfolio. A fleet half a million people use every day.

500K+
active users across the bots we build and operate
400K
people reached by a single broadcast · 300K on a quiet one
9,703
apps deployed through our own automation
50
bare-metal machines we build and run ourselves
Proof  Do not take my word for it

Check the numbers yourself.

Everything below is public. Open the updates channel and read the view counts under each post. Nothing here needs my word or a screenshot.

6,010
subscribers on @kustbots
462K
views on the most recent big announcement
290K+
views on every announcement listed here
503
forks of KustMusic on GitHub
8 JunLink remover major update346K
29 JunWent fully open source337K
8 JulKustMusic relaunch390K
24 AugVC music bot announcement383K
11 SepLink remover moved to Go339K
16 SepLink remover update297K

Views as shown on t.me/s/kustbots on 6 October 2026. Subscribers are far fewer than views, so open the channel and see the counts live, and judge reach and engagement for yourself.

Field notes  11 September 2026

We swapped the engine mid-flight.

Our two biggest bots, rewritten in Go and running in production. This is what that looked like from the inside.

Link remover · @linkremoverlbot
81,300groups

Python to Go in one dyno restart. 10–15 seconds.

The whole bot was rewritten in Go on the same database, so no group lost a single setting. The switch took one Heroku dyno restart: ten to fifteen seconds offline, then the Go binary was serving every group.

  • BeforePython, one long-running process for every group
  • CutoverA single dyno restart, 10–15 seconds offline, settings untouched
  • First bootTelegram had 72,000+ stale messages queued, growing by ~300 a second. The bot was busy clearing old updates instead of answering new ones.
  • FixDrop the backlog at startup and ignore anything older than a minute. The queue now sits at zero or one.
Read the full case study →
Music · voice-chat streaming
11voice servers

A Go playback fleet, routed by health.

Music streams into Telegram voice chats from a fleet of eleven Go playback servers behind one bot. Each chat stays on its server, and the router checks health before load, so a broken server can never look "idle" and swallow new chats.

  • Fleet11 Go playback servers, one bot in front
  • RoutingSticky per chat, least-loaded among healthy servers only
  • IntegrityEvery download checked against the track's real length, with a second source when the first cuts short
  • RolloutBot first, then servers in waves, so playback never stops for everyone at once
How we build music bots →
01  What we run

Twelve systems. All of them live.

Every one of these is serving real users somewhere right now, and every one of them is watched by the people who built it.

Moderation & Filtering
01 / 12

Moderation & Filtering→

Spam, massive raids, and malicious link floods handled directly inside the group before any members read them. We use per-chat policies and heuristic rules that can be updated on the fly without a redeploy. Every removal is strictly recorded in an immutable audit log.

MTProtopattern cacheaudit log
Voice Platforms
02 / 12

Voice Platforms→

High-fidelity audio streaming injected seamlessly into Telegram voice chats. We engineered custom queueing, precise seeking, multi-chat playback synchronization, and aggressive reconnection protocols when a data centre unpredictably drops the call mid-track.

WebRTCOpusvoice node
Voice Agents
03 / 12

Voice Agents→

Autonomous agents that hold a live voice call natively in Telegram. Speech in, speech out, entirely interruptible (barge-in support), complete with a rich transcript you can read afterwards. We strictly police end-to-end latency budgets to ensure natural conversations.

ASRLLMTTSbarge-in
Bot Cloning
04 / 12

Bot Cloning→

One robust codebase deployed dynamically per customer with securely isolated config, encrypted tokens, and separate storage. A new feature ships to thousands of instances simultaneously, but a configuration mistake reaches none of the others.

multi-tenanttoken vault
Deploy Automation
05 / 12

Deploy Automation→

Ship updates, instantly roll back, and know within seconds whether the new binary is serving traffic. Our deep health checks exercise real workloads against the database, because merely opening a listening port proves absolutely nothing.

Dockerhealth checkswatchdog
Secure Payments
06 / 12

Secure Payments→

Frictionless crypto and fiat card flows integrated directly inside chat. Native invoices, rigorous webhook cryptographic verification, daily reconciliation, and battle-tested retry loops that are mathematically guaranteed to never charge a user twice.

invoiceswebhooksidempotency
Observability Dashboards
07 / 12

Observability Dashboards→

The uncompromising operator view: instantly see what is currently running, what explicitly failed, what config changed, and what it cost on AWS. Built specifically for the tired engineer on call, not for a pretty marketing screenshot.

WorkersMongoDBtime series
Mini Apps & Web UI
08 / 12

Mini Apps & Web UI→

Full-stack Telegram Mini Apps bridging the gap between rich web interfaces and chat. We build deeply integrated, native-feeling UIs directly inside the messenger with seamless crypto wallet connections and smooth, 60fps animations.

ReactTelegram Web Appsanimations
Bare Metal & Offline Systems
09 / 12

Bare Metal & Offline Systems→

We do not just rent cloud instances. We build and run 50 of our own machines: high-volume scraping and MCP tooling, self-hosted SQL, and fully offline systems for work that must never touch the public internet. Regional routing sends each request to the nearest healthy node, whether that is our rack or a cloud region.

50 machinesself-hosted SQLofflineregional routing
Private LLM Hosting
10 / 12

Private LLM Hosting→

Strictly private deployment of open-weight AI models on dedicated hardware. We ensure your conversation data never leaves the premises while maintaining high-throughput, predictable inference latency.

GPUsvLLMLlama
AI Sales Agents
11 / 12

AI Sales Agents→

A sales agent any business can switch on in one call. It answers from that business's own website data, checks directions, nearby places, weather and exchange rates live, books appointments, and saves every lead. It calls real tools mid-conversation instead of guessing, remembers each customer without letting the prompt grow forever, and can hold a spoken conversation with local Whisper transcription and a fully offline voice.

RAGtool callingPostgreSQLmulti-tenant
Scraping, MCP & Automation
12 / 12

Scraping, MCP & Automation→

Web scraping at volume on our own hardware, browser automation for sites that have no API, and MCP servers that hand AI agents real tools. Real-time relays push one event to thousands of clients in milliseconds. Every job is queued, retried and supervised, so an overnight run finishes without anyone watching it.

headless browsersMCPqueuesWebSockets
02  The path of one update

A message leaves a group and comes back changed.

The whole round trip is ours: edge, routing, session state, the service that does the work, and the storage behind it. Nothing is a black box we cannot open at 3am.

A /play in a group chat, from the typed command to audio playing in the voice chat — and what happens when a data centre drops the call mid-track.

audio streams back into the voice chat
Voice Chat
listeners · opus
01 · someone types /play
Command Gateway
verify · rate limit
02 · 429 backoff, not a storm
Music Service
queue · playlist · dj
03 · decides what plays next
Search Resolver
query → track metadata
04 · title · duration · artwork
Download Balancer
edge cache · 1 year
05 · a cache hit skips extraction
Media Extractor
lowest-bitrate audio
06 · credential pool, rotated
Stream Node Pool
sticky · least loaded
07 · same chat, same node
Voice Transport
webrtc · jitter buffer
08 · dc failover, zero dropshealth checks exercise a real stream, not an open port

A spam link posted into a 41k-member group, from the raw update to the message being gone before anybody reads it.

the action lands in the group · 38ms p50
Group Chat
messages · links · raids
01 · one update arrives
Edge Filter
verify · rate limit
02 · 429 backoff, not a storm
Policy Router
per-chat policy
03 · every chat, its own rules
Rule Engine
patterns · confidence
04 · updated live, no redeploy
Policy Store
settings, warm cache
05 · read once, not per message
Decision Log
immutable audit row
06 · every removal recorded
Action Worker
delete · restrict · log
07 · runs before anyone reads it
User Notice
why it was removed
08 · admins can switch it offspam, raids and link floods are handled inside the group, not reported afterwards

An in-chat checkout, from the invoice to the feature unlocking — including the retry loop that makes a double charge impossible.

access unlocks back in the chat
Chat Checkout
invoice inside the chat
01 · crypto or card, no browser
Payment Gateway
hosted rails
02 · we never hold card details
Webhook Verifier
signature checked
03 · unsigned callbacks dropped
Settlement Worker
idempotent retries
04 · never charges twice
Ledger Store
one row per attempt
05 · the record of what happened
Reconciler
daily, line by line
06 · totals must match ours
Entitlements
who has what, until when
07 · expiry handled, not assumed
Access Grant
premium unlocked
08 · the feature turns oninvoices, webhook verification, payouts and daily reconciliation, all inside the messenger

One codebase running as thousands of separate bots, and the supervision loop that notices when one of them quietly stops working.

status comes back to the panel · live
Control Panel
one tenant, one token
01 · add a customer in a minute
Config Service
isolated per tenant
02 · a bad setting reaches one
Token Vault
encrypted at rest
03 · tokens never in the image
Deploy Controller
ship · roll back
04 · one atomic step, either way
Container Fleet
identical images
05 · staging and production match
Health Registry
real work, not a port
06 · an open port proves nothing
Supervisor
cross-checks, then acts
07 · cooldowns stop restart loops
Tenant Instances
thousands, isolated
08 · one feature ships to alla feature reaches every instance; a bad config reaches none of the others
03  How we work

Four rules we do not bend.

We build it, then we run it.
01

We build it, then we run it.

Delivery is the start, not the end. The engineers who architected the service are the exact same people woken up when it stops. Nothing gets handed over as a passive archive and forgotten. We own the entire lifecycle of the code we produce.

We work close to the metal.
02

We work close to the metal.

We use the Bot API where it is sufficient, and we drop down to MTProto where it is not. Voice and video streams are handled directly at the transport layer (WebRTC) rather than through a bloated wrapper, giving us absolute control over jitter and latency.

We design for failure.
03

We design for failure.

Rate limits, expired sessions, poisoned caches and half-dead processes are baseline assumptions, not surprises. We engineer with strict retry budgets, automatic circuit breakers, and health checks that fail loudly and page us immediately.

We answer directly.
04

We answer directly.

One message on Telegram reaches an engineer who inherently knows the system. No labyrinthine ticket queues, no account managers relaying your question to someone else. You get plain answers and immediate fixes.

Prashant Sahlot (Kust), the developer behind KustBots
About  Who you are hiring

One developer. No account manager in between.

I am Prashant Sahlot, known as Kust: an 18-year-old developer from Ghaziabad, India. I have been building Telegram software for six years, and I wrote and run every system on this page myself. When you message me, you reach the person who built it, not a sales team.

KustBots is not a registered company yet; that is in progress. Until it is, agreements are made with me personally, in writing, with a fixed scope and milestone payments. I would rather say that plainly than hide it.

6 years building on Telegram
Solo: you talk to the developer
Public work: github.com/kustbots
Based in India (IST), async-friendly
04  What we can build

If it lives in Telegram, we have built it.

Ask for something that is not on this list. Most of our best work started as a request nobody else would take.

  • Moderation & anti-spam
  • Giveaways
  • Referral systems
  • Support desks
  • Mini apps
  • Inline tools
  • Music streaming
  • Conference recording
  • Live voice agents
  • TTS pipelines
  • Call transcripts
  • REST & webhook APIs
  • WebSocket event relays
  • Cloudflare Workers
  • MTProto session services
  • Custom databases
  • Redis caching
  • CDN & edge caching
  • Queues & schedulers
  • Rate-limit proxies
  • Crypto checkout
  • Razorpay & UPI
  • Invoices
  • Subscriptions
  • Payouts
  • Reconciliation
  • Deploy pipelines
  • Health checks
  • Watchdogs
  • Log & metric dashboards
  • Migrations
  • Regional routing
  • Offline & air-gapped systems
  • Kubernetes & hypervisors
  • Infrastructure as code
  • AI sales agents
  • RAG knowledge bases
  • MCP servers
  • Web scraping at volume
  • Browser automation
  • Private LLM hosting
  • Agent fine-tuning
  • Agent hosting & support
Pricing  In US dollars

Clear prices, fixed scope.

Every job is quoted against a written scope, and I tell you the price before I build anything. Hosting and maintenance of what I build are handled by me.

Websites

Priced per page

Designed and built by me, fast and responsive.

Standard website$100 / page
Animated website$200 / page
3D animated website$300 / page
Payment flow add-on+ $600

Payment flow means checkout, verified webhooks and order records, connected to your payment provider.

Telegram bots

Priced per feature

Custom bots, built command by command.

Simple commandfrom $50
Complex command$300+
/start, help, infoincluded

A simple command replies or looks something up. A complex one involves payments, AI, voice, scraping or state across users. I price each one before I start.

Ready-made music bot

Your own, set up for you

A proven voice-chat music bot, customised for you and hosted by me.

Setup fee$100
Monthly (hosting + upkeep)$30 / mo
Handles3–4 voice chats at once

Want to test first? Open @vcmusiclubot, send /clone and your bot token, and get a working clone for free.

AI agents, web apps and everything else

Quoted per project

AI sales and support agents, scrapers and automation, dashboards, APIs and custom web apps. Tell me the problem, and I send a fixed price against a written scope. Hosting and maintenance are on me. AI usage (model and API fees) is billed separately, at cost, so you only pay for what your users actually use.

AI model / API usagebilled at cost
Hosting and maintenancecovered by me
Quote validity30 days

Payment: USDT or international bank transfer, plus UPI and Razorpay for clients in India, invoiced in milestones. Card payments through Stripe come once KustBots is a registered company.

Process  How a job works

From message to live.

01

You message me

Tell me what is broken or what you want built, on Telegram.

02

Written scope

I reply with a fixed price and a scope in writing, valid for 30 days.

03

Milestone payments

You pay in steps as parts are delivered, not all upfront for unseen work.

04

I build, you watch

Short updates as I go, and a working version you can click early.

05

Handover and upkeep

I host and maintain it, and it is yours once paid in full.

05  Technology

Chosen per job, not per fashion.

Ten layers, one team. We know each of them down to its failure modes, which is why we can promise to run what we build.

01

Languages

3

Picked for the job, not the trend.

  • GoServices that must never pause: voice nodes, event relays, and the link remover serving 81,300 groups.
  • PythonMTProto sessions, audio pipelines, and AI agent orchestration.
  • JavaScript & TypeScriptNode services, edge handlers, operator dashboards and Telegram Mini Apps.
02

Real-time & Telegram

4

Where milliseconds are the product.

  • Telegram Bot APICommands, webhooks, inline tools and in-chat payments.
  • MTProtoEverything the Bot API cannot reach: user sessions, voice chats, bulk history.
  • WebRTCVoice-chat transport with our own jitter buffering and data-centre failover.
  • WebSocket relaysOne event fanned out to thousands of connected clients in milliseconds, with reconnect and replay.
03

Data

5

Managed where it helps, written by us where it must be fast.

  • PostgreSQL & SQLRelational stores on managed clouds and on our own offline servers.
  • MongoDBChat state, per-chat policy, audit trails and time series.
  • Custom databasesStorage engines written in-house for hosting workloads where an off-the-shelf database is too slow or too heavy.
  • MySQL · MariaDB · SQLiteRelational engines chosen per project, from a clustered backend to a single-file store on an offline box.
  • S3 · R2 · object storageMedia, backups and exports on durable object storage, cached at the edge.
04

Cloud & bare metal

7

Multi-cloud, our own racks, and systems that run fully offline.

  • AWS · GCP · AzureMulti-cloud deploys, placed per region and per workload rather than per habit.
  • RackNerd & HerokuLean VPS capacity where cost matters, zero-ops containers where speed matters.
  • Cloudflare WorkersEdge auth, rate limiting and regional routing before traffic touches an origin.
  • Bare-metal fleetFifty machines we build and run ourselves, including fully offline, air-gapped systems.
  • DockerThe same image from laptop to production, and rollback in one step.
  • KubernetesOrchestrated fleets with rolling deploys, autoscaling and self-healing pods, on cloud or on our own metal.
  • HypervisorsProxmox, VMware ESXi, KVM and Hyper-V, carving our own hardware into isolated virtual machines.
05

AI & agents

7

Agents that call real tools instead of guessing.

  • LLM agentsTool-calling agents that search, quote, book and capture leads mid-conversation.
  • RAGAnswers grounded in a business's own website and documents, not the model's memory.
  • MCP serversModel Context Protocol servers that give AI agents real tools: browsers, databases, Telegram.
  • SpeechWhisper speech-to-text and neural text-to-speech for live voice agents.
  • Private inferenceOpen-weight models on our own GPUs with vLLM. Data never leaves the building.
  • Fine-tuningAgents fine-tuned on a business's own conversations and data, so they sound like the business and follow its rules.
  • Agent operationsWe help teams deploy, host, monitor and keep their own AI agents running, not only build them.
06

Hosting platforms

5

We have shipped to almost every host there is, so we choose on merit.

  • Render · Koyeb · RailwayPush-to-deploy services and workers when a project needs to be live today.
  • Vercel · Netlify · GitHub PagesFrontends, mini apps and static sites on global edge networks.
  • DigitalOcean · Linode · VultrPredictable droplets and VPS for long-running bots and relays.
  • Hetzner · OVHcloud · ContaboDedicated and high-memory servers at a fraction of hyperscaler prices.
  • Oracle Cloud · Fly.io · ScalewayFree-tier ARM capacity, regional edge apps and European hosting.
07

Automation

3

Jobs that run, retry and repair themselves overnight.

  • Web scrapingHigh-volume collection on our own hardware, with session and IP rotation.
  • Browser automationSelenium, Playwright and hardened headless Chrome for sites with no API.
  • Schedulers & watchdogsQueues, cron and supervisors that notice a silent failure and act on it.
08

Payments & security

4

Money and credentials handled like they matter.

  • Crypto paymentsOn-chain invoices, verified webhooks and idempotent settlement. Never charged twice.
  • Razorpay & UPICards, UPI and netbanking through Razorpay, with signed webhooks and the same never-twice settlement.
  • Session vaultsEncrypted storage for tokens and sessions, never baked into an image.
  • JWT & rate limitingSigned auth and per-client limits in front of every public API.
09

Caching & delivery

4

The fastest request is the one that never reaches the origin.

  • RedisHot caches, sessions, rate-limit counters, pub/sub and job queues, in memory and in microseconds.
  • CloudFront · Cloudflare CDN · BunnyMedia, downloads and static assets cached at the edge, close to every user.
  • Nginx · HAProxy · Traefik · CaddyReverse proxies, TLS and load balancing in front of every fleet.
  • RabbitMQ · Kafka · NATSMessage queues and event streams that absorb spikes instead of dropping them.
10

Observability & DevOps

5

If it is not measured, it is not running. We measure everything.

  • Prometheus · GrafanaMetrics and dashboards for every service, so a slow day shows up before a bad one.
  • Sentry · Loki · ELKErrors and logs collected in one place and searchable at 3am.
  • GitHub Actions & CI/CDEvery change tested, built and shipped by a pipeline, never by hand.
  • Terraform · AnsibleServers and cloud resources defined as code, so rebuilding a region is a command.
  • Linux · systemd · BashUbuntu and Debian servers tuned and run by people who live in the terminal.
11

Need something not on this list?

Most of our best systems started as a request nobody else would take. Tell us the problem; we will tell you plainly how we would build it and run it.

Message the developer →
06  Experience

We have run production Telegram infrastructure long enough to have solved the problems that only appear at scale: rate limits that escalate the harder you retry, sessions that expire silently, voice calls that fail between data centres, caches that poison themselves, and services that look healthy while quietly doing nothing.

None of it is theoretical
08  Questions

Asked and answered.

What does KustBots do?

KustBots (also written Kust Bots) designs, builds and operates Telegram bots, AI agents, APIs and the infrastructure behind them, used by more than 500,000 active users. The engineers who write the code are the people who run it in production.

Can KustBots build a custom Telegram bot for my business?

Yes. We build custom Telegram bots of every kind — moderation and anti-spam, music and voice chat, payments and Mini Apps — and we host and maintain them afterwards.

Do you build AI agents and chatbots?

Yes. We build AI sales and support agents that answer from your own data, book appointments and capture leads. We also fine-tune agents on your conversations and help teams deploy and run their own.

Can you host our bots, APIs and servers?

Yes. We run production hosting on our own 50-machine bare-metal fleet and on AWS, Google Cloud, Azure, Hetzner, DigitalOcean and more, with Kubernetes, Redis and CDNs in front.

Which payment methods can a Telegram bot accept?

Crypto, Razorpay, UPI, netbanking and cards, with verified webhooks, daily reconciliation and settlement that never charges a customer twice. See payment bots.

Do you offer web scraping and automation?

Yes. We run web scraping, browser automation and MCP servers on our own hardware, queued, retried and supervised.

How big are the systems you run?

Our bots serve more than 500,000 active users. Our link remover alone protects 81,300 groups, a single broadcast reaches 400,000 people, and we have deployed 9,703 apps through our own automation.

How much does it cost?

Websites start at $100 per page, animated sites are $200 per page and 3D sites $300 per page, with a full payment flow adding $600. Telegram bot features run from $50 for a simple command to $300+ for a complex one, and a ready-made music bot is a $100 setup plus $30 a month. See the pricing section.

How can I pay?

In US dollars, by crypto (USDT) or international bank transfer, with UPI and Razorpay for clients in India. Card payments through Stripe will be added once KustBots is a registered company. Work is invoiced in milestones against a written scope.

Can I try a music bot before paying?

Yes. Open @vcmusiclubot on Telegram, send /clone and your own bot token, and you get a working cloned music bot for free to test.

How do I get a quote?

Message @kustbhai on Telegram with what you need. Prashant answers himself, and every quote is fixed to a scope agreed in writing and valid for 30 days.