Automattic CEO Matt Mullenweg accuses Wix of copying WordPress for its mobile app, skirting GPL requirements of attribution and public release of code
Anyone who knows me knows that I like to try new things — phones, gadgets, apps. Last week I downloaded the new Wix (closed, proprietary, non-open-sourced, non-GPL) mobile app.
Context & Ripple Effects
The 2016 accusation is the opening shot in what becomes a decade-long Mullenweg-versus-Wix arc: he alleges Wix's closed mobile app copied WordPress code while skipping the GPL's attribution and source-release obligations. The charge matters because WordPress's license is its moat — anyone can build on the code, but derivatives must give back.
The pattern repeats on both sides over the following years: Wix later runs what Mullenweg calls a bizarre marketing campaign against WordPress, attacking its business model, while Mullenweg applies the same leverage elsewhere by pressing WP Engine for a licensing deal after years of stalled talks. The Wix app dispute is where that enforcement posture first goes public.
First-order effects
- Wix must either open-source and attribute the app's WordPress-derived code or defend a public GPL-compliance challenge from the project's most powerful steward, with its proprietary positioning directly at stake.
Second-order effects
- Other commercial site builders building on WordPress code now see that license enforcement is an active competitive tool, not a formality — raising the compliance bar for every closed product touching the codebase.
Third-order effects
- If enforcement keeps escalating from community shaming toward formal licensing demands, copyleft compliance hardens into a business lever: access to the WordPress ecosystem increasingly runs through Automattic's terms, as the later WP Engine standoff suggests.
The trend: WordPress's open-source license is evolving from a community norm into an enforcement instrument its steward wields against commercial rivals.