Helmut Wandl

<p>Peak Publisher turns your WordPress site into your own plugin update server. It’s built for agencies, product teams, and developers who want to create and ship their own custom plugins and want full control over distribution, versioning, and updates — without relying on third‑party services.</p>
<p>With a modern, task‑focused admin UI, you can add new plugins and releases via drag & drop, validate packages automatically, and publish or draft releases with one click. Your client plugins point to your Peak Publisher site via a standard <code>Update URI</code>, so WordPress will discover and install updates directly from you.</p>
<p><strong>With this solution, you can have your own self-hosted plugin update server in just 5 minutes, allowing you to centrally manage your plugins and deploy updates with incredible ease.</strong></p>
<p>—</p>
<h3>❇️ COMING SOON ❇️</h3>
<p><strong>Managing and Updating wp.org Plugins</strong></p>
<p>In just a few weeks, Peak Publisher will let you manage plugins hosted on wordpress.org the same way you already manage self-hosted ones. Drag and drop your plugin folder onto Peak Publisher, and everything else is handled automatically — no more SVN.</p>
<p>—</p>
<h3>KEY FEATURES</h3>
<p>🚀 <strong>Clean admin UI with a guided “Add New Plugin” flow</strong><br />
A short and focused user interface guides you through the entire process to deploy your first plugin with amazing ease within minutes.</p>
<p>☝️ <strong>Drag & drop a ZIP or simply the whole plugin folder</strong><br />
You can drop a ZIP file, but the easiest way is to simply drop the entire raw plugin folder or the folder’s contents. The ZIP file will then be created automatically for you.</p>
<p>✅ <strong>Automatic validation: headers, version, Update URI</strong><br />
Peak Publisher automatically checks each new release for required headers, proper semantic versioning, consistent update URIs, and more to ensure everything is correct.</p>
<p>🧽🫧 <strong>Auto‑cleanup of workspace artifacts (e.g. .git, node_modules)</strong><br />
To provide clean packages and reduce package size, Peak Publisher automatically removes development files and operating system artifacts from your uploads using patterns that you can configure. (optional)</p>
<p>🔐 <strong>Optional restriction via IP/domain whitelist</strong><br />
Packages are stored in a private, server-protected directory with no direct web access. By default, access via the API is still possible from anywhere. Using IP or domain whitelisting, you can restrict access to update metadata and downloads.</p>
<h4>Some More Features</h4>
<p>📈 <strong>Analytics:</strong> You can always see how many active installations there are.<br />
📄 <strong>Readme.txt:</strong> Provide your users with a description, changelog, tested up to and more.</p>
<h3>HOW IT WORKS</h3>
<ol>
<li><strong>Install Peak Publisher</strong><br />
on a dedicated WordPress site (recommended)<br />
or any site you control.</li>
<li><strong>Follow the “Add New Plugin” flow</strong><br />
add the <strong><code>Update URI</code></strong> header and the bootstrap code to your plugin.</li>
<li><strong>Upload your plugin</strong><br />
drag & drop the zipped plugin or the plugin folder.</li>
<li><strong>Peak Publisher validates your upload</strong><br />
and shows you the validation result.</li>
<li><strong>Click “Add new plugin”</strong><br />
to finish the process.</li>
<li><strong>Drop your next release with increased version number</strong><br />
once you have one ready.</li>
</ol>
<h3>WHO IS IT FOR?</h3>
<ul>
<li>Agencies that deliver custom plugins to multiple clients</li>
<li>Product teams with private/proprietary extensions</li>
<li>Creative plugin developers who want to deploy updates quickly and easily</li>
</ul>
<h3>Privacy</h3>
<p>Peak Publisher does not collect personal data, does not track usage, and does not use third‑party services. All files are stored on your server in a protected directory.</p>


Peak Publisher

Self‑host your plugin repository. Manage releases, serve updates, and streamline your workflow — all inside WordPress.

Rob Landry

