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 node canvas for video: building a whole clip on a single graph
The first three parts took the pipeline apart piece by piece — the LLM for the scriptwriter, the video model, the storyboard. Here I show the whole canvas at once: my own node editor on litegraph and the ComfyUI core, where Claude writes the script, characters live as reusable "souls", and the "one frame → video" trick holds a scene's opening. Plus the first clip the canvas assembled on its own, and the "cabbage hat" bug that taught me the most.
ReadMy Architect, part 10: a repo memory for the agent — a code graph it's not allowed to trust
The recursive-context story continues: four releases in one day teach the agent a persistent code graph (Graphify) under strict distrust rules — freshness gate, facts only from live files. Plus a controlled A/B test of graph vs grep on NestJS: −71% tokens on subsystem understanding, parity elsewhere — and the hidden sub-agent costs that make naive benchmarks lie.
ReadMy Architect, part 9: Recursive context — teaching the agent to admit what it hasn't read
From MIT's Recursive Language Models paper to the recursive-context skill in one day: why a huge context window doesn't solve big data, how a fan-out of isolated sub-agents with honest coverage replaced a Python library, and what only live runs could catch — from a baseline that turned out too good to a 14-millisecond bug.
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