For sellers
List Remotion packages on a moderated catalog. Buyers install via CLI or Library ZIP. Soft-launch: platform collects payments (Lemon Squeezy when live) and tracks your net sales.
1. Create a seller profile
Open /seller, set display name and storefront slug (
/sellers/your-slug).2. Enable payouts
Go to Payouts / onboarding. Checkout for your listings typically requires payout status ACTIVE. Soft-launch may settle seller net offline while platform MoR collects.
3. Package a ZIP
Follow packaging rules: real Remotion project,
package.json, entry + Composition, nonode_modules, no secrets in.env. Invalid packages are rejected before review.4. Upload
Seller UI: create draft → upload ZIP → wait for validation. Or use the Upload API (create → upload-url → package → submit).
5. Submit for review
Only versions with validation VALID can be submitted. Admin approves → PUBLISHED on the catalog. Updates re-enter review when you ship a new package.
6. FREE vs PREMIUM listing
FREE = any signed-in buyer can install. PREMIUM = Pro (or single purchase when enabled). Choose carefully — free packs drive adoption; premium is the monetization path.
7. Sales & analytics
Track orders and net under Sales. Platform fee is built into listed price. Slug must stay stable so CLI users keep working after updates.
Buyer install path
After publish, buyers run remotemp add your-slug. Put a clear composition id and README props table in the package — that is what shows up after CLI extract.
See CLI docs for the buyer-facing commands.
Checklist before submit
- Preview motion looks good on dark catalog background
- Title + description sell the use case (SaaS demo, deck, …)
- Tags match catalog collections (infra, charts, auth, …)
- Slug is final (hard to change later without breaking CLI users)
- No customer secrets / private keys in the ZIP