<p>I was working on a plugin that had a pro (paid) version. This plugin had 2 code bases and was hosted on an external site. This site charged upwards of 50% of what I was charging.</p>
<p>So I became interested in finding a way to provide updates and use only one code base. I also wanted to minimize the cost to sell the plugin so that the money was not going into someone elses pocket. With Sell My Plugin, you host your own plugins. You use PayPal to charge for the purchases. There is a transactions list so that you can keep track of your sales. If you sell 10 copies of your plugin in a month at <strong>$10/ea</strong>, this plugin will save you <strong>$360</strong> per year vs PlugPress and <strong>$600</strong> vs CodeCanyon.</p>
<p>This plugin also uses the familiar domain.com/extend/plugins/ layout just like wordpress.</p>
<h4>Free Features</h4>
<ul>
<li>Your.Domain.com/extend/plugins/ to list all of your plugins just like wordpress.</li>
<li>Your.Domain.com/extend/plugins/plugin-slug to display the plugin info.</li>
<li>A custom search on the plugins page to search for available plugins.</li>
<li>Number of downloads tracked to see which plugins are HOT!!</li>
<li>News updates to provide you with up-to-date info on Sell My Plugin.</li>
<li>Shortcodes are provided to display the plugin where ever you want.</li>
<li>A <a href="http://redmine.landry.me/projects/sell-my-plugin/boards" rel="nofollow ugc">Forum</a> and <a href="http://redmine.landry.me/projects/sell-my-plugin/issues" rel="nofollow ugc">Bug Tracker</a> to get help.</li>
</ul>
<h4>Pro Features</h4>
<ul>
<li>If the plugin is a paid plugin, ?transaction= is added to:</li>
<li>Your.Domain.com/extend/plugins/plugin-slug/version/ to allow downloads.</li>
<li>Your.Domain.com/extend/plugins/plugin-slug/update/ to display the update json to allow for plugin updates.</li>
<li>Your.Domain.com/extend/plugins/plugin-slug/update/ to display the update json to allow for plugin updates.</li>
<li>[sell-my-plugin] Displays the plugins list.</li>
<li>[sell-my-plugin slug=the-slug] Displays a small info box about the plugin.</li>
<li>[sell-my-plugin slug=the-slug format=full] Displays the full plugin info.</li>
<li>[sell-my-plugin slug=the-slug version=1.0 format=full] Displays the full plugin info for a particular version.</li>
<li>Transactions list for book keeping and tracking.</li>
<li>PayPal express checkout for purchase!</li>
<li>Downloads instantly activated upon completion of purchase.</li>
<li>UPDATES!! provided to plugins once a new version zip is uploaded!</li>
<li>PayPal Sandbox to test plugin purchases without mixing with REAL purchases.</li>
<li>Custom pricing of plugins in backend.</li>
<li>Ability to give paid plugins for free providing a FREE KEY!</li>
<li>
<p>Custom email following purchase including shortcodes to allow for injection of PayPal data!</p>
</li>
<li>
<p>And many more!…</p>
</li>
</ul>
<h3>Requirements</h3>
<p>There are a few things that you need to do to make sure that you can use this plugin.</p>
<h4>PHP 5 >= 5.2.0, PECL zip >= 1.5.0</h4>
<p>This plugin makes use of the ZipArchive class, introduced in PHP 5.2.0.  You must be running at least this version to use the plugin.</p>
<h4>Valid readme.txt and plugin headers</h4>
<p>Like plugins hosted on wordpress.org, you must include a valid readme.txt file and the proper plugin headers in your main plugin file.  Check out a <a href="https://wordpress.org/extend/plugins/about/readme.txt" rel="ugc">sample readme.txt file</a> and use the <a href="https://wordpress.org/extend/plugins/about/validator/" rel="ugc">readme validator</a>.  The Sell My Plugin plugin uses the readme.txt file and the plugin headers to render information about the plugin.</p>


Sell My Plugin

It has zero downloads because it doesn't even work.



Doesn't Even Download

This plugin allows you to host your own plugins on your wordpress installation.

Peak Publisher vs Sell My Plugin