Turning business vision into systems that scale.
I'm Dzmitry Harupa, Head of Architecture. 17 years of high-load systems, 10 of them in iGaming. I design architecture, take AI/ML to production and still write code myself. TOGAF, SAFe and AWS certified. 100% remote.
Four ways to start.
From a one-off consultation to a fractional CTO role — pick the depth you need now.
Advisory sessions
Architecture reviews and roadmap sessions. One call — specific recommendations.
- Free 30-min intro call
- Deep advisory session (90 min)
- Expert consulting packs
POC & delivery
From concept to a working prototype. Architecture documentation is part of the result.
- POC Starter: scope & architecture
- POC Build: working prototype
- Architecture package with ADRs
Ongoing partnership
Technology leadership part-time: from monthly advisory to a full CTO roadmap.
- Advisor Lite: monthly guidance
- Strategic CTO advisor
- Fractional CTO: full roadmap
Workshops & training
Hands-on workshops for your team: architecture, AI/ML, working with ADRs.
- Architecture workshops
- AI/ML strategy sessions
- Remote & on-site
Strategy through code — one architect, the whole stack.
Enterprise architecture, AI/ML and ten years of iGaming domain knowledge — hands-on, in code.
Technology strategy & roadmap
- IT strategy aligned with business goals
- Product roadmap
- TCO optimization & FinOps
Cloud & enterprise architecture
- AWS, GCP, Kubernetes
- Microservices & event-driven design
- TOGAF enterprise architecture
AI/ML strategy & implementation
- AWS Bedrock, SageMaker
- LLM, RAG & AI agents
- AI process automation
High-performance development
- Go, TypeScript, Python, C++
- SAFe & Lean-Agile delivery
- DevOps and CI/CD pipelines
iGaming expertise
- Platform architecture: PAM, payments
- Game math, RNG development
- Regulatory compliance
Documentation & standards
- Architecture Decision Records (ADR)
- Technical specifications
- Team standards & guidelines
Senior expertise without a full-time hire.
Cost effective
Senior-level expertise without a full-time salary and overhead.
Flexible scale
The scope changes with your needs. You pay for hours, not a seat.
Fast start
Hiring a CTO takes months. Here the first call is this week.
Low risk
Start with a free consultation. A retainer comes after you see results.
Hands-on delivery
Working prototypes, executable architectures, code in production.
100% remote
Flexible timezone coverage and async communication.
Outcomes you can measure.
AI call-center automation
>$1.2M saved per year on AWS Bedrock & SageMaker.
NATS event mesh at scale
200K+ msgs/sec across 1000+ systems, <100ms p99 latency.
Monolith → microservices
40% of transactional load migrated; release lead time down 57%, deploys under 15 minutes.
Decisions on data. Results in numbers.
An architect who stays until it ships.
Ten years in iGaming: Casino, Sports, Poker, PAM, payments and CRM. Production AI/ML on AWS Bedrock, SageMaker and LangGraph.
I grew an architecture practice from 6 to 12 architects plus 20 system analysts, mentored three of them to Head-of-Technology roles and led 200+ engineers. I still write production code.
Notes on architecture and AI.
What I work with: architecture, AI/ML, iGaming.
My Architect, part 11: eight hundred commits I didn't write
Not a demo but a live project — a video pipeline with 802 commits in 78 days, with a front end, a back end, video rendering, Python sidecars and five model vendors, and my_architect holding it all together. Inside: the real numbers from the tracker (650 nodes, 296 requirements, 63 RFCs), how a requirement is wired to a commit and a test through a coverage gate that fails the build, why I draw HTML wireframes before any code, what commit timestamps actually measure in the story of “I hand a task over at night and by morning it's done” — the day has two humps with the night between them, and morning commits are twice the size of daytime ones — and why all of this opens a door for teams instead of closing it.
ReadFrom canvas to studio: a reusable library, parallel runs and auto-packaged clips
Earlier the canvas assembled a single clip. Now it has a name — Vini Studio — and it grew from a graph into a workspace where I can turn out clips in batches. Inside: why the element library and the render cache are one mechanism over an artifacts table; a prompt manager with system and personal templates; a node that compresses the previous episode into ~1000 tokens of memory; parallel runs and the topological-sort bug that made scenes start before the scriptwriter feeding them; subtitles built not from my script but from what was actually said on screen; a design system I generated with a single prompt, and packaging rendered in Remotion. Plus an honest look at the numbers — twelve dollars a clip and 22% full-watch retention.
ReadKeeping the same characters across AI clips: universal elements instead of the first frame
In episode two of "Sheriff Potato" the cast grew, and the first-frame trick stopped carrying it — to keep characters from drifting between scenes I moved the canvas to references, my "universal elements". Inside: why video models force you to choose between a first frame and elements (and why Kling is the exception), what 8 seconds cost on Grok, Gemini and Seedance, the 480p trick, ImageRef tags and characters' distinguishing marks. Plus an honest look at scene-six bugs — and the finished episode at the end.
ReadTell me what you're building.
Describe the problem in a couple of paragraphs — or skip ahead and book a free 30-minute call.
Free 30-min strategy call
calendly.com/d7561985 · no commitment