Yes, we're a bit late to this party - the WordPress world caught fire back in 2024. But sometimes you need distance to see just how badly the bridge was burnt.
What happened
Matt Mullenweg called WP Engine a "cancer" on stage at WordCamp. Then WordPress.org cut off WP Engine's access to updates. Then WordPress took over Advanced Custom Fields and renamed it Secure Custom Fields. Literally hijacked the plugin from its creators.
Developers everywhere had the same thought: "Wait, they can just... do that?"
Why we left
The ACF seizure was the moment WordPress became unpitchable. How do you tell a client their website runs on software that can be hijacked overnight?
While hobbyists debated, professionals moved. Sanity, Payload, Strapi - CMS platforms that understand business doesn't stop for drama. No theft. No surprises. No explaining to clients why their site broke because someone had a bad day. Just boring, reliable tools for serious work.
WordPress isn't dead, it just lost it's credibility
Sure, WordPress still powers around 40% of the web. But for professionals? October 2024, was a fork in the road.
I'm not talking about the Elementor, Divi, and WP Bakery crowd with their clicking and dragging. WordPress will survive on agencies selling $5,000 websites built with pre-made themes and page builders. But for developers building custom solutions where platform stability matters? WordPress became a liability.
The new reality
WordPress is now the platform you inherit, not the one you choose. For new projects? We highly recommend against it (at least in the native sense).
The exodus wasn't about tech. It was about professionalism. About serving clients who invest in us for stability.
WordPress became the business risk we protect clients from.