Hey 👋
In self-hosted instances, the in-builder marketplace panel is always empty because ApprovedMarketplaceProduct is empty locally. There's no way to populate it without access to your approval process.
Two things would help the self-hosting community a lot:
1. Read: a public endpoint like GET /api/marketplace/items returning approved templates with metadata and asset URLs. Self-hosted instances could fall back to it when the local table is empty (via a simple MARKETPLACE_URL=https://webstudio.is env var).
2. Submit: a way to submit a template from a self-hosted instance to your existing review process. The moderation pipeline already exists for cloud users. The template build is what gets reviewed, not where it comes from.
Both would make self-hosting a first-class citizen of the Webstudio ecosystem without changing your review/approval flow at all.
Hey 👋
In self-hosted instances, the in-builder marketplace panel is always empty because
ApprovedMarketplaceProductis empty locally. There's no way to populate it without access to your approval process.Two things would help the self-hosting community a lot:
1. Read: a public endpoint like
GET /api/marketplace/itemsreturning approved templates with metadata and asset URLs. Self-hosted instances could fall back to it when the local table is empty (via a simpleMARKETPLACE_URL=https://webstudio.isenv var).2. Submit: a way to submit a template from a self-hosted instance to your existing review process. The moderation pipeline already exists for cloud users. The template build is what gets reviewed, not where it comes from.
Both would make self-hosting a first-class citizen of the Webstudio ecosystem without changing your review/approval flow at all.