MustUse gives WordPress products their own hosted plugin ecosystem — registry API, update server, author portal, full whitelabel. You define the rules. We run the infrastructure.
If you've built something extensible — a framework, a block library, a theme system — you've hit this wall.
Custom endpoints, transient hooks, license checks. It works, but it's a second product you never wanted to maintain.
Authors want to build on your product but there's no registry, no submission process, no way to distribute their work to your users.
Your add-ons are scoped to your product. The WordPress.org directory buries them alongside thousands of unrelated plugins.
Browse, search, filter, and download packages. Build any frontend you want — in-plugin directory, standalone site, WP Admin page.
Hooks into the standard update transient. Your users see updates in Dashboard → Updates like any other plugin. Channel-aware: stable, beta, dev.
Third-party developers submit packages. You set review and approval workflows. They manage versions. You control quality.
Free, freemium, or paid — your call. Per-site activation, subscription validation, or fully open. MustUse doesn't impose a business model.
Dedicated server, custom domain, full rebrand. Your users never see MustUse or Troy. It's your ecosystem.
Standardized plugin structure with shared update spec. Ship standalone (bundles your product) or dependency (requires it) variants from one package.
Register as a MustUse tenant. You get a dedicated registry instance on your own domain with your own branding.
What packages are allowed? How are authors vetted? Free or paid? Revenue share? You set the policies. MustUse enforces them.
Developers submit scoped plugins to your registry. Each one declares your product as its dependency. Thin, focused, standardized.
Your users browse the directory from wherever you surface it — WP Admin, your site, inside your plugin. One-click install, native updates.
MustUse is Troy deployed as a managed service. The daemon runs your registry, serves your updates, and handles your packages.
MustUse works for any WordPress product that has — or wants — a plugin directory around it.
You ship a rendering engine or templating layer. Authors build blocks on it. MustUse gives them a place to publish and your users a place to discover.
Blockstudio, Genesis Custom Blocks, ACF BlocksYour theme is a platform. Companion plugins add layouts, integrations, and features. Host them in a branded directory instead of scattering them across GitHub repos.
GeneratePress, Jesuspended, FlavorYou have a core plugin and a growing set of add-ons. Stop maintaining your own update server and licensing system. Let MustUse handle distribution.
WS Form, MetaBox, FacetWP, SearchWPYou build reusable plugins across client projects. Host a private directory your team installs from. Version control and updates without Git submodules or manual deploys.
Your agency's internal toolkitMustUse ships no frontend. The API is the product. You build whatever experience makes sense for your users.
You bring the product and the community. We bring the platform. MustUse is open-source infrastructure, hosted — so you can focus on what you build, not how it's distributed.