A Joint Venture

Install once.
Always on.

MustUse is the hosted infrastructure for WordPress plugin ecosystems. Powered by Troy's open-source daemon. Launching with Blockstudio as the first tenant.

A Pilot Between Three Open-Source Projects

Three layers.
One distribution backbone.

MustUse is a whitelabel platform. Troy is the daemon that powers it. Blockstudio is the first ecosystem to plug in.

Layer 3

Block Packages

Scoped WordPress plugins with one dependency: Blockstudio. A template folder, a block.json, and minimal PHP. Ships in two variants — standalone (bundles Blockstudio) or dependency (lightweight, requires it).

block.json scoped-plugin standalone | dependency
Layer 2

MustUse Cloud

The hosted service. Headless registry API, update server, package storage, author portal, license engine. Deployed on the tenant's domain with full rebrand. No imposed frontend — the tenant builds whatever UI they want.

registry-api update-server whitelabel headless
Layer 1

Troy Daemon

The open-source engine underneath. Always running, always listening. Handles package distribution, version management, and the WordPress-native update protocol. MustUse is Troy deployed as a managed service.

daemon open-source wp-update-api

From zero to ecosystem
in four moves.

Step 01

Tenant connects

Blockstudio signs up as a MustUse tenant. Gets a branded registry on their own domain — marketplace.blockstudio.dev — running on dedicated infrastructure.

Step 02

Authors publish

Block authors submit scoped plugins to the registry. Each one is thin — a template folder, a block.json, minimal PHP. Two build variants: standalone or dependency.

Step 03

Sites discover

Site owners browse available blocks from WP Admin, a standalone site, or an in-plugin directory. One click to install. Blockstudio is the only dependency.

Step 04

Updates flow

The Troy update server speaks native WordPress. Updates surface in the standard upgrade UI. Channel-aware: stable, beta, dev. No custom update mechanisms needed.

The daemon does the work.

Troy runs as an always-on process. MustUse wraps it in a managed cloud service. The WordPress sites never know the difference.

mustuse — registry

Headless by design.

MustUse ships no frontend. The registry API is the product. Tenants build whatever experience they want on top.

Tenant Frontend
In-Plugin Browser
Standalone Site
WP Admin Page
  REST API
MustUse Cloud  /  Troy Daemon
Registry API
Update Server
Author Portal
Package Storage
License Engine
Tenant Config
  WordPress Update API
WordPress Sites
Blockstudio
Scoped Block Plugins
Native Update UI

Everyone gets leverage.

For Blockstudio

Instant ecosystem

Every block plugin installed is another reason to keep Blockstudio active. Open-source adoption accelerates because third-party authors are building on it.

For Block Authors

Ship in minutes

Publish a Blockstudio block as a scoped plugin. No update server to maintain, no licensing to build, no distribution to figure out.

For Site Owners

One dependency, many blocks

No plugin bloat from five different rendering engines. Install Blockstudio once, then cherry-pick exactly the blocks you need from the directory.

For Troy / MustUse

Platform revenue

Every new tenant ecosystem is recurring infrastructure revenue. The open-source Troy project gains adoption because MustUse is the easy button.

The pilot starts now.

MustUse is the hosted layer. Troy is the engine. Blockstudio is the first ecosystem. Three open-source projects, one shared infrastructure play.