If you have solved a problem well for one client, you have probably solved it for a hundred companies you have never met. The marketplace lets you publish any of the four template families as a product, and handles the commercial machinery so you are not building a storefront instead of building software.
A product with a version history, so buyers can see what changed and you can supersede without abandoning existing customers.
One-time or recurring, with the pricing structure attached to the offer rather than hard-coded into the product.
Payment is collected and the entitlement is recorded. What a buyer is allowed to install is enforced, not assumed.
Revenue is paid out through Stripe Connect, with the tax and compliance surface handled there.
Buying from the marketplace should not mean trusting a stranger's zip file.
A product can be a single artifact or a bundle of components with a defined install order and required parts.
See what a product will add to your application before you commit to installing it.
Every install is recorded as a revision, so you can trace what arrived, when, and from which version.
You install the version you bought. A newer release does not silently replace it underneath you.
A marketplace product wraps any of the template types, and can bundle several together — a blueprint with the appliance it depends on and the harness pack that makes it useful in that industry.
Any builder on the platform. Becoming a seller means setting up a store profile and connecting payouts.
Yes. You set the offers and the prices attached to them.
Products can be withdrawn from listing while existing buyers keep the entitlement and the version they purchased.
Create an account, explore the full builder console, and launch your first application on a custom domain. Nothing is charged while your application is still in development.
No credit card required. The console preview, the documentation, and the architecture reference are all readable before you sign up.
Get started free Read the docsAn app has routed Core, Logs and AI database planes. Provisioning is a staged operation: wait for readiness and any reported setup requirements before inviting customers. Marketplace presentation installs are pinned snapshots; upgrading a template is explicit. Customer-hosted Appliance operation and optional extension compute have their own deployment requirements.
Read the guideCompose React pages in the Puck page designer, configure themes, assets, menus and User Types, and publish a reviewed page version. User Types select the experience; DataRoles and Locations control access to business records. A saved draft is separate from the version customers see.
Read the guide