Frappe SaaS
Launch your Frappe app as SaaS on Frappe Cloud : customers sign up, pay, and each gets their own isolated Frappe site, created automatically.
Who it is for: teams that build a Frappe or ERPNext app and want to sell it as a subscription product, with one site per customer. If you only host a couple of sites by hand, you do not need this. It is used in production by one product (see Used by).

The three pieces
| Piece | In one line |
|---|---|
saas_core | Frappe v16 control-plane app: plans, signup, billing, tenant provisioning and a versioned HTTP API. Also hosts the TypeScript SDK in sdk/. |
fcctl | Python CLI and library that drives Frappe Cloud v2; saas_core uses it to create customer sites. |
frappe-saaskit-starter | React front end (landing, pricing, signup, checkout, customer console) built on the SDK. Fork and brand it. |
The flow
browser -> starter + SDK -> saas_core -> fcctl -> Frappe Cloud
Your app reaches customers as a recipe that saas_core provisions per tenant. Details: Architecture.
What customers see






Used by · see who
Where next
- Not sure where to begin? Getting started.
- Want to see it run on your machine? Local demo.
- Using a coding agent? Agents.
Use at your own risk. Frappe SaaS is early alpha software, provided “as is” without warranty of any kind. We are not accepting pull requests or outside contributions. If you find a problem, please file an issue on frappe-saaskit , or on the docs repo for mistakes in these pages.

