From ca75193fda061f12600c0f53ab7e1302598a1e7b Mon Sep 17 00:00:00 2001 From: Tamal Chowdhury Date: Mon, 20 Jul 2026 17:32:01 +0600 Subject: [PATCH] add new business model --- .../set-up-options/kinde-business-model.mdx | 50 ++++++++++++++++--- 1 file changed, 43 insertions(+), 7 deletions(-) diff --git a/src/content/docs/build/set-up-options/kinde-business-model.mdx b/src/content/docs/build/set-up-options/kinde-business-model.mdx index 6ece6ce77..28515db4c 100644 --- a/src/content/docs/build/set-up-options/kinde-business-model.mdx +++ b/src/content/docs/build/set-up-options/kinde-business-model.mdx @@ -1,35 +1,42 @@ --- page_id: f310bbde-bdfb-4fad-81fc-499d9a84c429 title: Kinde for different business models -description: Comprehensive guide to different business models supported by Kinde including B2C, B2B, B2B2C, marketplace, agency, and membership organizations with configuration recommendations. +description: "Choose the right Kinde setup for B2C, B2B, B2B2C, marketplace, membership, agency, or multi-brand portfolios" sidebar: order: 1 +tableOfContents: + maxHeadingLevel: 3 relatedArticles: - 38e9186d-cca5-44a6-86ab-dde9f21167ff - 7b32cd0e-7af3-4d57-9c3c-4a37df3d14d1 - 556c9ce6-477b-4a31-9ce1-75f612eb3740 - d2d64a2b-1fb7-4c18-88bc-2986723724cb + - d82207a5-c72b-48d7-b02d-b3d1d77b88a2 topics: + - build + - set-up-options - business-models - - multi-tenancy - organizations sdk: [] languages: [] -audience: developers +audience: + - developers + - product-manager + - business owners complexity: beginner keywords: - - business models - B2C - B2B - B2B2C + - multi-tenancy - marketplace + - multi-brand - agency - membership - - multi-tenancy -updated: 2024-01-15 +updated: 2026-07-20 featured: false deprecated: false -ai_summary: Comprehensive guide to different business models supported by Kinde including B2C, B2B, B2B2C, marketplace, agency, and membership organizations with configuration recommendations. +ai_summary: "Guide to structuring Kinde for common SaaS and product business models. Covers B2C with a single user group in the default organization; B2B with one organization per customer company; B2B2C multi-tenant setups with separate user groups per organization; membership organizations for branches, clubs, or locations; marketplaces that separate buyers and sellers via organizations; agencies running multiple client businesses on Kinde; and multi-brand consumer portfolios where a parent company operates several distinct consumer products. Explains what to configure at the business and environment level versus per organization, including authentication, branding, roles and permissions, and feature flags. For multi-brand portfolios, clarifies when to model each property as a separate Kinde business versus an environment used only for development lifecycle stages such as staging and testing. Links to related guides on organizations, multiple businesses, and environments. Intended for developers, product managers, and business owners planning their Kinde architecture." --- Kinde is built to support many types of SaaS models, for apps, sites, and projects. @@ -194,3 +201,32 @@ You’ll set up each of your client’s businesses according to what type of bus /> Tip: You could adapt this model if you’re a large multi-location, multi-department, or multi-service enterprise. + +## You run a multi-brand consumer portfolio + +You’re a parent company with several distinct consumer products — each with its own brand, app or site, and user base. This is common for product studios, media groups, and consumer tech companies that launch multiple consumer-facing properties under one umbrella. + +Unlike the agency model (where you run Kinde for clients), these are your own products. The main decision is whether each property should be its own Kinde business, or live as an environment under one business. + +### Separate business vs environment + +**Use a separate business** for each consumer product when: + +- Each product has its own brand, domain, and sign-in experience +- Users, organizations, and activity should stay isolated per product +- Auth methods, roles, or billing differ between products +- Teams manage products independently + +[Run multiple businesses](/build/set-up-options/run-multiple-businesses/) on Kinde so organizations, users, branding, and activity are managed separately for each property. + +**Use an environment** only for the development lifecycle of a single product — for example production, staging, and testing. Environments are not meant to separate brands or consumer products. See [About environments](/build/environments/environments/). + +### Recommended setup + +For each product business, configure it like a B2C (or B2B / B2B2C if that product sells to companies): + +- [Authentication](/authenticate/about-auth/about-authentication/) for that product’s users +- [Global brand and page design](/design/brand/global-brand-defaults/) matched to the product brand +- [Roles and permissions](/manage-users/roles-and-permissions/user-roles/) for that product’s app + +Keep each product’s production setup in its own business’s production environment, and use non-production environments within that business for testing and staging.