Most WordPress plugins are made available under the GPL — a “copyleft” license originally created by Richard Stallman. The intention of the GPL is to ensure that software can be modified and shared without limitations. Any software published under the GPL license can be copied by anyone who wants to, as long as they are prepared to make the source code of any changes available if they choose to distribute the software.
Let’s say a developer created a new WordPress plugin and released it with a GPL licence. The developer intends to give away a limited version of the plugin for free and charge for premium features — something that’s perfectly compatible with the GPL. However, after releasing and promoting his plugin, he’s dismayed to find another developer has taken the code and is giving it away for free as part of a bundle of “premium” plugins.
While it might seem counterintuitive, according to the GPL, there’s nothing wrong with what the second developer did. There is a strong cultural prohibition not to behave like this in the WordPress world, but that doesn’t stop it happening. A recent question on the Advanced WordPress Facebook group highlights the issue. A developer asks what he can do to stop people copying his GPL WordPress plugin. The nutshell response is this: nothing. There is nothing a developer can do to stop someone copying GPL code. The GPL exists precisely to allow such copying.
Does that mean it’s impossible to make money by developing for the WordPress ecosystem? Not at all. But it won’t look like traditional software distribution.
The most obvious model is to simply sell plugins, Sure, they’ll be copied or “pirated” but most users are willing to pay developers for their work. Those who aren’t probably would not have paid in the first place.
This is considered a somewhat shady means of circumventing open source software by some in the community, but it’s entirely possible to break a plugin’s functionality up so that the bulk of it runs as an application on a server. The WordPress plugin provides an interface and integration between WordPress and the application running on the server. This technique is only going to work for suitable plugins, those that are a natural fit for a Software-as-a-Service model.
Premium Plugins With Support
Many WordPress plugin developers offer a free version of their plugin, alongside a premium version with more features and enhanced support. For some businesses, a WordPress plugin is a crucial part of their website. They’re more than happy to pay for support direct from the developer. Some will also be prepared to pay for additional development work to add a feature that they need or to help integrate a plugin with other components of their site.
This model, releasing software under an open source license and generating revenue from support contracts, is how many of the biggest open source software corporations — including the multi-billion-dollar Red Hat — make their money.
Plugin As Promotion
A WordPress plugin is a great way to establish a reputation as a competent WordPress developer. A smart developer can parlay that reputation into consulting and support contracts that are not directly related to the plugin.
Although GPL software can be copied, that doesn’t mean it’s impossible to make money in the WordPress ecosystem.Posted in: Webmaster