The project-curated "store" for plugins is located at https://plugins.deckbrew.xyz. Some plugins will be on https://testing.deckbrew.xyz while going through the submission process.
You can submit your own plugins there by following the instructions below. Keep in mind that plugins listed on the store must be approved by one of the Loader Team Members. This is done to ensure that plugins do not break the Deck or the Loader or are outright malicious, and is mostly done to protect the less tech-savvy users, who don't have the knowledge to audit plugins. You can obviously still install whatever you want, by copying folders to your plugin path or by using the Manual plugin install functionality in the Loader Settings.
Manual install is completely fine, but not recommended for security reasons.
Here are some guiding rules if you want to submit a plugin that requires financial transaction to use any amount of features:
Does the feature require significant server overhead or the developer to pay for a service?
Likely to be accepted. - If you have to pay for a service to make your plugin operate, it makes sense to crowdfund the subscription needed. It also makes sense if a feature will cause significant server overhead, such as storage or API spam concerns.
Is the feature a core part of the plugin?
Likely to be denied. - Our goal with the Decky Plugin Store is to promote free, open-source plugins created by our community. We are not interested in listing all plugins which require all users to pay a fee. Users can still install your plugin from outside the store.
Does the feature impact accessibility?
Likely to be denied. - We believe that plugins should be accessible to all users for free. Plugins which require payment to solve common complaints with motion sickness, colorblindness, or other disabilities may be denied.
Is the feature accessible on another platform (ex. website)?
Depends. - In some cases, the feature may be inconsequential and easy to access. However, reasoning like "the user could download the plugin from GitHub and remove the DRM" is not acceptable. Features should be either easy to access elsewhere or using other free tools (ex. using SyncThing in place of a saved game cloud system).
Is the feature unimportant to the overall plugin?
Likely to be accepted. - If a feature is important to the core reason users will install your plugin, then it should be accessible for free (ex. paid access to enable/disable themes in a customization app would likely be denied).
Approval of paid features within plugins is at the discretion of Steam Deck Homebrew developers. Though this brief list is used to establish precedent, each plugin is evaluated separately. Please ask a developer before working on a paid feature if you have any questions as to whether or not it would be accepted.
No. We do not accept any plugin that uses any LLM based code as these models do not comply with the GPL license (of which we are one of many many users) and thus cannot in good conscience accept plugins which have scraped or actively scrape the work of human beings without proper credit, permission and or compensation. This will not be a debate. Any LLM focused plugins will be rejected outright and there will be no appeals.
First, head over to the Decky Plugin Database Repository. All submitted plugins can be found in the plugins subfolder of the repo.
In order to add your own plugin to the database, simply create a Fork of the repository, add a submodule pointing to the commit you'd like to submit to the /plugins folder. Once that's done, create a Pull Request with your changes to the Database Repository. This starts the review process. One of the Team Members will take a look at your Plugin and if it's deemed to be okay, the Pull Request will be approved and subsequentially merged.
Please be aware that we do not allow private repositories, "black-box" binaries, deliberately obfuscated code and any other items, processes etc that would undermine the team's ability to verify the functionality of the plugin and or any underlying software etc.
- "Black-box" meaning binaries generated from either FOSS or proprietary source code with no link back to source code and or documentation of any changes made.
- In terms of obfuscation, minimized JS will be handled on a case by case basis.
In some situations, binary blobs for firmware and other similair items provided by companies/organizations may be the only way to provide functionality or features. This will be handled similairly to minimized JS, on a case by case basis.
All plugins submitted must include a license, provided as either LICENSE or LICENSE.MD.
If your plugin is based on the plugin template, copy your desired license to the top of the original LICENSE file that already exists in the repo. The original license must be included as per the terms of the template's license and is required for distribution on the store.
Your plugin will undergo a review process specified in Review Process. Please review the steps to make sure you are in compliance already which will make the review process far quicker for you.
As a part of this review process, you must have your plugin tested by someone using a Steam Deck running SteamOS. Specifically on the Beta or Preview branches if your plugin does falls under the "Beta/Preview testing required" specifications (see below). Otherwise Stable is preferred but not always required.
Plugin Backend Checklist
- Yes/No: I am using a custom backend other than Python.
- Yes/No: I am using a tool or software from a 3rd party FOSS project that does not have it's dependencies statically linked.
- Yes/No: I am using a custom binary that has all of it's dependencies statically linked.
To update your plugin, follow the same process as above and just make the submodule of your repository point to the new commit you want to submit.