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.
The GPL Trap for Commercial Developers
WordPress’s GPL license requires that derivative works — including plugins and themes — 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.
The GPL didn't create WordPress's plugin wealth. A massive user base and a low barrier to entry did.
The loophole many developers use — selling “pro” versions while releasing a “lite” GPL version — 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.
EmDash 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 — your choice, not the platform’s.
What MIT Unlocks That GPL Blocks
Three specific things change for commercial developers:
Clear ownership. 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.
Direct monetization. EmDash ships with a built-in 402 payment protocol. Combined with MIT licensing, you can charge per API call, per installation, or per month — without the GPL’s implicit pressure to give away your core logic. The platform supports the payment model; the license doesn’t undermine it.
Enterprise adoption without legal review. Large companies often ban GPL software from their infrastructure. The compliance overhead — tracking every dependency, auditing derivative use — 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.”
The One Counterargument That Deserves an Answer
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.
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 — 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.”
The Second-Order Effect Most Coverage Misses
The real shift isn’t about licensing philosophy. It’s about unit economics. WordPress plugin businesses are built on volume — thousands of small sales at low prices, because GPL allows resale and redistribution. The pricing ceiling stays low.
EmDash’s MIT license plus the 402 protocol enables a different model: per-use pricing for agents and AI tools. An AI agent that queries your plugin’s functionality can be charged per operation, not per seat. This changes the revenue math completely. A plugin that processes 100,000 automated requests generates recurring revenue without requiring 100,000 human users. The license and the infrastructure together unlock a pricing model that WordPress’s GPL architecture cannot support cleanly.
What Developers Should Do Now
If you’re a commercial WordPress developer, EmDash’s v0.1.0 beta isn’t production-ready. The ecosystem is empty. But the license and architecture are not changing. Start experimenting now. Port your most popular plugin to EmDash’s sandbox model. Test the 402 payment flow. Build the muscle memory for a license that lets you keep what you build.
- What is the main barrier EmDash's MIT license removes for commercial developers?It removes the GPL's requirement that derivative works carry the same license, allowing clear ownership and proprietary licensing.
- How does EmDash enable per-use pricing for plugins?EmDash ships with a built-in 402 payment protocol, and the MIT license allows charging per API call or operation without GPL pressure.
- Why do large companies often ban GPL software?The compliance overhead of tracking dependencies and auditing derivative use is expensive, while MIT software passes legal review quickly.
