vi4 Build Log

What I build

Working software, shipped in days.

I build Telegram bots that handle money and schedules, fast storefronts, and the Linux boxes they run on. Everything below is something I have built and run myself, not a course certificate. Fixed price per scope, half up front.

Telegram bot

from $250

Sales funnels, paid subscriptions, scheduled broadcasts, admin panel, CSV export. Crypto or card payments.

3–6 days

Landing page / storefront

from $400

Next.js, real catalog with filters and product pages, orders delivered into Telegram or WhatsApp.

5–9 days

Server setup & deploy

from $150

A VPS from bare to serving: Docker, systemd units, Caddy with TLS, Cloudflare, health checks, restart-safe services.

1–2 days

Scraper / automation

from $200

Python collectors that get past anti-bot pages, run on a schedule, and write to SQLite, CSV or an API your app can read.

2–5 days

Selected work

Three builds, with the parts that were actually hard.

Course funnel bot

In production Python · aiogram 3

A whole sales funnel inside one bot: deep-link attribution per ad creative, registration with an instant gift, a three-day warm-up sequence, webinar reminders at −24h / −1h / −5min, then the offer and two deadline pushes. The admin runs the entire launch from chat commands.

20 msg/secBroadcast rate, backing off on Telegram’s own RetryAfter
Restart-safeJobs persist in SQLite, so a reboot never drops a scheduled send
0 redeploysWebinar date and seat count change live from an admin command
Self-pruningUsers who block the bot are flagged on error and skipped later

Python 3.12 · aiogram 3.15 · APScheduler with SQLAlchemy job store · aiosqlite · Docker + systemd

AYBOND storefront

Demo build Next.js 16

A redesign I built on my own initiative for a five-store menswear chain, to show instead of tell: catalog with filters and sorting, product pages with real size tables, a store picker by city, and checkout that hands a pre-filled order to WhatsApp. Their live site was a free template with placeholder prices.

5 storesFilterable by city, each with its own hours and contact
0 cookiesNo third-party requests at all — fonts self-hosted, no analytics
Size-awareThe chosen size travels into the WhatsApp order message
CompliantSeparate privacy and consent pages, per local data law

Next.js 16 · Tailwind 4 · Motion · Vercel — live at aybond-demo.vercel.app

Multi-node proxy network

Retired Linux · Xray

A two-country VLESS network behind a single control panel, with a Telegram bot selling access for crypto. Each user got one subscription link carrying eight configs, so their client could pick the fastest route by itself. It ran unattended for months.

2 nodesOne master holding panel and database, one pure forwarding node
8 configsPer subscription link — REALITY, gRPC and WebSocket behind a CDN
60s checksBackground watcher paging the admin chat when a node dropped
Crypto billingInvoices and renewals handled in-bot, no manual steps

Debian · Docker · Xray-core · Marzban · Caddy · Cloudflare · aiogram · CryptoBot API

Stack

What I reach for.

Backend

Python 3.12, asyncio
aiogram 3 (Bot API)
APScheduler, persistent jobs
SQLite, aiosqlite, SQLAlchemy
FastAPI

Frontend

Next.js 16, React
Tailwind CSS 4
Motion, GSAP ScrollTrigger
Plain HTML and CSS when that is enough

Infrastructure

Debian and Ubuntu VPS
Docker, docker-compose
systemd units, journald
Caddy, Nginx, TLS
Cloudflare, Vercel

Payments

CryptoBot API (USDT, TON)
Telegram Stars
Invoice and renewal logic

How it works

Terms, in four lines.

Scope first. You describe the job, I come back with a fixed price, a deadline, and what is explicitly out of scope. No hourly guessing.
Half up front, half on delivery. Paid in USDT (TRC-20 or TON). Above $600 we split it into milestones instead, so neither of us carries the whole risk.
You get the source. The full repository, deploy instructions, and the server it runs on, configured. Two rounds of fixes included after delivery.
I say no when it will not work. If the idea has a hole in it, you hear that before you pay, not after.