Aliaksei P.Private profile: Upwork shows its earnings only to signed-in members, so we check it every few weeks, not daily. MRR here is a rough estimate (Upwork's six-month earnings ÷ months active). Last read Nov 5, 2026.

I take over PHP applications that other people built years ago and make them safe to run and cheap to change. Most of my work starts the same way. A business depends on a PHP system that still works, but nobody wants to touch it. The original developers are gone, the framework is three or four major versions behind, and every deployment feels like a gamble. Recent migrations: * PHP 7 to PHP 8.2 on a production SaaS platform * Symfony 2 to PHP 8.1 on a live application * Symfony 4 to Symfony 6, currently in progress * A custom in-house framework brought up to PHP 8.2, followed by ongoing work for the same client that is still running today That last one is the pattern I care about most. The upgrade is usually not the end of the engagement. My three largest contracts are 2,600+, 1,550+ and 580+ hours with single clients, and two of them are still open. Clients keep me because once the migration is done, I know the codebase better than anyone else available to them. How I work: * I read the code before quoting anything, and I tell you what I found, including the parts that worry me * Changes go in small reviewable steps, never one giant rewrite branch * I add tests around the behaviour I am about to change, especially the paths that fail * I use AI tooling daily (Claude Code in PhpStorm), but every line that reaches your repository is one I understand and can defend Stack: PHP 5.x through 8.x, Symfony 2 to 8, Laravel, Doctrine, MySQL, PostgreSQL, REST APIs, RabbitMQ, Docker, GitLab CI, Jenkins. Also Mautic and Sylius, where I have gone deeper than most. Send me a repository link, or just describe what you have. I will take a look and tell you what I think it involves before either of us commits to anything, at no charge. If it is not a good fit, I will say so.