Paul M.

I move WordPress sites off PHP and onto Cloudflare's edge, and I prove it with measurements taken before and after. What a migration looks like: - Every URL the site has today keeps answering: pages, posts, categories, tags, attachments, feeds and the sitemap. I compare all of them against the old site and hand you the result, so you see the misses I created instead of finding them in three months. - Nothing changes for a visitor. WordPress stays as your private editor if you still publish, and a plugin update or a traffic spike can no longer take the front end down. - You see a preview on its own address before your live site changes at all, and a rollback is taken before the first DNS record moves. - Serving costs collapse. On the last archive I moved, 473 articles across 1,379 URLs went from 40.60 USD a month on two servers to 10.62 at the edge. I also built the audit that answers "am I exposed" from outside, because almost no host discloses its PHP version in a header, so a scanner cannot check it. It reads speed from the edge, security headers, email authentication from DNS, and the WordPress surfaces that leak: author names over the API, XML-RPC, readme.html, uploads listing and the login path. Beyond sites I build the systems a business runs on: Python and TypeScript services, APIs on Cloudflare Workers, scrapers and integrations, and AI that does real work. Retrieval over your own documents, knowledge graphs, and the agents that operate my infrastructure day to day. I have been building and deploying since 2015. Before this the work was trading systems and TradingView indicators, which is where the twelve five-star reviews come from. If your site runs PHP, send me the domain. I will tell you which of the three situations you are in before you buy anything: a host that patches for you, a server you own, or a branch with no fix at all.