Skip to main content
Start from a working business instead of a blank file. The blueprint gallery at whop.com/blueprints is the canonical list: complete, running businesses built on the Current API, including blueprints published by the community. Deploying one gives you your own copy — products, pricing, and a live site — with nothing to build on your machine. See Blueprints for how deploying works and the 10% affiliate cut publishers earn. To change how a blueprint’s site works, clone its source. Every blueprint in whopio/templates is self-contained and ships with sample data, so it runs with no credentials. You can see the whole app before wiring up an account.
Or clone one straight from the gallery with the CLI, which registers a new app so the first whop apps deploy ships to your route:

​
App blueprints

An app that installs into a community is a different starting point from an API integration. Use whop-nextjs-app-template, or scaffold directly with whop apps init from the CLI.

​
Going live

Two rules apply to every blueprint:
  • Never ship a Whop API key in a client. Mint a short-lived access token on your own server, scoped to the acting user. See Auth & API keys.
  • Pin the API version. Each blueprint sends an Api-Version-Date header. See API versioning.
When you build with an AI assistant, point it at a blueprint plus the Docs MCP server and it has both a working shape and the current API in context.

​
Next steps

Blueprint gallery

Browse every blueprint, including community builds.

Deploy a blueprint

Products, pricing, and a live site in one step.

Build with the CLI and Claude

Scaffold from your terminal.