Work

Four projects,four different reasons.

One is a release scanner I built to answer a question a score cannot. One was built for a paying client, one for a lounge bar, and one started at a hackathon and did not place. Each case study covers what I built, the decisions behind it, and what went wrong.

Index

Four systems

Move between them and the drawing rearranges rather than restarting: the same nodes, in the shape each project actually took.

ALT QRRelease quality scanner · 2026 · Runs locally
1. A target URL is crawled inside a bounded, same-origin envelope
2. Each page produces typed evidence: HTTP, DOM, accessibility, console, and network
3. Fixed rules turn that evidence into findings with stable fingerprints
4. The baseline scan is compared to classify new, fixed, changed, and regressed findings
5. A release gate checks score, critical findings, broken pages, and broken links
6. The verdict is ready to ship, ready with warnings, needs attention, or blocked
99 AKTAUCommercial website · 2025 · Completed
1. Guest chooses a hall and sends a request
2. The request is stored with a status
3. An authenticated administrator reviews it
4. Accept, reject, or delete writes back
5. The guest sees the status that was set
TUESDAYHospitality website · 2026 · Live
1. Venue and atmosphere
2. Menu
3. Location and contacts
4. Table enquiry
5. On mobile the practical content moves up
MANGYSTAUHackathon prototype · 2026 · Prototype
1. Budget, days, interests, transport
2. One route is ordered from those inputs
3. The map reads that route
4. The location list reads the same route
5. Map and list share one order

Records

What each one is

01
ALT QR
Release quality scanner · 2026 · Runs locally
A deterministic release scanner that turns a website into evidence, then decides whether that release is allowed to ship.
My role: Scanner architecture, Rule and scoring model, Release gate and verdict logic, Cross-scan comparison engine, SSRF and request safety, Test and reliability suites.
- Source on GitHub
- Fixed rules, no model inference
- Unit, scanner, reliability, and E2E suites
- Overflow checked 320 to 1440
- Optional Supabase mirror
- Next.js
- TypeScript
- Playwright
- Chromium
- axe-core
- Lighthouse
- Zod
- Supabase
- Docker
Read the case study Source(opens in a new tab)
02
99 AKTAU
Commercial website · 2025 · Completed
A website for a PlayStation club, with guest booking requests and an admin area to manage them.
My role: Interface design, Responsive frontend, Supabase integration, Admin authentication, Booking statuses, Deployment setup.
- Built for a paying client
- Live in production
- Source on GitHub
- Supabase database
- Admin authentication
- Next.js
- TypeScript
- Tailwind CSS
- Supabase
- Vercel
Read the case study Visit website(opens in a new tab)Source(opens in a new tab)
03
Tuesday Lounge Bar
Hospitality website · 2026 · Live
A venue website for Tuesday Lounge Bar, built so the menu, location, contacts, and table enquiry stay one tap away.
My role: Page structure, Responsive interface, Frontend development, Menu and contact paths.
- Live in production
- Source on GitHub
- Mobile-first layout
- Russian and Kazakh
- Next.js
- TypeScript
- Responsive CSS
- Vercel
Read the case study Visit website(opens in a new tab)Source(opens in a new tab)
04
Mangystau Trials
Hackathon prototype · 2026 · Prototype
A travel-planning prototype for the Mangystau region, built during a hackathon. It did not reach the final.
My role: Product idea, Page structure, User flow, Route interface, Map, Frontend development.
- Prototype, not a finished product
- Deployed and reachable
- Source on GitHub
- Next.js
- React
- TypeScript
- Map interface
- Vercel
Read the case study Open prototype(opens in a new tab)Source(opens in a new tab)

Need a website?

Send a short description of the project, the pages you need, and any examples you like. I will read it and reply with questions.

Start a project GitHub

ALT QR

99 AKTAU

Tuesday Lounge Bar

Mangystau Trials

Need a website?