Hi, I'm Azizxon Bahodirov — Азизхон Баходыров. Full-stack developer — Next.js, React, TypeScript, Node.js, PostgreSQL: Next.js · React · TypeScript · Node.js · PostgreSQL.
Full-stack developer · Tashkent
Commerce sites, dashboards & APIs
Next.js · React · TypeScript · Node.js · PostgreSQL
- 3Systems in production
- 359/368Merchant-panel commits are mine
- 3Years in production
Available for freelance work · Noor · BUCHET.UZ
The short version
Full-stack, product first.
From the interface to the API and the database — one person owns the whole feature.
3 years in production.
1.5 of them at Noor, where 359 of 368 merchant-panel commits are mine.
I don't ship until I'm sure.
Edge cases and real data get tested before delivery, not after a client finds them.
Now learning Go.
For backend services. Heavy infrastructure I build together with a dedicated specialist.
What I've built
Different projects, different business needs. Some I can only talk about, the code belongs to a company. One's fully open, you can read every line. Another I'm building right now, in public.
Noor, operations and merchant admin systems
Three focused web systems with live order data, permissions, reports, courier logistics, WebSocket communication, and optimized route tracking.
BUCHET.UZ, website & admin support, solo RBAC build
Maintained the commerce flow and admin tools, then added roles, permissions, restricted navigation, reporting, banners, and multi-region operations.
Telegram Store (demo) — order system inside Telegram
A demo store that lives entirely inside Telegram: shopping, orders and sales analytics. Every business gets its own design and features built around its products and process.
Barber booking, Telegram Mini App & admin panel
A Telegram booking bot with service and time-slot selection, one-tap confirmation and self-service cancellation, plus a business-card landing page and an admin panel the barber runs himself.
Vocabulary, spaced-repetition word trainer
An open-source Next.js trainer with two independent SM-2 schedules, repository-based storage, and browser speech playback.
tg-notion-sync, Telegram to Notion finance automation
A small MTProto service that parses transaction messages, matches accounts, and writes structured records to Notion while leaving ambiguous categories for manual review.
Where I've worked
Reverse chronological — the places the cases above actually came from, not a resume for its own sake.
BUCHET.UZ
Frontend Developer, in-houseOngoing site and admin maintenance, plus RBAC built from scratch — roles, permissions, access-filtered navigation.
Noor
Frontend Developer, in-houseMerchant admin almost entirely mine (359 of 368 commits), plus principal architecture of the central ops panel and customer site.
What you can hire me for
Three packages, drawn from work I've actually shipped, not from a template. No prices here, we'll talk numbers once I understand what you need.
Online store development
A store customers can actually check out on, not another Instagram DM queue.
- Product catalog & cart
- Checkout — delivery or pickup
- Phone-based OTP login
Admin dashboard development
One screen to run daily operations from, instead of five chats and a spreadsheet.
- Order status pipeline, start to finish
- Role-based access — who sees what
- Live reports and tracking
Next.js maintenance and support
The system keeps working, and keeps getting a little better, without you having to ask twice.
- Hosting & monitoring
- Bug fixes
- One small feature or improvement a month
How we'd work together
Four clear steps, from a written brief to delivery through Contra milestones.
Scoping the problem
A written brief and an async conversation about what's actually broken today, not a feature wishlist. Half the work is figuring out what the MVP doesn't need yet.
Agreeing the MVP scope
A written scope: what's in, what's explicitly out, and a realistic timeline. No surprises about what "the app" was supposed to mean.
Building in phases, with demos
You see working software at each phase, not a status update. If something's off, we catch it at the demo, not after launch.
Handoff and support
The repository is yours from day one. After launch, I stay on for fixes and iteration through the support package, or hand off cleanly if you'd rather run it in-house.
Deliverables, milestones, and payment terms are set in the Contra proposal.
What I build with
By category, not by trend.
Notes from the Telegram channel
I write about the work as it happens: decisions, dead ends, and what I'm building this week.
Translated from Russian automatically, that's the language I write in.
Resume
The same story as this site, in two formats for quick sharing.
Questions worth answering before you ask
There's no fixed price list; it depends on scope. Once the scope is clear, I create a personal Contra proposal with deliverables, milestones, timeline, and payment terms, and payment goes through those milestones.
I say so as soon as I know, with the reason, not at the deadline. Phased delivery means you see working software early enough to catch a slip before it's a surprise.
You do. The repository is handed over, there's no separate fee to "buy the source code", it's yours from the start.
That's what the support package is for: hosting, monitoring, bug fixes, and a small improvement every month, so nothing depends on me being reachable at 2am.
Russian and English, both fluent enough for client work. I'm in Tashkent (UTC+5), which overlaps with European and Gulf-region clients during their morning.
Yes. I work across the whole product: interfaces, business logic, integrations, APIs and PostgreSQL. That product layer is where I'm strongest. Complex infrastructure, such as DevOps-heavy setups or high-load systems, I do together with a dedicated specialist.
For most web products, yes: the customer-facing side, the admin panel, the API and the database. If the project needs complex infrastructure, I bring in a dedicated specialist for that part and say so up front. I work in phases, a working MVP first and then iteration, and I can usually start as soon as the scope is agreed in writing.
Work with me through Contra
Describe the project in writing. After we agree on the scope, I will create a Contra proposal with deliverables, milestones, timeline and payment terms.
Describe your project
Send the details in writing through the brief, Telegram, or email.
Or by email: hello@untra.dev