WordPress plugin developers have spent two decades navigating a contradiction. The GPL license that made WordPress free also made it legally hostile to commercial software. EmDash’s MIT license isn’t a minor licensing preference. It’s an architectural statement that removes the single biggest barrier to building a paid plugin business on an open-source CMS.<\/p>\n
WordPress’s GPL license requires that derivative works \u2014 including plugins and themes \u2014 carry the same license. In practice, this means if you distribute a WordPress plugin, you must license it under GPL. You can charge for it, but the code itself must be freely redistributable. Competitors can fork your plugin. Customers can share your code without restriction.<\/p>\n
The loophole many developers use \u2014 selling “pro” versions while releasing a “lite” GPL version \u2014 works, but it’s legally fragile. The core tension never disappears: the GPL was designed to prevent proprietary software, yet the WordPress economy depends on proprietary plugins.<\/p>\n
EmDash<\/a> sidesteps this entirely. Plugins run in isolated sandboxes. They don’t share code with the core system. There’s no functional or legal entanglement that forces GPL inheritance. You write a plugin, declare its capabilities in a manifest, and license it however you want. MIT, Apache, closed-source, per-use \u2014 your choice<\/a>, not the platform’s.<\/p>\n Three specific things change for commercial developers:<\/p>\n Clear ownership.<\/strong> Your plugin code is yours. No one can legally demand you publish it. No ambiguity about whether a client’s custom integration triggers GPL obligations. The MIT license requires only attribution. That’s it.<\/p>\n Direct monetization.<\/strong> EmDash ships with a built-in 402 payment protocol. Combined with MIT licensing, you can charge per API call, per installation, or per month \u2014 without the GPL’s implicit pressure to give away your core logic. The platform supports the payment model; the license doesn’t undermine it.<\/p>\n Enterprise adoption without legal review.<\/strong> Large companies often ban GPL software from their infrastructure. The compliance overhead \u2014 tracking every dependency, auditing derivative use \u2014 is expensive. MIT software passes legal review in minutes. For a plugin targeting enterprise customers, this is the difference between a signed deal and a “we’ll get back to you.”<\/p>\n Skeptics argue that the GPL built WordPress’s ecosystem. Without its “viral” requirement, they say, developers won’t contribute back. The community fragments into proprietary walled gardens. WordPress’s 60,000-plugin library exists because GPL forced sharing.<\/p>\n This argument confuses cause with correlation. The GPL didn’t create WordPress’s plugin wealth. A massive user base and a low barrier to entry did. Most popular WordPress plugins already have paid “pro” versions \u2014 the GPL didn’t prevent proprietary monetization, it just made it legally ambiguous. EmDash’s MIT license removes the ambiguity without removing the incentive to build. The sandbox architecture already prevents the kind of code-sharing that the GPL was meant to protect. Plugins are isolated by design. There’s nothing to “viralize.”<\/p>\n The real shift isn’t about licensing philosophy. It’s about unit economics. WordPress plugin businesses are built on volume \u2014 thousands of small sales at low prices, because GPL allows resale and redistribution. The pricing ceiling stays low.<\/p>\nWhat MIT Unlocks That GPL Blocks<\/h2>\n
The One Counterargument That Deserves an Answer<\/h2>\n
The Second-Order Effect Most Coverage Misses<\/h2>\n