DEMONSTRATION

VOLYA.

Free internet through Telegram: the user messages the bot and connects in ten seconds — no registration, email or payment details.

bash — volya
VOLYA — interface snapshot

VOLYA — interface snapshot

10 sec
to a working connection
5
interface languages (RU · EN · UA · KZ · 中文)
0
activity logs
5
referral program tiers
3
speed tiers

A demonstration project, currently paused. The service ran in open beta with free access; the entire infrastructure was a single ARM server: access delivery, the website, and both environments (prod + staging).

// THE CHALLENGE

A VPN that doesn't get blocked — and that an ordinary person can use

Classic VPN protocols are visible to deep packet inspection (DPI): they're recognized by the connection's "fingerprint" and shut down. A service that gets blocked within a week is useless.

The second issue is the barrier to entry. Usually you need an account, an email, a card, a downloaded client, and a config entered by hand. At every step some people drop off, and support drowns in the same repeated questions.

// THE SOLUTION

A protocol that looks like an ordinary website. Entry — through a messenger

At its core is VLESS + Reality: the connection is disguised as ordinary HTTPS to a real third-party website. To an observer it's indistinguishable from regular traffic and shows no signs of a VPN.

The entire user journey lives in a Telegram bot: it issues a personal key, tracks traffic and devices, watches for abuse, and hands out bonuses for invited users. No registration, no email, no payment details.

// THE USER JOURNEY

Three steps and ten seconds

The most expensive part of any service is the moment a person first tries to use it. Here it's reduced to three actions in a messenger that's already installed.

01

Get a key

The user messages the bot and immediately gets a personal key link. No form, email or password.

02

Install the app

The bot hands over a verified link to a client for your platform — not third-party builds or dubious installers.

03

Connect

The key opens with a single tap — the config loads on its own, nothing needs to be entered by hand.

// WHAT'S INSIDE

A service like this lives at the intersection of three tasks: it must not be blocked, it must not be abused, and it must grow without an advertising budget.

01

DPI-resistant protocol

VLESS + Reality: the handshake is forged to mimic a real third-party website, and the server's real address is hidden behind Cloudflare. The traffic is indistinguishable from ordinary HTTPS — the service isn't blocked.

02

Speed tiers

Three entry points on different ports: the tier is the connection port, and blocking one entry point doesn't kill the whole service. Access levels and the referral program live inside the bot.

03

Handling abuse

A background monitor runs a ladder: a warning at 80% of the limit, then a strike, then a suspension — with the right to appeal directly in the bot. One violator doesn't spoil the service for everyone else.

04

Operations

A health check every 15 minutes, a daily backup, a rollback to the previous version with a single command. Failures don't surface through complaints.

Speed tiers — through separate ports

Instead of throttling each user individually, the server runs three independent entry points. The port a client connects to is its tier — changing tiers comes down to issuing a different key, with no settings to edit and no restarts.

T1
Basic
Mbit/s
T2
Extended
Mbit/s
T3
Maximum
Mbit/s

What went into the project

From the protocol to operations — everything the service needs to run itself and be handed over.

Frictionless entry

no registration, no email, no card. The messenger a person already has installed is the service's entire front desk.

A panel right inside Telegram

your account opens as a Mini App: traffic, devices, tier and diagnostics without installing a separate app.

A referral program

five tiers, eleven achievements, an anonymous leaderboard, and protection against gaming via an invitation limit.

Self-healing

if a key disappears on the panel's side, the bot notices on the next request and issues a new one. No support ticket.

Prod and staging

two independent environments on one machine with separate databases: updates are tested on a staging bot without touching live users.

A legal framework

terms of use, a data retention policy, and a procedure for responding to complaints are all worked out. The service doesn't operate in a legal vacuum.

Five languages

the website and bot in Russian, English, Ukrainian, Kazakh and Chinese. The texts are externalized and can be extended without touching the logic.

Invitations instead of an advertising budget

  • 01Five levels of participation: the more people you invite, the higher the tier and the more substantial the bonuses.
  • 02Rewards that matter: extra traffic, more devices, higher speed — not abstract points.
  • 03The bonus is credited not for a click, but when the invited user actually starts using the service.
  • 04Eleven achievements and an anonymous leaderboard — competition without revealing participants' identities.

What changed

git diff — FOR THE USER AND THE OPERATOR
− Registration, email, payment details
+ A key in Telegram in 10 seconds
− VPN traffic is visible to DPI and gets blocked
+ Indistinguishable from ordinary HTTPS (VLESS + Reality)
− One violator spoils the service for everyone
+ A ladder of warnings and an appeal
− Failures surface through complaints
+ Monitoring, backups, rollback with a single command

The result

  • A working service: the protocol, access delivery, the website, and operations — all built and launched.
  • Connecting takes seconds and requires neither an account nor payment details.
  • Abuse is handled automatically — with a warning and the right to appeal.
  • The service maintains itself: monitoring, backups, rollback, and separate environments.
//

OTHER SYSTEMS IN PRODUCTION

CASE 01 — eRENTAL · Cinema and photo gear rental platform · BudapestCASE 02 — US car calculator · Duty, excise, VAT and shipping · 5 countries · TG + WEBCASE 04 — YOURS · The next one on this list could be your task · $ DISCUSS_TASK →

Need a product, not a pile of pieces?

Here one person covered everything: networking, backend, bot, website, and operations. If your task needs the same breadth — let's talk it through.

new_request.form

© 2026 IHOR.WORK · ENGINEERING FOR GROWTH · EXIT CODE: 0