Frequently asked questions

Every item on the Marketplace is distributed as a Composer package rather than a downloadable zip. After checkout, you'll get a package name and, for paid items, an access token for our Private Packagist mirror. Add the repository to your project's composer.json and run composer require with the package name shown on your order confirmation and account dashboard.

You're licensed to use the item in your own Rhapsody applications, including client projects, for as long as your access token stays active. Redistributing the raw source as your own product isn't covered — check each listing's license terms, since sellers can set their own usage scope.

Yes. Composer resolves version constraints the normal way, so running composer update will pull newer releases the seller publishes, as long as they fall within the version range you required.

Check the listing's compatibility notes first — sellers declare a minimum arout/rhapsody-core version in their package's composer.json. If something still looks broken, open a support ticket from your order page and we'll loop in the seller.

Refund requests are handled case-by-case through support, typically for items that are broken as described or misrepresented in their listing.

Use the submission form from your seller dashboard. You'll provide your package's repository URL, a module.json manifest (for modules) or theme metadata, category, pricing, and screenshots. Submissions enter the moderation queue after that.

Reviewers verify the package installs cleanly against a stated Rhapsody version, that modules only request permissions they use, that a theme passes ThemeValidator's required-block checks, and that the listing content matches what's in the package.

Modules run inside a permission-checked ModuleContext. You declare the facades you need — for example database access — in your manifest, and each one is scoped: database access is prefixed to your module's own tables and can't reach the rest of the schema.

Payments run through Stripe. Payouts follow your Stripe Connect payout schedule once a purchase clears, minus the Marketplace's commission on paid items.

Yes — tag a new release on your package and it becomes available to buyers on the version constraints they installed with. Breaking changes should bump your major version so existing installs are not disrupted.

Rhapsody is a lightweight PHP MVC framework (arout/rhapsody-core) with Twig views, a custom dependency injection container, and a module system. The Marketplace is where the community shares themes and modules built on top of it.

You'll need a Rhapsody application to install purchases into, since everything ships as a Composer package meant to run inside one. Browsing the catalog doesn't require anything.

Reach out through the support link in your account dashboard and we'll get back to you.