Staged migration to Laravel
The legacy PHP monolith moves to Laravel piece by piece, behind feature flags: new code is switched on gradually and can be switched off instantly.
- Feature flags
- Tests on the money paths
- Instant switch-off of a change
E-commerce
An 800-thousand-item catalogue, 300–400 thousand users a month and a mobile app. We run the whole platform: backend, frontend, integrations, CI/CD and production support.
The problem
The platform runs under live load every day: hundreds of thousands of users, a large catalogue and orders that pass through accounting, the warehouse, delivery and payment. Sales depend on every one of these links.
At the same time, its core is a legacy PHP monolith. It has to move to Laravel without stopping the business or breaking the money paths, while the mobile app and the integrations keep evolving.
Technology
The solution
The legacy PHP monolith moves to Laravel piece by piece, behind feature flags: new code is switched on gradually and can be switched off instantly.
ERP and warehouse over RabbitMQ, CRM over REST and OAuth, plus WMS, carrier APIs and payments with bank acquiring and instalments.
A Flutter app for the App Store and Google Play, and the API behind it.
Security layers against attacks and intrusions on top of the platform and its integrations.
AI agents are part of daily development: their own settings for each project, tasks from written specifications, automatic checks of every change against real examples, AI cost tracking and protection of passwords and access keys.
Today
The platform is in production and under continuous support. The migration continues: new parts ship behind feature flags, money paths are covered by tests, and releases go out without stopping the business.
Contacts
Tell us in two paragraphs what's not working. We will tell you whether we take it on and where we suggest starting. Meetings online, or in person in Uzhhorod or Kyiv.