I'm Dmitrii Lutskov, an architect for complex, data-heavy systems: high-load e-commerce, geospatial platforms, network infrastructure, database integrations. I plan, architect, and direct delivery, and I'm drawn to any problem hard enough to be worth taking apart. Project, advisory, and consulting work.
I work as supervisor, architect, and lead, directing AI agents on execution. I use the best tool for each task. If designing or delegating gets a better result faster, I do that. When the agents fall short, I go deep myself.
That last part is not theory. On a hard Kubernetes ingress problem the models kept producing nonsense, so I took it apart by hand, used targeted queries only where they actually helped, and mapped, understood, and fixed it in three days. The fundamentals are still there. The AI is a lever, not a crutch.
The real bottleneck in good software was never typing. It is judgment: which design survives scale, which shortcut becomes next year's outage. That is what three decades of building gives you, and it is what a model does not have on its own.
These are where I'm deepest. They are examples, not a fence; I take on hard systems of many kinds.
Since 2009 owning the technical side of an online store with 60,000+ SKUs. Codebase, automated pricing and supply chain, infrastructure, and the marketing analytics on top.
I came into GIS on the vendor side, developing on and deploying a commercial platform in the class of ESRI, so I know the machinery, not just the APIs. I now build on the open-source stack: portals, routing, tiling, and the spatial databases underneath. FME and data integration are a standing interest.
Monitoring systems, client-server platforms, and DNS infrastructure, including a full-featured DNS service with DDoS and bot protection.
Full-stack systems and APIs since the early web. Backends, payment and platform integrations, and the database work underneath.
A timeboxed review, about three days deep in the repository and logs. You get a written report: the critical risks and a step-by-step stabilization roadmap. This includes rescuing AI-generated codebases that ran in a demo and broke under real load.
Ongoing technical direction for a founder or team. Architectural decisions, infrastructure, and development process, without a full-time hire.
A system designed and delivered end to end, with AI-directed execution, when you need the thing built and not only advised.
Project, advisory and consulting only, not staff roles. I work primarily async: written specs, code, and recorded walkthroughs, with calls as needed.
Anonymized engineering case studies. The architecture, stack, and engineering are real.
One of its market's longest-running online electronics retailers: a Rails core, a C# ERP integration, and automated pricing across a dozen-plus supplier feeds. About 60,000 SKU at 99.8% uptime, run by one engineer.
Built end to end, from a hand-written C socket listener that speaks the device protocol, through PostGIS and a real-time backend, up to the Flutter apps and a live map.
A layered defense in front of customer sites: authoritative DNS, an external layer for L4 and volumetric attacks, and an internal senginx protector doing L7 bot mitigation, whitelists, and port forwarding.
Took over a raw e-commerce platform after the previous team left and reworked it over three years, from falling over near a thousand users to tens of thousands of concurrent live users, on Kubernetes.
"He consistently delivers significant results with minimal supervision, often succeeding where others would require considerably more support. Reliable, straightforward to work with, and committed to high professional standards. I recommend him without hesitation."
Business development director · enterprise GIS · ~20-year collaboration
"Dmitrii goes into every question with detailed attention. I would come away with one or more solution paths, each step explained. Very high competence, and high professional ethics. Always open to communication."
Enterprise GIS client · FME data-integration project
Tell me what you're building, or what's breaking. I reply by email, usually within a day.