Leave PHP without freezing the product.
Your users stay on the PHP app while it is replaced one path at a time, in Go, Rust, Python, .NET, or Node.js. A one-page PDF gives twelve checks: pin what the PHP app does, replace it path by path, and pick a stack someone on your team will own.
Get the one-page PDFPin
The PHP app is the spec. What it does in production, including the behavior nobody wrote down, is pinned in tests before a line of the replacement is written.
Replace
One path at a time, behind a proxy. Users stay on the PHP app until their path is replaced, and every replaced path has a way back.
Own
The target stack is chosen by who will run it in 18 months. One person on your team is named for each replaced path, and hiring can stay open for the person who operates it after.
What is in the PDF
Twelve checks. One page. Four to pin what the PHP app does, four to replace it without a cut-over weekend, four for the stack and the people who own it. Three are below. The other nine are in the PDF.
Pin
Each path that stays has a parity test: the same recorded request goes to the PHP app and to the replacement, and the responses are compared. The PHP app is the spec.
Replace
Users stay on the PHP app until their path is replaced. A proxy in front routes one path at a time. Nobody waits for a cut-over weekend.
Own
The target stack is chosen by who will run it in 18 months, not by a benchmark. If nobody on the team writes Rust, Rust needs a hire before it needs a port.
The architecture is led by practitioners like Alexey Kichin. His prior work is enterprise architecture across banking and FinTech, including six years at Deutsche Bank.
Email me the checklist
One page, PDF, free. The link is on the next screen and in your inbox. One email. We do not start a sequence from this form.
The checklist is ready.
Download the PDF. The same link is on its way to your inbox. A 30-minute scoping call is optional — reply to that email if you want one.
PHP is the problem.
Sometimes. Check 10 asks for the baseline first: p95 latency and cost per request on today's traffic. If two endpoints are the trouble, the first milestone can replace those two and stop there.
We will rewrite it from scratch.
A ground-up rewrite freezes the product until the new one does everything the old one did, including what nobody wrote down. One path at a time keeps users on a working product the whole way.
An agent can port it.
Coding agents can write a lot of the port. They cannot tell you whether it behaves like the PHP app. The parity test in check 2 can, and it decides what ships.
Common questions
Yes. One page, PDF. The form puts the link on the next screen and sends it to your inbox. One email. We do not start a sequence from this form.
The rebuild is a sequence of fixed milestones, sized after the first one. The first is shaped for four weeks: the decision on what is replaced and what stays, and one replaced path in production. We do not publish a price, and we do not quote a whole product in four weeks.
The one your team will still run in 18 months. We build in Go, Rust, Python, .NET, and Node.js. If you have not decided, pick that on the form. Choosing the target is the first thing the AI Architect settles, before anyone estimates the port.
Read access to the PHP repo, production access logs or a sample of them, and someone who knows why the odd parts exist. Without the repo there is no baseline and no engagement. If coding agents wrote the PHP tree and nobody owns it, the first step is AI Code Cleanup. The work is a fixed milestone, and a senior practitioner leads every engagement.