Software that's been finely tuned.
I build and rescue enterprise web applications — Drupal platforms that have survived million-record migrations, Symfony products built from the schema up, and legacy systems everyone else had written off. 15+ years of making complex software work as intended — properly.
Most consultancies sell you a process. I sell you the bit that comes after the process: working software. It is, I'm told, the harder part.
A handful of finished projects.
Read each one like a quick spec. The interesting numbers live inside.
Three ways to engage.
All of them involve making things better. None of them involve the word 'synergy'.
Strategic Partnership
Thinking before building. Revolutionary, I know.
I join as a fractional CTO or technical lead — running discovery workshops to validate assumptions, reviewing architecture before it becomes technical debt, evaluating tech stacks against actual requirements (not hype cycles), and setting up CI/CD pipelines so your team ships confidently. I've done exactly this for a European insurtech: stabilised a platform that needed restarting every few days, fixed years-old bugs, and stood up the QA and delivery function it never had.
- Product definition & PoC validation
- Architecture reviews & tech audits
- Business process mapping
- Fractional CTO engagement
Enterprise Development
If your neighbour sees it, they’ll want one themselves.
Drupal 10/11 platforms with proper content modelling, custom entity types, and headless JSON:API delivery. Symfony products built from the schema up — modular monoliths with API Platform and Doctrine, the way Nightshelf is built. Drupal runs on Symfony, so it's one foundation, not two. The kind of system where adding a feature takes days, not weeks — because the architecture was right from the start.
- Enterprise Drupal DXP & headless CMS
- Symfony + API Platform products (e.g. Nightshelf)
- Commerce: Drupal Commerce · PrestaShop · WooCommerce
- CI/CD pipeline setup (GitHub Actions)
- D7 → D11 migrations with data integrity
Legacy Rescue & Modernisation
Your code’s not dead. It’s just resting.
Step one: containerise with Docker so we can stop the bleeding. Step two: forensic analysis with PHPStan to map complexity and find the landmines. Step three: runtime tracing with Blackfire to find where the actual bottlenecks hide. Step four: document everything so the next developer doesn't need archaeological training. I've taken a legacy WordPress community from a PageSpeed of 31 to 89 and migrated a backend off end-of-life PHP 5.6 without breaking the apps in the field. Yours is probably fine.
- Dockerisation & environment isolation
- PHPStan + Blackfire code forensics
- Strangler-fig incremental rewrites
- Documentation & knowledge transfer
The one who once rewrote the whole caching layer — for fun.
Most bad requirements are just poorly articulated existential dread about scalability.
I fix both — the requirements and the dread.
I'm a senior engineer and technical consultant specialising in enterprise PHP — specifically the Drupal and Symfony ecosystems. Since 2008 I've been building content platforms, complex backends, and rescuing legacy systems across healthcare, insurtech, pharma, public sector, e-commerce and social platforms. Based in Ukraine, working worldwide.
The work sits at the intersection of architecture and delivery. I write production code, set up CI/CD pipelines, profile database queries, and debug that weird caching issue that only appears on the third Tuesday of months ending in ‘y’.
"Tooning" — like automotive tuning. Every system can perform better with the right adjustments. I just happen to tune software instead of engines. And, full disclosure, also engines.
Things I've been writing.
Beside the code, that is.
Let's tune your project
Got a project that needs proper engineering? A system held together with hope and duct tape? A genuine architectural puzzle? Write me a note.
I read every message personally. If it's interesting, you'll hear back. If it involves the word 'synergy' more than twice, you might not.