Trusted by market leaders in Uzbekistan
Your bot runs around the clock on a server in Uzbekistan. Public IPv4 for webhooks, any stack: Python, Node.js, Go. Billing in UZS, with invoices and closing documents for your accounting.
Trusted by market leaders in Uzbekistan
From a simple auto-responder to a store with payments and an admin panel.
Catalog, cart, payment via Payme and Click, manager notifications. Orders and customer contacts stay in Uzbekistan.
Handling requests, CRM integration, mailing to your database, on-duty team incident alerts. The bot works without downtime for restarts.
Requests, approvals, and access to reports and dashboards for employees. Such a bot can be closed off in a private network without exposing it to the public internet.
Processing requests through language models, file recognition, task queues. GPU infrastructure connects right next to the server as load grows.
Start with a single server and move on as your audience grows, without changing your code.
| Single server | Server plus managed PostgreSQL | Managed Kubernetes | |
|---|---|---|---|
| Best for | first bot, MVP, small audience | a working bot with orders and payments | multiple bots and services, frequent releases |
| Where data lives | database on the same disk | managed PostgreSQL with automatic failover | managed PostgreSQL |
| Backups | snapshots or Backup as a Service | automatic, on a schedule | automatic, on a schedule |
| Bot updates | manual deploy or via CI | deploy via CI, database untouched | rolling update with no bot downtime |
| Scaling | vCPU and RAM change in the panel | server and database scale separately | automatic, based on load |
| Who administers | you | we manage the database, you manage the server | we manage the control plane |
| Price from | 208,000 UZS/month | depends on configuration | 500,000 UZS/month for the control plane |
Exact cost in UZS, VAT included. Start with the minimum and add resources as your audience grows.
Developers
Root access, any version of Python or Node.js, Docker, systemd, cron. Set up your environment the way you're used to, with no need to adapt to someone else's panel.
Studios and contractors
Isolate projects with containers, pay with a single invoice in UZS, and get closing documents for a legal entity for each contract.
Business
Orders, payments, and customer conversations run through the bot, so downtime costs money. 99.95% SLA, automatic restart on a standby node, and 24/7 support in Russian and Uzbek.
The price doesn't depend on the exchange rate. We sign the contract with an Uzbek legal entity and send invoices and closing documents online.
A static address is connected right when the server is created. You install SSL and configure the webhook, and Telegram delivers updates instantly, without constant API polling.
Any Linux distribution you choose, root, Docker, process managers, your own database. Long-running processes are not restricted in any way.
If the physical server fails, the virtual machine automatically restarts on a standby node. Users never notice an interruption in the bot's work.
vCPU, RAM, and disk change in the panel and apply almost instantly. There's no need to reinstall the system or migrate the project.
Conversations, phone numbers, and order history are stored in data centers in Uzbekistan. This meets LRU-547 requirements for personal data.
Create a server in the panel, choose an Ubuntu or Debian image, and get SSH access — this usually takes a few minutes. Then deploy your project the usual way: clone the repository, set up the environment, or launch a ready-made Docker image. For webhooks, add a public IPv4 and issue a certificate. You can keep the database on the same server or move it to managed PostgreSQL, and store media files and logs in S3 object storage.
Calculate a Configuration
Find answers to common questions about our services.
A bot with a small audience is fine with 2 vCPU, 2 GB RAM, and a 20 GB disk — that's 208,000 UZS per month, VAT included. If the bot works with a database, queues, or processes media files, take 4 GB RAM. Resources can be added at any time, so starting with the minimum is safe.
No. Hosting is designed for websites and doesn't allow you to keep a continuously running process, which a bot needs. You need a cloud server with full access.
Yes, for working via webhooks: Telegram needs to reach your server at an address with a valid SSL certificate. With long polling, the bot queries the API itself, so a dedicated address isn't formally required, but a webhook saves resources and gives lower latency.
Anything you like. Python with aiogram or python-telegram-bot, Node.js with telegraf, Go, PHP, Java. You get a clean Linux server with root access and install whatever versions you need yourself.
Billing is in UZS, invoiced to a legal entity. We send closing documents electronically through EDF systems.
In data centers in Uzbekistan. If the bot collects phone numbers, names, or order history, local storage satisfies LRU-547 requirements for personal data.
The virtual machine automatically restarts on a standby node in the cluster, with no administrator intervention required. Scheduled backups add another layer of protection.
First we increase vCPU and RAM without stopping the server. Then we move the database to managed PostgreSQL, files to S3, and put multiple bot instances behind a load balancer or on Managed Kubernetes.
Tell us what your bot does and how many users it has. We'll suggest a configuration and calculate the cost in UZS.
