Plugin Company, 2014 to 2026
We built and sold Magento extensions for twelve years. In 2026 we stopped selling and released all 25 extensions as open source, so the stores that rely on them can keep running.
What happened
Plugin Company took its first order in November 2014, for a Magento 1 extension. Over the next years the catalogue grew to 25 extensions for Magento 1, OpenMage and Magento 2, with 622 releases in their changelogs and 235 pages of documentation. Next to the extensions we did freelance and custom development work for stores and agencies.
In 2026 we stopped selling. Rather than let the code disappear with our servers, we published every extension on GitHub under the MIT license, removed the license checks and tagged each release with its original version number. The Composer repository and the documentation stay online at their old addresses.
More than 3,000 customers used our extensions and services. Thank you for twelve good years, for the bug reports, the feature ideas and the patience while we fixed things.
Milan Simek, founder
- First orders on plugin.company, for Magento 1 extensions
- First Magento 2 extensions, installable with Composer
- Custom Contact Forms for Magento 2 reaches 100 releases
- Sales stop. All 25 extensions released as open source under MIT
Some of the stores and agencies we worked with
Using the code
Every extension is released under the MIT License: Copyright (c) 2014-2026 Plugin Company. You may use, copy, modify, merge, publish, distribute, sublicense and sell copies of the software, in commercial projects too, as long as the copyright notice and the license text stay with the code. The software comes without warranty.
Each extension has its own repository under github.com/PluginCompany, with one tagged commit per released version, a README, a changelog and the user manual in docs/. Third-party libraries that ship with an extension keep their own licenses, listed in its THIRD-PARTY-NOTICES.md.
Plugin Company no longer actively develops the extensions. The repositories stay open: report bugs as issues, send fixes as pull requests, or fork an extension and maintain it yourself.
Installing with Composer
The Composer repository at plugin.company still works and now points to the release tags on GitHub, with the same package names and version numbers as before. No account or credentials needed:
composer config repositories.plugin.company composer https://plugin.company/composer require plugincompany/contactformsEvery extension page lists its package name and the manual install steps.
Questions and answers
Can I use the extensions in commercial and client projects?
Yes. The MIT license allows commercial use, modification and redistribution. Keep the copyright and license notice in the code.
Do I still need a license key?
No. The license checks and the license manager module have been removed from every extension. Nothing phones home and nothing expires.
How do I install an extension?
Every extension page has the exact commands. For Composer, add our repository once with composer config repositories.plugin.company composer https://plugin.company/ and then run composer require with the package name. You can also download the release ZIP from GitHub and copy the files into your store.
I installed an extension from plugin.company before. What now?
Keep the plugin.company repository entry in your composer.json: it now points to the open-source releases on GitHub, with the same package names and version numbers. Remove plugincompany/licensemanager if it is listed in your require section, then run composer update. The old credentials in auth.json are no longer needed. Your configuration and data stay as they are.
Will the extensions still get updates?
Plugin Company no longer actively develops the extensions. The repositories stay open for issues and pull requests, and you are free to fork them and maintain your own version.
Is Magento 1 still supported?
The Magento 1 extensions are published as they were last released, for Magento 1.x and OpenMage stores. Like the Magento 2 extensions they are no longer actively developed, but issues and pull requests are welcome.
Where is the documentation?
The user manuals from the old knowledge base are on this site under Docs, and as Markdown in the docs/ folder of each repository.
Can I still get paid support?
No. Support, sales and license management have ended. For questions and bug reports, open an issue on the extension's GitHub repository.