What we build with it
PHP is not what we would pick for a greenfield backend, and we will say so plainly. It is, however, what a large share of working software already runs on, and a product does not get rewritten because a new team arrived.
So our PHP work is mostly integration and extension: adding endpoints an existing system needs to serve a new mobile client, tightening what is already there, and building the Flutter or Vue front end on top without demanding a rewrite underneath.
Where we have shipped it
The white-label cashback and loyalty platform has a PHP backend serving the merchant tooling and the 15+ branded mobile apps built from a single Flutter codebase.
When we recommend it
When it is already there and working. Replacing a functioning PHP backend is usually the most expensive way to get the least visible improvement, and modern PHP with a maintained framework is a perfectly reasonable place for a product to live.
For a new backend we would reach for Go, Python with Django, or Rust depending on the workload — not because PHP cannot do the job, but because our team is deeper in those and you should be staffed by people working in their strongest language.
