Skip to main content
A blueprint is a whole Whop business: products with their pricing, and a website that sells them. The one in the gallery is a real business that’s running, and deploying it gives you your own copy. Browse them at whop.com/blueprints. Deploying a blueprint sets up:
  • Your products, copied from the blueprint with their pricing plans, images, and store page styling
  • Your website, live at your own whop.site address
  • The wiring between them, so the site can take payments from the moment it’s up
The rows partition the set, so a verified blueprint appears in the curated row only. Each card shows how many businesses have been created from it.

Deploy a blueprint

The 10% affiliate cut

Blueprints are a revenue stream for the people who publish them. When a business deploys your blueprint, you earn 10% of Whop’s profit on the sales its site makes — attributed automatically, the same model as referring a business to Whop. It comes out of Whop’s share, not the seller’s: if you deploy another creator’s blueprint, their 10% doesn’t change your pricing or your payouts. The cut is on sales only, and it’s tied to the deployed whop.site site — the sales that run through the copy you shipped are the ones that count.

Clone the source

Deploying gives you a running business. To change how the site works, get the code:
This registers a new app and downloads the source archive from the blueprint’s production build. The directory links to your app, so the first whop apps deploy ships to your route. Cloning a website blueprint carries the website type over, and --app_type overrides it. From there it’s an ordinary project — see the quickstart.

Next steps

Build a website with the CLI

Start from scratch instead of from an existing site.

How hosting works

Secrets, rollbacks, logs, and the injected API key.

Accept payments

Turn the site you deployed into something that sells.

Track visitors

The pixel is already installed — add your own events.